Subject : e1000e broke e1000
Submitter : Ingo Molnar <firstname.lastname@example.org>
Date : 2008-04-08 20:39
References : http://lkml.org/lkml/2008/4/8/256
This entry is being used for tracking a regression from 2.6.24. Please don't
close it until the problem is fixed in the mainline.
This bug is invalid, per design users have to switch to e1000e for some of the devices previously supported by e1000. This is _not_ a regression, only a migration problem.
Ingo, please reopen if you see fit.
Created attachment 15704 [details]
this patch fixes the problem for me.
a "migration problem" that resulted in a non-working networking interface and caused me more than 1 hour of debugging is a very good example of how we define regressions ...
Regressions list annotation:
Patch : http://bugzilla.kernel.org/attachment.cgi?id=15704&action=view
Confirmed to be present in 2.6.25-rc9.
References : http://lkml.org/lkml/2008/4/14/46
seems like we should still fix this?
Especially after commit d03157babed7424f5391af43200593768ce69c9a the only reasonable action seems to be a resolution as WILL_NOT_FIX.
this bug can be closed, the patch suggested won't even work any more because the device ID's were all moved over to e1000e.