Bug 454663 - mkinitrd missing scsi_wait_scan
Summary: mkinitrd missing scsi_wait_scan
Keywords:
Status: CLOSED DUPLICATE of bug 470628
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 10
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-09 15:38 UTC by Doug Chapman
Modified: 2008-12-09 20:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-09 20:00:30 UTC


Attachments (Terms of Use)
Correct variable name (495 bytes, patch)
2008-12-08 23:42 UTC, Nate Clark
no flags Details | Diff
Corrected all variable names (682 bytes, patch)
2008-12-09 06:24 UTC, Nate Clark
no flags Details | Diff

Description Doug Chapman 2008-07-09 15:38:29 UTC
Description of problem:
Recent mkinitrd no longer adds these lines to the init script:

modprobe scsi_wait_scan
rmmod scsi_wait_scan

also does not appear to be pulling in scsi_wait_scan at all.

This breaks booting on scsi.


Version-Release number of selected component (if applicable):
mkinitrd-6.0.54-1.fc10

testing 6.0.55 now but based on the changelog it does not appear this is fixed.


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Doug Chapman 2008-07-09 17:35:19 UTC
I confirmed mkinitrd-6.0.55-1.fc10 does still have this issue.


Comment 2 Jeremy Katz 2008-07-09 18:17:55 UTC
This is because scsi_mod is now built-in and that was what we used to key
needing scsi_wait_scan

Comment 3 Dave Jones 2008-07-09 23:24:55 UTC
ah, good catch.
I could flip this back to =m if there's no better way.
Strikes me as somewhat fragile to do it this way, though I admit I haven't got
any better ideas.

Comment 4 Jeremy Katz 2008-07-09 23:41:39 UTC
I guess we could try to do some form of determination based on symbols used in
the module, but then we have to be doing nm on modules.  Or we could use the
modules.block file and seeing if the driver is listed there



Comment 5 Bug Zapper 2008-11-26 02:32:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Nate Clark 2008-12-08 23:42:11 UTC
Created attachment 326229 [details]
Correct variable name

There is some code in there to wait for scsi to stop scanning it doesn't use the module but it would work if the variable name was consistent.

Comment 7 Nate Clark 2008-12-09 06:24:43 UTC
Created attachment 326270 [details]
Corrected all variable names

Last suggested patch made things worse this one makes all variables the same name.

Comment 8 Dave Jones 2008-12-09 20:00:30 UTC

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


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