Red Hat Bugzilla – Bug 129645
boot hangs on kudzu service
Last modified: 2015-01-04 17:08:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
Boot process hangs on kudzu service (I must skip them for
successful boot). Previous 2.6.6 kernel is ok.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
any idea what it is doing ?
do you have a firewire (controller) ?
I have the identical problem. Also I think this may be a dup of
128759. I am using an old VA Linux box with no firewire and no USB
devices. It is a generic FC2 system with latest updates.
Kernel is 2.6.8-1.521
kudzu is 220.127.116.11-1
When kudzu runs in bootup I see "Checking for new hardware" then an
appropriate pause for kudzu and then "Updating /etc/fstab" and a hang
from which ctrl-alt-del is possible.
After disabling kudzu boot is normal. I can then run kudzu and it
appears to work (though I have not made hardware changes for it to
find). There are no visible ill effects.
"with no firewire and no USB devices"
I lied. There is a USB mouse on this system.
is this still causing problems with the latest update kernels ?
I have the same problem on FC3.
[afolger@localhost ~]$ rpm -q kudzu
[afolger@localhost ~]$ rpm -q kernel
Kernel 2.6.8-1.603 boots with kudzu and everything works (except that on x86_64
sound often crashes). However, later kernels, up to and including
2.6.10-1.770_FC3 cough on kudzu during bootup. I disabled kudzu, and since, the
newer kernel boots. From the command line, kudzu runs just fine. The problem
exists on both the i386/686 and x86_64 platforms. I have one USB device, a HP
PSC2175 printer/scanner, and it works even with kudzu disabled. As you can tell
from the rpm query above, I applied all the latest updates.
The bug should be reclassified as FC3 all architectures.
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.