Red Hat Bugzilla – Bug 55497
'Unhandled exception' and crash while installing RedHat 7.2 on Dell Inspiron 8100 notebook
Last modified: 2007-04-18 12:37:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
About 2/3 through the rpm installation I get an exception message and a
crash dump. Apparently due to SystemError: 'Device or resource busy'. See
attached log for details.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install normally, graphically or in text mode (custom, most things
2. Installation inside an extended partition starting at about 6.5GB
3. Crash occurs during RPM installation
Actual Results: The installer crashes as described earlier.
Expected Results: Installation should have continued.
System is a Dell Inspiron 8100 notebook (P3-1130MHz, 384MB)
Created attachment 35981 [details]
The Anaconda dump file for this bug
Created attachment 36141 [details]
Report generated during 7.2 install at "free japanese font"
Same problem occurs with a standard workstation install of RH 7.2
attached is the anaconda dump for this.
running through the instalation again, with the exact same install settings.
Created attachment 36322 [details]
anaconda dump after crqash during RH7.2 install
the above dump is from the install on a desktop PC, not a laptop
firstname.lastname@example.org and morgan.dollard, I think both of you are seeing two
different problems (both from each other and from the original bug report).
Please open a new bug report for the problems you are seeing.
forda, did you download the ISO images or are these the retail cds? If you
downloaded them, did you check the md5sums? It looks like the kernel is having
trouble reading the cdrom.
It was the downloaded ISO images. I've used these CDs to install another
(stationary) machine w/o problems before. However, the CD drive in the laptop
has had reading problems on other CDs, so it is entirely possible that it has
had reading problems here as well.
Yes, that would probably explain the problem. Please reopen this report if you
see the behavior on a different cdrom drive. Thanks for your report.