Description of problem: If you boot up the installer with the dmraid option, it will crash before detecting network interfaces. Without dmraid, it works fine. Version-Release number of selected component (if applicable): F11-Preview How reproducible: Every time, on i386 and x86_64 Steps to Reproduce: 1.Take vmlinuz and initrd.img from pxeboot in the install image, and set grub up to boot from them, passing 'ks nodmraid' to it 2.Boot up the installer Actual results: running /sbin/loader loader received SIGSEG! Backtrace: /sbin/loader(loaderSegvHandler+0xa0)[0x804fffe0] [0xa60400] /sbin/loader(isKickstartFileremote+0x3d)[0x8058f6d] /sbin/loader[0x804f9d5] /sbin/loader(main+0x674)[0x8051014] /sbin/loader(__libc_start_main+0xe6)[0x5de8e6] /sbin/loader[0x804dd91] install exited abnormally [1/1] Expected results: No such crash. Booting up without nodmraid probes and configures the network interface to obtain the kickstart file. Additional info: All there is in VT3 is the kernel command line INFO line. VT$ ends with detection of the synaptics touchpad.
What does your boot command line look like? I think this is the first time I've ever seen a segfault in this function before.
...by which I meant, can you paste the complete line in here? Or is it just "ks nodmraid"?
Just ks nodmraid was enough to trigger the problem. I had ramdisk_size=8192, noipv6 and ksdevice=eth0 as well, but discarding them didn't make any difference.
This will be fixed in the next build of anaconda. Thanks for the bug report.