[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48F0DE8C.6040309@tuffmail.co.uk>
Date: Sat, 11 Oct 2008 18:12:44 +0100
From: Alan Jenkins <alan-jenkins@...fmail.co.uk>
To: "Rafael J. Wysocki" <rjw@...k.pl>
CC: Alexey Starikovskiy <astarikovskiy@...e.de>,
linux acpi <linux-acpi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: acpi-test tree on eeepc: EC error message on second resume
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists