From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ec locking issue
Date: Thu, 15 Feb 2007 23:16:18 +0300 [thread overview]
Message-ID: <45D4BF92.5050401@linux.intel.com> (raw)
In-Reply-To: <20070215192616.GA31595@isilmar.linta.de>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Hi,
ec is locked only in acpi_ec_transaction, and it is only once in your
stack.
I doubt that this patch could change something, but worth a try...
Is bisect finds something?
Regards,
Alex.
Dominik Brodowski wrote:
> Hi,
>
> Current kernels (e.g. 2.6.20-git-as-of-yesterday) don't boot for me, and
> it seems like ACPI is the cause: the last thing I can see in the log is
>
> swapper/1 is trying to acquire lock
> &ec->lock
>
> but task is already holding lock
> &ec->lock
>
> Snippets from the call trace:
>
> acpi_ec_transaction
> acpi_ec_read
> acpi_ec_space_handler
> acpi_ev_address_space_dispatch
> acpi_ex_access_region
> acpi_ex_field_datum_
> acpi_ex_extract_from_field
> ...
> acpi_ex_ns_evaluate
> acpi_ev_execute_reg_method
> acpi_ev_reg_run
> acpi_ns_walk_namespace
> acpi_ev_execute_reg_methods
> acpi_install_address_space_handler
> acpi_ec_start
> acpi_start_single_object
> acpi_device_probe
> really_probe
> ...
> bus_add_driver
> ...
> acpi_ec_init
>
>
>
> Ideas? Patches?
>
> Thanks,
> Dominik
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: ec_unlock_mutex_in_error_path.patch --]
[-- Type: text/plain, Size: 483 bytes --]
diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index 743ce27..8f5aaf7 100644
--- a/drivers/acpi/ec.c
+++ b/drivers/acpi/ec.c
@@ -280,8 +280,10 @@ static int acpi_ec_transaction(struct ac
mutex_lock(&ec->lock);
if (ec->global_lock) {
status = acpi_acquire_global_lock(ACPI_EC_UDELAY_GLK, &glk);
- if (ACPI_FAILURE(status))
+ if (ACPI_FAILURE(status)) {
+ mutex_unlock(&ec->lock);
return -ENODEV;
+ }
}
/* Make sure GPE is enabled before doing transaction */
next prev parent reply other threads:[~2007-02-15 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 19:26 ec locking issue Dominik Brodowski
2007-02-15 20:16 ` Alexey Starikovskiy [this message]
2007-02-16 17:54 ` Len Brown
2007-02-19 13:44 ` Dominik Brodowski
2007-02-19 21:45 ` Dominik Brodowski
2007-02-20 18:24 ` Alexey Starikovskiy
2007-02-20 19:59 ` Dominik Brodowski
2007-02-20 22:07 ` Alexey Starikovskiy
2007-02-22 1:04 ` Dominik Brodowski
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=45D4BF92.5050401@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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