Red Hat Bugzilla – Bug 230913
kernel panic and autofs hangs
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
Kernel panic'd overnight, leaving automounts in a hung state.
Version-Release number of selected component (if applicable):
Not at all; this happened randomly in the middle of the night. autofs appeared
to be hung afterward, as the system couldn't shut down without a hard reset, and
all mounts were hanging.
We've had occasional freezing with this machine since moving to autofs-mounted
home directories. This is the first time we've had a panic reported. I've
attached the relevant snippet of /var/log/messages.
Created attachment 149212 [details]
Kernel panic output
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
The problem appears to have been resolved since moving from Fedora 6 to 8. (We
were on 7 only long enough to complete the upgrade to 8, so I can't say whether
a change in 7 resolved it. If anyone is curious, the server tracked Fedora
releases pretty closely, and so was running 7 and 8 shortly after their release.)
Our interim resolution to the problem, which wouldn't be acceptable to most, was
a nightly automated reboot of the problematic machine, which headed off the
issue most of the time. Since moving to 8, we've found it unnecessary to do so.