From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-pm <linux-pm@lists.osdl.org>
Subject: Re: lockdep report in hibernate code
Date: Tue, 23 Oct 2007 00:39:29 +0200 [thread overview]
Message-ID: <200710230039.30224.rjw@sisk.pl> (raw)
In-Reply-To: <1193062264.9793.11.camel@johannes.berg>
On Monday, 22 October 2007 16:11, Johannes Berg wrote:
> I just got this on my quad powermac which then failed to hibernate
> (separate mail coming soon):
>
> Oct 22 15:37:59 quad kernel: [ 362.782679] [ INFO: possible circular locking dependency detected ]
> Oct 22 15:37:59 quad kernel: [ 362.782687] 2.6.23-g55b70a03-dirty #268
> Oct 22 15:37:59 quad kernel: [ 362.782696] -------------------------------------------------------
> Oct 22 15:37:59 quad kernel: [ 362.782704] pm-hibernate/4231 is trying to acquire lock:
> Oct 22 15:37:59 quad kernel: [ 362.782710] (pm_mutex){--..}, at: [<c00000000008ae28>] .disk_store+0x70/0x17c
> Oct 22 15:37:59 quad kernel: [ 362.782742]
> Oct 22 15:37:59 quad kernel: [ 362.782744] but task is already holding lock:
> Oct 22 15:37:59 quad kernel: [ 362.782751] (&buffer->mutex){--..}, at: [<c00000000013a620>] .sysfs_write_file+0x58/0x19c
> Oct 22 15:37:59 quad kernel: [ 362.782771]
> Oct 22 15:37:59 quad kernel: [ 362.782773] which lock already depends on the new lock.
That's strange and almost certainly not true.
> Oct 22 15:37:59 quad kernel: [ 362.782776]
> Oct 22 15:37:59 quad kernel: [ 362.782782]
> Oct 22 15:37:59 quad kernel: [ 362.782783] the existing dependency chain (in reverse order) is:
> Oct 22 15:37:59 quad kernel: [ 362.782795]
> Oct 22 15:37:59 quad kernel: [ 362.782797] -> #1 (&buffer->mutex){--..}:
> Oct 22 15:37:59 quad kernel: [ 362.782831] [<c00000000007d190>] .__lock_acquire+0xcf0/0xf60
> Oct 22 15:37:59 quad kernel: [ 362.782910] [<c00000000007d4d0>] .lock_acquire+0xd0/0x11c
> Oct 22 15:37:59 quad kernel: [ 362.782982] [<c0000000003e0ed8>] .mutex_lock_nested+0x150/0x3e8
> Oct 22 15:37:59 quad kernel: [ 362.783061] [<c00000000013a7bc>] .sysfs_read_file+0x58/0x1a0
> Oct 22 15:37:59 quad kernel: [ 362.783137] [<c0000000000dd130>] .vfs_read+0xd8/0x1b0
> Oct 22 15:37:59 quad kernel: [ 362.783211] [<c0000000000dd960>] .sys_read+0x5c/0xac
> Oct 22 15:37:59 quad kernel: [ 362.783285] [<c000000000008014>] .try_name+0x88/0x260
> Oct 22 15:37:59 quad kernel: [ 362.783362] [<c000000000008430>] .name_to_dev_t+0x244/0x2e8
> Oct 22 15:37:59 quad kernel: [ 362.783439] [<c00000000008b33c>] .software_resume+0x7c/0x200
> Oct 22 15:37:59 quad kernel: [ 362.783516] [<c00000000054e8f8>] .kernel_init+0x214/0x3e8
> Oct 22 15:37:59 quad kernel: [ 362.783588] [<c000000000024cdc>] .kernel_thread+0x4c/0x68
> Oct 22 15:37:59 quad kernel: [ 362.783623]
> Oct 22 15:37:59 quad kernel: [ 362.783625] -> #0 (pm_mutex){--..}:
> Oct 22 15:37:59 quad kernel: [ 362.783659] [<c00000000007d088>] .__lock_acquire+0xbe8/0xf60
> Oct 22 15:37:59 quad kernel: [ 362.783733] [<c00000000007d4d0>] .lock_acquire+0xd0/0x11c
> Oct 22 15:37:59 quad kernel: [ 362.783810] [<c0000000003e0ed8>] .mutex_lock_nested+0x150/0x3e8
> Oct 22 15:37:59 quad kernel: [ 362.783884] [<c00000000008ae28>] .disk_store+0x70/0x17c
> Oct 22 15:37:59 quad kernel: [ 362.783960] [<c00000000013a160>] .subsys_attr_store+0x58/0x70
> Oct 22 15:37:59 quad kernel: [ 362.784033] [<c00000000013a6f4>] .sysfs_write_file+0x12c/0x19c
> Oct 22 15:37:59 quad kernel: [ 362.784104] [<c0000000000dcf80>] .vfs_write+0xd8/0x1b0
> Oct 22 15:37:59 quad kernel: [ 362.784179] [<c0000000000dda0c>] .sys_write+0x5c/0xac
> Oct 22 15:37:59 quad kernel: [ 362.784255] [<c000000000007550>] syscall_exit+0x0/0x40
> Oct 22 15:37:59 quad kernel: [ 362.784331]
> Oct 22 15:37:59 quad kernel: [ 362.784333] other info that might help us debug this:
> Oct 22 15:37:59 quad kernel: [ 362.784336]
> Oct 22 15:37:59 quad kernel: [ 362.784349] 1 lock held by pm-hibernate/4231:
> Oct 22 15:37:59 quad kernel: [ 362.784360] #0: (&buffer->mutex){--..}, at: [<c00000000013a620>] .sysfs_write_file+0x58/0x19c
> Oct 22 15:37:59 quad kernel: [ 362.784411]
> Oct 22 15:37:59 quad kernel: [ 362.784413] stack backtrace:
> Oct 22 15:37:59 quad kernel: [ 362.784423] Call Trace:
> Oct 22 15:37:59 quad kernel: [ 362.784434] [c000000010783650] [c00000000000e758] .show_stack+0x78/0x1a4 (unreliable)
> Oct 22 15:37:59 quad kernel: [ 362.784473] [c000000010783700] [c00000000000e8a4] .dump_stack+0x20/0x34
> Oct 22 15:37:59 quad kernel: [ 362.784503] [c000000010783780] [c00000000007a74c] .print_circular_bug_tail+0x88/0xac
> Oct 22 15:37:59 quad kernel: [ 362.784535] [c000000010783850] [c00000000007d088] .__lock_acquire+0xbe8/0xf60
> Oct 22 15:37:59 quad kernel: [ 362.784567] [c000000010783940] [c00000000007d4d0] .lock_acquire+0xd0/0x11c
> Oct 22 15:37:59 quad kernel: [ 362.784599] [c000000010783a00] [c0000000003e0ed8] .mutex_lock_nested+0x150/0x3e8
> Oct 22 15:37:59 quad kernel: [ 362.784619] [c000000010783af0] [c00000000008ae28] .disk_store+0x70/0x17c
> Oct 22 15:37:59 quad kernel: [ 362.784650] [c000000010783ba0] [c00000000013a160] .subsys_attr_store+0x58/0x70
> Oct 22 15:37:59 quad kernel: [ 362.784680] [c000000010783c20] [c00000000013a6f4] .sysfs_write_file+0x12c/0x19c
> Oct 22 15:37:59 quad kernel: [ 362.784712] [c000000010783ce0] [c0000000000dcf80] .vfs_write+0xd8/0x1b0
> Oct 22 15:37:59 quad kernel: [ 362.784742] [c000000010783d80] [c0000000000dda0c] .sys_write+0x5c/0xac
> Oct 22 15:37:59 quad kernel: [ 362.784772] [c000000010783e30] [c000000000007550] syscall_exit+0x0/0x40
>
>
--
"Premature optimization is the root of all evil." - Donald Knuth
next prev parent reply other threads:[~2007-10-22 22:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 14:11 lockdep report in hibernate code Johannes Berg
2007-10-22 22:39 ` Rafael J. Wysocki [this message]
2007-10-23 10:34 ` Johannes Berg
2007-10-23 21:39 ` Rafael J. Wysocki
2007-10-23 21:56 ` Alan Stern
2007-10-23 22:18 ` Rafael J. Wysocki
2007-10-24 8:40 ` Johannes Berg
2007-10-24 21:57 ` Greg KH
2007-10-25 13:31 ` Johannes Berg
2007-10-25 17:13 ` Alan Stern
2007-10-26 10:36 ` Johannes Berg
2007-10-27 22:29 ` Alan Stern
2007-10-28 10:38 ` Johannes Berg
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=200710230039.30224.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.osdl.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