Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #51765 > unrolled thread

Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

Back to article view | Back to linux.debian.kernel

Contents

  Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4 Alexandre <ar.community@devnco.fr> - 2015-12-15 14:50 +0100
    Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4 Ben Hutchings <ben@decadent.org.uk> - 2017-01-23 18:40 +0100
    Processed: Re: linux-image-4.4.0-rc4-amd64: Fails to boot on  kernel 4.4rc4 owner@bugs.debian.org (Debian Bug Tracking System) - 2017-01-23 18:40 +0100

#51765 — Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

Package: linux-image-4.4.0-rc4-amd64
Version: 4.4~rc4-1~exp1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Actually, i'm usging linux-image-4.3.0-trunk-amd64 on Dell XPS 13 9350. In
order to fix WiFi problem i would install linux-image-4.4.0rc4 but it makes it
impossible to boot my laptop.

I have this message before Luks ask passphrase :

Loading, please wait...
modprobe: module microcode not found in modules.dep
lvmetad is not active yet, using direct activation during sysinit
volume group "vg" not found
Cannot process volume group vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.




-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (1001, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#56705

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 jessie

As you know, the problem is that initramfs-tools wasn't including the
nvme driver in the initramfs since it moved to a different directory. 
This was fixed in version 0.121.

I also cherry-picked the fix for initramfs-tools in version
0.120+deb8u2, which was included in a stable point release (8.4).

Just in case someone tries to upgrade the kernel and hasn't upgraded
initramfs-tools yet, I'll increase the minimum version.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
        Inside every large problem is a small problem struggling to get
out.

[toc] | [prev] | [next] | [standalone]

#56706 — Processed: Re: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

Processing control commands:

> tag -1 jessie
Bug #808038 [src:linux] linux-image should force upgrade of initramfs-tools to ensure nvme is included
Added tag(s) jessie.

-- 
808038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808038
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web