Skip to contentSkip to conversation

New: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

Bug 109901 [email protected] 1 participant 1 message Dec 24, 2015

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=109901

            Bug ID: 109901
           Summary: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel
                    4.4rc4
           Product: File System
           Version: 2.5
    Kernel Version: 4.4.0-rc4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: ext4
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Actually, i'm usging linux-image-4.3.0-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.

I have the same problem with Rc5 & Rc6

- Debian Jessie
- dell XPS 9350 (december 2015, professionnal version, no developer version)

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.