Bug 161163 - kickstart installer does a signal 11 with a intel e1000 dual port nic installed
kickstart installer does a signal 11 with a intel e1000 dual port nic installed
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
3.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-20 17:39 EDT by its-systems
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-21 17:15:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description its-systems 2005-06-20 17:39:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
Kickstart process signal 11s everytime an install is attempted. Removing NIC and no signal 11, replace NIC, signall 11 remove NIC process OK. tried on RHAS3 and RHAS3-update5.

cd 1 checked for errors, none reported, normall install looks OK. 

Version-Release number of selected component (if applicable):
rhas3-update 5

How reproducible:
Always

Steps to Reproduce:
1.Insert NIC
2.start kickstart process
3.Install aborts with a signal 11
  

Actual Results:  I get a signal 11 and need to reboot

Expected Results:  kickstart process should have run

Additional info:

This is a dual ported Intel Pro e1000 NIC in a Dell 2650 running bios A19.

Part number is 

CN-0j1679-46551-462-017Q Rev A00

LAN CARD J1679 E-G021-03-1161 (B)

It is a Intel PCB.

Bar code is 000423A92F12 234SC C40896-004
Comment 1 its-systems 2005-06-20 17:55:59 EDT
Removed e1000 and inserted 3com NIC, this does the same thing, suggesting a 
Dell motherboard/bios issue and not a NIC issue as the cards are different
Comment 3 Jeremy Katz 2005-06-21 13:32:35 EDT
You might try running memtest86 on the system to see if there's a memory issue.
 That's usually one of the primary causes of a sig11.
Comment 4 Jeremy Katz 2005-09-21 17:15:21 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.

Note You need to log in before you can comment on or make changes to this bug.