[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <912683.73513.qm@web39308.mail.mud.yahoo.com>
Date: Mon, 20 Dec 2010 17:20:24 -0800 (PST)
From: Brian Neu <proclivity76@...oo.com>
To: "Wyborny, Carolyn" <carolyn.wyborny@...el.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
> 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.
View attachment "lspci.txt" of type "text/plain" (37550 bytes)
Powered by blists - more mailing lists