LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: linux-next: possible recursive locking detected
Date: Wed, 3 Mar 2010 11:10:27 +1100	[thread overview]
Message-ID: <20100303111027.03ab3c15.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

Hi all,

next-20100302 (and next-20100301) produce this log during boot on a
Power5 lpar.

calling  .hvc_vio_init+0x0/0x34 @ 1

=============================================
[ INFO: possible recursive locking detected ]
2.6.33-autokern1 #1
---------------------------------------------
swapper/1 is trying to acquire lock:
 (&dev->mutex){+.+...}, at: [<c000000000345490>] .__driver_attach+0x80/0xe0

but task is already holding lock:
 (&dev->mutex){+.+...}, at: [<c000000000345480>] .__driver_attach+0x70/0xe0

other info that might help us debug this:
1 lock held by swapper/1:
 #0:  (&dev->mutex){+.+...}, at: [<c000000000345480>] .__driver_attach+0x70/0xe0

stack backtrace:
Call Trace:
[c0000000400cf590] [c000000000010780] .show_stack+0x70/0x184 (unreliable)
[c0000000400cf640] [c000000000096c24] .validate_chain+0x6e4/0xf2c
[c0000000400cf750] [c000000000097d8c] .__lock_acquire+0x920/0x9e4
[c0000000400cf850] [c000000000097ef8] .lock_acquire+0xa8/0xec
[c0000000400cf920] [c000000000567fc4] .mutex_lock_nested+0x5c/0x468
[c0000000400cfa00] [c000000000345490] .__driver_attach+0x80/0xe0
[c0000000400cfa90] [c000000000343f0c] .bus_for_each_dev+0x84/0xdc
[c0000000400cfb40] [c000000000344e6c] .driver_attach+0x28/0x40
[c0000000400cfbc0] [c0000000003448ec] .bus_add_driver+0xd8/0x2b0
[c0000000400cfc70] [c000000000345830] .driver_register+0xd4/0x1a8
[c0000000400cfd20] [c00000000002225c] .vio_register_driver+0x40/0x5c
[c0000000400cfdb0] [c0000000007ff4d4] .hvc_vio_init+0x1c/0x34
[c0000000400cfe30] [c0000000000094c0] .do_one_initcall+0x9c/0x1cc
[c0000000400cfee0] [c0000000007d6d2c] .kernel_init+0x218/0x294
[c0000000400cff90] [c000000000026c00] .kernel_thread+0x54/0x70
initcall .hvc_vio_init+0x0/0x34 returned 0 after 1904 usecs

Any ideas?
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2010-03-03  0:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100303111027.03ab3c15.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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