From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-pm@lists.linux-foundation.org,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [linux-pm] ACPI/ACPICA: resume hang (battery related)
Date: Sun, 22 Nov 2009 15:15:18 +0100 [thread overview]
Message-ID: <200911221515.18735.rjw@sisk.pl> (raw)
In-Reply-To: <1258896971.3432.6.camel@maxim-laptop>
On Sunday 22 November 2009, Maxim Levitsky wrote:
> I had just disabled the AC driver, yeah, got similar backtrace from acpi
> video driver.
>
> Ok, enough, pattern is visible.
> The common point is that all backtraces lead to
> acpi_ex_acquire_global_lock
>
> According to sources, it is only taken on access to ACPI hardware ranges
> that are marked as 'Lock'.
>
> On my system only EC space is marked as such, thus this leads me to two
> conclusions.
>
> Ether during suspend EC access isn't synced (this is, EC transaction is
> still pending),or that EC gets busted (suprise...) on resume or suspend,
> and first read/write cycle to/from it never finishes.
>
> I am using hibernate cycles using 'reboot' mechanism.
OK, at this point I think it's better to file a bug report in the kernel
and assign it to ACPI (please add my address to the CC list in there).
Thanks,
Rafael
next prev parent reply other threads:[~2009-11-22 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 20:59 ACPI/ACPICA: resume hang (battery related) Maxim Levitsky
2009-11-19 21:55 ` Rafael J. Wysocki
2009-11-19 21:55 ` [linux-pm] " Rafael J. Wysocki
2009-11-19 22:37 ` Maxim Levitsky
2009-11-19 22:37 ` [linux-pm] " Maxim Levitsky
2009-11-22 12:20 ` Maxim Levitsky
2009-11-22 13:36 ` Maxim Levitsky
2009-11-22 13:36 ` [linux-pm] " Maxim Levitsky
2009-11-22 14:15 ` Rafael J. Wysocki [this message]
2009-11-22 14:15 ` Rafael J. Wysocki
2009-11-22 12:20 ` Maxim Levitsky
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=200911221515.18735.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.