| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1196199297.7323.10.camel@dell> Date: Tue, 27 Nov 2007 13:34:57 -0800 From: "Michael Chan" <mchan@...adcom.com> To: Valdis.Kletnieks@...edu cc: linux-kernel@...r.kernel.org, "netdev" <netdev@...r.kernel.org> Subject: Re: 2.6.23-mm1 tg3 wake-on-lan oddity... On Tue, 2007-11-27 at 01:35 -0800, Valdis.Kletnieks@...edu wrote: > > Issue: > > I (for unrelated reasons) run powertop, and it suggests I conserve power > by doing 'ethtool -s eth0 wol d'. I look at it, and think that it's daft, > because (a) the Dell factory default is WOL disabled and (b) if it wasn't > the default, I'd have *set* it to disabled, and (c) I even went back and > rebooted and checked the BIOS setting - disabled. Nonetheless: > > # ethtool eth0 | grep Wake > Supports Wake-on: g > Wake-on: g > > Is this expected behavior? What's happening is that there are 2 WoL settings: one in the BIOS and one in the NIC's NVRAM. For WoL to work, I think both settings have to be enabled. Apparently in this case, when you turn off WoL in the BIOS, the NVRAM's WoL setting is unchanged, and will be seen by tg3 as enabled. Ideally, the BIOS should modify the NVRAM's setting when it is changed. We will talk to Dell to get their opinion on this as this is very confusing to the user. Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists