Just a datapoint for those who collect strange phenomena:
Sometimes on our news server (2.0.33 vanilla) the buslogic driver gets a
bad hairday and decides to reset itself:
scsi : aborting command due to timeout : pid 661112429, scsi0, channel 0, id 2, lun 0 0x0a 02 9a 4e 02 00
scsi0: Aborting CCB #661132799 to Target 2
scsi0: CCB #661132799 to Target 2 Aborted
SCSI host 0 abort (pid 661112152) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Sending Bus Device Reset CCB #661132828 to Target 2
SCSI host 0 abort (pid 661112153) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 2
scsi0: *** BusLogic BT-958 Initialized Successfully ***
scsi0: Tagged Queuing now active for Target 8
scsi0: Tagged Queuing now active for Target 2
scsi0: Tagged Queuing now active for Target 0
This sequence is almost certainly either a cabling and termination problem, or
most likely buggy disk drive firmware. What are the startup messages from the
BusLogic driver and SCSI subsystem?
Leonard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu