public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
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
Date: Sat, 11 Oct 2008 18:12:44 +0100	[thread overview]
Message-ID: <48F0DE8C.6040309@tuffmail.co.uk> (raw)
In-Reply-To: <200810111909.48897.rjw@sisk.pl>

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

  reply	other threads:[~2008-10-11 17:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 16:57 acpi-test tree on eeepc: EC error message on second resume Alan Jenkins
2008-10-11 17:09 ` Rafael J. Wysocki
2008-10-11 17:12   ` Alan Jenkins [this message]
2008-10-11 17:53     ` Rafael J. Wysocki
2008-10-11 18:15       ` Alan Jenkins
2008-10-11 18:39         ` Alexey Starikovskiy
2008-10-11 19:30           ` Rafael J. Wysocki
2008-10-11 19:31             ` Alexey Starikovskiy
2008-10-11 19:40               ` Rafael J. Wysocki
2008-10-11 19:38                 ` Alexey Starikovskiy
2008-10-11 20:54                   ` Rafael J. Wysocki
2008-10-12  9:13                     ` Alan Jenkins
2008-10-12 19:23                       ` Alexey Starikovskiy
2008-10-13  5:56                         ` Zhao Yakui
2008-10-13  8:22                         ` Alan Jenkins
2008-10-13 16:39                           ` Alan Jenkins
2008-10-15 22:02                             ` [PATCH] ACPI: EC: Check for IBF=0 periodically if not in GPE mode Alexey Starikovskiy
2008-10-16 22:14                               ` Len Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48F0DE8C.6040309@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=astarikovskiy@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox