Bug 452289

*** Bug 454825 has been marked as a duplicate of this bug. ***

=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-07-09 17:30 EDT
1. Feature Id:	[201494]
Feature Name:	IGB Driver Update
Sponsor:	xSeries
Category:	Device Drivers and IO
Request Type:	Driver - Update Version

2. Short Description
An updated version of igb driver is required to address several bug fixes and enhancements. Intel
will provide the latest available version.

3. Business Case
The igb driver is on several key System x products. We need the in-distro driver to be as current as
possible so known critical bugs are ensured to be corrected.

4. Sponsor Priority	1
IBM Confidential:	yes
Code Contribution:	no
Upstream Acceptance:	In Progress
Component Version Target:	Driver Update
Performance Assistance:

5. PM Contact:	Monte Knutson, mknutson.com, 877-894-1495

6. Technical contact(s):
Kevin Stansell, kstansel.com
Chris McDermott, mcdermoc.com

7. LTC Manager: Julio Alvarez, julioa.com

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

*** Bug 451858 has been marked as a duplicate of this bug. ***

High for HP and IBM.  This covers the Kawela NIC, the Zoar NIC, and the LOM on
Tylersburg reference designs.

Are these changes also in the Andy's latest test kernel that we are testing or the ICH9m, ICH10 and Hartwell?  If so we can test Kawela and Zoar as well.

Updating PM score.

Linking IT#225360 to this ticket because WOL didn't work on 2.6.9-78.0.1
Adding keyword regression because it has worked on 4.6.

RHEL4.6 igb    native WOL ..... OK ... RX600S4(Zoar)
RHEL5.1 igb    native WOL ..... OK ... RX600S4(Zoar)
RHEL5.2 igb    native WOL ..... OK ... RX600S4(Zoar)
RHEL4.7 igb    native WOL ..... NG ... RX600S4(Zoar)

More information:
---
The problem does not occur with OEM igb driver 1.2.44.3.
The problem does not occur with EL5.2, neither with the native igb driver 
nor with 1.2.44.3.
---

The update to latest upstream version will probably fix this issue too.

Flavio

This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being marked as a blocker for this release.  

Please resolve ASAP.

Andy,

Since we are coming up on the deadline for kernel submissions I was wondering what the status of this bug is?

John, I just haven't gotten to it yet, I'm hoping to have it done by the deadline.

Again, we are testing 5.3 at this time.  4.8 will get done after 5.3 is finished.

My test kernels have been updated to include a patch for this bugzilla.

http://people.redhat.com/agospoda/#rhel4

Please test them and report back your results.

My test kernels have been updated to include a patch for this bugzilla.

http://people.redhat.com/agospoda/#

Please test them and report back your results.  Without immediate
feedback there is a good chance this or any other fix for this driver
will not be included in the upcoming update.

Committed in 78.28.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/

fit those packages in rhel 5.2? i've the similar isue

delete my post !! i answered myself foundind the package over agospoda site's 

my apologies for all :(

Has anyone tested these patches at all?  I did some initial testing with a Kawela NIC yesterday and things were not looking good.  I should know more later today.

Basic functionality seems to be OK, but netdump isn't working.  I've already had to fix this up for another driver (so I expected this), but it will take me a little bit to get this going.

I just created some new test kernels that should make using netdump with igb-based cards more reliable.  Any testing would be greatly appreciated.

http://people.redhat.com/agospoda/#rhel4

*** Bug 475657 has been marked as a duplicate of this bug. ***

~~ Attention Partners!  ~~
RHEL 4.8 Partner Alpha has been released on partners.redhat.com. There should be a fix present in the Beta, which addresses this URGENT priority bug. If you haven't had a chance yet to test this bug, please do so at your earliest convenience, to ensure that only the highest possible quality bits are shipped in the upcoming public Beta drop.

If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager.

Thanks, more information about Beta testing to come.
 - Red Hat QE Partner Management

~~ Attention Partners!  ~~
RHEL 4.8 Partner Alpha has been released on partners.redhat.com. There should
be a fix present in the Beta, which addresses this bug. If you have already completed testing your other URGENT priority bugs, and you still haven't had a chance yet to test this bug, please do so at your earliest convenience, to ensure that only the highest possible quality bits are shipped in the upcoming public Beta drop.

If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. Further questions can be directed to your
Red Hat Partner Manager.

Thanks, more information about Beta testing to come.
 - Red Hat QE Partner Management

Ran network test in RHEL 4.8 Alpha (64 bit) with IGB Driver.  netdump did not work. Rest of the tests passed.

Thanks for the feedback.  I have some patches in my test kernels to resolve the netdump issue.

As always, they are available here:

http://people.redhat.com/agospoda/#rhel4

network tests on RHEL 4.8 alpha (32 and 64 bit)  passed with IGB and Kawela. netdump issue is being tracked by another IBM BZ # 51813.

(In reply to comment #29)
> network tests on RHEL 4.8 alpha (32 and 64 bit)  passed with IGB and Kawela.
> netdump issue is being tracked by another IBM BZ # 51813.
>

test passed on Zoar too.

Clearing needinfo since information has been provided.

~~ Attention Partners!  ~~
RHEL 4.8Beta has been released on partners.redhat.com. There should
be a fix present, which addresses this bug. Please test and report back results on this OtherQA Partner bug at your earliest convenience.

If you encounter any issues, please set the bug back to the ASSIGNED state and
describe any issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you've encountered. Further questions can be directed to your Red Hat Partner Manager.

If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs.

 - Red Hat QE Partner Management

HP verified successfully with RHEL 4.8 Beta.

Partners. I'm moving this to VERIFIED, as we've had several groups report positive test results already. The exception being, that there are some issues related to netdump. A new bug was created to track it. Please note that an updated test kernel has been posted already that should resolve the netdump issues. Please grab it and report test results to bug 484376.

https://bugzilla.redhat.com/show_bug.cgi?id=484376

If you encounter any additional issues with this update of the igb driver, please clone this bug and describe the issues you're encountering and request to your Partner Manager to have it reviewed for inclusion as an exception.

I have performed basic, minimal testing with igb 1.2.45-k2 as provided in kernel 2.6.9-87.ELsmp, x86_64. I have not encountered any undesirable behavior.

On testing to the latest 4.8 snapshot this driver is missing support for this:

#define E1000_DEV_ID_82576_NS	150A
Intel(R) 82576NS Gigabit Ethernet Controller	

device ID.  It probably needs to be added.

Committed in 89.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/

Intel, has the -89 kernel resolved the issue in comment #50?

Patch is in -89.EL kernel.

The device ID is indeed in the -89 kernel and is working in the tests so far.  So this BZ can be closed.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1024.html