Bug 87001 - 3.18RC2 fails to boot
Summary: 3.18RC2 fails to boot
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: btrfs (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-27 12:12 UTC by Eugene
Modified: 2015-05-26 21:27 UTC (History)
5 users (show)

See Also:
Kernel Version: 3.18RC2
Tree: Mainline
Regression: Yes


Attachments

Description Eugene 2014-10-27 12:12:27 UTC
After installing new 3.18RC2 kernel, I found it fails to boot with following messages:

Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/b76fc0ae-d31c-4b13-8f4e-424542d850c9 does not exist. Dropping to a shell!

BusyBox v.1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs)

The thing is 3.18RC1 boots well. So it seems a some kind of regression (?)

My partitions table:
/dev/sda1    clean         bios_grub
/dev/sda2    linux-swap
/dev/sda3    btrfs         /,/home,/mnt/pool/main

Kubuntu 14.10 x86-64
Comment 1 Sean Rhone 2014-10-28 03:52:43 UTC
Can confirm the same on rc2.

Using Ubuntu 14.10 (x86_64), my main drive is the standard setup for EFI boot (EFI partition, main ext4 partition, swap partition); no encryption. Using onboard SATA controller (on 990FX motherboard) in AHCI mode.

rc1 was fine; I noticed one of the daily kernels past rc1 also did this, but can't recall which one.
Comment 2 Doug Smythies 2014-10-28 16:59:51 UTC
Ubuntu made many changes to the kernel config file between 3.18RC1 and 3.18RC2. The Ubuntu 3.18RC2 kernel fails for me also, but for different reasons. In my case it was just that networking didn't work. Similarly for the kernel.org version of the kernel compiled using the Ubuntu kernel config file.

However, by reverting this change:

< # CONFIG_MODULE_COMPRESS is not set
---
> CONFIG_MODULE_COMPRESS=y
> CONFIG_MODULE_COMPRESS_GZIP=y
> # CONFIG_MODULE_COMPRESS_XZ is not set

back to "CONFIG_MODULE_COMPRESS is not set" the kernel works fine for my case.
Comment 3 volker_kempter 2014-10-28 19:44:47 UTC
can confirm Eugene.

No boot for any of my machines under 14.10 with 3.18-rc2, including one virtual machine in virtual box; rc1 was fine, though.

This is for Lubuntu 14.10 x86-32.

I feel that the initrd.img (created during kernel installation) may be defect (ls -l /boot/initrd*): file is much too small.
Comment 4 Doug Smythies 2014-10-28 23:23:52 UTC
There is now an Ubuntu version of 3.18RC2 with the above noted config file change at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc2-vivid/
Posters that had issues should try it.
Comment 5 Eugene 2014-10-29 02:48:59 UTC
(In reply to Doug Smythies from comment #4)
> There is now an Ubuntu version of 3.18RC2 with the above noted config file
> change at:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc2-vivid/
> Posters that had issues should try it.

Yes, this RC2-vivid is booting well.
Comment 6 volker_kempter 2014-10-29 09:06:07 UTC
3.18-rc2-vivid:

boots well as a VM, lubuntu-14.10, in virtualbox

lubuntu-14.10 real machine: 
/boot/initrd.img is now much larger than with 3.18-rc2-utopic! Machine almost boots, BUT does not entirely come up, in particular, no horizontal task bar, no WIFI, cannot start synaptic.

This is for Lubuntu 14.10 x86-32 on dell e6500 (3.18-rc1 runs perfectly well!).
Comment 7 volker_kempter 2014-10-29 16:32:14 UTC
still 3.18rc2-vivid:

situation is rather weird:
as stated in my comment 6, 3.18rc2-vivid does not entirely boot in my dell e6500, but boots well in my old dell D505 (10 years old); both in lubuntu-14.10, x86-32.
Comment 8 Eugene 2014-10-29 19:28:11 UTC
The only thing I've missed is that during boot one message appears:

kernel: [   36.205270] init: Error while reading from descriptor: Broken pipe

But nevertheless it boots.

Note You need to log in before you can comment on or make changes to this bug.