From: Len Brown <lenb@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: spinlock bad magic on CPU#0
Date: Fri, 14 Jan 2011 14:26:08 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1101141424330.9760@x980> (raw)
In-Reply-To: <20110114140803.GA4003@swordfish>
On Fri, 14 Jan 2011, Sergey Senozhatsky wrote:
> Hello,
>
> Acer Aspire 5741g
> 2.6.37-git11
>
> Got this trace today:
>
> [ 0.814609] ACPI: EC: Look up EC in DSDT
> [ 0.825556] BUG: spinlock bad magic on CPU#0, swapper/1
> [ 0.825639] lock: ffffffff8242fa90, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> [ 0.825741] Pid: 1, comm: swapper Not tainted 2.6.37-dbg-git11-07456-gdbc61c6-dirty #359
> [ 0.825841] Call Trace:
> [ 0.825923] [<ffffffff81247919>] ? spin_bug+0x9c/0xa3
> [ 0.826004] [<ffffffff812479e9>] ? do_raw_spin_lock+0x29/0x122
> [ 0.826093] [<ffffffff814867e5>] ? _raw_spin_lock_irqsave+0x56/0x60
> [ 0.826181] [<ffffffff81275e8a>] ? acpi_os_acquire_lock+0x9/0xb
> [ 0.826264] [<ffffffff81275e8a>] ? acpi_os_acquire_lock+0x9/0xb
> [ 0.826350] [<ffffffff81288fad>] ? acpi_ev_acquire_global_lock+0x10b/0x206
> [ 0.826438] [<ffffffff8129620c>] ? acpi_ex_acquire_mutex_object+0xa3/0x11d
> [ 0.826525] [<ffffffff812952e3>] ? acpi_ex_acquire_global_lock+0x61/0xa2
Does the failure go away if you revert this commit?
commit 9cd031441a4fd09273b7c2beb337d0b2683d104c
ACPI / ACPICA: Fix global lock acquisition
thanks,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-14 19:26 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 [this message]
2011-01-14 21:09 ` Rafael J. Wysocki
2011-01-14 21:51 ` Sergey Senozhatsky
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=alpine.LFD.2.02.1101141424330.9760@x980 \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox