Bug 436922 - igb driver in RHEL5.2 beta makes system crash.
Summary: igb driver in RHEL5.2 beta makes system crash.
Keywords:
Status: CLOSED DUPLICATE of bug 252004
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Andy Gospodarek
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-11 06:41 UTC by austin
Modified: 2014-06-29 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-11 12:28:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description austin 2008-03-11 06:41:14 UTC 
Description of problem:
RHEL5.2 beta integrated igb driver with version 1.0.8-k2. This driver will make 
system crash when it was loaded. In Caneland and Stoakley, which have Intel 
82575EB Gigabit Network controller, reboot machine after installation, the 
system crash when load igb.ko driver. If disable the driver's loading, system 
will work fine. 

Downloaded the latest igb driver from sf with version 1.2.22, this driver works 
well in 5.2 beta.

(I'm not sure the component to file the bug, I didn't 
find 'network', 'NIC', 'network driver'..., so I just file it to 'net-tools' 
component, please forword to right persons. thanks)

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


How reproducible:
always with Intel 82575EB Gigabit Network controller.

Steps to Reproduce:
1.install 5.2 beta in machine with Intel 82575EB Gigabit Network controller.
2.reboot
3.system crash.

  
Actual results:
system crash due to loading of igb driver

Expected results:
integrated workable igb driver.

Additional info:
Comment 1 Andy Gospodarek 2008-03-11 12:27:45 UTC 
This should be fixed in the next Snapshot (which should be released quite soon).
Comment 2 Andy Gospodarek 2008-03-11 12:28:35 UTC 

*** This bug has been marked as a duplicate of 252004 ***
Note You need to log in before you can comment on or make changes to this bug.