Skip to contentSkip to conversation

IDE CDROM locks the system hard on media error

DISCUSSION Stanislav Meduna 6 participants 9 messages Dec 24, 2001 – Jan 2, 2002

lore
Share & tools
lore
#0 lore raw

Hello,

I am catalogizing my set of CDs and so I have tortured my CD drive with a bunch of less-than-optimal CDs. I had two hard lockups most probably connected to problematic media.

The last message in log is

kernel: scsi0: ERROR on channel 0, id 0, lun 0,
CDB: Request Sense 00 00 00 40 00
kernel: Current sd0b:00: sense key Medium Error
kernel: Additional sense indicates No seek complete
kernel: I/O error: dev 0b:00, sector 504
kernel: ISOFS: unable to read i-node block

Shortly (but not immediately, the kernel tried a bit more to get some data from the drive) after that the system froze - not even SysRq worked.

I am using vanilla 2.4.17, hdc=ide-scsi, my drive is Mitsumi CR-4804TE, motherboard is Abit BP6 SMP, Intel PIIX4 IDE controller,

More details available upon request. Please, Cc: replies to me.

Regards

Signature · 1 line
                                   Stano
#1 lore raw
Quoted 2 lines

I am using vanilla 2.4.17, hdc=ide-scsi, my drive is Mitsumi CR-4804TE, motherboard is Abit BP6 SMP, Intel PIIX4 IDE controller,

I've seen a few similar reports of this back to about 2.4.10 or so, maybe earlier even. Right now I don't think anyone knows what is up

#2 lore raw
Quoted 5 lines · Alan Cox
Quoted 2 lines

I am using vanilla 2.4.17, hdc=ide-scsi, my drive is Mitsumi CR-4804TE, motherboard is Abit BP6 SMP, Intel PIIX4 IDE controller,

I've seen a few similar reports of this back to about 2.4.10 or so, maybe earlier even. Right now I don't think anyone knows what is up

If it is DMAing and there is a 1us transaction delay it is toast. Intel PIIX4 AB/EB is a NO-NO for doing ATAPI on.

Regards,

Andre Hedrick
CEO/President, LAD Storage Consulting Group
Linux ATA Development
Linux Disk Certification Project

#3 lore raw

Hello,

Quoted 1 line

If it is DMAing and there is a 1us transaction delay it is toast.

Oh... But why does the whole kernel lock up?

Quoted 1 line

Intel PIIX4 AB/EB is a NO-NO for doing ATAPI on.

Only when using DMA or generally?

Maybe there should be some "quirk" disallowing this or at least warn when the user happens to select this?

Regards

Signature · 1 line
                                      Stano
#4 lore raw

Only in UltraDMA for all devices.
Switch to MWDMA2 and it is all cool.

Quoted 6 lines · Stanislav Meduna

Hello,

Quoted 1 line

If it is DMAing and there is a 1us transaction delay it is toast.

Oh... But why does the whole kernel lock up?

Quoted 11 lines
Quoted 1 line

Intel PIIX4 AB/EB is a NO-NO for doing ATAPI on.

Only when using DMA or generally?

Maybe there should be some "quirk" disallowing this or at least warn when the user happens to select this?

Regards

Signature · 1 line
                                      Stano

Andre Hedrick
CEO/President, LAD Storage Consulting Group
Linux ATA Development
Linux Disk Certification Project

#5 lore raw
In reply to Andre Hedrick
Quoted 2 lines

If it is DMAing and there is a 1us transaction delay it is toast. Intel PIIX4 AB/EB is a NO-NO for doing ATAPI on.

So we should set ATAPI devices on the PIIX4 to non DMA modes ?

#6 lore raw
Quoted 2 lines

So we should set ATAPI devices on the PIIX4 to non DMA modes ?

Setting it to mdma2 fixes the problem on my system, and there is no slowdown whatsoever. (Due to its already slow speed?)

It would have to be verified by someone with a faster device than mine, but right now there doesn't seem to be any downside.

#7 lore raw
In reply to Alan Cox

My mobo is an Abit KT7E - which has some VIA (KT133 I think) chipset and it still happens here under certain circumstances - I doubt this is the issue.

Quoted 9 lines · Alan Cox
Quoted 2 lines

