mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.33-rc3 -- INFO: possible recursive locking -- (s_active){++++.+},  at: [<c10d2941>] sysfs_hash_and_remove+0x3d/0x4f
Date: Sat, 9 Jan 2010 16:10:49 -0800	[thread overview]
Message-ID: <20100109161049.773a84a6@infradead.org> (raw)
In-Reply-To: <a44ae5cd1001060454g22fb5a0ay8185bc680cd4fc67@mail.gmail.com>

On Wed, 6 Jan 2010 07:54:59 -0500
Miles Lane <miles.lane@gmail.com> wrote:

> [ 6967.926563] ACPI: Preparing to enter system sleep state S3
> [ 6967.956156] Disabling non-boot CPUs ...
> [ 6967.970401]
> [ 6967.970408] =============================================
> [ 6967.970419] [ INFO: possible recursive locking detected ]
> [ 6967.970431] 2.6.33-rc2-git6 #27


I get the same on changing cpufreq governor.....


[  165.356101] bash/1965 is trying to acquire lock:
[  165.356214]  (s_active){++++.+}, at: [<c04ea0a9>]
sysfs_hash_and_remove+0x3d/0x4f [  165.356257] 
[  165.356257] but task is already holding lock:
[  165.356257]  (s_active){++++.+}, at: [<c04eba15>]
sysfs_get_active_two+0x16/0x35 [  165.356257] 
[  165.356257] other info that might help us debug this:
[  165.356257] 4 locks held by bash/1965:
[  165.356257]  #0:  (&buffer->mutex){+.+.+.}, at: [<c04ea81f>]
sysfs_write_file+0x25/0xeb [  165.356257]  #1:  (s_active){++++.+}, at:
[<c04eba15>] sysfs_get_active_two+0x16/0x35 [  165.356257]  #2:
(s_active){++++.+}, at: [<c04eba20>] sysfs_get_active_two+0x21/0x35
[  165.356257]  #3:  (dbs_mutex){+.+.+.}, at: [<c066a2e2>]
cpufreq_governor_dbs+0x366/0x3fe [  165.356257] [  165.356257] stack
backtrace: [  165.356257] Pid: 1965, comm: bash Not tainted 2.6.33-rc3
#83 [  165.356257] Call Trace:
[  165.356257]  [<c07801d4>] ? printk+0xf/0x13
[  165.356257]  [<c04556ef>] __lock_acquire+0xc8a/0x13a7
[  165.356257]  [<c0454081>] ? mark_held_locks+0x43/0x5b
[  165.356257]  [<c04543de>] ? debug_check_no_locks_freed+0xfd/0x107
[  165.356257]  [<c0455e95>] lock_acquire+0x89/0xa2
[  165.356257]  [<c04ea0a9>] ? sysfs_hash_and_remove+0x3d/0x4f
[  165.356257]  [<c04eb7d4>] sysfs_addrm_finish+0x8f/0x100
[  165.356257]  [<c04ea0a9>] ? sysfs_hash_and_remove+0x3d/0x4f
[  165.356257]  [<c04ea0a9>] sysfs_hash_and_remove+0x3d/0x4f
[  165.356257]  [<c04ec5ae>] sysfs_remove_group+0x76/0xa5
[  165.356257]  [<c066a2f2>] cpufreq_governor_dbs+0x376/0x3fe
[  165.356257]  [<c0452a63>] ? trace_hardirqs_off+0xb/0xd
[  165.356257]  [<c044963c>] ? cpu_clock+0x2d/0x4e
[  165.356257]  [<c0452a85>] ? lock_release_holdtime+0x20/0x17a



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  parent reply	other threads:[~2010-01-10  0:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 12:54 Miles Lane
2010-01-06 13:36 ` Miles Lane
2010-01-10  0:10 ` Arjan van de Ven [this message]
2010-01-10  8:47 ` Américo Wang
2010-01-10  8:58   ` Américo Wang
2010-01-10 17:23     ` Eric W. Biederman
2010-01-10 18:35       ` Rafael J. Wysocki
2010-01-11  2:26         ` Eric W. Biederman
2010-01-11 20:18           ` Rafael J. Wysocki
2010-01-12  0:31           ` Tejun Heo
2010-01-12  0:32             ` Eric W. Biederman
2010-01-12  3:01               ` Dave Chinner
2010-01-12  9:22                 ` Eric W. Biederman
     [not found]               ` <a44ae5cd1001130817v7a3ffbc9yc83d7cc701f8620@mail.gmail.com>
2010-01-13 18:37                 ` Eric W. Biederman
2010-01-13 21:11                 ` Miles Lane
2010-01-12 14:44           ` Américo Wang
2010-01-14  2:47           ` Miles Lane
2010-01-14  3:09             ` Eric W. Biederman
2010-01-14  9:13               ` Peter Zijlstra

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=20100109161049.773a84a6@infradead.org \
    --to=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=pavel@ucw.cz \
    --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

Powered by JetHome