From: Dave Jones <davej@redhat.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: jeff@garzik.org, e1000-devel@lists.sourceforge.net,
Herbert Xu <herbert.xu@redhat.com>,
greg@suse.de, stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] e1000: Don't enable polling in open() (was: e1000: assertion hit in e1000_clean(), kernel 2.6.21.1)
Date: Mon, 21 May 2007 21:22:27 -0400 [thread overview]
Message-ID: <20070522012227.GD11401@redhat.com> (raw)
In-Reply-To: <46524033.4030901@intel.com>
On Mon, May 21, 2007 at 05:58:27PM -0700, Kok, Auke wrote:
> >> This probably doesn't solve the latter bug.
> >> The code you reference isn't there in the kernel tested in that bug
> >> (2.6.21) In 2.6.21, netif_poll_enable is only called from
> >> e1000_up(), not e1000_open()
> >
> > Yes we need a different fix for 2.6.21. There e1000_open calls
> > e1000_up which is why we still get the netif_poll_enable.
>
> yes, basically they need the patch that introduced(exposed) the problem as well,
> but that is a rather significant change and kind of moves the whole
> netstack-init code in e1000 around. The size was the reason why that patch
> didn't go into 2.6.21 in the first place, but perhaps they can pull both patches
> into the FC tree.
>
> For reference, this is the commit:
>
> commit e0aac5a289b1dacbc94bd9ae8c449bcdf9ab508c
> Author: Auke Kok <auke-jan.h.kok@intel.com>
> Date: Tue Mar 6 08:57:21 2007 -0800
>
> e1000: FIX: be ready for incoming irq at pci_request_irq
>
> DEBUG_SHIRQ code exposed that e1000 was not ready for incoming interrupts
> after having called pci_request_irq. This obviously requires us to finish
> our software setup which assigns the irq handler before we request the
> irq.
>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>
> Dave, would that be an option for you?
Sounds like a plan. I'll do a test-build with this and the other
patch, and throw it at the people seeing the problem tomorrow.
Thanks,
Dave
--
http://www.codemonkey.org.uk
-------------------------------------------------------------------------
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-22 1:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 21:51 [PATCH] e1000: Don't enable polling in open() (was: e1000: assertion hit in e1000_clean(), kernel 2.6.21.1) Auke Kok
2007-05-21 22:16 ` Dave Jones
2007-05-22 0:49 ` Herbert Xu
2007-05-22 0:58 ` Kok, Auke
2007-05-22 1:22 ` Dave Jones [this message]
2007-05-21 23:42 ` Jeff Garzik
2007-05-22 0:04 ` Kok, Auke
2007-05-22 1:01 ` Herbert Xu
2007-05-22 16:56 ` Chuck Ebbert
2007-05-22 17:02 ` Kok, Auke
2007-05-23 10:47 ` Herbert Xu
2007-05-23 23:34 ` Chris Wright
2007-05-23 23:38 ` Kok, Auke
2007-05-24 1:29 ` Herbert Xu
2007-05-24 4:31 ` Chris Wright
2007-05-24 1:29 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2007-05-21 15:32 Auke Kok
2007-05-21 21:26 ` 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=20070522012227.GD11401@redhat.com \
--to=davej@redhat.com \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greg@suse.de \
--cc=herbert.xu@redhat.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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).