Bug 36562

Summary:	e1000 network driver causes kernel oops
Product:	Drivers	Reporter:	bryan.christ
Component:	Network	Assignee:	drivers_network (drivers_network)
Status:	RESOLVED OBSOLETE
Severity:	high	CC:	alan
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.38.6-26.rc1.fc14.x86_64	Subsystem:
Regression:	No	Bisected commit-id:

Description bryan.christ 2011-06-02 19:20:04 UTC

After running for about 12-48 hours we typically have several servers which kernel oops on the e1000

http://www.mediafire.com/imgbnc.php/e65c4a4b220096cabfa8746195898c1c5520b65cdde108921f027a309c179f6a6g.jpg

Comment 1 Andrew Morton 2011-06-02 19:32:33 UTC

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Thu, 2 Jun 2011 19:20:08 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=36562
> 
>            Summary: e1000 network driver causes kernel oops
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.38.6-26.rc1.fc14.x86_64
>           Platform: All
>         OS/Version: Linux
>               Tree: Fedora
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: bryan.christ@gmail.com
>         Regression: No
> 
> 
> After running for about 12-48 hours we typically have several servers which
> kernel oops on the e1000
> 
>
> http://www.mediafire.com/imgbnc.php/e65c4a4b220096cabfa8746195898c1c5520b65cdde108921f027a309c179f6a6g.jpg
> 

It crashed deep down in TCP.  That may not be e1000-related.

I think we still have two drivers: e1000 and e1000e.  You're using
e1000e.

Comment 2 bryan.christ 2011-06-02 19:52:57 UTC

So do I need recategorized the bug?