From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932254AbYJKRtL (ORCPT ); Sat, 11 Oct 2008 13:49:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932162AbYJKRs4 (ORCPT ); Sat, 11 Oct 2008 13:48:56 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:58849 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932161AbYJKRs4 (ORCPT ); Sat, 11 Oct 2008 13:48:56 -0400 From: "Rafael J. Wysocki" To: Alan Jenkins Subject: Re: acpi-test tree on eeepc: EC error message on second resume Date: Sat, 11 Oct 2008 19:53:04 +0200 User-Agent: KMail/1.9.9 Cc: Alexey Starikovskiy , linux acpi , "linux-kernel" References: <48F0DB0C.7060201@tuffmail.co.uk> <200810111909.48897.rjw@sisk.pl> <48F0DE8C.6040309@tuffmail.co.uk> In-Reply-To: <48F0DE8C.6040309@tuffmail.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810111953.04610.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday, 11 of October 2008, Alan Jenkins wrote: > 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. I can't reproduce this on any hardware available to me, so far. Is this related to any other problem, like things not working etc.? Rafael