netdev - RE: e1000e crash with 82574L 2.6.37-0.rc5

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: <EDC0E76513226749BFBC9C3FB031318F012396E558@orsmsx508.amr.corp.intel.com>
Date:	Tue, 21 Dec 2010 10:13:47 -0800
From:	"Wyborny, Carolyn" <carolyn.wyborny@...el.com>
To:	Brian Neu <proclivity76@...oo.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: RE: e1000e crash with 82574L  2.6.37-0.rc5



>-----Original Message-----
>From: Brian Neu [mailto:proclivity76@...oo.com]
>Sent: Monday, December 20, 2010 5:20 PM
>To: Wyborny, Carolyn; netdev@...r.kernel.org
>Cc: e1000-devel@...ts.sourceforge.net
>Subject: Re: e1000e crash with 82574L 2.6.37-0.rc5
>
>> Hello,
>
>
>Thanks for responding.  I really wasn't sure where to report this.
>
>> We have some  known issues with 82574L but most have been resolved in
>the
>>latest versions, so  I'll need some more information.
>>
>> What version of e1000e are you using  exactly?  Are you able to
>download and
>>test the latest version of the  driver from SourceForge?
>
>
>This is the fedora build of kernel 2.6.37.0.rc5 which I downloaded from
>koji.fedoraproject.org.  I'm not sure which version of e1000e is
>included, but
>if I need to build a new module, just let me know.
>
>I had opened a bugzilla report with redhat which also has more
>backtraces:
> https://bugzilla.redhat.com/show_bug.cgi?id=625776
>
>> Please open an issue at SourceForge.net for easier  tracking of
>debugging
>>information.
>>
>> Please provide an output of lspci  -vvv.
>
>
>Attached.
>
>> What hw platform is this happening on?
>
>It's a Supermicro MB for AMD Socket G34
>
>> How often does it  happen and how long does it take to happen after
>reset or
>>reboot?
>
>It usually doesn't happen unless the system has been running for hours
>or days.
>
>>Is ASPM  enabled or disabled on your system.  Its possible to disable
>this in
>>the  BIOS, but not all BIOS provide the option.  If its enabled for
>some reason,
>>please disable it and try the driver  again.
>
>
>I'm going to check on this very soon and reply to the e1000 list only.

Hello Brian,

With this being a variant of Fedora, filing a Bugzilla was the right thing to do.  I missed that in your first email.

I checked your lspci output and ASPM *is* disabled as it should be.

When the adapter crashes/resets (per the log) does it come back up or stay down?

Since you're downloading off the Fedora build site, you could be encountering any number of things as these are live untested builds at this point.

Can you download a vanilla upstream build from kernel.org complete and see if the problem is happening there?  Or, you can download the latest released Fedora 14 from fedoraproject.org and see if the problem is happening with that build.  

Let me know how it goes,

Thanks,

Carolyn

Carolyn Wyborny
Linux Development
LAN Access Division
Intel Corporation

  
--
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