Red Hat Bugzilla – Bug 869341
NULL pointer dereference at irq_move_cleanup_interrupt during boot
Last modified: 2014-09-13 15:00:20 EDT
Created attachment 632172 [details]
Photograph of the kernel panic message
Description of problem:
We have a lab of 50 Dell Optiplex 9010 SFF PCs running Fedora 17 and all updated to kernel 3.6.2. On any one day when they are all switched on, about 5-10 of the machines will either get stuck on the Plymouth boot screen or display a kernel panic message at approximately 16-17 seconds from boot.
Since this seems to happen at a network interrupt, it may be relevant that we have uninstalled NetworkManager and are using the SYSV "network" service. The crash happens at about the time the system starts up that service.
Version-Release number of selected component (if applicable):
about 1 in every 10 boots
Steps to Reproduce:
1. Turn the machine on
Created attachment 632173 [details]
Hand-transcription of the kernel panic message (apols for any typos)
This looks relevant:
It's blowing up at exactly the line
in arch/x86/kernel/apic/io_apic.c (line 2266).
(Author of the above post says this was "raised a while back" - that seems to mean in May 2012. There was a dispute as to whether the check should go before or after the lock is taken.)
Experienced this crash during boot on my new dell laptop with Fedora-17+updates-testing running kernel 3.6.3-1.fc17.x86_64.
Photo of crash log is attached.
Created attachment 634071 [details]
Another photograph of crash-log
Created attachment 634072 [details]
Another photograph of crash-log
This happens on a Dell Precision M4600, too.
*** Bug 872216 has been marked as a duplicate of this bug. ***
Has been fixed in kernel-3.6.6-3
We've had reports of this not being fixed with 3.6.6-3. Reopening.
*** Bug 875722 has been marked as a duplicate of this bug. ***
Could people seeing this issue please boot this kernel when it completes building and let me know if the issue seems to be resolved:
I have tried to reproduce it with kernel-3.6.6-4.fc18, no errors occured (on a machine that previously ran into the trace on every boot). Re-booted ~10 cycles without a problem.
Tried the same with kernel-3.6.6-1.fc17. The problem still seems to exist here.
I am going to re-check it with your updated build.
Also verified with the 4679582 build. Tested about 15 cycles without any problem.
Will this fix be released for f17?
(In reply to comment #14)
> Will this fix be released for f17?
Yes. A patch went into the fedora git tree yesterday.
kernel-3.6.6-9.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.6.6-9.fc18'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
kernel-3.6.7-1.fc18 has been submitted as an update for Fedora 18.
kernel-3.6.7-2.fc16 has been submitted as an update for Fedora 16.
kernel-3.6.7-2.fc17 has been submitted as an update for Fedora 17.
kernel-3.6.7-5.fc18 has been submitted as an update for Fedora 18.
kernel-3.6.7-4.fc17 has been submitted as an update for Fedora 17.
kernel-3.6.7-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.6.7-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 879414 has been marked as a duplicate of this bug. ***
kernel-3.6.7-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.6.8-2.fc17 has been submitted as an update for Fedora 17.
*** Bug 880384 has been marked as a duplicate of this bug. ***
kernel-3.6.8-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.