Description of problem:
System hang at the udev line when booting up using the SMP kernel.
Version-Release number of selected component (if applicable):
All Fedora Core 5 SMP kernels.
It happens every time.
Steps to Reproduce:
1. Boot up the system with the 3ware 8506-8 card in the system.
Boot hang at the udev line. The OK never shows up.
Expected system to boot normally.
This problem only happens if I boot using the SMP kernel and the 3ware card. If
I boot with the non-SMP kernel then the system boots fine with the 3ware card.
Also if I take the 3ware card out of the system, then I can boot using the SMP
kernel. This problem didn't exist on Fedora Core 4, so I think it must have
been a recent change with the udev system since kernel 2.6.15. I have the
latest BIOS on the motherboard and the 3ware card. I also tried various kernel
boot options such as 'noapic', etc.
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.
Since I couldn't wait for this bug to be fixed, I moved my RAID card to another
machine with a different chip set. So now I can't verify if this new kernel
fixes this bug or not. Sorry.