All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Ertman, DavidX M" <davidx.m.ertman@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>
Subject: RE: [E1000-devel] i217-LM boot wreckage
Date: Thu, 20 Mar 2014 17:37:56 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1403201724500.18573@ionos.tec.linutronix.de> (raw)
In-Reply-To: <2B0E3F215D1AB84DA946C8BEE234CCC9370CEFE3@ORSMSX101.amr.corp.intel.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1104 bytes --]

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

[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 29160 bytes --]

  reply	other threads:[~2014-03-20 16:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 12:58 i217-LM boot wreckage Thomas Gleixner
2014-03-20 13:45 ` Thomas Gleixner
2014-03-20 15:12   ` [E1000-devel] " Ertman, DavidX M
2014-03-20 16:37     ` Thomas Gleixner [this message]
2014-03-21 14:36       ` Thomas Gleixner
2014-03-21 14:51         ` [E1000-devel] " Thomas Gleixner
2014-03-21 15:07           ` Ronciak, John
2014-03-21 15:09             ` Ertman, DavidX M
2014-03-21 15:57               ` Thomas Gleixner
2014-03-21 21:28                 ` [E1000-devel] " Ertman, DavidX M
2014-03-21 22:01                   ` Thomas Gleixner
2014-03-26 17:42                     ` [E1000-devel] " Ertman, DavidX M
2014-03-21 15:57             ` Thomas Gleixner

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=alpine.DEB.2.02.1403201724500.18573@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=davidx.m.ertman@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --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.