Bug 197804

Description of problem:
I saw this last week and thought it was the same as 195749 but since that one is
just with http installs (I am using nfs) and that one should be fixed and I
still see this one it looks like this is a separate issue.

This is seen during a kickstart install on one of my HP Integrity (ia64)
servers.  Odd thing is I don't see this on my other systems.  I have not yet
seen this with interactive installs.  This is really odd since it had not yet
brought up the eth device so it would not have been able to get the kickstart
file yet so I don't know _why_ I am only seeing this with kickstart.  However,
when I do an interactive install this appears to be the point where it would ask
for the language and it doesn't do that for a KS intstall.

Last message seen from anaconda before the crash was "Loading cciss driver...".
 This is a serial console system so I am unable to get much info out of it (it
would be really cool if there were some way to store the logs from a failed
install in these situations).




 *** glibc detected *** /sbin/loader: double free or corruption (fasttop):
0x600000000012ec40 ***
======= Backtrace: =========
[0x40000000002c4cf0]
[0x40000000002ce2c0]
[0x4000000000030a40]
[0x4000000000036e70]
[0x400000000002b960]
[0x400000000001e3b0]
[0x4000000000008040]
[0x4000000000270710]
[0x4000000000000280]
======= Memory map: ========
00000000-00004000 r--p 00000000 00:00 0
2000000000030000-2000000000070000 rw-p 2000000000030000 00:00 0
2000000000100000-2000000000124000 rw-p 2000000000100000 00:00 0
2000000000124000-2000000000200000 ---p 2000000000124000 00:00 0
4000000000000000-400000000046c000 r-xp 00000000 00:01 29                
/sbin/loader
6000000000008000-6000000000034000 rw-p 00468000 00:01 29                
/sbin/loader
6000000000034000-6000000000200000 rw-p 6000000000034000 00:00 0          [heap]
60000fff7fffc000-60000fff80000000 rw-p 60000fff7fffc000 00:00 0
60000ffffe9e4000-60000ffffea38000 rw-p 60000ffffe9e4000 00:00 0          [stack]
a000000000000000-a000000000020000 ---p 00000000 00:00 0          [vdso]
install exited abnormally [0/0] -- received signal 6
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
/proc/bus/usb done
/proc done
/dev/pts done
/sys done
/tmp/ramfs done
you may safely reboot your system



Version-Release number of selected component (if applicable):
rawhide-20060706
anaconda-11.1.0.53-1

How reproducible:
On one particular system (hplp2 on my private net) every time when I do a
kickstart install.  I have not seen this on 

Steps to Reproduce:
1. network boot with: append="ks=nfs:10.12.11.1:/export/10.12.11.41-kickstart
ksdevice=eth0 selinux=0"

(note, I also tried without the selinux=0 with same results)