Bug 61043 - "kmod: failed to exec /sbin/modprobe" during hampton beta2 bootup
"kmod: failed to exec /sbin/modprobe" during hampton beta2 bootup
Status: CLOSED DUPLICATE of bug 62145
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-03-12 11:36 EST by Clay Cooper
Modified: 2007-04-18 12:40 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-22 16:28:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Dmesg from bigmem kernel (13.74 KB, text/plain)
2002-03-12 11:37 EST, Clay Cooper
no flags Details

  None (edit)
Description Clay Cooper 2002-03-12 11:36:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019

Description of problem:
On a 6450 w/ hampton beta2 (2.4.9-0.1bigmem), w/ bios A10, 5GB ram, 2GB swap,
and Perc3/SC boot controller. 

Dmesg reports:
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 

Occurs in up, smp, and bigmem kernels.

Attaching dmesg output from bigmem kernel

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

How reproducible:

Steps to Reproduce:
1.  Install hampton beta2 on a 6450 w/ Perc3/SC boot controller
2.  Check dmesg for kmod error

Actual Results:  Kmod error in dmesg

Expected Results:  No error

Additional info:
Comment 1 Clay Cooper 2002-03-12 11:37:27 EST
Created attachment 48285 [details]
Dmesg from bigmem kernel
Comment 2 Clay Cooper 2002-03-21 12:36:59 EST
Not fixed in beta3
Comment 3 Michael K. Johnson 2002-03-28 11:49:46 EST
Something in user space, I think mkinitrd, is opening a scsi device that
doesn't (yet) exist, and kmod is trying to load the scsi host adapter.  I
do not know what scsi device is being accessed, but in any case this is
not a kernel bug.  The kernel is doing the right thing as far as I can tell.
Comment 4 Clay Cooper 2002-04-04 16:27:53 EST
Reproduced in beta4
Comment 5 Clay Cooper 2002-04-22 16:28:45 EDT
Reproduced in Hampton gold.
Comment 6 Erik Troan 2002-05-21 17:29:34 EDT

*** This bug has been marked as a duplicate of 62145 ***

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