Red Hat Bugzilla – Bug 160990
"install exited abnormally -- received signal 11" after getting an IP address
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Description of problem:
I am trying to install FC4, via NFS, on my Sony Vaio PCG-Z600TEK (700MHz, 256M) and it fails immediately after getting or assigning an IP address with "install exited abnormally -- received signal 11"
This problem exists with NFS, HTTP, FTP installs images/boot.iso, rather than the whole DVD/CS. It does not happen with an install from CD, unless I try to install it with the vnc option - again it fails immediately after getting/assigning an IP address.
It does not make a difference if I manually assign an IP address, or if one is obtained with DHCP.
This bug did not exist on FC4 test 1, but does exist on FC4 test 3. I do not know about FC4 test 2. If it would help you if I tried that, it would not be a problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install from FC4 images/boot.iso
2. Select any install method that requires network
3. Enter IP info, install crashes.
Actual Results: Installation crash
Expected Results: No crash
Is this with wireless or wired? Are there any error messages on tty3 or tty4?
No error messages on any tty. Will create some attachments in case there is
anything of use there.
I tried FC4T2, and the problem exists there too.
After the SIGSEV is reported, the host is pingable.
lspci reports nic is '00:0b.0 Ethernet controller: Intel Corporation 82557/8/9
[Ethernet Pro 100] (rev 08)'
Created attachment 115733 [details]
Created attachment 115734 [details]
tty3 after error using dhcp
Created attachment 115735 [details]
tty4 after error using dhcp
aaarrggghh, sorry, should have created jpgs for the attachments
*** Bug 161184 has been marked as a duplicate of this bug. ***
Please test with one of the upcoming FC5 test releases. We've fixed a
segmentation fault or two in the loader so I believe this may be taken care of.
Looks like this problem has been fixed. Thanks.