Red Hat Bugzilla – Bug 12420
anaconda lockup after boot disk was created.
Last modified: 2008-05-01 11:37:56 EDT
Got as far as "creating a boot disk". Told it to create a boot disk. The
floppy grumbled for a while, then anaconda froze up.
Went to a terminal window on ctrl-alt-f3. The hard disk, with the
installed system, was mounted. I am attaching the output of ps + strace
analysis of the anaconda processes (there was a setxkbmap zombie process
I've reproduced this twice. This was a stock server install, but NFS
server was unchecked, and I told anaconda to wipe and partition the 9 GB
disk by itself.
Created attachment 543 [details]
autopsy of a locked up anaconda.
hmm ... I am having trouble reproducing this behavior ...
does this occur for all occurences of boot disk creation (TUI and GUI) ...?
does this occur regardless of install type (custom, server, etc.) ...?
does this occur over multiple disks (ie no bad disk) ...?
textmode install is fine.
i've only tried twice to do a server install, happened every time. will have to
try some other types of installs.
the attached ps dump shows setxkbmap zombie process. things must be crashing
some time after setxkbmap is executed to do whatever it's supposed to do, but
before the parent process has a chance to reap it.
*** This bug has been marked as a duplicate of 12284 ***