Bug 84146 - Scanning PCI bus when no PCI present causes Signal 11
Scanning PCI bus when no PCI present causes Signal 11
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: pciutils (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-12 15:02 EST by Lee Olsen
Modified: 2014-03-16 22:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-12 15:50:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
text file briefly describing bug identification and resolution (884 bytes, text/plain)
2003-02-12 15:17 EST, Lee Olsen
no flags Details

  None (edit)
Description Lee Olsen 2003-02-12 15:02:12 EST
Description of problem:Signal 11 in /sbin/loader


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


How reproducible:Attempt to install Redhat 7.3 on a system *WITHOUT* a PCI bus


Steps to Reproduce:
1.Make a boot floppy per the installation manual
2.boot non-PCI system from floppy
3.enter "linux dd" at "boot:" prompt
    
Actual results:Signal 11 from /sbin/loader


Expected results:Menu box requesting a driver disk


Additional info:Entering "linux nousb dd" delays the crash to after loading
additional drivers
Comment 1 Bill Nottingham 2003-02-12 15:03:55 EST
Can you try this with the phoebe beta?
Comment 2 Lee Olsen 2003-02-12 15:17:40 EST
Created attachment 90038 [details]
text file briefly describing bug identification and resolution

Since 8.0 is out, a patch against 7.3 probably doesn't make much sense.
I hope the function name, pci_scan_bus, the fact that it is a one line
function,
and the problem (methods is NULL) should make resolving this straight forward.
Enjoy
Lee
Comment 3 Bill Nottingham 2003-02-12 15:50:50 EST
Fixed in 2.1.10-7, thanks!

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