From: Doug Chapman <doug.chapman@hp.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
herbert@gondor.apana.org.au, doug.chapman@hp.com
Subject: Re: REGRESSION: panic on e1000 driver
Date: Wed, 30 May 2007 19:31:31 -0400 [thread overview]
Message-ID: <1180567891.23536.1.camel@athlon> (raw)
In-Reply-To: <465E0149.6030307@intel.com>
On Wed, 2007-05-30 at 15:57 -0700, Kok, Auke wrote:
> Doug Chapman wrote:
> > All,
> >
> > I reported this a few weeks ago and it was fixed but it appears the
> > offending code was again re-submitted. This causes a panic on HP
> > Integrity servers and from what I hear many other platforms using e1000
> > as well.
> >
> > My original report was via kernel.org BZ:
> > http://bugzilla.kernel.org/show_bug.cgi?id=8455
> >
> > I am seeing the same panic with a kernel built from today's git pull.
> >
> >
> > It was fixed by this commit:
> > 3e1657c8ef53e1cd541cc1e420f3230dc075949b
> >
> >
> > but once again broken just yesterday by the following commit. I have
> > backed just this commit out and verified I no longer panic.
> >
> >
> > commit 47313054352b879a2bc65379d55b05f48a0af7ec
> > Author: Herbert Xu <herbert@gondor.apana.org.au>
> > Date: Tue May 29 15:07:31 2007 -0700
> >
> > e1000: restore netif_poll_enable call but make sure IRQs are off
>
> Hmm, we're making a mess of it.
>
> Herbert, wouldn't it just have been a lot easier to do just add a
> netif_poll_disable in e1000_probe, so that any and all other poll
> enable/disables are symmetric ? Something like this?
>
> Auke
>
>
> PS: apologies for the whitespace damage... it's a cut'n'paste
> ---
>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
>
> diff --git a/drivers/net/e1000/e1000_main.c b/drivers/net/e1000/e1000_main.c
> index 49be393..a8a3c5f 100644
> --- a/drivers/net/e1000/e1000_main.c
> +++ b/drivers/net/e1000/e1000_main.c
> @@ -1149,6 +1149,7 @@ e1000_probe(struct pci_dev *pdev,
> /* tell the stack to leave us alone until e1000_open() is called */
> netif_carrier_off(netdev);
> netif_stop_queue(netdev);
> + netif_poll_disable(netdev);
>
> DPRINTK(PROBE, INFO, "Intel(R) PRO/1000 Network Connection\n");
Auke,
I tested this and it does indeed fix the panic on my systems. I will
leave the decision as to if it is the "right" thing to do to those who
are more knowledgeable with the code.
- Doug
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-30 23:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 21:22 REGRESSION: panic on e1000 driver Doug Chapman
2007-05-30 22:57 ` Kok, Auke
2007-05-30 23:31 ` Doug Chapman [this message]
2007-05-31 0:51 ` Herbert Xu
2007-05-31 4:51 ` Kok, Auke
2007-05-31 5:06 ` Herbert Xu
2007-05-31 14:54 ` Kok, Auke
2007-05-31 21:49 ` Herbert Xu
2007-05-31 22:11 ` Kok, Auke
2007-05-31 1:08 ` Herbert Xu
2007-05-31 15:16 ` Doug Chapman
2007-05-31 15:23 ` [E1000-devel] " Kok, Auke
2007-05-31 21:48 ` Herbert Xu
2007-05-31 22:10 ` Kok, Auke
2007-05-31 22:10 ` Herbert Xu
2007-05-31 22:38 ` Doug Chapman
2007-06-01 0:34 ` Herbert Xu
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=1180567891.23536.1.camel@athlon \
--to=doug.chapman@hp.com \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=herbert@gondor.apana.org.au \
--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).