From: Aaron Lu <aaron.lu@intel.com>
To: maciej.rutecki@gmail.com, Mandeep Singh Baines <msb@chromium.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, ibm-acpi@hmh.eng.br,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [REGRESSION] [3.9-rc1] BUG: ktpacpi_nvramd/446 still has locks held!
Date: Tue, 05 Mar 2013 15:28:29 +0800 [thread overview]
Message-ID: <51359E9D.7040802@intel.com> (raw)
In-Reply-To: <201303042055.38040.maciej.rutecki@gmail.com>
On 03/05/2013 03:55 AM, Maciej Rutecki wrote:
> Last known good: 3.8.0
> Bad version: 3.9-rc1
>
> [ 6.116492] =====================================
> [ 6.116614] [ BUG: ktpacpi_nvramd/446 still has locks held! ]
> [ 6.116737] 3.9.0-rc1 #1 Not tainted
> [ 6.116821] -------------------------------------
> [ 6.116900] 1 lock held by ktpacpi_nvramd/446:
> [ 6.116973] #0: (&hotkey_thread_mutex){+.+...}, at: [<ffffffffa024e87e>]
> hotkey_kthread+0x1f/0x354 [thinkpad_acpi]
> [ 6.117193]
> [ 6.117193] stack backtrace:
> [ 6.117268] Pid: 446, comm: ktpacpi_nvramd Not tainted 3.9.0-rc1 #1
> [ 6.117381] Call Trace:
> [ 6.117445] [<ffffffff810877ea>] debug_check_no_locks_held+0x8f/0x93
> [ 6.117600] [<ffffffff8107d8ac>] set_freezable+0x3e/0x64
> [ 6.117703] input: ThinkPad Extra Buttons as
> /devices/platform/thinkpad_acpi/input/input5
> [ 6.117918] [<ffffffffa024e890>] hotkey_kthread+0x31/0x354 [thinkpad_acpi]
> [ 6.118088] [<ffffffffa024e85f>] ? issue_volchange.29885+0x54/0x54
> [thinkpad_acpi]
> [ 6.118250] [<ffffffff8105e296>] kthread+0xac/0xb4
> [ 6.118356] [<ffffffff8105e1ea>] ? __kthread_parkme+0x60/0x60
> [ 6.118491] [<ffffffff814b243c>] ret_from_fork+0x7c/0xb0
> [ 6.118614] [<ffffffff8105e1ea>] ? __kthread_parkme+0x60/0x60
>
> Config:
> http://mrutecki.pl/download/kernel/3.9.0-rc1/config-3.9.0-rc1
>
> full dmesg:
> http://mrutecki.pl/download/kernel/3.9.0-rc1/dmesg-3.9.0-rc1.txt
>
Thanks for the report!
Looks like the following commit is related:
commit 6aa9707099c4b25700940eb3d016f16c4434360d
Author: Mandeep Singh Baines <msb@chromium.org> Thu Feb 28 09:03:18 2013
lockdep: check that no locks held at freeze time
And the code to trigger this problem is here:
static int hotkey_kthread(void *data)
{
struct tp_nvram_state s[2];
u32 poll_mask, event_mask;
unsigned int si, so;
unsigned long t;
unsigned int change_detector;
unsigned int poll_freq;
bool was_frozen;
mutex_lock(&hotkey_thread_mutex);
if (tpacpi_lifecycle == TPACPI_LIFE_EXITING)
goto exit;
set_freezable();
~~~~~~~~~~~~~~~~~~~~~~~~~~
in thinkpad_acpi.c.
I don't know much about freeze, I've no idea what is the problem.
So Mandeep and Henrique, can you please kindly take a look? Thanks.
-Aaron
next prev parent reply other threads:[~2013-03-05 7:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 19:55 [REGRESSION] [3.9-rc1] BUG: ktpacpi_nvramd/446 still has locks held! Maciej Rutecki
2013-03-05 7:28 ` Aaron Lu [this message]
2013-03-05 16:04 ` Mandeep Singh Baines
2013-03-05 17:34 ` [PATCH] thinkpad-acpi: fix potential suspend blocking issue Mandeep Singh Baines
2013-03-05 17:48 ` Oleg Nesterov
2013-03-05 17:59 ` Mandeep Singh Baines
2013-03-05 18:05 ` Oleg Nesterov
2013-03-05 20:55 ` Mandeep Singh Baines
2013-03-05 23:26 ` Henrique de Moraes Holschuh
2013-03-06 15:44 ` Oleg Nesterov
2013-03-06 23:32 ` Henrique de Moraes Holschuh
[not found] ` <20130306233232.GA12645-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2013-03-07 17:53 ` [PATCH 0/1] thinkpad-acpi: kill hotkey_thread_mutex Oleg Nesterov
2013-03-07 17:53 ` [PATCH 1/1] " Oleg Nesterov
2013-03-07 18:42 ` Mandeep Singh Baines
[not found] ` <CACBanvqP0jx_d-LtV5+fRD7M698M_b6j0Sv=v0uoTBpjEusQCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-09 21:34 ` Henrique de Moraes Holschuh
2013-03-26 13:14 ` Rafael J. Wysocki
2013-03-26 13:09 ` Oleg Nesterov
2013-03-26 13:50 ` Rafael J. Wysocki
2013-03-05 19:18 ` [PATCH] thinkpad-acpi: fix potential suspend blocking issue Maciej Rutecki
2013-03-05 22:18 ` Andrew Morton
2013-03-06 15:50 ` Oleg Nesterov
2013-03-06 20:18 ` Artem Savkov
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=51359E9D.7040802@intel.com \
--to=aaron.lu@intel.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=msb@chromium.org \
--cc=platform-driver-x86@vger.kernel.org \
/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