From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Regression: ACPI AC driver doesn't work on Toshiba Portege R500 (bisected) Date: Mon, 24 Nov 2008 00:37:15 +0100 Message-ID: <200811240037.15835.rjw@sisk.pl> References: <200811230053.14211.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:39768 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750837AbYKWXh3 (ORCPT ); Sun, 23 Nov 2008 18:37:29 -0500 In-Reply-To: <200811230053.14211.rjw@sisk.pl> Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: ACPI Devel Maling List Cc: Alexey Starikovskiy , Len Brown , LKML , Zhang Rui , walken On Sunday, 23 of November 2008, Rafael J. Wysocki wrote: > Hi, > > With current mainline (2.6.28-rc6-git1 as of today) on Toshiba Portege R500 the > status of the AC adapter is not updated when the adapter is unplugged and > plugged in. Evidently, /sys/class/power_supply/ADP1/online always contains the > same value. Interestingly enough, though, if the box is suspended to RAM and > resumed, the status of the AC adapter is correctly updated, but the value read > at that time remains in /sys/class/power_supply/ADP1/online until the next > suspend/resume cycle regardless of what's going on with the AC adapter. > > 2.6.27.7 works correctly on this box so the recent EC patches don't seem to > cause this regression to happen. > > Any other ideas? The problem was introduced by the following commit: commit faee816b1502385dc9bc5abf2960d1cc645844d1 Author: Zhang Rui Date: Fri Sep 12 11:12:25 2008 +0800 ACPI: don't enable control method power button as wakeup device when Fixed Power button is used don't enable control method power button as wakeup device when Fixed Power button is used. http://bugzilla.kernel.org/show_bug.cgi?id=10503 Tested-by: walken@zoy.org Signed-off-by: Zhang Rui Signed-off-by: Len Brown Reverting this commit on top of the current mainline makes the kernel behave correctly again. Thanks, Rafael