From: Ingo Molnar <mingo@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
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:54:24 +0100 [thread overview]
Message-ID: <20130214145424.GA26071@gmail.com> (raw)
In-Reply-To: <20130214144510.GC25282@gmail.com>
> CPU0 appears to be idle:
>
> [ 118.510000] Call Trace:
> [ 118.510000] [<7900844b>] cpu_idle+0x86/0xb4
> [ 118.510000] [<792a91df>] rest_init+0x103/0x108
> [ 118.510000] [<794558cc>] start_kernel+0x2c7/0x2cc
So, I've done a partial bisection, the breakage appears to have
gone upstream between v3.8-rc3 and v3.8-rc4.
This roughly coincides with the time frame when I first saw
these lockups pop up, so in that sense it's a plausible result -
but there weren't all that many commits in -rc4 and none looks
really suspicious, so this might be one of those non-bisectable
bugs.
( Later today I'll try to finish the bisection just in case it
results in something useful. )
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-14 14:54 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 [this message]
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 ` [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? Linus Torvalds
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=20130214145424.GA26071@gmail.com \
--to=mingo@kernel.org \
--cc=axboe@kernel.dk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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).