From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Alexey Starikovskiy <aystarik@gmail.com>,
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: Mon, 13 Oct 2008 17:39:32 +0100 [thread overview]
Message-ID: <48F379C4.9070105@tuffmail.co.uk> (raw)
In-Reply-To: <48F30554.1010607@tuffmail.co.uk>
Alan Jenkins wrote:
> Alexis Starikovskiy wrote:
>
>> Alan Jenkins wrote:
>>
>>> Rafael J. Wysocki wrote:
>>>
>>>> On Saturday, 11 of October 2008, Alexey Starikovskiy wrote:
>>>>
>>>>
>>>>> Rafael J. Wysocki wrote:
>>>>>
>>>>>
>>>>>>> No, we discussed this before -- we are outside of the
>>>>>>> transaction, thus no GPE
>>>>>>> activity could interfere with ec_check_ibf0.
>>>>>>>
>>>>>>>
>>>>>> Ok, this is in the process context and we don't really expect to
>>>>>> get an
>>>>>> interrupt at this point, but what happens if the EC generates an
>>>>>> event that's
>>>>>> not related to any transiaction. Is that guaranteed to never happen?
>>>>>>
>>>>>>
>>>>> Interrupt handler in this case can't cause a change to status
>>>>> register, thus our read of it will not be affected by interrupt.
>>>>>
>>>>>
>>>> Ok, thanks.
>>>>
>>>> Alan, does the patch work for you?
>>>>
>>>> Rafael
>>>>
>>>>
>>> Yes. Two reboot cycles, three suspend/resume cycles each, and no error
>>> message.
>>>
>>> I hope we have a better fix in mind though :-P. The patch doesn't solve
>>> the unnecessary 500ms delay when this thing happens.
>>>
>> Something like this?
>>
>> Regards,
>> Alex.
>>
>
> You sent it as an attachment again :-).
>
> That should work, odd as it looks. We don't need to worry about the GPE
> workaround because that's only active _inside_ the transaction. I don't
> know what Zhao thinks is missing.
>
> Sorry I can't test right now. I tried to install 3D support on my
> laptop for showing-off purposes, and somehow broke X.
>
Drama over, I've now tested it. No error messages, and the printk
timings show that it has stopped hanging for half a second.
Thanks
Alan
next prev parent reply other threads:[~2008-10-13 16:39 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
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 [this message]
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=48F379C4.9070105@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--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