| Summary: | device e1000e: probe of 0000:00:19.0 failed with error -3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Konstantin Olchanski <olchansk> |
| Component: | kernel | Assignee: | Andy Gospodarek <agospoda> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.5 | CC: | jarod, jstancek, peterm |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-17 01:26:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Konstantin Olchanski
2011-03-01 23:27:05 UTC
I hit this with 2.6.18-238.el5. I was at the console at the time, so I tried rmmod/modprobe, which didn't help. Issue was gone only after next reboot.
00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 06)
Subsystem: Hewlett-Packard Company Device 170b
Kernel modules: e1000e
[root@machine ~]# rmmod e1000e
[root@machine ~]# modprobe e1000e
PCI: Enabling device 0000:00:19.0 (0100 -> 0102)
e1000e: probe of 0000:00:19.0 failed with error -3
Is this still a problem with RHEL5.7 (kernels 2.6.18-274.el5) and later? I'm seeing this with all newer drivers, so I do not expect this to be resolved with RHEL5.7. (In reply to comment #0) > > my mobo is Intel DP55WG socket 1156, CPU is i7-860. > > K.O. What does 'ethtool -i eth0' output look like for this system? I have worked with Intel and they tested this same motherboard with the firmware listed as: firmware-version: 0.12-2 and they cannot reproduce the problem. Please reopen if your firmware is listed as the following version or later and you can still reproduce. If your firmware is an earlier version a BIOS update should update it. |