Bug 12420

Summary: anaconda lockup after boot disk was created.
Product: [Retired] Red Hat Linux Reporter: Sam Varshavchik <mrsam>
Component: anacondaAssignee: Brock Organ <borgan>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-06-27 18:40:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
autopsy of a locked up anaconda. none

Description Sam Varshavchik 2000-06-18 17:23:53 UTC 
Graphical install.

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
too).

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.
Comment 1 Sam Varshavchik 2000-06-18 17:25:09 UTC 
Created attachment 543 [details]
autopsy of a locked up anaconda.
Comment 2 Brock Organ 2000-06-19 22:26:33 UTC 
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) ...?
Comment 3 Sam Varshavchik 2000-06-19 22:32:51 UTC 
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.
Comment 4 Brock Organ 2000-06-27 18:40:50 UTC 

*** This bug has been marked as a duplicate of 12284 ***