public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda.linux@googlemail.com>
To: shogunx <shogunx@sleekfreak.ath.cx>
Cc: Matthias Hentges <oe@hentges.net>,
	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, 3 Sep 2006 15:55:24 +0200	[thread overview]
Message-ID: <200609031555.24901.vda.linux@googlemail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0609021939100.28542-100000@sleekfreak.ath.cx>

On Sunday 03 September 2006 01:49, shogunx 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.
> 
> Ack.  Awaiting more info.  I pushed it pretty hard last night with both
> kernel revisions, scp'ing cd iso images and kernel tarballs back and forth
> across the interface, and could not get it to lock.  I am using a 88E8053
> chipset.  I'll ask my friend what chipset his is.  Perhaps its a
> different bug that is hitting you now...

scp isn't "pushing very hard". It takes some time to do ssh crypto
and even if your CPU is fast enough for that to be not an issue,
scp is using TCP, which is _designed_ to not saturate links to 100.00%.

Give it a real hard beating with uni- and bidirectional UDP netcat flood! :)
--
vda

-- 
VGER BF report: U 0.511791

  parent reply	other threads:[~2006-09-03 13:56 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
2006-09-02 23:49                   ` shogunx
2006-09-02 23:55                     ` shogunx
2006-09-03 13:55                     ` Denis Vlasenko [this message]
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=200609031555.24901.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe@hentges.net \
    --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