From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: net: skge breakage on 2.6.24-rc1
Date: Wed, 7 Nov 2007 23:50:30 +0100 [thread overview]
Message-ID: <200711072350.30645.rjw@sisk.pl> (raw)
In-Reply-To: <20071107215348.GB8865@zakalwe.fi>
On Wednesday, 7 of November 2007, Heikki Orsila wrote:
> On Wed, Nov 07, 2007 at 11:46:21PM +0200, Heikki Orsila wrote:
> > After some bisecting, I found that net skge driver broke on
> >
> > commit 7fb7ac241162dc51ec0f7644d4a97b2855213c32
> >
> > My network card is:
> >
> > 0000:00:0e.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
> >
> > Linux cheradenine 2.6.24-rc1-dirty #15 Wed Nov 7 23:39:28 EET 2007 x86_64 GNU/Linux
>
> Sorry, forgot to say what the problem is. Doing
>
> nc host port < /dev/zero
>
> on a sending machine (not skge) to an skge machine that is receiving:
>
> nc -l -p port >/dev/null
>
> with ~60 MiB/s speed, causes the interface go malfunct. A slow
> transfer doesn't cause a problem.
>
> Also, after some fiddling, I noticed that not changing the register
> write order on patch:
>
> + skge_write32(hw, RB_ADDR(q, RB_END), end);
> skge_write32(hw, RB_ADDR(q, RB_WP), start);
> skge_write32(hw, RB_ADDR(q, RB_RP), start);
> - skge_write32(hw, RB_ADDR(q, RB_END), end);
>
> fixes the visible effect.. Possibly not the root cause of the problem,
> but changing the order back fixes networking here.
Please put all of the relevant information into the bugzilla entry at
http://bugzilla.kernel.org/show_bug.cgi?id=9321
Thanks,
Rafael
next prev parent reply other threads:[~2007-11-07 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:46 net: skge breakage on 2.6.24-rc1 Heikki Orsila
2007-11-07 21:53 ` Heikki Orsila
2007-11-07 22:50 ` Rafael J. Wysocki [this message]
2007-11-07 23:06 ` Andrew Morton
2007-11-07 23:13 ` Heikki Orsila
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=200711072350.30645.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=shdl@zakalwe.fi \
/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