From: Miek Gieben <miekg@atoom.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.5 network related crash
Date: Thu, 8 Apr 2004 18:38:44 +0200 [thread overview]
Message-ID: <20040408163844.GA21251@atoom.net> (raw)
Hello,
I've experienced a 2.6.5 crash today, I believe it is network related.
I don't have a oops it just locked solid. Below is information I do
have. What can I do to narrow this down?
regards, Miek
In the logs:
Apr 8 10:46:17 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:46:17 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:46:17 kasteel kernel: Rx ring cba1d000: 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 0000 80000000 80000000 80000000 8 10:46:33 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:46:33 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:46:33 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:46:33 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:46:33 kasteel kernel: Rx ring cba1d000: 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 0000 8 10:47:13 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:13 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:13 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:13 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:13 kasteel kernel: Rx ring cba1d000: 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000
Apr 8 10:47:13 kasteel kernel: Tx ring cba1e000: 80000000 80000000 80000000 0000 80000000 80000000
Apr 8 10:47:19 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:19 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:19 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:19 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:19 kasteel kernel: Rx ring cba1d000: 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000
Apr 8 10:47:19 kasteel kernel: Tx ring cba1e000: 80000000 80000000 80000000 80000000 0000 80000000
Apr 8 10:47:25 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:25 kasteel kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 8 10:47:25 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:25 kasteel kernel: eth0: Transmit timed out, status 00000000, resetting...
Apr 8 10:47:25 kasteel kernel: Rx ring cba1d000: 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000
Apr 8 10:47:25 kasteel kernel: Tx ring cba1e000: 80000000 80000000 80000000 0000 80000000 8000
Information about eth0:
eth0 Link encap:Ethernet HWaddr 00:02:44:52:09:30
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::202:44ff:fe52:930/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4735 errors:0 dropped:0 overruns:0 frame:0
TX packets:5215 errors:0 dropped:0 overruns:0 carrier:0
collisions:3 txqueuelen:1000
RX bytes:793790 (775.1 KiB) TX bytes:3111062 (2.9 MiB)
Interrupt:10 Base address:0xec00
The card in question is a:
00:0a.0 Ethernet controller: MYSON Technology Inc SURECOM EP-320X-S 100/10M Ethernet PCI Adapter
using irq 10 and the fealnx module
Modules loaded:
# lsmod
Module Size Used by
ipt_LOG 5024 2
ipt_limit 1824 2
ipt_state 1376 4
ipt_MARK 1600 12
ipt_REJECT 5312 38
ip_nat_ftp 3984 0
ip_conntrack_ftp 71092 1 ip_nat_ftp
ipt_mark 1248 0
iptable_mangle 2048 1
iptable_nat 20044 2 ip_nat_ftp
iptable_filter 2112 1
ipv6 227552 8
3c509 11924 0
8139too 19328 0
fealnx 13352 0
mii 3968 2 8139too,fealnx
--
today's fortune:
BOFH excuse #162:
bugs in the RAID
reply other threads:[~2004-04-08 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040408163844.GA21251@atoom.net \
--to=miekg@atoom.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®