Hello!
I am noticing the messages below, scsi is aic7xxx, eth0 is tulip and
kernel is 2.1.126.
Nov 1 21:12:42 defiant kernel: scsi : aborting command due to timeout : pid 508134,
scsi0, channel 0, id 6, lun 0 Write (10) 00 00 69 8f b4 00 00 02 00
Nov 1 21:12:42 defiant kernel: (scsi0:0:6:0) Abort called with bogus Scsi_Cmnd
pointer.
Nov 1 21:12:57 defiant kernel: scsi : aborting command due to timeout : pid 508136,
scsi0, channel 0, id 6, lun 0 Write (6) 00 c0 38 02 00
Nov 1 21:12:57 defiant kernel: (scsi0:0:6:0) Abort called with bogus Scsi_Cmnd
pointer.
...
Nov 3 01:14:19 defiant kernel: scsi : aborting command due to timeout : pid 53143,
scsi0, channel 0, id 6, lun 0 Write (10) 00 00 4e c0 64 00 00 02 00
Nov 3 01:14:19 defiant kernel: (scsi0:0:6:0) Abort called for already completed
command.
Nov 3 01:14:34 defiant kernel: scsi : aborting command due to timeout : pid 53146,
scsi0, channel 0, id 6, lun 0 Write (10) 00 00 74 26 ae 00 00 02 00
Nov 3 01:14:34 defiant kernel: (scsi0:0:6:0) Abort called with bogus Scsi_Cmnd
pointer.
...
Nov 5 23:13:45 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000021c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
Nov 5 23:13:50 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000000c6, CSR13 ffffef05, CSR14 ffffff3f, resetting...
Nov 5 23:13:55 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000010c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
Nov 5 23:14:00 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000000c6, CSR13 ffffef05, CSR14 ffffff3f, resetting...
... until ...
Nov 6 09:10:55 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000020c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
Nov 6 09:11:00 defiant kernel: hdc: timeout waiting for DMA
Nov 6 09:11:00 defiant kernel: hdc: irq timeout: status=0xd0 { Busy }
Nov 6 09:11:00 defiant kernel: hdc: DMA disabled
Nov 6 09:11:00 defiant kernel: ide1: reset: success
Nov 6 09:11:00 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000020c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
... until ...
Nov 6 09:27:49 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000000c6, CSR13 ffffef05, CSR14 ffffff3f, resetting...
Nov 6 09:27:54 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000020c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
Nov 6 09:28:04 defiant last message repeated 2 times
Nov 6 09:28:09 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000000c6, CSR13 ffffef05, CSR14 ffffff3f, resetting...
Nov 6 09:28:14 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000020c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
Nov 6 09:28:19 defiant kernel: eth0: 21041 transmit timed out, status fc6980c5, CSR12
000021c4, CSR13 ffffef09, CSR14 fffff7fd, resetting...
reboot
Nov 6 09:35:50 defiant kernel: eth0: No 21041 10baseT link beat, Media switched to
10base2.
And then this:
Nov 6 10:23:09 defiant kernel: stuck on smp_invalidate_needed IPI wait (CPU#1)
Nov 6 10:23:11 defiant kernel: stuck on smp_invalidate_needed IPI wait (CPU#1)
So it seems that I have timeouts nearly on everything in here. Maybe also
on the PS/2 keyboard and mouse because sometimes they are locked under X
and I have to rlogin to kill the XServer. But nothing about this in the
logs.
What does it mean "stuck on smp_invalidate_needed IPI wait"? The machine
is working on but sometimes, as described, the time runs twice as fast.
The ugly things are the timeouts on scsi, because then the machine hangs
and wants to be rebooted very hard.
Greetings
Robert Sander "Is it Friday yet?"
@Home http://home.pages.de/~gurubert
pgp available there
