Bug 191257 - Kernel panic upon boot with kernel 2.6.16-1.2113_FC5
Kernel panic upon boot with kernel 2.6.16-1.2113_FC5
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-05-10 03:25 EDT by Marcus Specht
Modified: 2008-02-05 08:35 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-05 08:35:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marcus Specht 2006-05-10 03:25:03 EDT
Description of problem:
i get this error message while booting:

Uncompressing Linux...  OK, booting the kernel.
Red Hat nash version 5.0.32
  Reading all physical volumes. This may take a while...
  Found group volume "VolGroup00" using metadata type lvm2
  2 logical volumes(s) in volume group "VolGroup00" now active
mount: error mounting /dev/root on /sysroot as ext3,user_xattr: No such
setuproot: moving /dev failed: No such file or directory
setuproot: moving /proc: No such file or directory
setuproot: moving /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempt to kill init

Version-Release number of selected component (if applicable):
kernel 2.6.16-1.2113_FC5

How reproducible:

Steps to Reproduce:
Actual results:
kernel panic

Expected results:
boot normally

Additional info:
Hardware is a laptop fujitsu siemens lifebook S6120
Comment 1 Thomas Maier 2006-05-13 03:53:13 EDT
Same here.
Last working version was 2.6.16-1.2098_FC5.
Comment 2 Dave Jones 2006-10-16 17:39:57 EDT
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.
Comment 3 Dave Jones 2006-11-24 17:11:37 EST
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug after installing all the
current updates, please reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

Thank you.
Comment 4 Jon Stanley 2008-02-05 08:35:08 EST
Closing since there was an error in previous mass-close and they remained in

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