From: Ian Kumlien <pomac@vapor.com>
To: Linux-kernel@vger.kernel.org
Cc: shemminger@linux-foundation.org
Subject: [BUG] Sky2 driver in 2.6.22-rc5-git1-cfs-v17
Date: Thu, 21 Jun 2007 22:51:32 +0200 [thread overview]
Message-ID: <1182459092.7032.11.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Hi,
recently have started to see this in my dmesg:
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 449 .. 408 report=449 done=449
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 48K
sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control rx
I'm not using MSI since it seems to have caused problems in the past.
I run with a 9k mtu
sky2 eth0: transmit ring 18 .. 489 report=18 done=18
---- I assume ring max is 512 (ie 1-512) since:
Ring parameters for eth0:
Current hardware settings:
RX: 168
RX Mini: 0
RX Jumbo: 0
TX: 511
And 489 + 41 - 18 = 512
sky2 eth0: transmit ring 197 .. 156 report=197 done=197
sky2 eth0: transmit ring 480 .. 439 report=480 done=480
sky2 eth0: transmit ring 413 .. 372 report=413 done=413
sky2 eth0: transmit ring 320 .. 279 report=320 done=320
Else, they are all off by 41.
Is this a known bug?
Comments? ideas?
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on
udp fragmentation offload: off
--
Ian Kumlien <pomac (a) vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2007-06-21 21:01 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=1182459092.7032.11.camel@localhost \
--to=pomac@vapor.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.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
Powered by JetHome