Bug 459991

Summary:	nash-hotplug goes into tight loop on firmware load request
Product:	[Fedora] Fedora	Reporter:	James Bottomley <james.bottomley>
Component:	mkinitrd	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8	CC:	dcantrell, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-09 06:44:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Bottomley 2008-08-25 14:34:39 UTC

Description of problem:

Trying to boot FC8 with an aic94xx based system, the aic94xx driver won't load because its firmware is not loaded.

Have verified that the firmware is present in /lib/firmware.  Also verified that it can be loaded manually (by putting bash in the initrd).

What seems to happen is that nash-hotplug goes into an endless loop when it sees the firmware request.  Putting ps into the initrd shows it to be eating up CPU cycles at roughly the same time as the wall clock.

Additionally, when the aic94xx firmware is loaded manually, the root device doesn't appear:  Further evidence that nash-hotplug hasn't seen the device creation event.


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

6.0.52-2.fc9

How reproducible:

All the time

Steps to Reproduce:
1. boot with aic94xx as root

Additional info:

This situation in an initrd is almost impossible to debug because of the monolithic nature of nash.  This boot system needs to be dumped in the nearest landfill where it belongs and standard system components (which are actually debuggable) used instead.

Just by way of illustration, the system will boot if I make debian mkinitramfs build the initrd.  The ramdisk that does this, including bash and a host of nice debugging tools, is only 50% bigger than the RH/nash one.

Comment 1 Peter Jones 2008-08-25 14:41:29 UTC

What kernel are you using here?

Comment 2 James Bottomley 2008-08-25 15:02:46 UTC

The latest: 2.6.24.14-69.fc8

Comment 3 Bug Zapper 2008-11-26 11:07:10 UTC

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-01-09 06:44:38 UTC

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.