Red Hat Bugzilla – Bug 197763
Last modified: 2015-01-04 17:27:44 EST
Description of problem:
insmod: error inserting '/lib/jbd.ko': -1 Operation not permitted
insmod: error inserting '/lib/ext3.ko': -1 Unknown Symbol in module
Version-Release number of selected component (if applicable):2.6.17-1.2145_FC5
Steps to Reproduce:
1. Install the new kernel rpm
2. reboot system
Actual results: kernel panic
Expected results:boot into system
*** Bug 197762 has been marked as a duplicate of this bug. ***
why on *earth* is it looking in /lib for the modules ?!
What did you use to install this kernel ?
yum -y upgrade kernel-xxxx
Is this right??
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.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen