Bug 630254

Summary: Anaconda crashes during "Examing storage devices"
Product: [Fedora] Fedora Reporter: Phil Cole <filcole>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-04 16:11:12 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:
Attachments:
Description Flags
error log produced by anaconda
none
Output of "lspci -vnn"
none
Output of "dmesg" none

Description Phil Cole 2010-09-04 12:49:29 UTC
Created attachment 443056 [details]
error log produced by anaconda

Description of problem:
Using either the graphical and tetx based installs anaconda will crash immediately after displaying "Examining storage devices".  

Version-Release number of selected component (if applicable):
Fedora 14-Alpha DVD

How reproducible:
Reproducable everytime - I don't know a workaround.


Steps to Reproduce:
1. Attempt to install from Fedora alpha 14 DVD.
2. Continue through until "Install Anyway" is displayed, and say "Install Anyway".
3. "Examining Storage Devices" is flashed on the screen
  
Actual results:
Anaconda crashes with the attached backtraces.

Expected results:
List of devices on which I could install fedora/partition editor.

Additional info:
Installing on a HP Compaq 6715b laptop.  Previous install on this laptop was Ubuntu 10.04 with an ext4 drives.

Comment 1 Phil Cole 2010-09-04 13:02:33 UTC
Created attachment 443057 [details]
Output of "lspci -vnn"

Comment 2 Phil Cole 2010-09-04 13:03:33 UTC
Created attachment 443058 [details]
Output of "dmesg"

Comment 3 Phil Cole 2010-09-04 16:11:12 UTC

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