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


Groups > linux.debian.kernel > #51765

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

From Alexandre <ar.community@devnco.fr>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4
Date 2015-12-15 14:50 +0100
Message-ID <qFY9k-4Mo-19@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


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)

Back to linux.debian.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

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

csiph-web