linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alexander Viro <viro@ftp.linux.org.uk>,
	"Theodore Ts'o" <tytso@mit.edu>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup?
Date: Thu, 14 Feb 2013 15:05:14 -0800	[thread overview]
Message-ID: <CA+55aFwpFFg+Z28aZ=92bGdU+Va00j08BzL-2frtLarKWt=qOQ@mail.gmail.com> (raw)
In-Reply-To: <20130213111007.GA11367@gmail.com>

On Wed, Feb 13, 2013 at 3:10 AM, Ingo Molnar <mingo@kernel.org> wrote:
>
> Setting up Logical Volume Management: [   13.140000] BUG: spinlock lockup suspected on CPU#1, lvm.static/139
> [   13.140000] BUG: spinlock lockup suspected on CPU#1, lvm.static/139
> [   13.140000]  lock: 0x97fe9fc0, .magic: dead4ead, .owner: <none>/-1, .owner_cpu: -1

Btw, this is an entirely unrelated thing, but it just struck me: you
have  CONFIG_DEBUG_LOCK_ALLOC in your config, so that spinlock has a
_name_, and the not-so-helpful "spin_dump()" is too stupid to even
bother to print it out.

Now, in this case, it doesn't much matter, since the callchain really
does end up showing pretty unambiguously what the lock is, but
shouldn't we print that lock name when we dump the lock information?

I dunno. Maybe the names aren't useful, and the callchain ends up
always making them redundant. But it seems an oversight in our debug
output.

                  Linus

  parent reply	other threads:[~2013-02-14 23:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 21:51 Linux v3.8-rc7 Linus Torvalds
2013-02-10  0:14 ` [REGRESSION] -rc7/-rc4+: unable to USB boot - enumeration partially broken (was: Linux v3.8-rc7) Andreas Mohr
2013-02-10 14:05   ` Andreas Mohr
2013-02-12 16:07     ` Andreas Mohr
2013-02-12 16:16       ` Greg KH
2013-02-12 21:25         ` Andreas Mohr
2013-02-13  6:44         ` [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci a separate driver Andreas Mohr
2013-02-13  7:16           ` Andreas Mohr
2013-02-13  7:44             ` Andreas Mohr
2013-02-13 10:05               ` Andreas Mohr
2013-02-13 10:50                 ` Colin Guthrie
2013-02-13 16:13                   ` Andreas Mohr
2013-02-13 16:26                     ` Colin Guthrie
2013-02-13 11:10 ` [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? Ingo Molnar
2013-02-13 16:59   ` Linus Torvalds
2013-02-13 23:20     ` Thomas Gleixner
2013-02-14 14:45       ` Ingo Molnar
2013-02-14 14:54         ` Ingo Molnar
2013-02-14 15:08           ` Ingo Molnar
2013-02-14 17:28             ` Thomas Gleixner
2013-02-14 18:22             ` Yinghai Lu
2013-02-15 11:44               ` [-rc7 regression] Buggy commit: "mm: use aligned zone start for pfn_to_bitidx calculation" Ingo Molnar
2013-02-15 22:06                 ` Greg KH
2013-02-16  8:29                   ` Ingo Molnar
2013-03-01 16:50                     ` Greg KH
2013-03-01 17:07                       ` Linus Torvalds
2013-03-01 17:14                         ` Greg KH
2013-02-16  8:25                 ` Ingo Molnar
2013-02-16 18:26                 ` Linus Torvalds
2013-02-16 19:38                   ` Yinghai Lu
2013-02-16 19:51                     ` Linus Torvalds
2013-02-18  8:49                   ` Ingo Molnar
2013-02-18 14:46                   ` Mel Gorman
2013-02-18 18:42                     ` Laura Abbott
2013-02-14 23:05   ` Linus Torvalds [this message]
2013-02-15 11:39     ` [PATCH] spinlock/debugging: Print out lock name when available Ingo Molnar

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='CA+55aFwpFFg+Z28aZ=92bGdU+Va00j08BzL-2frtLarKWt=qOQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).