Bug 145875
Summary: | kernel panic at boot: spin_is_locked on uninitialized spinlock | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ville Skyttä <scop> | ||||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||||
Status: | CLOSED ERRATA | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3 | CC: | idletask, pfrields, riel, wtogami | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-07-16 15:48:57 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Ville Skyttä
2005-01-22 22:56:55 UTC
I got it too, but it happened only once until now. rhgb was enabled, and the subsequent reboot went fine. Same kernel and same CPU; so a hardware problem seems very unlikely. The box here is now fully up-to-date, running kernel-2.6.10-1.760_FC3, but has shown no sign of trouble yet -- though unfortunately, this doesn't seem to be easily reproducible. Created attachment 111240 [details]
lspci -v
This still happens with 2.6.10-1.766_FC3, but I managed to narrow it down
somewhat.
When trying to boot having a USB device (tested with a X10 receiver for a ATI
Remote Wonder remote controller and a USB keyboard) plugged into a hub that
shares IRQ with a Sigma Designs Hollywood+ MPEG decoder card, the panic at boot
happens _almost_ always. Not 100%, but I guesstimate something like 95%.
If no USB devices are plugged in, there are no problems.
Ditto, everything seems to be fine now that I've shuffled PCI cards so that the
HW+ and USB stuff never share an IRQ.
This setup with HW+ and USB sharing IRQ and USB devices plugged in has worked
with no problems noticed before; the first kernel I witnessed problems with was
2.6.10-1.741_FC3.
Will attach the output of lspci -v and lsusb -v. Additionally, the current
/proc/interrupts is:
CPU0
0: 65393843 XT-PIC timer
1: 7 XT-PIC i8042
2: 0 XT-PIC cascade
5: 4790742 XT-PIC saa7146 (0), ohci1394
8: 1 XT-PIC rtc
9: 0 XT-PIC acpi
10: 1580052 XT-PIC ide2, eth1
11: 314586 XT-PIC uhci_hcd, uhci_hcd, eth0
12: 6389228 XT-PIC EMU10K1, em8300
14: 587776 XT-PIC ide0
NMI: 0
ERR: 0
Note that this is with the "fixed" setup. The problems arose when em8300 and
uhci_hcd were sharing IRQ's.
Created attachment 111241 [details]
lsusb -v
This bug should be fixed by the RHEL4 0day errata's 4/4G split fix. Previously on 3:1 split kernels with the 4/4 split patch applied there was a bug that could leave the kernel page tables inconsistent between processes... Note that if my guess is right, the bug only hits after X has been started and quit. If the bug is hit without ever starting X, my guess is wrong ;) In that case, I'm afraid your guess is wrong :(. The panic occurred very early during boot, at the time rc.sysinit loads "other" modules. No X. And I don't have rhgb installed. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. I have moved on to FC4, and in the meantime, the possible culprit here (the out-of-tree em8300 driver) has got some changes that may have solved this problem. Anyway, I haven't seen this occur in a long time, nor on FC3 or FC4. Will close, and reopen later if I happen to run into it again. |