netdev - RE: [E1000-devel] i217-LM boot wreckage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2B0E3F215D1AB84DA946C8BEE234CCC9370D01E4@ORSMSX101.amr.corp.intel.com>
Date:	Wed, 26 Mar 2014 17:42:42 +0000
From:	"Ertman, DavidX M" <davidx.m.ertman@...el.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	"Ronciak, John" <john.ronciak@...el.com>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [E1000-devel] i217-LM boot wreckage

Just an update.  A patch for this issue was submitted into our internal queue on Monday and is in review/testing.

Dave Ertman

-----Original Message-----
From: Thomas Gleixner [mailto:tglx@...utronix.de] 
Sent: Friday, March 21, 2014 3:01 PM
To: Ertman, DavidX M
Cc: Ronciak, John; e1000-devel@...ts.sourceforge.net; netdev@...r.kernel.org
Subject: RE: [E1000-devel] i217-LM boot wreckage

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.

Take your time and don't spoil your weekend!

It's not a show stopper, as we know how to work around the issue.

If you need testing of some early patch or help with gathering information, let me know. We have 4 reproducer systems handy.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html