Bug 124662

Summary: installer exited abnormaly -- received signal 11
Product: [Fedora] Fedora Reporter: Stefan <panbiker>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-03 21:33:24 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:

Description Stefan 2004-05-28 11:57:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; i-
NavFourF)

Description of problem:
Booting from DVD

After /sbin/loader, ist takes 20 seconds, then "install exited 
abnormaly -- received signal 11" shows up.
The next lines are -disabling swap
-unmounting filesystems
-list of file systems......
and at least "you may safely reboot your system"



Version-Release number of selected component (if applicable):
fedora core 2 test 1 dvd

How reproducible:
Always

Steps to Reproduce:
1.insert dvd
2.sleecting kernel and parameters
3.hardware probing starts
4./sbin/loader
    

Actual Results:  after 20 seconds, "install exited abnormaly -- 
received signal 11"
shows up

Expected Results:  continue installation

Additional info:

Toshiba Tecra 8200 Laptop

allready tried "linux acpi=off, nobf, mem=128 (installed is 256MB), 
pci=off, nowardwareprobing.

RH9 is installes and perfectly running at the moment.

Comment 1 Steve Gonzales 2004-07-15 14:50:22 UTC
It also happens in Fedora Core 3 Test 1 on an Asus P4B533 motherboard

Comment 2 Steve Gonzales 2004-07-16 16:15:03 UTC
The installation media server had IPTABLES such that NFS was blocked.
 When I flushed the tables, NFS installation worked as advertised.


Comment 3 Jeremy Katz 2004-11-03 21:33:24 UTC
This has been fixed since FC3 test1.