From: Martin Volf <mv@inv.cz>
To: linux-kernel@vger.kernel.org
Subject: e1000, 2.6.1[34] - WOL not working
Date: Sun, 27 Nov 2005 15:29:05 +0100 [thread overview]
Message-ID: <4389C2B1.5020001@inv.cz> (raw)
Hello,
with 2.6.13 and 2.6.14, after I shutdown the computer I can't wake it up with
the "MagicPacket" over the network. With 2.6.12 and 2.6.12.x it is working.
Steps to reproduce:
Boot 2.6.14, "ethtool -s eth0 wol g", press the power button, acpid runs
"/sbin/init 0", the computer poweroffs, the link LED on the switch goes off
and WOL is not working. With 2.6.12 the link remains on and WOL is working.
More mystery:
When I pull out the power cord for a while after the shutdown from 2.6.14, the
link LED on the switch goes on and WOL is working. So it looks like 2.6.13 and
.14 is in fact disabling the WOL.
Distribution: Gentoo
Hardware Environment:
CPU P4 with HT, MB Asus P4C800-E Deluxe (Intel 875P chipset) with onboard
e1000 (Intel 82547EI) connected to a 10/100 switch
Software Environment:
latest BIOS
SMP kernel, more info: http://columbia.dragon.cz/~volf/wol_problem/
ver_linux says:
Gnu C 3.3.6
Gnu make 3.80
binutils 2.15.92.0.2
util-linux 2.12r
mount 2.12r
module-init-tools 3.0
e2fsprogs 1.38
reiserfsprogs 3.6.19
reiser4progs line
nfs-utils 1.0.6
Linux C Library 2.3.5
Dynamic linker (ldd) 2.3.5
Procps 3.2.5
Net-tools 1.60
Kbd 1.12
Sh-utils 5.2.1
udev 070
Modules Loaded radeon intel_agp drm agpgart nfsd exportfs lockd sunrpc
microcode w83627hf i2c_sensor i2c_isa i2c_i801 e1000 snd_pcm_oss snd_mixer_oss
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_bt87x
snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page_alloc
usblp sata_promise libata scsi_mod uhci_hcd ehci_hcd usbcore loop tuner
tvaudio bttv video_buf firmware_class i2c_algo_bit v4l2_common btcx_risc
tveeprom i2c_core videodev ide_cd cdrom
Contents of some /proc files, output of lspci -vvvx and the .config are here:
http://columbia.dragon.cz/~volf/wol_problem/
--
Martin Volf
reply other threads:[~2005-11-27 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4389C2B1.5020001@inv.cz \
--to=mv@inv.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox