From: "Ertman, DavidX M" <davidx.m.ertman@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "e1000-devel@lists.sourceforge.net" <e1000-devel@lists.sourceforge.net>
Subject: RE: [E1000-devel] i217-LM boot wreckage
Date: Thu, 20 Mar 2014 15:12:48 +0000 [thread overview]
Message-ID: <2B0E3F215D1AB84DA946C8BEE234CCC9370CEFE3@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403201431580.18573@ionos.tec.linutronix.de>
Hello Thomas,
Could you provide the exact kernel version and kernel config you are using?
Do you have Runtime Power Management enabled?
Have you tried the latest driver from sourceforge.net (3.0.4.1)?
>From your lspci output it looks like you have a Management Engine enabled platform. Do you know what version of ME is loaded? Have 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)?
Thanks
-----Original Message-----
From: Thomas Gleixner [mailto:tglx@linutronix.de]
Sent: Thursday, March 20, 2014 6:45 AM
To: netdev@vger.kernel.org
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] i217-LM boot wreckage
On Thu, 20 Mar 2014, Thomas Gleixner wrote:
> So it looks like the BIOS is setting something up, when the cable is
> plugged at power on time, which is not visible through our debug
> output.
Some more info:
I prevented e1000e from being autoloaded and booted with the cable unplugged.
T1:
Plug cable
modprobe e1000e -> Works
T2:
modprobe e1000e
plug cable -> Works not
rmmod e1000e
modprobe e1000e -> works not
unplug cable
rmmod e1000e
modprobe e1000e -> works
rmmod e1000e
unplug cable
modprobe e1000e
plug cable -> Works not
rmmod e1000e
unplug cable
plug cable
modprobe e1000e -> Works not
So if the module is loaded w/o the cable plugged it does not work. If I unplug before unloading the module and then plug in before loading the module again it works again.
Thanks,
tglx
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2014-03-20 15:15 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 ` Ertman, DavidX M [this message]
2014-03-20 16:37 ` [E1000-devel] " Thomas Gleixner
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=2B0E3F215D1AB84DA946C8BEE234CCC9370CEFE3@ORSMSX101.amr.corp.intel.com \
--to=davidx.m.ertman@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.