Bug 410521 - loader fails with sigsegv
Summary: loader fails with sigsegv
Keywords:
Status: CLOSED DUPLICATE of bug 374311
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-04 15:56 UTC by Dan Shea
Modified: 2007-12-07 17:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-07 17:46:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dan Shea 2007-12-04 15:56:36 UTC 
Description of problem:

The anaconda installer fails at loader with SIGSEGV

loader received SIGSEGV! Backtrace:

[0x804a030]
[0x110420]
[0x81a3f42]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
install exited abnormally [1/1]

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


How reproducible:

It happens every single time.  DVD was verified as good by the installer, upon
selecting continue it crashes every time.

Steps to Reproduce:
1. Insert Fedora 8 DVD into CDROM of HP nc6000 laptop
2. Start installation process (graphical or text)
3. Get to the part where it wishes to check the media, it will fail upon
selecting continue
  
Actual results:

loader received SIGSEGV! Backtrace:

[0x804a030]
[0x110420]
[0x81a3f42]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
install exited abnormally [1/1]

Expected results:

Continuation of install process

Additional info:

See above for backtrace info.
Comment 1 Jeremy Katz 2007-12-04 21:57:50 UTC 
Does booting with 'linux nopcmcia' help?
Comment 2 Dan Shea 2007-12-07 08:07:22 UTC 
I booted and edited the grub menu to pass nopcmcia at boot.
The installer then proceeded and I was able to install Fedora 8.
Thank you!
Comment 3 Chris Lumens 2007-12-07 17:46:21 UTC 

*** This bug has been marked as a duplicate of 374311 ***
Note You need to log in before you can comment on or make changes to this bug.