From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: netxen: box stuck in netxen_napi_disable()
Date: Thu, 22 Jan 2015 09:37:01 +0100 [thread overview]
Message-ID: <1421915821.5286.71.camel@marge.simpson.net> (raw)
In-Reply-To: <1421909520.3471.2.camel@edumazet-glaptop2.roam.corp.google.com>
On Wed, 2015-01-21 at 22:52 -0800, Eric Dumazet wrote:
> On Thu, 2015-01-22 at 07:15 +0100, Mike Galbraith wrote:
> > On Wed, 2015-01-21 at 21:57 -0800, Eric Dumazet wrote:
> >
> > > This driver doesn't follow the NAPI model correctly.
> > >
> > > Please try following fix :
> >
> > Thanks Eric, I'll plug it in in a bit and poke at it. No news is good
> > news, as good as news gets for unknown repeatability bugs that is ;-)
>
> To trigger the bug, all you had to do was to stress the transmit side.
Nope, it's easier than that...
> You could reduce MAX_STATUS_HANDLE from 64 to 4 to trigger it even
> faster.
Wow, that made it amazingly easy to verify.
With MAX_STATUS_HANDLE=4, without your patch applied box hangs as soon
as I bring the network up. Add your patch on top, all is peachy. Fresh
boot, or rmmod/modprobe and network restart, doesn't matter, box works
with your patch, is dead without it.
Here's an ornament for the fix if you think it'll look prettier :)
Reported-and-tested-by: Mike Galbraith <umgwanakikbuti@gmail.com>
-Mike
next prev parent reply other threads:[~2015-01-22 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 4:43 netxen: box stuck in netxen_napi_disable() Mike Galbraith
2015-01-22 5:57 ` Eric Dumazet
2015-01-22 6:15 ` Mike Galbraith
2015-01-22 6:52 ` Eric Dumazet
2015-01-22 8:37 ` Mike Galbraith [this message]
2015-01-22 15:56 ` [PATCH net] netxen: fix netxen_nic_poll() logic Eric Dumazet
2015-01-23 10:59 ` Manish Chopra
2015-01-25 8:22 ` David Miller
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=1421915821.5286.71.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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