All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Chris Mason <clm@fb.com>, jbacik@fb.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs: hang on boot due to tests
Date: Mon, 09 Jun 2014 12:17:50 -0400	[thread overview]
Message-ID: <5395DE2E.7080700@oracle.com> (raw)
In-Reply-To: <5395D9D6.3080101@fb.com>

On 06/09/2014 11:59 AM, Chris Mason wrote:
> On 06/09/2014 11:16 AM, Sasha Levin wrote:
>> > Hi all,
>> > 
>> > It seems that some recent changes to btrfs tests make it hang during boot:
>> > 
>> > [   49.730033] NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [swapper/0:1]
>> > [   49.730033] Modules linked in:
>> > [   49.730033] hardirqs last enabled at (6389143): restore_args (arch/x86/kernel/entry_64.S:829)
>> > [   49.730033] hardirqs last disabled at (6389144): apic_timer_interrupt (arch/x86/kernel/entry_64.S:1021)
>> > [   49.730033] softirqs last enabled at (6389142): __do_softirq (./arch/x86/include/asm/preempt.h:22 kernel/softirq.c:296)
>> > [   49.730033] softirqs last disabled at (6389139): irq_exit (kernel/softirq.c:346 kernel/softirq.c:387)
>> > [   49.730033] CPU: 34 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc8-next-20140606-sasha-00021-ga9d3a0b-dirty #597
> 
> This is 3.15-rc8 + linux-next?  I'll try to reproduce here, but the
> tests were working for me.

Yes, it's the latest -next tree available.

Also note that it doesn't happen every time, so might be some sort of a race?


Thanks,
Sasha

  reply	other threads:[~2014-06-09 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 15:16 btrfs: hang on boot due to tests Sasha Levin
2014-06-09 15:59 ` Chris Mason
2014-06-09 16:17   ` Sasha Levin [this message]
2014-06-10 11:14     ` Ed Tomlinson
2014-06-10 13:26       ` Chris Mason
2014-06-12 16:02         ` Sasha Levin
2014-06-11 23:14       ` Filipe David Manana

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=5395DE2E.7080700@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=clm@fb.com \
    --cc=davej@redhat.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.