linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: "G. Richard Bellamy" <rbellamy@pteradigm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Upgrade to 3.19.2 Kernel fails to boot
Date: Thu, 19 Mar 2015 17:19:32 -0600	[thread overview]
Message-ID: <CAJCQCtRkUnXvvMP=uSpxkusNMgXNVvmXKCeJ-rfNe9gi6W+Gqw@mail.gmail.com> (raw)
In-Reply-To: <CADw2B2Nxr5PPSaVWpQWxg0ZaXYSpOTye_pMU1HbjCHif8q9_LQ@mail.gmail.com>

On Thu, Mar 19, 2015 at 5:06 PM, G. Richard Bellamy
<rbellamy@pteradigm.com> wrote:
> When I upgrade to the 3.19.2 Kernel I get a deadlocked boot:
> INFO: task mount:302 blocked for more than 120 seconds.
> INFO: task btrfs-transacti:329 blocked for more than 120 seconds.

If you boot single user is it semi-responsive enough to sysrq+w [1]
and post the resulting dmesg?


>My 3.18.6 works just fine.

What do you get for 'btrfs check <dev>' You either need to run this
from the initramfs (totally unmounted file system) or rescue media
with a decently recent btrfs progs.


[1]
https://www.kernel.org/doc/Documentation/sysrq.txt


-- 
Chris Murphy

  reply	other threads:[~2015-03-19 23:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 23:06 Upgrade to 3.19.2 Kernel fails to boot G. Richard Bellamy
2015-03-19 23:19 ` Chris Murphy [this message]
2015-03-22 21:15 ` Ochi
2015-03-22 21:25   ` Roman Mamedov
2015-03-23  8:23 ` Anand Jain
2015-03-23 13:22   ` Rich Freeman
2015-03-23 16:37     ` Rich Freeman
2015-03-24  6:31       ` Anand Jain
2015-03-24 10:40         ` Rich Freeman
2015-04-01  6:50           ` Anand Jain
2015-04-01 19:48             ` Rich Freeman
2015-03-31 21:24 ` Benjamin Hodgetts
2015-03-31 22:23   ` Chris Murphy

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='CAJCQCtRkUnXvvMP=uSpxkusNMgXNVvmXKCeJ-rfNe9gi6W+Gqw@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rbellamy@pteradigm.com \
    /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).