Red Hat Bugzilla – Bug 141934
Anaconda crashes installing packages
Last modified: 2007-11-30 17:07:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
This is a kickstart install, and the same install works fine on an HP
Vectra with 256 Mbytes RAM.
This test machine is a Dell optiplex GXa Pentium II 300 Mhz.
I am attempting a network kickstart text-mode install.
I was able to do a network manual GUI install.
The last package accessed on my web server is
As you can see from the photo above, there is no opportunity to
conduct any forensics: Anaconda crashes and the system promptly reboots.
It happens every time on this machine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Choose your Dell GXa
2. PXE-boot my kickstart file
3. Make a cuppa:-)
Actual Results: Anconda crash, temination messages scattered over the
Expected Results: Clean install.
Created attachment 107936 [details]
The kickstart file for this install
This is the same ks file used for my initscripts bug and which I emailed to
You're basically getting a sig11 when package installation starts. If
this is reproducible on this machine, you might want to run memtest86+
to check the memory...
Well, I _did_ do a manual gui install w/o problems.
memtest has completed one pass without error.
I booted into rescue mode (could we have a kickstart-style resuce
mode?) and found the install log. There were three packages listed as
installed. Not much of note.
memtest has been running 14 hours and 18 minutes.
I gave up on the unexciting memorytest and tried an fc3 kickstart.
Failed too, looked like the same point.
ks file available on request.
Note: I'm using http installs; if you want to patch something bear
that in mind and give me clear instructions about what goes where.
I could try fc2 if you're interested.
Might this be running out of memory?
I tried a manual install of _everything_ on the same machine and that
crashed similarly except that
a. it did not automatically reboot
b. It happened earlier.
One of the VC displays showed Kernel Killer knocked off Anaconda.
I suggest Anaconda be changed to check whether this might be likely
and offer the possibility of using a swap file. It has got past disk
formatting, so the swap file is feasible.
We recommend using swap. If you continue and don't create a swap partition,
then weird things can happen.