> I've also hat some errors like this:
> hdb: irq timeout: status=0xd0 { Busy }
> ide: failed opcode was: unknown
> hdb: DMA disabled
The drive went away and stopped talking
> hdb: ATAPI reset complete
> hdb: irq timeout: status=0x80 { Busy }
> ide: failed opcode was: unknown
> hdb: ATAPI reset complete
> hdb: irq timeout: status=0x80 { Busy }
> ide: failed opcode was: unknown
> hdb: cdrom_read_intr: data underrun (4 blocks)
> end_request: I/O error, dev hdb, sector 7831400
> Buffer I/O error on device hdb, logical block 1957850
And eventually got back to sanity
> That happened on a DVD (successfully read in and played by the drive),..
> but when I pushed the eject button (while xine sill was playing) I got
> those errors,..
> I assume that xine continued to read data but the DVD was already
> ejected and thus the request errors....
> But I think there shouldn't be a request error but more something like
> "no medium found" or the eject button should have been disabled at
> all,... so I think something goes really wrong with that drive ;)
The requests were outstanding so the behaviour is expected. As to the
eject button - Xine chooses not to lock the drive. I don't know why it
prefers to work that way but it's an application choice on the whole.
-
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/
