Bug 179998 - Every Kernel since 1884 broken
Summary: Every Kernel since 1884 broken
Status: CLOSED DUPLICATE of bug 179743
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-04 13:27 UTC by Partha Bagchi
Modified: 2015-01-04 22:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-10 02:46:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Partha Bagchi 2006-02-04 13:27:35 UTC
Description of problem:

Version-Release number of selected component (if applicable): 2.6.15-1.1907_FC5

How reproducible:

Steps to Reproduce:
1.boot with the new kernel
Actual results: Kernel panic

Expected results: Normal boot

Additional info: Unfortunately, I am unable to capture any information since the
kernel panics as soon as it boots. There is nothing in the log to report as it
does not get to that part at all. I do think I see some child processes related
to acpi and something to do with mutex. 

Please let me know what kind of information you want me to provide.

My hardware AMD Turion 64 ML-37 (2.0 GHz)
128 ATI XPRESS 200M w/Hypermemory 
1 GBram

Comment 1 Partha Bagchi 2006-02-09 00:19:05 UTC
I have update to the following kernel 2.6.15-1.1914_FC5. As before, I get kernel
panick with child process related to acpi. So, I rebooted with acpi=off. This
booted fine.

So, the problem seems to be acpi. Note that 2.6.15-1.1884_FC5 boots just fine
without have to use acpi=off as a kernel option.

Is there anyone else having this issue?

Comment 2 Dave Jones 2006-02-10 02:46:50 UTC

*** This bug has been marked as a duplicate of 179743 ***

Note You need to log in before you can comment on or make changes to this bug.