From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
htejun@gmail.com
Subject: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected
Date: Tue, 24 Apr 2007 22:15:50 -0700 [thread overview]
Message-ID: <a44ae5cd0704242215w1b474c52r7860f0d49bc64d6c@mail.gmail.com> (raw)
[ 59.677312] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[ 59.688633] NFSD: starting 90-second grace period
[ 60.221454]
[ 60.221456] =============================================
[ 60.221461] [ INFO: possible recursive locking detected ]
[ 60.221464] 2.6.21-rc7-mm1 #53
[ 60.221466] ---------------------------------------------
[ 60.221469] S20powernowd/3584 is trying to acquire lock:
[ 60.221472] (&sd->s_active){----}, at: [<c01a2436>]
sysfs_hash_and_remove+0x91/0x10e
[ 60.221486]
[ 60.221487] but task is already holding lock:
[ 60.221489] (&sd->s_active){----}, at: [<c01a2a20>]
sysfs_write_file+0xb9/0x14a
[ 60.221496]
[ 60.221497] other info that might help us debug this:
[ 60.221499] 4 locks held by S20powernowd/3584:
[ 60.221501] #0: (&sd->s_active){----}, at: [<c01a2a20>]
sysfs_write_file+0xb9/0x14a
[ 60.221508] #1: (&sd->s_active){----}, at: [<c01a2a32>]
sysfs_write_file+0xcb/0x14a
[ 60.221515] #2: (&per_cpu(cpu_policy_rwsem, cpu)){--..}, at:
[<c024081b>] lock_policy_rwsem_write+0x20/0x37
[ 60.221524] #3: (userspace_mutex){--..}, at: [<c0299dfe>]
mutex_lock+0x1f/0x23
[ 60.221534]
[ 60.221535] stack backtrace:
[ 60.221538] [<c0104e0f>] show_trace_log_lvl+0x1a/0x30
[ 60.221543] [<c0105a26>] show_trace+0x12/0x14
[ 60.221547] [<c0105ab3>] dump_stack+0x16/0x18
[ 60.221551] [<c0134d63>] __lock_acquire+0x12e/0xb4c
[ 60.221557] [<c01357e9>] lock_acquire+0x68/0x82
[ 60.221561] [<c012ddda>] down_write+0x3a/0x53
[ 60.221567] [<c01a2436>] sysfs_hash_and_remove+0x91/0x10e
[ 60.221571] [<c01a2bb0>] sysfs_remove_file+0x10/0x12
[ 60.221575] [<c0241756>] cpufreq_governor_userspace+0x10c/0x1dc
[ 60.221579] [<c023fd2b>] __cpufreq_governor+0x9c/0xd0
[ 60.221583] [<c023fed0>] __cpufreq_set_policy+0x171/0x209
[ 60.221587] [<c02400b5>] store_scaling_governor+0x14d/0x184
[ 60.221591] [<c0240bee>] store+0x3e/0x60
[ 60.221594] [<c01a2a85>] sysfs_write_file+0x11e/0x14a
[ 60.221599] [<c01699fb>] vfs_write+0x90/0x119
[ 60.221605] [<c0169eef>] sys_write+0x3d/0x61
[ 60.221609] [<c0103e66>] sysenter_past_esp+0x5f/0x99
[ 60.221613] =======================
[ 60.763809] Clocksource tsc unstable (delta = -75646443 ns)
next reply other threads:[~2007-04-25 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 5:15 Miles Lane [this message]
2007-04-25 5:18 ` Tejun Heo
2007-04-25 14:48 ` Antonino A. Daplas
2007-04-25 23:45 ` Nonfunctional ethernet (was Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected) Antonino A. Daplas
2007-04-26 1:02 ` Antonino A. Daplas
2007-04-26 1:13 ` Andrew Morton
2007-04-26 2:26 ` Tejun Heo
2007-04-26 2:53 ` Andrew Morton
2007-04-26 14:50 ` [PATCH] sysfs: use different lockdep subclass for s_active deactivation Tejun Heo
2007-04-26 15:22 ` Greg KH
2007-04-26 17:21 ` Miles Lane
2007-04-26 17:33 ` Tejun Heo
2007-04-26 18:51 ` Miles Lane
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=a44ae5cd0704242215w1b474c52r7860f0d49bc64d6c@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®