Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 159769 - kernel crash while loading modules
Summary: kernel crash while loading modules
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mkinitrd
Version: 4.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
: ---
Assignee: Brian Lane
QA Contact: Kevin Baker
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-07 20:57 UTC by Andrew Elmore
Modified: 2014-12-01 23:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-07-27 17:57:41 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Andrew Elmore 2005-06-07 20:57:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050131

Description of problem:
in the init script in /boot/initrd....img, a sequence of insmod commands gets invoked in parallel.  I'm not sure how this happens, but the upshot is that the 6 modules for the scsi subsystem and the boot filesystem aren't able to be loaded due to their dependencies being unresolved.  the real init isn't able to be invoked, and the system crashes.  Putting "sleep 2" in between each of the insmods fixed the problem for me.  The real fix would be for the Linux kernel to serialize module instantiation.

note that this is a 4 way SMP box (an IBM RS/6000 7044-270).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. reboot after install.

Actual Results:  system crashed.

Expected Results:  I would expect the system to come up properly.

Additional info:

Comment 1 Bill Nottingham 2005-06-07 21:03:24 UTC
Assigning to kernel, cc'ing mkinitrd maintainer.

Comment 2 Dave Jones 2005-06-21 17:51:24 UTC
That script is firmly in the realm of mkinitrd, reassigning.

Note You need to log in before you can comment on or make changes to this bug.