From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (X11; U; HP-UX B.10.20 9000/785)
"linux updates" with anaconda fix from your bug fix website and get the
same error: Process anaconda install exited abnormally recevied signal 11;
also gave call trace c011f4c1 c012f5c0 c012a907 c012ab14 c012ac90 c01232c2
c0123507 c0107aac ; code 89 07 8b 4c 24 10 8b 09 89 4c 24 10 83 ee 01 73 b5
c7 01 00
This is an HP machine with an Adaptec AHA-2940 AU -- SCSI adapter, TEAC
Loaded boot diskette and CD-Rom to start since this machine had SCO UNIX on
it before. Deleted the UNIX partiction before beginning.
(Needed to use boot diskette or it goes to SCO UNIX. So deleted UNIX
partition, then NO OS INSTALLED so using CDROM.)
Steps to Reproduce:
1.Reboot machine with Red Hat BOOT DISKETTE
2.type "linux updates" at the boot prompt
3. Binary CD in the CD ROM drive
4. when prompted loaded the anaconda bug fix update-disk-20001009.img
5. crashes with error given in description
Actual Results: crashes during Process anaconda with error install exited
abnormally recevied signal 11; also gave call trace c011f4c1 c012f5c0
c012a907 c012ab14 c012ac90 c01232c2 c0123507 c0107aac ; code 89 07 8b 4c 24
10 8b 09 89 4c 24 10 83 ee 01 73 b5 c7 01 00
Expected Results: Install RED HAT 7.0
This sounds like a kernel oops...
Created attachment 10944 [details]
anaconda fails during upgrade or installtion
Created attachment 14343 [details]
Install Crash w/ Anaconda
The anaconda traceback is likely just a side effect of the real problem. If
there was a kernel oops on the system, then that's the information I need to be
able to diagnose this issue. I also need to know what was happening at the time
of the oops (was the system trying to load any drivers, etc).
The crash happens when the installer is "Reading Package Information..."
Can you get new floppy disks and remake the boot disk and the updates disks.
The error you have sounds suspiciously like something is corrupted somewhere and
that usually happens because of bad disks (please note, I've personally had 4
bad disks in a row and not gotten a good disk until my fifth try in the past, so
please don't assume disks are good, always check them when in doubt). The best
way to check a disk is to format it under DOS/Windows or linux and see if they
report any bad sectors. If they report bad sectors during the format, then just
throw the disk away, it's useless. If you are using linux machines and don't
have a DOS/Windows machine then use the command fdformat /dev/fd0H1440 and it
will either succeed with all good sectors or tell you there was a format
My CD-ROM drive (Creative 36x) crashed during the install and I bought a Samsung
52x. I also changed my Targa 14" monitor to a NEC 15". This time I booted from
the CD-ROM drive, with the first CD of the download version of RH7.0. If I
dont't start with "linux updates expert" the Anaconda crash still happens, but
if I do that it works. Even having started with "linux updates expert" I don't
have the choice of intalling in text mode, but it works fine in graphical mode.
I don't know if it was the new CD-ROM drive, the new monitor (with the other
monitor the install stalled when changing to graphical mode) or the boot from
CD-ROM, but now it works. Booting from the CD is different from booting with the
disk -- perhaps the disk was damaged as you said.
Good enough, I'll close this bug out then as NOTABUG and assume there was
something flaky in the hardware setup of the machine prior to the changes.