Bug 559335 - e1000e: wol is broken on 2.6.18-185.el5 [rhel-5.4.z]
Summary: e1000e: wol is broken on 2.6.18-185.el5 [rhel-5.4.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Andy Gospodarek
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 557974
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-27 19:26 UTC by RHEL Program Management
Modified: 2014-06-29 23:02 UTC (History)
6 users (show)

Fixed In Version: kernel-2.6.18-164.13.1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-17 00:19:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhel54z-e1000e-wol.patch (3.10 KB, patch)
2010-02-09 20:35 UTC, Andy Gospodarek
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0147 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-03-17 00:18:44 UTC

Description RHEL Program Management 2010-01-27 19:26:28 UTC
This bug has been copied from bug #557974 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 3 Andy Gospodarek 2010-02-09 20:35:08 UTC
Created attachment 389843 [details]
rhel54z-e1000e-wol.patch

Proposed patch against 5.4.z.  I should have test results shortly.

Comment 4 Andy Gospodarek 2010-02-09 21:37:57 UTC
Tested against 2.6.18-164.12.1.el5 and the attached patch works well.

Comment 6 Jiri Pirko 2010-02-10 07:40:47 UTC
in 2.6.18-164.13.1.el5

Comment 12 errata-xmlrpc 2010-03-17 00:19:37 UTC
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-2010-0147.html


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