[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1403201724500.18573@ionos.tec.linutronix.de>
Date: Thu, 20 Mar 2014 17:37:56 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Ertman, DavidX M" <davidx.m.ertman@...el.com>
cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>
Subject: RE: [E1000-devel] i217-LM boot wreckage
On Thu, 20 Mar 2014, Ertman, DavidX M wrote:
> Hello Thomas,
>
> Could you provide the exact kernel version and kernel config you are using?
3.14-rc7. config attached
> Do you have Runtime Power Management enabled?
According to .config yes
> Have you tried the latest driver from sourceforge.net (3.0.4.1)?
Nope, why should I?
> From your lspci output it looks like you have a Management Engine
> enabled platform. Do you know what version of ME is loaded? Have
9.0.2.1345
Disabling ME in the BIOS does not help.
> you checked to see that you are on the latest BIOS/NVM image (looks
> like a new one was released on March 11th for the M93z)?
Yep. Latest BIOS does not help either.
100% reproducible. I just follow the steps below:
1 plug cable
2 modprobe e1000e -> Works
3 rmmod e1000e
4 unplug cable
5 modprobe e1000e
6 plug cable -> Works not
7 rmmod e1000e
8 modprobe e1000e -> Works not
9 unplug cable <- This makes the difference unplug while module loaded!
10 rmmod e1000e
11 plug cable
12 modprobe e1000e -> Works
Fun, isn't it?
Thanks,
tglx
Download attachment "cfg.xz" of type "APPLICATION/octet-stream" (29160 bytes)
Powered by blists - more mailing lists