From: Christoph Kuhles (ck_at_aquatix.de)
Date: Sat 08 Mar 2003 - 09:54:46 GMT
Hi there,
I had the second 'crash' with ctx-15 running a few days ago. The box
didn't exactly crash, it was working fine, except for the network
card. After a reboot everything worked again and I found the following
in /var/log/messages:
Mar 5 10:16:06 adjana kernel: NETDEV WATCHDOG: eth0: transmit timed out
Mar 5 10:16:06 adjana kernel: eth0: transmit timed out, tx_status 00 status e601.
Mar 5 10:16:06 adjana kernel: diagnostics: net 0cc0 media 8802 dma 0000003b.
Mar 5 10:16:06 adjana kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Mar 5 10:16:06 adjana kernel: Flags; bus-master 1, dirty 143444689(1) current 143444689(1)
Mar 5 10:16:06 adjana kernel: Transmit list 00000000 vs. dfca1240.
Mar 5 10:16:06 adjana kernel: 0: @dfca1200 length 8000002a status 8000002a
Mar 5 10:16:06 adjana kernel: 1: @dfca1240 length 80000036 status 00000036
Mar 5 10:16:06 adjana kernel: 2: @dfca1280 length 8000003a status 0000003a
Mar 5 10:16:06 adjana kernel: 3: @dfca12c0 length 80000036 status 00000036
Mar 5 10:16:06 adjana kernel: 4: @dfca1300 length 80000036 status 00000036
Mar 5 10:16:06 adjana kernel: 5: @dfca1340 length 80000036 status 00000036
Mar 5 10:16:06 adjana kernel: 6: @dfca1380 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 7: @dfca13c0 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 8: @dfca1400 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 9: @dfca1440 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 10: @dfca1480 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 11: @dfca14c0 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 12: @dfca1500 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 13: @dfca1540 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 14: @dfca1580 length 8000002a status 0000002a
Mar 5 10:16:06 adjana kernel: 15: @dfca15c0 length 8000002a status 8000002a
The cabelling etc. was all ok, it must have been the machine itself
that caused this error. Does anyone have an idea what could have
happened and how it can be prevented from happening in the future? Any
advice appreciated.
-- Mit freundlichen Gruessen / Best regardsChristoph Kuhles Geschaeftsleitung / Managing Director
Aquatix IT-Services e.K. Telefon: +49 471 3914540 Gildemeisterstr. 15 Telefax: +49 800 1234500 27568 Bremerhaven E-Mail: ck_at_aquatix.de AG Bremerhaven, HRA 4216 Web: http://www.aquatix.de/