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
Then it runs fine for days again, BUT at this point the ethernet interface
is dead (the epic100 driver, same as included in the 2.0.34-pre series).
Downing eth0 and ifconfiging it again brings it back to life...
This box is on a remote site, fortunately all boxes there have a serial
console and a RPB (remote power boot device).
Mike.
--
Miquel van Smoorenburg | Our vision is to speed up time,
miquels@cistron.nl | eventually eliminating it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu