With 2.6.31-rc2 brasero doesn't recognize the drive at all, gnomebaker does but fails to burn with message: ":-( unable to INQUIRY: Bad address" Ejecting the dvd with the eject button on Dell Vostro 1310 does not work, it only unmounts the media but does not eject it... With 2.6.31-git6 everything worked fine I think and with 2.6.30.1 everything works with the same disc that is failing with 2.6.31-rc2 dmesg|grep sr cdrom: This disc doesn't have any tracks I recognize! sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda caddy sr 0:0:0:0: Attached scsi CD-ROM sr0 sr 0:0:0:0: Attached scsi generic sg0 type 5 sr 0:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08 sr 0:0:0:0: [sr0] Sense Key : 0x5 [current] sr 0:0:0:0: [sr0] ASC=0x21 ASCQ=0x0 end_request: I/O error, dev sr0, sector 0 Buffer I/O error on device sr0, logical block 0 sr 0:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08 sr 0:0:0:0: [sr0] Sense Key : 0x5 [current] sr 0:0:0:0: [sr0] ASC=0x21 ASCQ=0x0 end_request: I/O error, dev sr0, sector 0 Buffer I/O error on device sr0, logical block 0 dmesg|grep ata ACPI: SSDT 000000007f6d7b04 002AD (v01 SataRe SataAhci 00001000 INTL 20061109) #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] PERCPU: Embedded 26 pages at ffff880001649000, static data 76704 bytes Memory: 2047556k/2087744k available (3299k kernel code, 408k absent, 39164k reserved, 1418k data, 412k init) ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62 libata version 3.00 loaded. ata_piix 0000:00:1f.1: version 2.13 ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ata_piix 0000:00:1f.1: setting latency timer to 64 scsi0 : ata_piix scsi1 : ata_piix ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1810 irq 14 ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15 ata3: SATA max UDMA/133 abar m2048@0xf8504000 port 0xf8504100 irq 29 ata4: SATA max UDMA/133 abar m2048@0xf8504000 port 0xf8504180 irq 29 ata5: SATA max UDMA/133 abar m2048@0xf8504000 port 0xf8504200 irq 29 ata1.00: ATAPI: TEAC DVD+/-RW DVW28SLC, A.06, max UDMA/33 ata1.00: configured for UDMA/33 ata4: SATA link down (SStatus 0 SControl 300) ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5: SATA link down (SStatus 0 SControl 300) ata3.00: _GTF unexpected object type 0x1 ata3.00: ATA-8: WDC WD1600BEVT-75ZCT0, 11.01A11, max UDMA/133 ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) ata3.00: _GTF unexpected object type 0x1 ata3.00: configured for UDMA/133 EXT4-fs (sda1): mounted filesystem with ordered data mode EXT4-fs (sda5): mounted filesystem with ordered data mode
Can you please attach full output of 'dmesg' which contain both boot and error messages preferably with printk timestamp turned on?
Created attachment 22270 [details] dmesg 2.6.31-rc2 Burning failed
Created attachment 22271 [details] dmesg 2.6.30.1 Burning success with the same media
Created attachment 22272 [details] .config 2.6.31-rc2
Created attachment 22273 [details] .config 2.6.30.1
Arch vostro 2.6.31-rc2-TEST #1 SMP PREEMPT Sun Jul 5 09:57:29 CEST 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux Arch vostro 2.6.30.1-DELL #1 SMP PREEMPT Fri Jul 3 11:02:25 CEST 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux I would be glad to send any additional info if required
I've just noticed when I inserted a dvd wich contain some data on it the following error in dmesg, just add it to the end of the output in 2.6.31-rc2 1057.302721] <6>sadc[5506]: segfault at 18 ip 00007fa7e5e413ea sp 00007fff5fa01450 error 4 in libc-2.10.1.so[7fa7e5dcf000+149000] [ 1059.916104] ISO 9660 Extensions: RRIP_1991A [ 1101.805664] ISO 9660 Extensions: RRIP_1991A
Hmmm... there's no ATA error. The only relevant outputs are the followings. [ 87.867085] sr 3:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08 [ 87.867097] sr 3:0:0:0: [sr0] Sense Key : 0x5 [current] [ 87.867106] sr 3:0:0:0: [sr0] ASC=0x21 ASCQ=0x0 [ 87.867113] end_request: I/O error, dev sr0, sector 0 [ 87.867121] Buffer I/O error on device sr0, logical block 0 [ 87.874334] sr 3:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08 [ 87.874345] sr 3:0:0:0: [sr0] Sense Key : 0x5 [current] [ 87.874353] sr 3:0:0:0: [sr0] ASC=0x21 ASCQ=0x0 [ 87.874361] end_request: I/O error, dev sr0, sector 0 It's probably from media presence polling after you inserted blank media. The system tries to open and read the device to determine what kind of media it is. As it's blank, read fails with LOGICAL BLOCK ADDRESS OUT OF RANGE (ASC/ASCQ 21/00). This is the expected behavior. sadc is the process collecting system stats. Maybe it can't cope with the device changing size or something? At any rate, it segfaulting isn't relevant to the burning failure. Can you try to burn with wodim with -vvv option and see what it reports? The drive probably have failed certain commands and those failures would have been reported directly to the burning program. OS and drivers just play a messenger while burning and nothing went wrong while delivering commands and responses back and forth. Thanks.
Created attachment 22284 [details] wodim and dmesg output Strange, wodim wont start the burning as regular user, when I run it as root it fails again with Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error and in addition there is some new dmesg output: [ 2487.704099] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 2487.704115] ata4.00: cmd a0/01:00:00:00:f8/00:00:00:00:00/a0 tag 0 dma 63488 out [ 2487.704117] cdb 2a 00 00 00 03 07 00 00 1f 00 00 00 00 00 00 00 [ 2487.704118] res 40/00:02:0c:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout) [ 2487.704123] ata4.00: status: { DRDY } [ 2492.753157] ata4: link is slow to respond, please be patient (ready=0) [ 2497.751159] ata4: device not ready (errno=-16), forcing hardreset [ 2497.751177] ata4: soft resetting link [ 2502.952160] ata4: link is slow to respond, please be patient (ready=0) [ 2507.797176] ata4: SRST failed (errno=-16) [ 2507.797194] ata4: soft resetting link [ 2512.998139] ata4: link is slow to respond, please be patient (ready=0) [ 2517.843154] ata4: SRST failed (errno=-16) [ 2517.843172] ata4: soft resetting link [ 2523.043158] ata4: link is slow to respond, please be patient (ready=0) [ 2552.880158] ata4: SRST failed (errno=-16) [ 2552.880175] ata4: soft resetting link [ 2557.927153] ata4: SRST failed (errno=-16) [ 2557.927162] ata4: reset failed, giving up [ 2557.927168] ata4.00: disabled [ 2557.927491] ata4: EH complete I cant even eject the blank dvd now with eject /dev/sr0
[combuster@vostro ~]$ eject /dev/sr0 eject: unable to eject, last error: Inappropriate ioctl for device I get this when I try to eject a device from console, it unmounts it but does not eject the dvd...
Everything is ok with 2.6.31-rc2-git7, seems that this have been the cause of problems... isofs: fix Joliet regression commit 5404ac8e4418ab3d254950ee4f9bcafc1da20b4a ("isofs: cleanup mount option processing") missed conversion of joliet option flag resulting in non-working Joliet support. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8711c67bee675b4f7a378c71ad5a59c981ec3df0
Ah... strange. The failed command is WRITE_10 and I don't really see how isofs update can affect burning. Hmmmm... well, if it works now, I suppose all is well. If you really wanna what fixed it, bisection might be the only option. :-( Thanks.