Red Hat Bugzilla – Bug 115735
kudzu in FC2 Test1 sometimes hangs
Last modified: 2014-03-16 22:42:15 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
Running FC2 Test1 now since 2 days on my test system today I had kudzu
hanging twice during system startup.
The system seems to respond to keyboard input, but the bootup process
does not go on.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. wait for kudzu to hang
Can you get a strace/backtrace?
You mean when starting kudzu manually? Will try so.
Samt thing here with FC2test2. Booting stops at 'updating /etc/fstab',
just after 'staring kudzu'. It does not happen when skipping kudzu.
Will try to start it manually and see what it does.
It really is not kudzu that is the issue for me. It works fine, but
updfstab makes the boot process stop.
What seems weird to me is that running updfstab from the command line
works just fine.
I wonder if that could be related to a SELinux issue, that would
prevent the script from updating fstab.
Maybe. A strace of it when it hangs would be nice.
SELinux is definitely involved here, because SELINUX=disabled in
/etc/sysconfig/selinux now makes kudzu detect all my hardware at boot
The problem is that it still hangs the boot process, maybe when
running updfstab, but since kudzu fils the boot screen with blue, I
can't see what is causing the problem now.
Again, running them from command line works smoothly.
So, i'll try to strace them from the boot script, but I make no
promise for the result, since FC2 test2 ALWAYS breaks my ext2
partition when rebooting. Then fsck, 2 reboots, and back to normal...
FYI, I updated kernel to 2.6.5 and kudzu to latest up2date version and
it does the same.
sorry for mistake, upgrading kernel and kudzu DID solve the problem.
(And the ext2 breaking at reboot was due to label in /etc/fstab,
changing it to device file solved it.)
Now I guess downgrading to get the strace is not needed anymore then...
Marking as fixed in rawhide, then.
Is this the same issue?: