Red Hat Bugzilla – Bug 171357
Kernel panic on boot
Last modified: 2015-01-04 17:22:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
Dell Inspiron 5150 laptop with today's kernel update panics on boot. I should note that a similar error occurred with the 526 kernel as well, but did not have a chance to copy the panic error msg. I used a digital camera to collect the panic messages today and copied these over to text. The output follows. All services were [OK] except the nifd, for which there is no output status.
Starting system logger
Starting kernel logger
Starting NFS statd
Starting RPC idmapd
Starting Bluetooth services
Mounting other filesystems
Starting nifd [No Status output]
Starting acpi daemon
Starting cups: Kernel panic - not syncing: arch/i386/kernel/semaphore.c:102: spin_is_locked on uninitialized spinlock f7c4b8a0.
If you require further information on the above or more information on my hardware, let me know.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the system with today's kernel
Actual Results: Kernel panic as above
Expected Results: Successful boot
Seeing something very similar with an Inspiron 5160 and 2.6.13-1.1532, happy to
provide additional info, tests, etc.
2.6.14-1.1633_FC4smp (from updates-testing) appears to be working fine on my
Inspiron 5160 with none of the problems I saw in 2.6.13-xxxx.
Bingo! Indeed, a successful boot with 2.6.14-1.1633_FC4 (non-SMP).
Thanks for the heads up Brian!
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Dave, as per my comment #3 above, this bug was resolved with the .14 testing
kernels and continues to be fine with today's stable release. So we can put this
one to bed.
BTW, on an slightly related note, is there a timeframe for the /proc/i8k fix
that we discussed on the FC Test list? This is far from critical and there are
of course, workarounds for the time being.
Thanks for your time on this!
Dave, my results are the same as Marcs, .14 has been working great and so far no
problems with today's 1637 (smp).
ok, will close.
Marc, the i8k thing I thought I had fixed already in the current update.
I'll double check, and if I've missed anything, I'll drop it into the next update.