Red Hat Bugzilla – Bug 75830
fresh installed RH8.0 hangs on first load of a kernel module
Last modified: 2008-08-01 12:22:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126
Description of problem:
installed kernel should be able to have kernel modules added
on boot (e.g. network loop back interface).
On RedHat 7.3 (clean reinstall) newly installed kernel booted fine.
The problem is HW laptop Sony VAIO GR series dependent.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.fresh install RedHat 8.0
2.after installation reboot
3.on e.g. network load loop back network interface
Actual Results: module install command hangs and actualy shows via cat
/proc/modules that the
module is loaded.
I tried to start the system avoiding the kernel to load modules
(e.g. network off, etc).
This works fine up to the moment a kernel module realy is needed so
that command/process will hang. The kernel itself will proceed.
So a reboot while modules are loaded will hang on the first kernel module load
Expected Results: the "modprobe" command should finish
Maybe: ACPI plays a role here?
RedHat 7.3 reinstallment went ok, also with the RedHat 7.3
new kernels updated.
could you try getting the i586 kernel installed instead ?
Have reinstalled RedHat8.0 and updated the Linux 2.4.18-14 kernel with
the i586 kernel.
(Not real problem yet: got unresolved variable for modules longhaul, microcode,
speedstop, and p4-clockmod)
More severe: again the insmod command hang on multiuser boot on the first kernel
module to be installed (network loopback interface).
I tried the kernel-2.4.18-14.i686.rpm kernel as well:
same problem: kernel modules installment will hang.
Fresh RedHat 8.0 will not run on my Sony VAIO GR laptop.
Thanks for your rappid reply at Sunday.
can you enable sysreq (see /etc/sysctl.conf) and see if sysreq-T gives something
in /var/log/messages ?
Have changed the value kernel.sysrq = 0 -> 1 in /etc/sysctl
Noticed before and after the change that lenght of /var/log/messages
is zero (null). So no kernel info available.
The /var was mounted on another ext3 partition.
So I changed that: deleted the mount from /etc/fstab and created
a proper (copy from the original dirs) /var subtree directly on /
Rebooted and still hang on the rc.init script when network loopback
kernel was initiated.
It's crazy there is no info at all in /var/log/messages!
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/