Red Hat Bugzilla – Bug 177456
kudzu segfault at boot
Last modified: 2014-03-16 22:57:31 EDT
Description of problem:
Just installed FC4 from DVD iso downloaded from mirror site.
kudzu segfaults on boot or from command line
Version-Release number of selected component (if applicable):
Not sure how to find. It's whatever is in the current FC4 distribution.
Kernel is 2.6.11-1.1369_FC4.
Also happens with 2.6.11-1.1369_FC4smp.
Steps to Reproduce:
1. Install FC4
2. boot or type kudzu at command line
Hardware is Intel D865PERL with P4 3.2ghz, 1gB RAM
/boot is on IDE hda1, grub is on MBR of that disk.
/ and swap are on SATA sda2 (WinXP is on sda1).
During boot, message is:
Checking for new hardware/etc/rc3.d/S05kudzu: line 23: 1749 Segmentation
fault /usr/sbin/kudzu $KUDZU_ARGS -z
/etc/rc3.d/S05kudzu: line 23: 1750 Segmentation fault /usr/sbin/kudzu
Created attachment 123011 [details]
kudzu strace from command line
kudzu in RPMS on DVD is kudzu-184.108.40.206-2.i386.rpm
I have now started over and installed FC5, and I have the same problem.
I had the exactly same problem. It turned out that the /etc/sysconfig/hwdata
file was corrupted (with lots of cryptic characters in the middle).
Erasing this file fixed the problem for ever.
Hmm, I don't seem to have a /etc/sysconfig/hwdata file.
Sorry, not /etc/sysconfig/hwdata but /etc/sysconfig/hwconf.
I guess it went corrupted after some upgrade of kudzu.
I've still got problem with latest kudzu from rawhide
Checking for new hardware/etc/rc5.d/S05kudzu: line 23: 1717 Segmentation fault
Dex: your problem is different, and will be fixedin kudzu-1.2.23-1.
I have a segfault with kudzu-1.2.30-1.
I have an IT8212 disk controller. When there are disks attached to it I get the
kudzu segfault; where there are no disks attached to it, I don't.
Andrew, can you open up a new bug - this sounds different than what we currently
have in this bug.
Please attach a backtrace from gdb (you'll probably want to install
Forget it -- kudzu.x86_64 0:220.127.116.11-1 fixes the problem.
Sorry for the noise.
root@localhost log]# rpm -qa "kudzu*"
[root@localhost ~]# uname -r
I can see the disk led on for about 1 second, then absolute lockup. Tried to
wait 5 minutes to see if there would be a time out, but there was none.
Leslie - that is unrelated to this issue.
Please forgive me. I looked at the title and then skimmed the rest. Only after I
saw that it was a FC4 problem.
I will remove myself from the CC.
I have almost the same problem with my FC2 box. Once my PC was shutting down
very slowly I waited the process end. On the next day I turned my PC on again,
and the problem persists.The system stops responding at the hardware/detection
step:FreeConfmodules called with the NULL POINTER. Dont do that.
/etc/rc5.d/S05kudzu line 97 1371 *this number changes every time I try to reboot
PC* ABORTED /usr/sbin/S05kudzu $KUDZU_ARGS -t 30. After this point in the
kernel without xserver the PC boots normally and goes into text mode. Then I can
access into gui desktop by the following way:login as root, then cd into install
folder, then "nvidia-installer --uninstall. After this reinstall the drivers and
then with "startx" command I can access into GUI. But the PC is without
integrated peripherals such as the network adapter, USB and so on. ONLY PCI
soundcard and PS2 MOUSE and AGP video are working. hwbrowser hangs after its
execution. I am able only browse in the harddisk, launch installed programs and
so on but this all without additional devices. If I log/off then PC goes back to
the textmode and this all will start again.
After the some tests of the reboots are clear some facts:
1. If I do the calm reset and try to boot into another kernel without x drivers
then text mode login is successful.
2. If I try to reboot after such login text mode then in the x driver installed
kernel boots with the GUI but will stay slow as before, stops responding at
first in the swap enabling point or at the second hardware detection point.
3. Reinstall the FC2 is not possible because I have installed two separated FC2
OS-es on the separated hard disks. THe boot files are in the hda but the OS I
try to access is in the hdb. Anaconda gives up at the install information copy
> No enough space> But I checked the disks all is OK:
I have a DSL linux LIVE CD. This small linux distro found all the peripherals on
my mobo. I mounted my hard disks in the mountpoints and I can to read/write on
them, so HDD-s should be OK. Also with the the FC2 Rescue CD I can to access
into the harddisks..
4. What causes the hang-up of the kudzu? What launches and uses kudzu?
I think that something is wrong with the kudzu bash script but i dont see the
error messages anywhere on the system logfiles...
I tried to turn kudzu off but this not help me...
If somebody can help me then please respond at this thread or mail me at the
Fixed in 1.2.41-1 by removing the offending code.