From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org
Subject: sky2 hang.
Date: Tue, 31 Oct 2006 09:11:44 +0300 [thread overview]
Message-ID: <20061031061144.GA1562@2ka.mipt.ru> (raw)
sky2 from debian etch kernel (2.6.17-2) has stopped today after quite
big amount of traffic transferred (30MB/sec for about 3-4 hours).
rmmod/insmod does not help, reboot required.
Here is dmesg output:
Oct 31 06:40:07 kano kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 31 06:40:07 kano kernel: sky2 eth0: tx timeout
Oct 31 06:40:07 kano kernel: sky2 eth0: transmit ring 198 .. 175 report=221 done=221
Oct 31 06:40:07 kano kernel: sky2 status report lost?
Oct 31 06:40:42 kano kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 31 06:40:42 kano kernel: sky2 eth0: tx timeout
Oct 31 06:40:42 kano kernel: sky2 eth0: transmit ring 221 .. 198 report=221 done=221
Oct 31 06:40:42 kano kernel: sky2 hardware hung? flushing
Oct 31 06:54:07 kano kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 31 06:54:07 kano kernel: sky2 eth0: tx timeout
Oct 31 06:54:07 kano kernel: sky2 eth0: transmit ring 198 .. 175 report=221 done=221
Oct 31 06:54:07 kano kernel: sky2 status report lost?
Oct 31 06:54:42 kano kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 31 06:54:42 kano kernel: sky2 eth0: tx timeout
Oct 31 06:54:42 kano kernel: sky2 eth0: transmit ring 221 .. 198 report=221 done=221
Oct 31 06:54:42 kano kernel: sky2 hardware hung? flushing
And here is rmmod/insmod dmesg:
Oct 31 08:58:19 kano kernel: sky2 eth0: disabling interface
Oct 31 08:59:00 kano kernel: ACPI: PCI interrupt for device 0000:05:00.0 disabled
Oct 31 08:59:21 kano kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNKD] -> GSI 18 (level, low) -> IRQ 98
Oct 31 08:59:21 kano kernel: PCI: Setting latency timer of device 0000:05:00.0 to 64
Oct 31 08:59:21 kano kernel: sky2 v1.6.1 addr 0xfbefc000 irq 98 Yukon-EC (0xb6) rev 2
Oct 31 08:59:21 kano kernel: sky2 eth0: addr 00:17:31:9a:e5:be
Oct 31 08:59:21 kano kernel: sky2 eth0: enabling interface
Oct 31 08:59:21 kano kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 31 08:59:23 kano kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Oct 31 08:59:23 kano kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
--
Evgeniy Polyakov
next reply other threads:[~2006-10-31 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 6:11 Evgeniy Polyakov [this message]
2006-10-31 6:24 ` sky2 hang Stephen Hemminger
2006-10-31 7:04 ` Evgeniy Polyakov
2006-10-31 7:08 ` Alexander Wirt
2006-10-31 7:33 ` Evgeniy Polyakov
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=20061031061144.GA1562@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).