From: Steven Rostedt <rostedt@goodmis.org>
To: "John Bäckstrand" <sandos@home.se>
Cc: Matt Mackall <mpm@selenic.com>, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: lockups with netconsole on e1000 on media insertion
Date: Sun, 07 Aug 2005 22:29:38 -0400 [thread overview]
Message-ID: <1123468178.18332.150.camel@localhost.localdomain> (raw)
In-Reply-To: <42F6792D.4030608@home.se>
On Sun, 2005-08-07 at 23:12 +0200, John Bäckstrand wrote:
> Steven Rostedt wrote:
> > I don't have the card, so I can't test it. But if this works (after
> > removing the previous patch) then this is the better solution.
>
> I can confirm that this alone does not work for the simple
> unplug/re-plug cycle I described, it still locks up hard. Tried this
> alone on -rc6.
Darn it. If I had a e1000 I could debug it. I have other methods of
logging than printks in all there varieties (see relayfs and friends).
I still believe that the e1000_netpoll is not turning on the queue for
some reason and the netpoll_send_skb is locking up because of that.
Especially since Andi's patch fixes the problem.
In e1000_clean_tx_irq, which I added to the e1000_netpoll call, has the
following lines:
if(unlikely(cleaned && netif_queue_stopped(netdev) &&
netif_carrier_ok(netdev)))
netif_wake_queue(netdev);
The netif_queue_stopped is true, since that causes the looping in
netpoll_send_pkt. So either it didn't clean any buffers (cleaned is
false) or netif_carrier_ok is false. I don't know what the e1000 does
when you pull the cable while it's transmitting, does it call the
e1000_down? If so it could cause the carrier_ok to fail.
Oh well, someone with a e1000 card will need to look into this. The
problem should be easily found. Good luck.
-- Steve
next prev parent reply other threads:[~2005-08-08 2:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42F347D2.7000207@home.se.suse.lists.linux.kernel>
2005-08-05 11:45 ` lockups with netconsole on e1000 on media insertion Andi Kleen
2005-08-05 12:44 ` John Bäckstrand
2005-08-05 13:49 ` Steven Rostedt
2005-08-05 13:55 ` Andi Kleen
2005-08-05 14:10 ` Steven Rostedt
2005-08-05 14:14 ` Andi Kleen
2005-08-05 14:27 ` Steven Rostedt
2005-08-05 14:36 ` David S. Miller
2005-08-05 15:02 ` Steven Rostedt
2005-08-05 14:36 ` [PATCH] netpoll can lock up on low memory Steven Rostedt
2005-08-05 20:01 ` Matt Mackall
2005-08-05 20:57 ` Steven Rostedt
2005-08-05 21:28 ` Matt Mackall
2005-08-06 0:23 ` Steven Rostedt
2005-08-06 1:53 ` Matt Mackall
2005-08-06 2:32 ` Steven Rostedt
2005-08-06 7:30 ` Daniel Phillips
2005-08-06 7:58 ` Ingo Molnar
2005-08-06 23:10 ` Matt Mackall
2005-08-06 9:46 ` David S. Miller
2005-08-06 9:57 ` Steven Rostedt
2005-08-06 12:09 ` John Bäckstrand
2005-08-07 5:40 ` Matt Mackall
2005-08-05 21:26 ` Andi Kleen
2005-08-05 21:42 ` Matt Mackall
2005-08-05 21:51 ` Andi Kleen
2005-08-06 1:16 ` Matt Mackall
2005-08-06 0:30 ` Steven Rostedt
2005-08-06 7:45 ` Ingo Molnar
2005-08-06 11:29 ` Andi Kleen
2005-08-07 21:12 ` lockups with netconsole on e1000 on media insertion John Bäckstrand
2005-08-08 2:29 ` Steven Rostedt [this message]
2005-08-05 20:12 ` Matt Mackall
2005-08-05 21:56 ` Andi Kleen
2005-08-05 23:20 ` Matt Mackall
2005-08-05 23:51 ` Andi Kleen
2005-08-06 1:22 ` Matt Mackall
2005-08-06 1:37 ` Daniel Phillips
2005-08-05 11:04 John Bäckstrand
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=1123468178.18332.150.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=sandos@home.se \
/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