From Bugzilla Helper:
User-Agent: Opera/8.51 (X11; Linux i686; U; en)
Description of problem:
During boot up both 2.6.15 (1830 and 1831) kernels hang at hardware
initialisation after the audio entry. (The audio entry is displayed)
There is no keyboard interrupt.
Version-Release number of selected component (if applicable):
kernel-2.6.15-1.1830, -1.1830smp , -1.1831, -1.1831smp_FC4
Steps to Reproduce:
1. boot into a 2.6.15 fc4 kernel
Actual Results: No keyboard interrupt - nothing
You have to reset you PC with the reset switch
Expected Results: Smooth boot
Maybe it is related to a (not yet known) hardware-bug in my MSI 865PE NEO3 Board
(/w P4 2.8 HT), because the poweroff bug was never resolved for my system (I
have to switch off the pc manually)
I've read # 179968
so I left my PC on during one night to see if the machine boots up finally, but
*** Bug 180460 has been marked as a duplicate of this bug. ***
*** Bug 180459 has been marked as a duplicate of this bug. ***
*** Bug 180458 has been marked as a duplicate of this bug. ***
*** Bug 180457 has been marked as a duplicate of this bug. ***
*** Bug 180456 has been marked as a duplicate of this bug. ***
*** Bug 180455 has been marked as a duplicate of this bug. ***
*** Bug 180454 has been marked as a duplicate of this bug. ***
*** Bug 180453 has been marked as a duplicate of this bug. ***
Created attachment 124362 [details]
the dmesg output in my 2.6.14-1.1656_FC4
mavbe it is useful ...
Well, I resolved it for me. It seems that the harware init has some trouble with
my Microsoft USB Keyboard. After plugging the keyboard into the keyboard and
mouse PS/2 ports now the kernel boots smoothly.
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
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.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.