RE: Can anyone boot a system using btrfs root with linux 3.14 or newer?

Пламен Петров
2014-04-24T21:23:47Z

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

> -----Original Message-----
> From: Chris Murphy [mailto:lists@colorremedies.com]
> Sent: Friday, April 25, 2014 12:06 AM
> To: Пламен Петров
> Cc: 'Marc MERLIN'; linux-btrfs@vger.kernel.org
> Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or
> newer?
>
>
> 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.
>

Well, the actual time doesn't matter - I use this monolithic kernel on both virtual machines as well as a physical server. Up until 3.13.x this arrangement worked flawlessly, now for 3.14.x - everything will be the same except me using BTRFS...

> 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?

The most recent dmesg dumps were from a virtual machine.

>
> 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.

I will try to provide these, but it will have to wait for tomorrow as currently my monolithic kernel .config does not support serial ports, so I will have to reconfigure, recompile both 3.13.x and 3.14.x to test them and provide the requested data.

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

The requested diff was posted earlier, reattaching once more.
---------------------------------
Plamen Petrov

[-- Attachment #2: diff-3.14.1-to-3.13.11.txt --]
[-- Type: text/plain, Size: 1916 bytes --]

diff config-v3.14.1-mix64 config-v3.13.11-mix64
3c3
< # Linux/x86 3.14.1 Kernel Configuration
---
> # Linux/x86 3.13.11 Kernel Configuration
155a156
> # CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set
230,234d230
< CONFIG_HAVE_CC_STACKPROTECTOR=y
< # CONFIG_CC_STACKPROTECTOR is not set
< CONFIG_CC_STACKPROTECTOR_NONE=y
< # CONFIG_CC_STACKPROTECTOR_REGULAR is not set
< # CONFIG_CC_STACKPROTECTOR_STRONG is not set
309d304
< # CONFIG_XEN_PVH is not set
358a354
> CONFIG_MICROCODE_INTEL_LIB=y
407d402
< # CONFIG_ZSMALLOC is not set
419a415
> # CONFIG_CC_STACKPROTECTOR is not set
430d425
< # CONFIG_RANDOMIZE_BASE is not set
762,763d756
< # CONFIG_NET_SCH_HHF is not set
< # CONFIG_NET_SCH_PIE is not set
794,795c787
< # CONFIG_CGROUP_NET_PRIO is not set
< # CONFIG_CGROUP_NET_CLASSID is not set
---
> # CONFIG_NETPRIO_CGROUP is not set
944d935
< # CONFIG_GENWQE is not set
997a989
> # CONFIG_SCSI_AIC7XXX_OLD is not set
1158d1149
< CONFIG_DM_BUFIO=y
1256d1246
< # CONFIG_I40EVF is not set
1489d1478
< CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y
1608d1596
< # CONFIG_I2C_DESIGNWARE_PLATFORM is not set
1622d1609
< # CONFIG_I2C_ROBOTFUZZ_OSIF is not set
1807a1795
> # CONFIG_CPU_THERMAL is not set
1811d1798
< # CONFIG_ACPI_INT3403_THERMAL is not set
1851d1837
< # CONFIG_MFD_MAX14577 is not set
1872d1857
< # CONFIG_MFD_LP3943 is not set
1904d1888
< CONFIG_INTEL_GTT=y
1928d1911
< # CONFIG_DRM_I915_UMS is not set
1940d1922
< # CONFIG_DRM_BOCHS is not set
1978d1959
< # CONFIG_FB_OPENCORES is not set
2080a2062
> # CONFIG_HID_LOGITECH_DJ is not set
2184d2165
< # CONFIG_USB_MUSB_HDRC is not set
2186d2166
< # CONFIG_USB_DWC2 is not set
2225d2204
< # CONFIG_USB_OTG_FSM is not set
2269d2247
< # CONFIG_RTC_DRV_ISL12057 is not set
2403d2380
< CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
2450a2428
> CONFIG_GENERIC_ACL=y
2604d2581
< CONFIG_PANIC_TIMEOUT=0