I have a problem with my Toshiba Satellite A100-237 laptop. With kernel out-of-box and kernel-smp-2.6.17-1.2145_FC5 things are the same. When I run kernel with default arguments, FC hang durring udev start. Then I try 'acpi=off' it work, but error appear 'PCI: Bus #08 (-#0b) is hidden behind transparent bridge #07 (-#07) (try 'pci=assign-busses')', so I run kernel with 'acpi=off pci=assign-busses', next error appear 'irq 169: nobody cared (try booting with the "irqpoll" option)' then 'acpi=off pci=assign-busses irqpoll' and kernel boot without this error but I don't have ACPI (it useful in laptop :)). In dmesgs we can see something is wrong with uhci_hcd, so lets try with just 'nousb' and booting went ok WITH ACPI. I also attach acpidecode, lspci -vvnx (all from 'nousb') and lsmod, /proc/interrupts from all cases. What's strange for me is that with 'pci=assign-busses' or 'pci=assign-busses irqpoll' my network card isn't working, as you can see in /proc/interrupts it's XT-PIC not IO-APIC, maybe this cause it? I wanted to file a bug in Linux Kernel Tracker, but "Distro bugs should not be reported here, but to the distro's own bug tracking system.".
Created attachment 132140 [details] dmesg with acpi=off
Created attachment 132141 [details] dmesg with acpi=off pci=assign-busses
Created attachment 132142 [details] dmesg with acpi=off pci=assign-busses irqpoll
Created attachment 132143 [details] dmesg with nousb
Created attachment 132144 [details] lsmod with acpi=off pci=assign-busses irqpoll
Created attachment 132145 [details] lspci -vvnx (nousb)
Created attachment 132146 [details] acpidump (nousb)
Created attachment 132147 [details] /proc/interrupts (acpi=off pci=assign-busses irqpoll)
I won't attach all this stuff (there are too many of them already), if you need something more write.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
Can't reproduce it any more.