Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 607264 - [RHEL 6.0] e1000e: add PCI device id to enable support for 82567V-4
[RHEL 6.0] e1000e: add PCI device id to enable support for 82567V-4
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Andy Gospodarek
Network QE
Depends On:
  Show dependency treegraph
Reported: 2010-06-23 12:33 EDT by Andy Gospodarek
Modified: 2010-11-11 11:09 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-11 11:09:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andy Gospodarek 2010-06-23 12:33:51 EDT
I was just doing some last-minute auditing of the e1000e driver and see we do
not have support for this ID upstream:

E1000_DEV_ID_ICH10_D_BM_V (0x1525)

Need to add this so RHEL6 hardware support matches upstream.

commit 10df0b9116e2039d5585a196753e5f36d7afcba2
Author: Bruce Allan <bruce.w.allan@intel.com>
Date:   Mon May 10 15:02:52 2010 +0000

    e1000e: add PCI device id to enable support for 82567V-4
Comment 1 RHEL Product and Program Management 2010-06-23 12:52:52 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 3 Aristeu Rozanski 2010-07-01 12:13:00 EDT
Patch(es) available on kernel-2.6.32-42.el6
Comment 7 releng-rhel@redhat.com 2010-11-11 11:09:48 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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