linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Sean Clarke <sean.clarke@sec-consulting.co.uk>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: 3.11 and 3.12rc continual hard lock ups
Date: Thu, 24 Oct 2013 04:47:56 -0400	[thread overview]
Message-ID: <20131024084756.14051.61595@localhost.localdomain> (raw)
In-Reply-To: <CAHCKNJj2=qfWEpWWUOBit5cJakwd+oFr1U-xj8MS-w9oQo6YQg@mail.gmail.com>

Quoting Sean Clarke (2013-10-23 15:26:15)
> Hi,
>    I have an Intel Core i7 based fileserver with 18TB BTRFS in a 6x
> 3TB RAID 1+0 configuration. The system was working fine running Ubuntu
> 13.04 (kernel 3.11.0-12-generic). The system was upgraded to Ubuntu
> 13.10 (kernel 3.11) and began to lock up daily, sometimes every couple
> of hours. Previously it never crashed and was only taken down for
> maintenance so a bug was files on launchpad
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237794).

Does your kernel  config include the softlockup detector?  If you could
please do sysrq-w and sysrq-t while it is locked, it'll help us track it
down.

It will be much easier if you have a serial console or network console,
and you've increased your kernel logging level to the highest value
(dmesg -n7)

-chris

  parent reply	other threads:[~2013-10-24  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 19:26 3.11 and 3.12rc continual hard lock ups Sean Clarke
2013-10-23 20:05 ` Duncan
2013-10-24  8:47 ` Chris Mason [this message]
2013-10-27  9:06   ` Sean Clarke
2013-10-27 21:08     ` Sean Clarke

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=20131024084756.14051.61595@localhost.localdomain \
    --to=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sean.clarke@sec-consulting.co.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).