From: Roman Mamedov <rm@romanrm.net>
To: Ochi <ochi@arcor.de>
Cc: rbellamy@pteradigm.com, linux-btrfs@vger.kernel.org
Subject: Re: Upgrade to 3.19.2 Kernel fails to boot
Date: Mon, 23 Mar 2015 02:25:14 +0500 [thread overview]
Message-ID: <20150323022514.2d805594@natsu> (raw)
In-Reply-To: <550F3103.7080609@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Sun, 22 Mar 2015 22:15:47 +0100
Ochi <ochi@arcor.de> 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.
>
> I had a similar behavior today after I accidentally pulled the power
> plug of my machine (Arch Linux, Kernel 3.19.2). I tried to boot several
> times, but "mount" timed out.
This message by itself is not a "time out" of any kind, it's just a warning
which says exactly what it says and nothing more. If you are certain that
there was no access whatsoever to the HDD/SSD (the access light not flashing),
then yeah maybe it got stuck. But it also could be it simply needed 1-2 more
minutes to complete whatever it was doing.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-03-22 21:25 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
2015-03-22 21:15 ` Ochi
2015-03-22 21:25 ` Roman Mamedov [this message]
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=20150323022514.2d805594@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=ochi@arcor.de \
--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 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.