Bugzilla – Bug 133118
cd burning broken in suse linux 10.0
Last modified: 2006-12-20 05:42:14 UTC
burning a cd-rom with k3b creates a hanging cdrecord process with following kernel messages in /var/log/messages: Nov 9 21:54:41 athlon kernel: hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest } Nov 9 21:54:41 athlon kernel: ide: failed opcode was: unknown Nov 9 21:54:41 athlon kernel: hdd: drive not ready for command Nov 9 21:54:41 athlon kernel: hdd: status timeout: status=0xd0 { Busy } Nov 9 21:54:41 athlon kernel: ide: failed opcode was: unknown Nov 9 21:54:41 athlon kernel: hdd: drive not ready for command Nov 9 21:54:41 athlon kernel: hdd: ATAPI reset complete Nov 9 21:54:46 athlon kernel: hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest } Nov 9 21:54:46 athlon kernel: ide: failed opcode was: unknown Nov 9 21:54:46 athlon kernel: hdd: drive not ready for command Nov 9 21:54:46 athlon kernel: hdd: status timeout: status=0xd0 { Busy } Nov 9 21:54:46 athlon kernel: ide: failed opcode was: unknown Nov 9 21:54:46 athlon kernel: hdd: drive not ready for command Nov 9 21:54:46 athlon kernel: hdd: ATAPI reset complete Nov 9 21:54:47 athlon kernel: hdd: status error: status=0x08 { DataRequest } Nov 9 21:54:47 athlon kernel: ide: failed opcode was: unknown Nov 9 21:54:47 athlon kernel: hdd: drive not ready for command Hardware information: device is a CyberDrv CW088D CD-R/RW 110F (/dev/hdd, ) at /media/cdrecorder [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R] cpu is a athlon2400, motherboard is a Gigabyte 7VAXFS with Via KT400 chipset I can burn under Suse Linux 9.1 and 9.2 without problems.
This appears to be a hardware problem. At first, try using another software, like cdrecord (from the cdrtools package). If the same error occours, this is most definitely a hardware problem.
The kernel messages are caused by cdrecord (it is called by k3b and then cdrecord hangs). How can it be a hardware problem if I can burn with suse9.2 on this same machine, using the same cd writer device? Looks like a kernel problem?
Add the output of hwinfo here and 500 lines of your syslog (please don't compress anything).
Created attachment 57304 [details] output of hwinfo as requested by comment#3
Created attachment 57305 [details] last 500 lines of /var/log/messages as requested by comment#3
I did a cdrecord -v -V -dummy speed=0 dev=/dev/hdd burn.iso Initially it is able to request some information and then it hangs. output attached also
Created attachment 57307 [details] extract of cdrecord output
Vladimir: Might this problem be known? Ordinarily I'd say the problem lies in the filesystem layer. Taking Chris into CC.
It looks like a kernel or hardware problem. Jens, can you look into it, please?
ive got similar comunicates when kernel loads, during checking connected nodma hard disc. maybe you should turn off dma for that drive
I see the same problem on my machine.
Turning off dma for the drive does not help.
The error messages in /var/log/messages look the same as in the original comment of this bug report.
Has there been any progress here? Has this been fixed in SuSE Linux 10.1?
No progress in Suse 10.1, same behaviour: Jul 3 20:26:42 athlon kernel: cdrom: This disc doesn't have any tracks I recognize! Jul 3 20:29:20 athlon kernel: hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest } Jul 3 20:29:20 athlon kernel: ide: failed opcode was: unknown Jul 3 20:29:20 athlon kernel: hdd: drive not ready for command Jul 3 20:29:20 athlon kernel: hdd: status timeout: status=0xd0 { Busy } Jul 3 20:29:20 athlon kernel: ide: failed opcode was: unknown Jul 3 20:29:20 athlon kernel: hdd: DMA disabled Jul 3 20:29:20 athlon kernel: hdd: drive not ready for command Jul 3 20:29:20 athlon kernel: hdd: ATAPI reset complete Jul 3 20:29:26 athlon kernel: hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest } Jul 3 20:29:26 athlon kernel: ide: failed opcode was: unknown Jul 3 20:29:26 athlon kernel: hdd: drive not ready for command Jul 3 20:29:26 athlon kernel: hdd: status timeout: status=0xd0 { Busy } Jul 3 20:29:26 athlon kernel: ide: failed opcode was: unknown Jul 3 20:29:26 athlon kernel: hdd: drive not ready for command Jul 3 20:29:26 athlon kernel: hdd: ATAPI reset complete Jul 3 20:29:26 athlon kernel: hdd: status error: status=0x08 { DataRequest } Jul 3 20:29:26 athlon kernel: ide: failed opcode was: unknown Jul 3 20:29:26 athlon kernel: hdd: drive not ready for command Jul 3 20:30:06 athlon kernel: hdd: irq timeout: status=0xd0 { Busy } Jul 3 20:30:06 athlon kernel: ide: failed opcode was: unknown Jul 3 20:30:06 athlon kernel: hdd: ATAPI reset complete ... and so on
burning with kubuntu (kernel 2.6.15) works! It issues similar messages for about 2 minutes, stops with "scsi: unknown opcode 0x01" and starts burning. Here their kernel messages: Jul 29 14:53:13 athlon kernel: [4295786.241000] hdd: status error: status=0xd0 { Busy } Jul 29 14:53:13 athlon kernel: [4295786.241000] ide: failed opcode was: unknown Jul 29 14:53:13 athlon kernel: [4295786.241000] hdd: DMA disabled Jul 29 14:53:13 athlon kernel: [4295786.241000] hdd: drive not ready for command Jul 29 14:53:43 athlon kernel: [4295816.241000] hdd: ATAPI reset timed-out, status=0x80 Jul 29 14:53:43 athlon kernel: [4295816.241000] hdc: DMA disabled Jul 29 14:53:43 athlon kernel: [4295816.291000] ide1: reset: success Jul 29 14:54:43 athlon kernel: [4295876.497000] hdd: irq timeout: status=0xd0 { Busy } Jul 29 14:54:43 athlon kernel: [4295876.497000] ide: failed opcode was: unknown Jul 29 14:54:43 athlon kernel: [4295876.547000] hdd: ATAPI reset complete Jul 29 14:54:43 athlon kernel: [4295876.754000] hdd: status error: status=0x08 { DataRequest } Jul 29 14:54:43 athlon kernel: [4295876.754000] ide: failed opcode was: unknown Jul 29 14:54:43 athlon kernel: [4295876.754000] hdd: drive not ready for command ... Jul 29 14:55:27 athlon kernel: [4295920.247000] hdd: status timeout: status=0xd0 { Busy } Jul 29 14:55:27 athlon kernel: [4295920.247000] ide: failed opcode was: unknown Jul 29 14:55:27 athlon kernel: [4295920.247000] hdd: drive not ready for command Jul 29 14:55:27 athlon kernel: [4295920.297000] hdd: ATAPI reset complete Jul 29 14:55:27 athlon kernel: [4295920.515000] scsi: unknown opcode 0x01
Still happen with the latest 10.1 kernel update?
Created attachment 96233 [details] kernel messages during burning
it burns if one follows this procedure: - set DMA on for burning device and reboot if necessary - start burning, the desktop will freeze - wait one or two minutes - press eject button of burning device - desktop becomes usable and burning starts Last week I replaced my failing motherboard (VIA chipset) with one having a Nforce2 chipset. So I tested burning again and found out that the above procedure works - but with one difference: before the kernel update I had to use DMA off, after the kernel update I have to use DMA on. In both cases the inverted DMA state did not freeze the desktop, but did not allow burning either. It is strange that the kernel disables DMA before burning, but the procedure needs an initial setting of DMA on (I tried it!) kernel messages during burning are attached as file
just a clarification: after burning one cd, then DMA is turned off by kernel and it is not possible to burn another cd without reboot on my system. If I try to burn another cd without reboot, the kernel writes to /var/log/messages: Aug 16 17:08:16 athlon kernel: cdrom: This disc doesn't have any tracks I recognize! Aug 16 17:08:38 athlon kernel: hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest } Aug 16 17:08:38 athlon kernel: ide: failed opcode was: unknown Aug 16 17:08:38 athlon kernel: hdd: drive not ready for command Aug 16 17:08:38 athlon kernel: hdd: status timeout: status=0xd0 { Busy } Aug 16 17:08:38 athlon kernel: ide: failed opcode was: unknown Aug 16 17:08:38 athlon kernel: hdd: drive not ready for command Aug 16 17:08:38 athlon kernel: hdd: ATAPI reset complete Aug 16 17:08:38 athlon kernel: hdd: request sense failure: status=0x51 { DriveReady SeekComplete Error } Aug 16 17:08:38 athlon kernel: hdd: request sense failure: error=0x50 { LastFailedSense=0x05 } Aug 16 17:08:38 athlon kernel: hdd: request sense failure: status=0x51 { DriveReady SeekComplete Error } Aug 16 17:08:38 athlon kernel: hdd: request sense failure: error=0x50 { LastFailedSense=0x05 } Thats it, i.e. cdrecord cannot be killed anymore, even not by root with kill -9. This nasty behaviour destroys my master boot record at halt so that I have to recover with a dd from Rescue
Reopen for 10.1 if the bug still exists.
sorry, bug is still present in 10.1. See comments #15 to #20
Still present in 10.2? If so, please reopen.