From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
Description of problem:
Installed FC2 from CDs (Kernel 2.6.5-1.358). Updated system via yum.
Tried to boot new kernel, but Machine hangs forever at line:
Machine is a IPC PowerNote Green795 laptop with a AMD K6-2 500MHz,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
can you try booting with the boot parameter initcall_debug and see if that
prints out anything useful just before it hangs ?
Oh, yes, i added the initcall_debug and removed the "quiet" switch. Last some
ACPI: Processor: [CPU0] (supports C1, 8 throttling state)
isapnp: scanning for PnP Cards ...
isapnp: No Plug & Play device found
You need more lines or hardware info?
get any further if you boot with acpi=off ?
Thanks, yes this works. But is that a real option for a laptop?
I wasnt recommending running with it the whole time, just trying to find
the root cause of the problem. Intel ACPI folks CC'd. Maybe they have some ideas
where to go next.
> Updated system via yum
not really sure what kernel we're working with here,
I guess this is an FC2 kernel that is newer than 2.6.9?
Does kernel.org 2.6.9 do the same?
Please confirm that "acpi=noirq" is sufficient workaround to boot.
a complete dmesg would be helpful.
Even better, a console capture of the failure, if possible.
Len -- the FC2 kernel is at 2.6.9-ac10
Created attachment 107725 [details]
dmesg output with acpi=noirq
acpi=noirq worked. I'll try to configure grub and the kernel to use the serial
port. Then i can give you some more bootmessages.
Created attachment 107736 [details]
example script to update grub's menu.lst file
Here's the script I use to update grub's config file on my test machines.
Note that it also adds "debug" to the cmdline so that we see everything
over the wire that dmesg would see. Hack at will:-)
Created attachment 107785 [details]
Captured boot messages with acpi=on
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.