All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: "Пламен Петров" <plamen@petrovi.no-ip.info>
Cc: "'Marc MERLIN'" <marc@merlins.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or newer?
Date: Thu, 24 Apr 2014 15:06:01 -0600	[thread overview]
Message-ID: <8953EAE6-E8DD-40DC-B485-128BE7CB4BA1@colorremedies.com> (raw)
In-Reply-To: <002301cf5fee$346fefc0$9d4fcf40$@petrovi.no-ip.info>


On Apr 24, 2014, at 12:51 PM, Пламен Петров <plamen@petrovi.no-ip.info> wrote:
> 
> I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went OK, here is what dmesg said:
> [   12.412465] Btrfs loaded

For me, with Btrfs not compiled in the kernel, and with an initramfs, on SSD I get Btrfs loaded at 2.4 seconds. On HDD, it still happens by 6-7 seconds.

So without an initrd and with btrfs compiled into the kernel I'd expect to see Btrfs loaded before 12.4 seconds. Is this an SSD? Or HDD, or hardware raid?

I'd like to see the dmesg from the beginning, until "Btrfs Loaded", for both 3.13.11 and 3.14.1 (via serial console output). I think the clue is in the part before Btrfs loaded.

Also can you post a diff of the config file for the working 3.13.11 and not working 3.14.1 kernels?

Chris Murphy

  parent reply	other threads:[~2014-04-24 21:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
2014-04-23 18:54 ` Marc MERLIN
2014-04-23 19:02   ` Hugo Mills
2014-04-23 19:06   ` Пламен Петров
2014-04-23 19:15     ` Marc MERLIN
2014-04-23 19:37       ` Пламен Петров
2014-04-23 20:58         ` Marc MERLIN
2014-04-23 21:54           ` Пламен Петров
2014-04-23 22:03             ` Marc MERLIN
2014-04-23 22:20               ` Пламен Петров
2014-04-23 22:40                 ` Chris Murphy
2014-04-23 22:43                   ` Hugo Mills
2014-04-23 22:50                     ` Marc MERLIN
2014-04-23 22:53                       ` Hugo Mills
2014-04-23 22:41               ` Hugo Mills
2014-04-24 12:34           ` Chris Mason
2014-04-24 12:36             ` Chris Mason
2014-04-24 17:08               ` Пламен Петров
2014-04-24 17:19       ` Пламен Петров
2014-04-24 17:33         ` Marc MERLIN
2014-04-24 17:44           ` Пламен Петров
2014-04-24 18:51           ` Пламен Петров
2014-04-24 19:31             ` Marc MERLIN
2014-04-24 20:26               ` Пламен Петров
2014-04-24 21:47                 ` Chris Murphy
2014-04-24 21:06             ` Chris Murphy [this message]
2014-04-24 21:23               ` Пламен Петров
     [not found]               ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>
2014-04-24 23:07                 ` Marc MERLIN
2014-04-25  0:04                   ` Chris Murphy
2014-04-25  0:08                     ` Chris Mason
2014-04-25  5:04                       ` Пламен Петров
2014-04-25  7:02                       ` Duncan
2014-04-25  5:03                     ` Пламен Петров
2014-04-23 19:06 ` Kai Krakow
2014-04-23 20:25   ` Calvin Walton
2014-04-23 22:34   ` Chris Murphy
2014-04-24  3:23 ` Chris Murphy
2014-04-24  6:27   ` Fajar A. Nugraha

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=8953EAE6-E8DD-40DC-B485-128BE7CB4BA1@colorremedies.com \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    --cc=plamen@petrovi.no-ip.info \
    /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.