From: David Miller <davem@davemloft.net>
To: andy@greyhouse.net
Cc: mchan@broadcom.com, netdev@vger.kernel.org, benli@broadcom.com
Subject: Re: [PATCH net-next 1/6] [BNX2]: Allow phy reset to be skipped during chip reset.
Date: Fri, 16 May 2008 22:17:52 -0700 (PDT) [thread overview]
Message-ID: <20080516.221752.201026485.davem@davemloft.net> (raw)
In-Reply-To: <20080516213430.GC20212@gospo.usersys.redhat.com>
From: Andy Gospodarek <andy@greyhouse.net>
Date: Fri, 16 May 2008 17:34:30 -0400
> On Fri, May 16, 2008 at 02:29:36PM -0700, Michael Chan wrote:
> > [BNX2]: Allow phy reset to be skipped during chip reset.
> >
> > Andy Gospodarek <andy@greyhouse.net> found that netconsole would
> > panic when resetting bnx2 devices.
> >
> > >From Andy:
> > "The issue is the bnx2_set_link in bnx2_init_nic will print a link-status
> > message before we are fully initialized and ready to start polling.
> > Polling is currently disabled in this state, but since the
> > __LINK_STATE_RX_SCHED is overloaded to not only try and disable polling
> > but also to make the system aware there is something waiting to be
> > polled, we really have to fix this in drivers.
> >
> > The problematic call is the one to netif_rx_complete as it tries to
> > remove an entry from the poll_list when there isn't one."
> >
> > While this netconsole problem should be fixed separately, we really
> > should not reset the PHY when changing ring sizes, MTU, or other
> > similar settings. The PHY reset causes several seconds of unnecessary
> > link disruptions.
> >
> > Signed-off-by: Michael Chan <mchan@broadcom.com>
> > Cc: Andy Gospodarek <andy@greyhouse.net>
>
> Acked-by: Andy Gospodarek <andy@greyhouse.net>
Applied, thanks everyone.
prev parent reply other threads:[~2008-05-17 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 21:29 [PATCH net-next 1/6] [BNX2]: Allow phy reset to be skipped during chip reset Michael Chan
2008-05-16 21:34 ` Andy Gospodarek
2008-05-17 5:17 ` David Miller [this message]
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=20080516.221752.201026485.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=benli@broadcom.com \
--cc=mchan@broadcom.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;
as well as URLs for NNTP newsgroup(s).