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
| ||
|
Date: Mon, 22 Oct 2012 19:18:07 -0700 From: "Michael Chan" <mchan@...adcom.com> To: "Ben Hutchings" <ben@...adent.org.uk> cc: 690845@...s.debian.org, "Teodor MICU" <mteodor@...il.com>, netdev <netdev@...r.kernel.org> Subject: Re: Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12 On Tue, 2012-10-23 at 02:45 +0100, Ben Hutchings wrote: > Well we knew that much! Is the problem that the system firmware 'owns' > the WoL control registers so the host can't safely change them? Is it > possible to *read* the WoL configuration, if not to change it? It's a hardware problem and I don't understand all the details. There is an internal PCIX to PCIE bridge on this chip and it gates the NIC's PME event. During S5 reset, the bridge gets reset by the BIOS and the WoL setting done by the driver will no longer work. Newer chip revs have fixed the problem in hardware. The driver reads the pre-boot WoL setting from NVRAM and it becomes the ethtool WoL default setting. Apparently, it is also not working in this case. I know that it doesn't work on some LOM designs as the setting is actually in BIOS NVRAM as opposed to NIC NVRAM. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists