RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 590335 - e1000e fails probe, RHEL 5 works
Summary: e1000e fails probe, RHEL 5 works
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Andy Gospodarek
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-08 22:14 UTC by Pete Zaitcev
Modified: 2014-06-29 23:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-23 15:11:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dmesg - RHEL 5 works ok (24.38 KB, text/plain)
2010-05-08 22:15 UTC, Pete Zaitcev 		no flags Details
dmesg - failed probe (41.33 KB, text/plain)
2010-05-08 22:16 UTC, Pete Zaitcev 		no flags Details
suggested patch from upstream (801 bytes, patch)
2010-05-11 04:05 UTC, Pete Zaitcev 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 15944 0 None None None Never

Description Pete Zaitcev 2010-05-08 22:14:15 UTC 
Description of problem:

When loading e1000e, the interface is not detected and cannot be brought up.
The following is seen in dmesg:

e1000e: probe of 0000:00:19.0 failed with error -2

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

2.6.32-19.el6.x86_64

How reproducible:

Synchronous, but needs a given hardware

Steps to Reproduce:
1. Reboot
2. modprobe e1000e
  
Actual results:

Failure to detect and initialize the interface

Expected results:

Working like RHEL 5

Additional info:

Upstream never had it working right, I think. Something is special
about the e1000e driver in RHEL 5, but I don't know what. Hasn't
tried to diff them yet.
Comment 1 Pete Zaitcev 2010-05-08 22:15:25 UTC 
Created attachment 412579 [details]
dmesg - RHEL 5 works ok
Comment 2 Pete Zaitcev 2010-05-08 22:16:53 UTC 
Created attachment 412580 [details]
dmesg - failed probe
Comment 4 RHEL Program Management 2010-05-08 23:26:37 UTC 
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
inclusion.
Comment 5 Pete Zaitcev 2010-05-11 04:05:22 UTC 
Created attachment 413037 [details]
suggested patch from upstream
Comment 6 Andy Gospodarek 2010-05-18 15:19:05 UTC 
Pete, I presume the patch attached in comment#5 fixes the issue for you?

Did a BIOS update fix it too or were you not able to try that?

For reference this is the upstream patch in comment #5:

commit 627c8a041f7aaaea93c766f69bd61d952a277586
Author: Bruce Allan <bruce.w.allan>
Date:   Wed May 5 22:00:27 2010 +0000

    e1000e: Reset 82577/82578 PHY before first PHY register read
Comment 7 Pete Zaitcev 2010-05-18 23:27:38 UTC 
Unfortunately, no, the patch in comment #5 does not work. It was suggested
that the firmware update may fix it on this box (Intel D3CB1). I'm trying
to find it. Our QA folks supposedly had an ISO somewhere (Intel Premier
seems sadly useless, therefore the delay).
Comment 8 Andy Gospodarek 2010-05-19 00:06:47 UTC 
That's too bad.  I've been seeing errors with e1000e lately that appear to be 'fixed in firmware' but I've been holding out hope that there are some software workarounds too.  Looks like that is not the case with this one. :-/
Comment 9 RHEL Program Management 2010-07-15 14:09:56 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 10 Andy Gospodarek 2010-07-15 14:16:11 UTC 
Pete, can you test the latest kernel again?  I've added a bunch of e1000e patches since you opened this -- several of them resolved PHY issues.  Also did this only happen when PXE booting or all the time?
Comment 11 Pete Zaitcev 2010-07-15 16:34:00 UTC 
I can test. Do you mean latest upstream or latest RHEL 6? If upstream,
from what tree (I would prefer Linus' -rcX tip).

BTW, the firmware upgrade fell through. Intel posted an update, but they
specifically excluded the mainboard type that I have as too old.
Comment 12 Andy Gospodarek 2010-07-15 18:05:03 UTC 
Latest RHEL6, was all I was asking.  You can test the latest from Linus' tree if you like for a data-point if you like.

If this is an Intel SDV that they are no longer supporting we can try and make something work, but unfortunately their lack of support doesn't make me interested in working too much on it either.

I can find a way to ship you another card if you really need one. :-)
Comment 13 Pete Zaitcev 2010-07-23 15:11:40 UTC 
Latest git of RHEL6 (2.6.32-50) isn't helping.
I think it's a lost cause, closing.
Note You need to log in before you can comment on or make changes to this bug.