DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding
         :sender;
        b=tryjvjOxmNJQu9ALU3fABQC70gzEO5nI2F31ywGfA44QiRL/2yWzSw4YpXGePqWLXi
         Y7QhbWRqpGTceJ6dERF1Rp5tEWO8Mx2vc7uNMnLQZhjoR+KQx8/wPbYMnUM3j1V5Gjgr
         UveJUMhDP7s6sl3Zb6/yKBOoTwVYqYESCot5M=
Message-ID: <48F0DE8C.6040309@tuffmail.co.uk>
Date: Sat, 11 Oct 2008 18:12:44 +0100
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: "Rafael J. Wysocki" <rjw@sisk.pl>
CC: Alexey Starikovskiy <astarikovskiy@suse.de>,
       linux acpi <linux-acpi@vger.kernel.org>,
       linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: acpi-test tree on eeepc: EC error message on second resume
References: <48F0DB0C.7060201@tuffmail.co.uk> <200810111909.48897.rjw@sisk.pl>
In-Reply-To: <200810111909.48897.rjw@sisk.pl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1492
Lines: 40

Rafael J. Wysocki wrote:
> On Saturday, 11 of October 2008, Alan Jenkins wrote:
>   
>> I've just run an acpi-test kernel on my EeePC and noticed a new issue. 
>> It seems to be caused (or revealed) by the EC interrupt transaction patch.
>>
>> On the second suspend/resume cycle, I see a kernel error message.
>>
>> [   78.747707] ACPI: Waking up from system sleep state S3
>> [   79.330001] ACPI: EC: input buffer not empty, aborting transaction
>> [   79.423327] ACPI: EC: non-query interrupt received, switching to
>> interrupt mode
>>
>> I still don't see any issues in the code.  I'll try getting a DEBUG
>> trace to see the EC interrupts.  Any other suggestions?
>>     
>
> Not really, but is this reproducible?  I mean, does it happen always on the
> second resume and does it happen on every next resume after the first one?
>
> Thanks,
> Rafael
>   

Ah.  No, I spoke to soon.  It happened on the second resume the first
two times I tried it.  But this third time with DEBUG enabled, it
happened on the first suspend/resume.

And it doesn't happen on all subsequent resumes either.  I've had one
suspend/resume without the error, just after a suspend/resume with the
error.

So it's not deterministic, but it is easy to reproduce.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/