From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aurelien Jarno <aurelien@aurel32.net>
Subject: IAMT broken by commit 82776a4bcd7aa5fbcd2e6339b3ce88b727dd40ab
Date: Sun, 30 May 2010 03:02:19 +0200
Message-ID: <20100530010219.GA20368@volta.aurel32.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: netdev@vger.kernel.org
To: Bruce Allan <bruce.w.allan@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from hall.aurel32.net ([88.191.82.174]:41826 "EHLO hall.aurel32.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753114Ab0E3BmL (ORCPT <rfc822;netdev@vger.kernel.org>);
	Sat, 29 May 2010 21:42:11 -0400
Content-Disposition: inline
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

Hi,

I have recently upgrade my kernel, and found that Intel AMT support is
not working anymore as expected. I have configured IAMT so that is=20
always available, even when the machine is off ("Desktop: ON in S0, S3,
S4-5").

On recent kernels, IAMT support does not work after the machine has=20
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:

|=A0commit 82776a4bcd7aa5fbcd2e6339b3ce88b727dd40ab
| Author: Bruce Allan <bruce.w.allan@intel.com>
| Date:   Fri Aug 14 14:35:33 2009 +0000
|=20
|     e1000e: WoL does not work on 82577/82578 with manageability enabl=
ed
|    =20
|     With manageability (Intel AMT) enabled via BIOS, PHY wakeup does =
not get
|     configured on newer parts which use PHY wakeup vs. MAC wakeup whi=
ch causes
|=A0    WoL to not work.  The driver should configure PHY wakeup whethe=
r or not
|     manageability is enabled.
|    =20
|     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 motherboar=
d
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=
=20
chip models, and I will appreciate any help in fixing this issue.

Thanks,
Aurelien


--=20
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net