From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
"David S. Miller" <davem@davemloft.net>
Subject: Re: 2.6.23-rc4-mm1: e1000e napi lockup
Date: Sun, 09 Sep 2007 23:31:47 -0700 [thread overview]
Message-ID: <46E4E4D3.7040905@intel.com> (raw)
In-Reply-To: <46E4E305.6010406@gmail.com>
Jiri Slaby wrote:
> Kok, Auke napsal(a):
>> Jiri Slaby wrote:
>>> I still have problems with the driver. When I do `ip link set eth0
>>> up', ksoftirq
>>> runs with 100 % cpu time, so I think you endlessly re-schedule some
>>> timer (or
>>> the new napi layer?)
>> something changed in the logic and e1000e apparently does something
>> wrong. I'll look into it on monday and resubmit a fixup patch (see
>> robert olsson's mail as well discussing this issue)
>
> he's posted me a patch, but no change on my side :(.
that's what I feared/thought as well when I saw his patch - e1000e and e1000 are
slightly different so the exit condition will be as well.
> Anyway, I'm going away of the box on monday (today). will be back on fri to
> test patches :).
I'll be on top of it. Since e1000e will be merged I need to get this workign
properly before the merge window opens - no pressure :)
Auke
prev parent reply other threads:[~2007-09-10 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 7:19 2.6.23-rc4-mm1: e1000e napi lockup Jiri Slaby
2007-09-07 8:03 ` David Miller
2007-09-07 16:24 ` Kok, Auke
2007-09-07 23:31 ` Jeff Garzik
2007-09-07 23:40 ` Kok, Auke
2007-09-07 23:49 ` Jeff Garzik
2007-09-07 23:52 ` Kok, Auke
2007-09-09 9:58 ` Jiri Slaby
2007-09-09 22:50 ` Kok, Auke
2007-09-10 6:24 ` Jiri Slaby
2007-09-10 6:31 ` Kok, Auke [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=46E4E4D3.7040905@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jirislaby@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.