From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: spinlock bad magic on CPU#0
Date: Fri, 14 Jan 2011 23:51:18 +0200 [thread overview]
Message-ID: <20110114215118.GA3893@swordfish> (raw)
In-Reply-To: <201101142209.35892.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
On (01/14/11 22:09), Rafael J. Wysocki wrote:
> > Hello,
>
> Does the appended patch help?
>
>
Hello,
Yes, it does. Seems to be fixed.
Tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Thanks,
Sergey
> ---
> drivers/acpi/acpica/acglobal.h | 2 ++
> drivers/acpi/acpica/evmisc.c | 2 --
> drivers/acpi/acpica/utmutex.c | 1 +
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> Index: linux-2.6/drivers/acpi/acpica/acglobal.h
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/acpica/acglobal.h
> +++ linux-2.6/drivers/acpi/acpica/acglobal.h
> @@ -228,8 +228,10 @@ ACPI_EXTERN u8 acpi_gbl_global_lock_pres
> */
> ACPI_EXTERN spinlock_t _acpi_gbl_gpe_lock; /* For GPE data structs and registers */
> ACPI_EXTERN spinlock_t _acpi_gbl_hardware_lock; /* For ACPI H/W except GPE registers */
> +ACPI_EXTERN spinlock_t _acpi_ev_global_lock_pending_lock; /* For global lock */
> #define acpi_gbl_gpe_lock &_acpi_gbl_gpe_lock
> #define acpi_gbl_hardware_lock &_acpi_gbl_hardware_lock
> +#define acpi_ev_global_lock_pending_lock &_acpi_ev_global_lock_pending_lock
>
> /*****************************************************************************
> *
> Index: linux-2.6/drivers/acpi/acpica/evmisc.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/acpica/evmisc.c
> +++ linux-2.6/drivers/acpi/acpica/evmisc.c
> @@ -293,8 +293,6 @@ static void ACPI_SYSTEM_XFACE acpi_ev_no
> *
> ******************************************************************************/
> static u8 acpi_ev_global_lock_pending;
> -static spinlock_t _acpi_ev_global_lock_pending_lock;
> -#define acpi_ev_global_lock_pending_lock &_acpi_ev_global_lock_pending_lock
>
> static u32 acpi_ev_global_lock_handler(void *context)
> {
> Index: linux-2.6/drivers/acpi/acpica/utmutex.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/acpica/utmutex.c
> +++ linux-2.6/drivers/acpi/acpica/utmutex.c
> @@ -85,6 +85,7 @@ acpi_status acpi_ut_mutex_initialize(voi
>
> spin_lock_init(acpi_gbl_gpe_lock);
> spin_lock_init(acpi_gbl_hardware_lock);
> + spin_lock_init(acpi_ev_global_lock_pending_lock);
>
> /* Mutex for _OSI support */
> status = acpi_os_create_mutex(&acpi_gbl_osi_mutex);
>
[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-01-14 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 14:08 BUG: spinlock bad magic on CPU#0 Sergey Senozhatsky
2011-01-14 19:26 ` Len Brown
2011-01-14 21:09 ` Rafael J. Wysocki
2011-01-14 21:51 ` Sergey Senozhatsky [this message]
2011-01-14 22:25 ` Rafael J. Wysocki
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=20110114215118.GA3893@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=lenb@kernel.org \
--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