From: "Michael Chan" <mchan@broadcom.com>
To: "Ben Hutchings" <ben@decadent.org.uk>
Cc: 690845@bugs.debian.org, "Teodor MICU" <mteodor@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12
Date: Mon, 22 Oct 2012 19:18:07 -0700 [thread overview]
Message-ID: <1350958687.8764.170.camel@LTIRV-MCHAN1.corp.ad.broadcom.com> (raw)
In-Reply-To: <1350956707.5283.48.camel@deadeye.wl.decadent.org.uk>
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.
next prev parent reply other threads:[~2012-10-23 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121018134717.9579.22997.reportbug@palomino.museglobal.com>
[not found] ` <1350570748.26833.102.camel@deadeye.wl.decadent.org.uk>
[not found] ` <CAG2Wgfee=qsiUhAk5reYTypcOZL0kM5A58J+LjB1wuQ_k9FrfA@mail.gmail.com>
2012-10-19 1:30 ` Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12 Ben Hutchings
2012-10-19 19:38 ` Michael Chan
2012-10-22 7:52 ` Teodor MICU
2012-10-22 22:54 ` Michael Chan
2012-10-23 1:45 ` Ben Hutchings
2012-10-23 2:18 ` Michael Chan [this message]
2012-10-24 14:23 ` Ben Hutchings
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=1350958687.8764.170.camel@LTIRV-MCHAN1.corp.ad.broadcom.com \
--to=mchan@broadcom.com \
--cc=690845@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=mteodor@gmail.com \
--cc=netdev@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