Bug 80730
Summary: | SMP-kernel Oops, UP works fine | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Magnus Johansson <l_magnus_j> | ||||
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 9 | CC: | john, peterm | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-02-21 18:50:47 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 79578 | ||||||
Attachments: |
|
Description
Magnus Johansson
2002-12-30 15:52:22 UTC
does this get fixed if you use "acpi=off" ? Yes, the SMP-kernel now boots up fine. For a beta-release we're now OK, this issue can be closed. Please attach the output of 'dmidecode' from the kernel-utils package on your system. Created attachment 89028 [details]
Output from dmidecode as requested
I ran successfully a test with Memtest86 3.0 on the hardware. I should also mention that this test-machine has also successfully run Solaris 8 and FreeBSD 4.7 UP. The reason that I mention this is that I get both SMP and UP kernel oops (with acpi=off, obviously) when I have httpd started during boot-up, which was a big surprise. If I start httpd from a Gnome-terminal, the kernel doesn't Oops, but httpd goes into infinite 99.9% CPU consumption. Unfortunately it is difficult to get good Oops messages for this. Sometimes the screen just goes black, sometimes the messages are reported very fast in an infinite loop. Should this be reported as a separate error? *** This bug has been marked as a duplicate of 82123 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |