[TriLUG] X Crashes, SCSI drive to blame???

Al Koscielny alko at nc.rr.com
Thu Jan 24 10:27:01 EST 2002


On Thursday 24 January 2002 10:16, you wrote:
> Jan 24 10:10:49 sec22 kernel: scsi : aborting command due to timeout :
> pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 00 10 00 00 01 00
> Jan 24 10:10:49 sec22 kernel: hdd: timeout waiting for DMA
> Jan 24 10:10:49 sec22 kernel: ide_dmaproc: chipset supported
> ide_dma_timeout func only: 14
> Jan 24 10:10:49 sec22 kernel: hdd: status timeout: status=0xd0 { Busy }
> Jan 24 10:10:49 sec22 kernel: hdd: drive not ready for command
> Jan 24 10:10:49 sec22 kernel: scsi : aborting command due to timeout :
> pid 0, scsi0, channel 0, id 0, lun 0 Read TOC 02 00 00 00 00 05 00 0c 00
> Jan 24 10:11:14 sec22 kernel: scsi : aborting command due to timeout :
> pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 00 10 00 00 01 00
> Jan 24 10:11:14 sec22 kernel: SCSI host 0 abort (pid 0) timed out -
> resetting

If you boot to runlevel 3 and try to use the CD/RW, can you read a CD?  The 
messages make me suspect that the drive itself has failed.  I don't know what 
that has to do with X crashing, tho.
-- 
Al Koscielny
alko at nc.rr.com



More information about the TriLUG mailing list