If it is DMAing and there is a 1us transaction delay it is toast. Intel PIIX4 AB/EB is a NO-NO for doing ATAPI on.

So we should set ATAPI devices on the PIIX4 to non DMA modes ? -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#8 lore raw
In reply to Stanislav Meduna
Quoted 16 lines · Stanislav Meduna

Hello,

I am catalogizing my set of CDs and so I have tortured my CD drive with a bunch of less-than-optimal CDs. I had two hard lockups most probably connected to problematic media.

The last message in log is

kernel: scsi0: ERROR on channel 0, id 0, lun 0,
CDB: Request Sense 00 00 00 40 00
kernel: Current sd0b:00: sense key Medium Error
kernel: Additional sense indicates No seek complete
kernel: I/O error: dev 0b:00, sector 504
kernel: ISOFS: unable to read i-node block

Quoted 4 lines

Shortly (but not immediately, the kernel tried a bit more to get some data from the drive) after that the system froze - not even SysRq worked.

Actually I've wanted to report the same problem - I even believe I've already reported this long time ago in the dark ages when everyone has been saying some stupid things about BP6... Usualy reading CD-ROM && hdparm -t /dev/hda was quite easy way to deadlock the whole system.

Now I would say that 2.4.17rc2 becames more stable but still I've been faced with similar problem - I have tried to read damaged CD with movie
and this is part of log:

begin of errors - please notice the TIME values!

Dec 29 22:02:04 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:02:13 decibel kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
Dec 29 22:02:13 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:02:20 decibel kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
Dec 29 22:02:20 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:02:27 decibel kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
Dec 29 22:02:27 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:02:33 decibel kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
Dec 29 22:02:33 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:02:33 decibel kernel: hdc: DMA disabled
Dec 29 22:02:33 decibel kernel: hdc: ATAPI reset complete
...
Dec 29 22:03:19 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:03:19 decibel kernel: hdc: ATAPI reset complete
Dec 29 22:03:19 decibel kernel: end_request: I/O error, dev 16:00 (hdc),
sector 321092
...
Dec 29 22:05:47 decibel kernel: hdc: ATAPI reset complete
Dec 29 22:05:47 decibel kernel: end_request: I/O error, dev 16:00 (hdc),
sector 321976Dec 29 22:08:37 decibel kernel: end_request: I/O error, dev
16:00 (hdc), sector 322416
Dec 29 22:08:43 decibel kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
...
Dec 29 22:08:59 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:09:25 decibel kernel: SysRq : Emergency Sync
Dec 29 22:09:25 decibel kernel: Syncing device 21:41 ... OK
Dec 29 22:09:25 decibel kernel: Syncing device 21:46 ... OK
Dec 29 22:09:25 decibel kernel: Syncing device 21:47 ... OK
Dec 29 22:09:25 decibel kernel: Syncing device 16:00 ... OK
Dec 29 22:09:25 decibel kernel: Syncing device 03:05 ... OK
Dec 29 22:09:25 decibel kernel: Done.

deadlock here after 'U' - reset button required

then again:

Dec 29 22:23:39 decibel kernel: hdc: cdrom_decode_status: error=0x30
Dec 29 22:23:39 decibel kernel: hdc: ATAPI reset complete
Dec 29 22:23:39 decibel kernel: end_request: I/O error, dev 16:00 (hdc),
sector 321980
...
Dec 29 22:28:10 decibel kernel: hdc: ATAPI reset complete
Dec 29 22:28:10 decibel kernel: end_request: I/O error, dev 16:00 (hdc),
sector 322420
...
Dec 29 22:29:30 decibel kernel: hdc: ATAPI reset complete
Dec 29 22:29:30 decibel kernel: end_request: I/O error, dev 16:00 (hdc),

sector 321980

And looping for loooong time without any progress here - around some numbers.

I've tried then to use 'dd' with conv=noerror but I had
to skip error part manualy via skip simply because linux was unable to make any progress here even after 10 minutes.

I guess my CD-ROM was in DMA mode initialy but after it switchies DMA of the computer becomes almost unusable.

Another problem I would like to see solved one day - why just my machine is completely unable while anacron does it's jobs ???
Why there couldn't be option in /proc to set limit for maximum amount of RAM
for caching filesystem ??? (like 30MB from my 128MB ram ?)

(I think I know better what I need that the Linux VM)

bye

kabi