public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Bäckstrand" <sandos@home.se>
To: linux-kernel@vger.kernel.org
Subject: lockups with netconsole on e1000 on media insertion
Date: Fri, 05 Aug 2005 13:04:50 +0200	[thread overview]
Message-ID: <42F347D2.7000207@home.se> (raw)

I've been trying to hunt down a hard lockup issue with some hardware of 
mine, but I've possibly hit a kernel bug instead. When using netconsole 
on my e1000, if I unplug the cable and then re-plug it, the machine 
locks up hard. It manages to print the "link up" message on the screen, 
but nothing after that. Now, I wonder if this is supposed to be so? I 
tried this on 4 different configurations, 2.6.13-rc5 and 2.6.12 with and 
without "noapic acpi=off", same result on all of them. I've tried with 1 
and 3 other NICs in the machine at the same time.

It seems to be working fine on other NICs, such as rtl8139 and 3c59x. 
Any ideas on how to debug this further? (Btw, is there an easy way of 
"inserting" dmesg messages manually?)

---
John Bäckstrand

             reply	other threads:[~2005-08-05 11:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 11:04 John Bäckstrand [this message]
     [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-07 21:12     ` John Bäckstrand
2005-08-08  2:29       ` Steven Rostedt
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

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=42F347D2.7000207@home.se \
    --to=sandos@home.se \
    --cc=linux-kernel@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