From: "Andrew Hall" <andrew.hall@bluereefnetworks.com>
To: "Stephen Hemminger" <shemminger@osdl.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] sky2: tx pause bug fix
Date: Fri, 22 Sep 2006 14:11:04 +1000 [thread overview]
Message-ID: <089101c6ddfd$20ba4320$0b00000a@bluereef.local> (raw)
In-Reply-To: 20060919133159.27165976@localhost.localdomain
Unfortunately I spoke too soon.. :-(
The driver no longer appears to fail under load but still fails randomly
with relatively light load:
Sep 22 07:04:38 localhost syslog.info -- MARK --
Sep 22 07:24:38 localhost syslog.info -- MARK --
Sep 22 07:31:52 localhost user.info kernel: NETDEV WATCHDOG: eth1: transmit
timed out
Sep 22 07:31:52 localhost user.err kernel: sky2 eth1: tx timeout
Sep 22 07:31:52 localhost user.debug kernel: sky2 eth1: transmit ring 27 ..
498 report=27 done=27
Sep 22 07:31:52 localhost user.info kernel: sky2 hardware hung? flushing
Sep 22 07:39:27 localhost user.info kernel: NETDEV WATCHDOG: eth1: transmit
timed out
Sep 22 07:39:27 localhost user.err kernel: sky2 eth1: tx timeout
Sep 22 07:39:27 localhost user.debug kernel: sky2 eth1: transmit ring 498 ..
457 report=27 done=27
Sep 22 07:39:27 localhost user.info kernel: sky2 status report lost?
Sep 22 07:40:07 localhost user.info kernel: NETDEV WATCHDOG: eth1: transmit
timed out
Sep 22 07:40:07 localhost user.err kernel: sky2 eth1: tx timeout
Sep 22 07:40:07 localhost user.debug kernel: sky2 eth1: transmit ring 27 ..
498 report=27 done=27
Sep 22 07:40:07 localhost user.info kernel: sky2 hardware hung? flushing
The driver version that I am using is 1.6.1 with the tx pause bug fix
manually applied. This is compiled against 2.6.17.13 stock.
This fault (since releasing this version into production) has now occured in
3 sites since upgrading them yesterday. The previous version of kernel that
was being used was 2.6.12 (based on the old sk98lin driver) which didn't
manifest any of these problems.
If there's anything I can do to help isolate this issue please let me know.
----- Original Message -----
From: "Stephen Hemminger" <shemminger@osdl.org>
To: "Andrew Hall" <andrew.hall@bluereefnetworks.com>
Cc: <netdev@vger.kernel.org>
Sent: Wednesday, September 20, 2006 6:31 AM
Subject: Re: [PATCH 1/3] sky2: tx pause bug fix
> On Mon, 11 Sep 2006 11:35:11 +1000
> "Andrew Hall" <andrew.hall@bluereefnetworks.com> wrote:
>
>> Stephen,
>>
>> After some serious testing, this patch seems to fix the lockup issue
>> completely. I manually applied these changes against the 2.6.17.13
>> release.
>
> Any more problems?
next prev parent reply other threads:[~2006-09-22 4:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 19:44 [PATCH 1/3] sky2: tx pause bug fix Stephen Hemminger
2006-09-11 1:35 ` Andrew Hall
2006-09-19 20:31 ` Stephen Hemminger
2006-09-19 22:44 ` Andrew Hall
2006-09-22 4:11 ` Andrew Hall [this message]
2006-09-22 4:35 ` Larry Finger
2006-09-11 13:13 ` Jeff Garzik
2006-09-19 21:13 ` [PATCH] sky2: process tx pause frames Stephen Hemminger
2006-09-20 21:49 ` Jeff Garzik
2006-09-20 21:53 ` Stephen Hemminger
2006-09-13 17:28 ` [PATCH 1/3] sky2: tx pause bug fix Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 8:40 Andrew Hall
2006-09-22 17:27 ` Stephen Hemminger
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='089101c6ddfd$20ba4320$0b00000a@bluereef.local' \
--to=andrew.hall@bluereefnetworks.com \
--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).