Bug 187646 - exception dump attached -- possibly a hardware problem
Summary: exception dump attached -- possibly a hardware problem
Keywords:
Status: CLOSED DUPLICATE of bug 186761
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-02 08:59 UTC by James G. Sack
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-03 19:04:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
gzipped anacdump from floppy-save (31.65 KB, application/octet-stream)
2006-04-02 08:59 UTC, James G. Sack
no flags Details

Description James G. Sack 2006-04-02 08:59:04 UTC
Created attachment 127198 [details]
gzipped anacdump from floppy-save

Comment 1 James G. Sack 2006-04-02 08:59:04 UTC
Description of problem:
 (dump-attached)
 sudden exception after retry-butten pressed after cdrom read error 
 possibly related to flakey hardware 

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

How reproducible:
 unknown (1 time), but seems associated with other cd malfunctions 
 suspect flakey hardware: cd access seems to get unreliable after
 1-hour+ of install (once on the very last rpm!). 

 Upon previous failures the cd device (hdc) itself seems to no longer
 be recognized! Reboot and retry shows errors on first cd. Problem 
 seems to go away after a few-minutes power-off rest. I suppose this 
 might also be explained by a device driver bug. 


Steps to Reproduce: (?)
1. fail install (cd problem) on disk5. device hdc seems to disappear(!?!)
2. warm reboot, gives errors on first disk, retry offered
3. retry causes exception (see attached dump)
  
Actual results:


Expected results:


Additional info:
 see attached

Comment 2 Chris Lumens 2006-04-03 19:04:45 UTC

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


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