Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 565496 - e1000e: wol is broken in kernel 2.6.9-89.19 [rhel-4.8.z]
e1000e: wol is broken in kernel 2.6.9-89.19 [rhel-4.8.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.9
All Linux
medium Severity medium
: rc
: ---
Assigned To: Vitaly Mayatskikh
Red Hat Kernel QE team
: ZStream
Depends On: 558607
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-15 08:43 EST by RHEL Product and Program Management
Modified: 2013-01-10 21:47 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-16 20:47:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0146 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-03-16 20:46:47 EDT

  None (edit)
Description RHEL Product and Program Management 2010-02-15 08:43:00 EST
This bug has been copied from bug #558607 and has been proposed
to be backported to 4.8 z-stream (EUS).
Comment 2 Vitaly Mayatskikh 2010-02-25 05:05:10 EST
Committed in 89.0.22.EL
Comment 8 Andy Gospodarek 2010-03-05 15:29:57 EST
I tested -89.0.21.EL and -89.0.22.EL, but WoL appears to be disabled on both.
Comment 14 errata-xmlrpc 2010-03-16 20:47:28 EDT
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-0146.html

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