From: Stephen Hemminger <shemminger@osdl.org>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.20-rc1 sky2 problems (regression?)
Date: Thu, 14 Dec 2006 15:31:46 -0800 [thread overview]
Message-ID: <20061214153146.52d5de40@freekitty> (raw)
In-Reply-To: <87zm9qkqsj.fsf@sycorax.lbl.gov>
On Thu, 14 Dec 2006 15:21:00 -0800
Alex Romosan <romosan@sycorax.lbl.gov> wrote:
> Stephen Hemminger <shemminger@osdl.org> writes:
>
> > Another useful bit of information is the statistics (ethtool -S eth0).
> > When there were flow control bugs, they would show up as count of 1.
>
> the driver locked up again, even with msi interrupts disabled and
> idle_timeout=10. the console message was pretty much as before:
>
> kernel: NETDEV WATCHDOG: eth0: transmit timed out
> kernel: sky2 eth0: tx timeout
> kernel: sky2 eth0: transmit ring 336 .. 296 report=336 done=336
> kernel: sky2 hardware hung? flushing
> kernel: NETDEV WATCHDOG: eth0: transmit timed out
> kernel: sky2 eth0: tx timeout
> kernel: sky2 eth0: transmit ring 296 .. 255 report=336 done=336
> kernel: sky2 status report lost?
>
> and this is the output from ethtool -S:
>
> NIC statistics:
> tx_bytes: 3092123897
> rx_bytes: 546577898
> tx_broadcast: 20
> rx_broadcast: 4376
> tx_multicast: 0
> rx_multicast: 459
> tx_unicast: 2585993
> rx_unicast: 1550758
> tx_mac_pause: 1
If this is repeatable... and mac_pause is always one then the
problem is hardware flow control. I saw bugs before in the bus
interface where it would not resume on unaligned buffer, but
that was on receive.
next prev parent reply other threads:[~2006-12-14 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87psammchi.fsf@sycorax.lbl.gov>
2006-12-14 21:30 ` 2.6.20-rc1 sky2 problems (regression?) Stephen Hemminger
2006-12-14 22:00 ` Alex Romosan
2006-12-14 22:25 ` Alex Romosan
2006-12-14 22:47 ` Stephen Hemminger
2006-12-14 22:57 ` Alex Romosan
2006-12-14 23:08 ` Alex Romosan
2006-12-14 23:21 ` Alex Romosan
2006-12-14 23:31 ` Stephen Hemminger [this message]
2006-12-15 1:04 ` Alex Romosan
2006-12-15 2:24 ` Herbert Xu
2006-12-15 3:22 ` Stephen Hemminger
2006-12-15 3:53 ` Alex Romosan
2006-12-16 1:25 ` Stephen Hemminger
2006-12-16 1:53 ` Alex Romosan
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=20061214153146.52d5de40@freekitty \
--to=shemminger@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
/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).