Bug 3936 - kernel disables wake-on-lan
Summary: kernel disables wake-on-lan
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Arnaldo Carvalho de Melo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-22 07:07 UTC by gene resnik
Modified: 2006-11-12 03:39 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.9
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description gene resnik 2004-12-22 07:07:13 UTC
Distribution:Gentoo
Hardware Environment:x86, athlon xp, via-rhine
Software Environment:linux, xorg, kde
Problem Description:Two different computers - same problem: After upgrading from
2.6.7 to 2.6.9 wake-on-lan stopped working. In BIOS WoL is enabled. Checking
with ethtool shows:
Supports Wake-on: pumbg
        Wake-on: d
Doing
#ethtool -s eth0 wol g
helps for one shutdown, as soon as system boots WoL is disabled again and after
shutdown does not respond to ether-wake commands. Booting kernel 2.6.7 restores
WoL functionality.

Steps to reproduce:
Comment 1 S.Mohideen 2006-04-09 05:01:19 UTC
Does the problem still persists in latest kernel release 2.6.16
Comment 2 gene resnik 2006-04-09 17:30:20 UTC
> ------- Does the problem still persists in latest kernel release 2.6.16
I have no idea, but thanks for prompt response.

On Sunday 09 April 2006 5:01 am, you wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=3936
>
> root@switch.net.in changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- Summary|kernel disables wake-on-lan |kernel disables wake-on-lan
>
>
>
> ------- Additional Comments From root@switch.net.in  2006-04-09 05:01
> ------- Does the problem still persists in latest kernel release 2.6.16
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.

Comment 3 Adrian Bunk 2006-11-12 03:39:00 UTC
Please reopen this bug if it's still present in kernel 2.6.18.

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