Red Hat Bugzilla – Bug 374381
kernel crash during fedora 8 upgrade on hp nx6125
Last modified: 2008-06-18 18:36:15 EDT
Description of problem:
after some google search i found out how to get through the dependencies
resolution after 26% (remove dbus, expat and avahi) i able to ugrade 3
of my workstations to f8. the problem comes when i try to upgrade my hp
nx6125 laptop which has exactly the same packages installed as my
workstations and works with fedora 7 (i386 and still would like to use
i386). after another few google i found these:
i exactly has the same syndrome with f8 upgrade from dvd ie. it'e
terrible slow (10-100 times!!!). if i gives the noapic nolapic kernel
option for the installer it's use the normal speed, but kernel crash
when start /sbin/loader.
so my question is there any solution for this?
is it a kernel bug or is there any solution to be able to upgrade to f8
and use it in an acceptable speed?
anyways if i do live yum upgrade (ie. not boot from dvd) the the new kernel will
run with the same speed after reboot? since in this case i rather wait for an
updated kernel. or it's not a kernel related problem?
thanks in advance.
Version-Release number of selected component (if applicable):
while the previous version with f7 kernel-22.214.171.124-21.fc7 has no such problem.
Steps to Reproduce:
and here is the solution:
The only way to find out without installing Ubuntu 32bit is to use an Ubuntu
(32-bit) LIVECD and to try to prompt one (and ONLY 1 PER TIME) of the following
options at boot:
1) noapic nolapic
2) noapic acpi=noirq
3) noapic acpi=off
5) noapictimer irqpoll
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Live Yum upgrades are
not recommended as per:
and if you are having issues then I would recommend using the DVD to upgrade.
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
the problem still exists, the only solution what i find is:
kernel option. and in this case i can boot, but i don't think this can be a
please close this bug since it's been already solved in f9