netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maksim Lin <maks@manichord.com>
To: netdev@vger.kernel.org
Subject: Re: i217-LM boot wreckage
Date: Tue, 25 Mar 2014 13:41:37 +1100	[thread overview]
Message-ID: <CA+ZDVGN5g3frxBoG1PLU4ZUEXGcTFOqMfgFrHWLCAiXBy3AXbA@mail.gmail.com> (raw)

On Fri, 21 Mar 2014, Ertman, DavidX M wrote:

> I have discovered the cause of this issue.  It is related to the
> change in the application of a Si errata workaround.
>
> I will be working on grok'ing the total impact of this issue and
> writing up the patch over the weekend and will have something pushed
> into our internal queue early next week.

Hi,

Not sure if its helpful to have another report, but I'm pretty sure I
am seeing the same thing on my Dell Latitude 7440 running 3.14.0-rc7
but with a slightly different card:

$ ethtool -i eth0
driver: e1000e
version: 2.3.2-k
firmware-version: 0.6-3
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes

and from lspci -v:

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection
I218-LM (rev 04)
    Subsystem: Dell Device 05cb
    Flags: bus master, fast devsel, latency 0, IRQ 59
    Memory at f7e00000 (32-bit, non-prefetchable) [size=128K]
    Memory at f7e3c000 (32-bit, non-prefetchable) [size=4K]
    I/O ports at f080 [size=32]
    Capabilities: <access denied>
    Kernel driver in use: e1000e
    Kernel modules: e1000e

I can try testing patches if it helps too.

thanks,
Maks.

             reply	other threads:[~2014-03-25  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  2:41 Maksim Lin [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=CA+ZDVGN5g3frxBoG1PLU4ZUEXGcTFOqMfgFrHWLCAiXBy3AXbA@mail.gmail.com \
    --to=maks@manichord.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).