From: David Miller <davem@davemloft.net>
To: aurelien@aurel32.net
Cc: bruce.w.allan@intel.com, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org
Subject: Re: IAMT broken by commit 82776a4bcd7aa5fbcd2e6339b3ce88b727dd40ab
Date: Mon, 31 Jan 2011 12:36:05 -0800 (PST) [thread overview]
Message-ID: <20110131.123605.226778418.davem@davemloft.net> (raw)
In-Reply-To: <20110131114558.GA28303@volta.aurel32.net>
From: Aurelien Jarno <aurelien@aurel32.net>
Date: Mon, 31 Jan 2011 12:45:58 +0100
>> On recent kernels, IAMT support does not work after the machine has
>> been powered-off. Even worse, it also goes into this state when I try
>> to reboot it.
>>
>> I have done a bisect and got this commit:
>>
>> | commit 82776a4bcd7aa5fbcd2e6339b3ce88b727dd40ab
>> | Author: Bruce Allan <bruce.w.allan@intel.com>
>> | Date: Fri Aug 14 14:35:33 2009 +0000
>> |
>> | e1000e: WoL does not work on 82577/82578 with manageability enabled
>> |
>> | With manageability (Intel AMT) enabled via BIOS, PHY wakeup does not get
>> | configured on newer parts which use PHY wakeup vs. MAC wakeup which causes
>> | WoL to not work. The driver should configure PHY wakeup whether or not
>> | manageability is enabled.
>> |
>> | Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>> | Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> | Signed-off-by: David S. Miller <davem@davemloft.net>
>>
>> I have tried to revert it on recent kernels (2.6.34), and IAMT is then
>> working as expected. My machine is using a Gigabyte EQ45M-S2 motherboard
>> with an 82567LM-3 ethernet chip (8086:10de), that is a different model
>> than the one of the original problem.
>>
>> I do wonder if the changes in the patch should not only be done on some
>> chip models, and I will appreciate any help in fixing this issue.
>>
>
> Just a short mail to say this problem is still present in 2.6.38-rc2.
> The same solution still applies, that is reverting the above commit.
> Note that reverting the first hunk only is enough to get it working
> again.
Intel folks please look into this.
next prev parent reply other threads:[~2011-01-31 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 1:02 IAMT broken by commit 82776a4bcd7aa5fbcd2e6339b3ce88b727dd40ab Aurelien Jarno
2010-06-01 23:33 ` Allan, Bruce W
2011-01-31 11:45 ` Aurelien Jarno
2011-01-31 20:36 ` David Miller [this message]
2011-01-31 23:24 ` Jeff Kirsher
-- strict thread matches above, loose matches on Subject: below --
2010-06-01 23:35 Kirsher, Jeffrey T
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=20110131.123605.226778418.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aurelien@aurel32.net \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.t.kirsher@intel.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;
as well as URLs for NNTP newsgroup(s).