Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230913 - kernel panic and autofs hangs
Summary: kernel panic and autofs hangs
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Brian Brock
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-04 17:48 UTC by Ed Marshall
Modified: 2008-08-02 23:40 UTC (History)
4 users (show)

Fixed In Version: Fedora 8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-04-04 12:25:32 UTC

Attachments (Terms of Use)
Kernel panic output (deleted)
2007-03-04 17:48 UTC, Ed Marshall
no flags Details

Description Ed Marshall 2007-03-04 17:48:28 UTC
Description of problem:
Kernel panic'd overnight, leaving automounts in a hung state.

Version-Release number of selected component (if applicable):

How reproducible:
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.

Additional info:
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.

Comment 1 Ed Marshall 2007-03-04 17:48:28 UTC
Created attachment 149212 [details]
Kernel panic output

Comment 2 Bug Zapper 2008-04-04 06:27:01 UTC
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
the change.

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: 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

Comment 3 Ed Marshall 2008-04-04 12:15:45 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.