Bug 498307 - F11-Preview installer loader crashes when booting installer with ks nodmraid
F11-Preview installer loader crashes when booting installer with ks nodmraid
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-29 15:54 EDT by Alexandre Oliva
Modified: 2009-04-30 17:23 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-04-30 17:23:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexandre Oliva 2009-04-29 15:54:51 EDT
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):

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:
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.
Comment 1 Chris Lumens 2009-04-29 16:12:51 EDT
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.
Comment 2 Chris Lumens 2009-04-29 16:14:45 EDT
...by which I meant, can you paste the complete line in here?  Or is it just "ks nodmraid"?
Comment 3 Alexandre Oliva 2009-04-29 22:00:40 EDT
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.
Comment 4 Chris Lumens 2009-04-30 17:23:54 EDT
This will be fixed in the next build of anaconda.  Thanks for the bug report.

Note You need to log in before you can comment on or make changes to this bug.