Bug 114401
Summary: | smp kernel panics early in boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steven Pritchard <steve> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | 64bit_fedora, mrsam, sahil.verma |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-03-23 08:38:50 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: |
Description
Steven Pritchard
2004-01-27 18:35:46 UTC
At what point in the boot does this happen? Any chance of getting a serial console soon? I hope to get to it soon. I'm working on the box, trying to resolve other showstoppers first. The kernel panics right after initializing CPU 1 on this Dual Opteron. The call trace in the panic includes some symbol information, without the benefit of ksymoops. The panic occurs in: set_cpu_allowed+411. The next entries in the call trace are: free_uid+2, ksoftirq+77, child_rip+8, ksoftirq+0, child_rip+0 Code: 8b 4b 3c 48 69 c9 ... Still working on a serial console, to capture the whole thing, hopefully the above may be helpful in the meantime. I have the serial console attached; however it looks like the SMP kernel does not panic consistently. I've been able to boot the SMP kernel a couple of times already, with the serial console attached. I will keep the serial console available, and update this bug when I capture a panic. After some additional testing I cannot reproduce the bug after updating to kernel build 2.4.22-1.2166.nptlsmp and flashing the motherboard to the latest OEM BIOS. There does appear to be a residual problem with the aic79xx.o module (I can crash it fairly reliably), but that's going to be a different bug. This bug can be closed. |