netdev - RE: [bisected regression] e1000e: "Detected Hardware Unit Hang"

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Feb 2015 23:28:27 +0000
From:	"Brown, Aaron F" <aaron.f.brown@...el.com>
To:	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	Thomas Jarosch <thomas.jarosch@...ra2net.com>
CC:	'Linux Netdev List' <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>,
	e1000-devel <e1000-devel@...ts.sourceforge.net>
Subject: RE: [bisected regression] e1000e: "Detected Hardware Unit Hang"

> From: Kirsher, Jeffrey T
> Sent: Wednesday, February 11, 2015 3:34 AM
> To: Thomas Jarosch; Brown, Aaron F
> Cc: 'Linux Netdev List'; Eric Dumazet; e1000-devel
> Subject: Re: [bisected regression] e1000e: "Detected Hardware Unit Hang"
> 
> On Wed, 2015-02-11 at 12:23 +0100, Thomas Jarosch wrote:
> > Hi Jeff,
> >
> > On Thursday, 15. January 2015 06:59:13 Jeff Kirsher wrote:
> > > > Sure, you basically reverted my patch.
> > > >
> > > > You are not the first to report a problem caused by this patch.
> > > >
> > > > This patch is known to have uncovered some driver bugs.
> > > >
> > > > We are not going to revert it. We are going to fix the real bugs.
> > > >
> > > > Thanks
> > >
> > > Agreed, we are looking into issue Thomas.
> >
> > any news from the Intel labs what might be going on here?
> >
> > We started seeing those hangs on "MSI B85M ECO" boards, too,
> > though it's way more sporadic there.
> 
> I have not heard anything, so I have added Aaron Brown to see if he has
> any additional information.

I do not have any real info.  I had been asked to try and reproduce some unit hangs (maybe for this) recently and did not succeed in producing them on the parts I have.  Reading through the thread I see this is showing up in a NAT environment.  The port that is getting the unit hang in the NAT system?

I will make some attempts at replicating this with the port in a NAT and or forwarding role.  Has a bug been opened for this?  Or has information for this specific unit hang been entered into one of the other unit hang bugs opened against e1000e?