From: "Cef (LKML)" <cef-lkml@optusnet.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: ifplugd/e1000 oops
Date: Mon, 19 Apr 2004 15:32:00 +1000
User-Agent: KMail/1.6.2
References: <20040419050001.GE4288@evdebs.org>
In-Reply-To: <20040419050001.GE4288@evdebs.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200404191532.01938.cef-lkml@optusnet.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1253
Lines: 27

On Mon, 19 Apr 2004 03:00 pm, Adam Goode wrote:

> I'm using ifplugd to monitor the link beat and automatically bring up
> or down the network interfaces on my laptop.
>
> When I unplugged my cable today, I got an oops. When I plugged it back
> in, nothing happened. (Normally it should beep and bring the interface
> back up.) When I removed and inserted the e1000 module, I got a freeze.

I've got a report of a similar oops, also using ifplugd. User in question (on 
IRC) is complaining that this has been happening for all of 2.6, in late 2.5 
(hasn't pinpointed any specific version) and in 2.4 since about 2.4.23.

Unfortunately in his case, it dies processing interrupts, so he gets nothing 
on disk, and is reluctant to set up a serial console on his box. I've tried 
emulating it here, but as yet have had no luck in getting it to oops.

Note: He's using an Intel EEPro/100B in his box, though he has a spare 
(unused) Realtek 8029 in there as well.

BTW: Kernel & ifplugd versions might be useful.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/