From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Jenkins Subject: Re: acpi-test tree on eeepc: EC error message on second resume Date: Sat, 11 Oct 2008 18:12:44 +0100 Message-ID: <48F0DE8C.6040309@tuffmail.co.uk> References: <48F0DB0C.7060201@tuffmail.co.uk> <200810111909.48897.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from nf-out-0910.google.com ([64.233.182.190]:24948 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760091AbYJKRMt (ORCPT ); Sat, 11 Oct 2008 13:12:49 -0400 Received: by nf-out-0910.google.com with SMTP id d3so469731nfc.21 for ; Sat, 11 Oct 2008 10:12:47 -0700 (PDT) In-Reply-To: <200810111909.48897.rjw@sisk.pl> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Alexey Starikovskiy , linux acpi , linux-kernel 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