From: Matthias Hentges <oe@hentges.net>
To: shogunx <shogunx@sleekfreak.ath.cx>
Cc: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
Stephen Hemminger <shemminger@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sky2 hangs on me again: This time 200 kb/s IPv4 traffic, not easily reproducable
Date: Sun, 03 Sep 2006 01:27:20 +0200 [thread overview]
Message-ID: <1157239640.18988.10.camel@mhcln03> (raw)
In-Reply-To: <Pine.LNX.4.44.0609021908320.28542-100000@sleekfreak.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Am Samstag, den 02.09.2006, 19:11 -0400 schrieb shogunx:
> On Sat, 2 Sep 2006, Matthias Hentges wrote:
> > Well, it just crapped out on me again :(
> >
> > Sep 2 23:36:13 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed
> > out
> > Sep 2 23:36:13 localhost kernel: sky2 hardware hung? flushing
> >
> > Only a rmmod / modprobe cycle helps at this point.
>
> Really? What is the error condition causing it? On my friends lap, which
> has an integrated sky2, his drops out with a full sustained TX...
> uploading to another box for example, at about 4-8MB of transfer. The
> fix in his case is ifdown eth0 && ifup eth0. I have
> yet to see the error occur at all on my ExpressCard device, either with
> 2.6.18-rc5 or 2.6.17.5. I built the rc5 as a preemptive measure, but I
> cannot get it to fail under any conditions.
>
I have yet to find a reproduceable way to trigger the bug but I'll try a
few things tomorrow.
Currently it appears to be completely ranom. I've loaded the driver w/
debug=10, maybe it'll give some clues.
--
Matthias 'CoreDump' Hentges
Webmaster of hentges.net and OpenZaurus developer.
You can reach me in #openzaurus on Freenode.
My OS: Debian SID. Geek by Nature, Linux by Choice
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-02 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 18:41 sky2 hangs on me again: This time 200 kb/s IPv4 traffic, not easily reproducable Thomas Glanzmann
2006-09-02 0:53 ` Matthias Hentges
2006-09-02 0:57 ` shogunx
2006-09-02 1:28 ` Matthias Hentges
2006-09-02 2:41 ` shogunx
2006-09-02 17:25 ` Matthias Hentges
2006-09-02 17:49 ` Stephen Hemminger
2006-09-02 19:41 ` shogunx
2006-09-02 21:42 ` Matthias Hentges
2006-09-02 23:11 ` shogunx
2006-09-02 23:27 ` Matthias Hentges [this message]
2006-09-02 23:49 ` shogunx
2006-09-02 23:55 ` shogunx
2006-09-03 13:55 ` Denis Vlasenko
2006-09-03 18:21 ` shogunx
2006-09-04 17:24 ` shogunx
2006-09-04 23:34 ` Matthias Hentges
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=1157239640.18988.10.camel@mhcln03 \
--to=oe@hentges.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=shogunx@sleekfreak.ath.cx \
--cc=sithglan@stud.uni-erlangen.de \
/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