[lkml]   [2006]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: cdrom: a dirty CD can freeze your system

    > It's worse than that. See
    > and other similar reports. So far, noone cares it seems (for several years already).

    woops ... fortunately, I dont have that kind of problem. my code just does:

    loop {
    ioctl( SG_IO - timeout=3 seconds);
    write block to disk.

    SG_IO behaves a bit more friendly.... than, say, "CDROMREAD{MODE1,MODE2,AUDIO}" does.
    nevertheless, the IDE interface becomes unusable until you reboot the system.

    e.g., just right now, I did:

    o insert bad CD
    o read it until an error occurs.
    o "hdparm -w /dev/hdb" - this will turn DMA off. kernel log shows:
    hdb: DMA disabled
    hdb: ATAPI reset complete
    o "hdparm -d 1 /dev/hdb" to reenable DMA, "hdparm /dev/hdb" to look at the
    drive settings. the kernel log then shows:
    hdb: irq timeout: status=0xd0 { Busy }
    ide: failed opcode was: unknown
    hdb: ATAPI reset complete
    hdb: status error: status=0x49 { DriveReady DataRequest Error }
    hdb: status error: error=0x04 { AbortedCommand }
    ide: failed opcode was: unknown
    hdb: drive not ready for command
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hdb: request sense failure: status=0x51 { DriveReady SeekComplete Error }
    hdb: request sense failure: error=0x44 { AbortedCommand LastFailedSense=0x04 }

    hdparm is now in state "D" -> reboot required.
    not so good, da?

    kind regards,
    herbert rosmanith
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-05-04 15:03    [W:0.020 / U:125.616 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site