Red Hat Bugzilla – Bug 241312
kernel 2.6.21-1.3189.fc7 panics starting net interface - one off
Last modified: 2008-04-03 21:26:08 EDT
Description of problem:
While booting with kernel 2.6.21-1.3189.fc7, and of course when
I was not watching closely what happens, I ended up with
a kernel panic with a screen image attached. It looks like
that bringing up a network interface stumbled.
No traces in logs after a reboot.
I was booting this kernel a number of times before and after
and this was the only incident of that sort.
I have seen that only once.
Created attachment 155415 [details]
a screen image with a kernel panic
This happens sporadically but it happens. I just got an identical
panic but starting kernel-2.6.21-1.3194.fc7 for a change.
Was this an e1000 by any chance?
> Was this an e1000 by any chance?
Attached picture says that this happened with RIP
"e100: e100_poll+0x2fb/0x346". After this long time I am not even
entirely sure on which machine this was registered although I think
that more or less I know.
In any case I did not see something of that sort for a while now
but this was not a frequent event even those five months ago.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
I do recall similar incidents on other occasions.