Bug 13448 - from 2.6.28.9 to 2.6.28.10 NForce3 eth ifup -> kernel panic
Summary: from 2.6.28.9 to 2.6.28.10 NForce3 eth ifup -> kernel panic
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-04 00:57 UTC by Petr Grigoriev
Modified: 2009-06-05 19:35 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.28.10
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Petr Grigoriev 2009-06-04 00:57:00 UTC 
from 2.6.28.9 to 2.6.28.10 NForce4 eth ifup -> kernel panic
kernel is loading normally but initializing network -> kernel panic
after update kernel two servers to down remotely and not reponding on net... only locally up...
gcc-4.3.3-10 debian unstable
Comment 1 Petr Grigoriev 2009-06-04 01:54:39 UTC 
first post NForce4 error, NForce3 chipset on Athlon64
Comment 2 Petr Grigoriev 2009-06-04 02:10:11 UTC 
bug only in 2.6.28.10. 2.6.29.4 work normally
Comment 3 Petr Grigoriev 2009-06-04 02:20:32 UTC 
on Sempron 3300+ NForce3 bug is it also.
Comment 4 Andrew Morton 2009-06-05 19:35:19 UTC 
(In reply to comment #2)
> bug only in 2.6.28.10. 2.6.29.4 work normally

That doesn't make sense - please clarify?

How did this bug get into the CLOSED PATCH_ALREADY_AVAILABLE
state??
Note You need to log in before you can comment on or make changes to this bug.