Red Hat Bugzilla – Bug 431278
loader received SIGABRT during ks install
Last modified: 2008-08-02 19:40:36 EDT
* rawhide-20080201 i386
* Kickstart / ks=http://server/ks.cfg
When starting a ks installation, an error occurs in stage1:
> loader received SIGABRT! Backtrace:
> install exited abnormally [0/0] -- received signal 6
> sending termination signals...done
> sending kill signals...done
> disabling swap...
> unmounting filesystems...
> /proc done
> /dev/pts done
> /sys done
> you may safely reboot your system
On i386, this behavior does not occur if the same kernel/initrd are booted, but
without the ks= line to designate kickstart ...
Note: for x86_64, kickstart installations did not encounter this problem ...
What's the last line on tty3 when this happens?
Are you still seeing this on more recent trees?
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.