Comment 0 for bug 1611831

Greetings,

I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu 16.04. If I try booting from 4.4.0-34, my system freezes just after I enter my password to decrypt my hard-drive. If I ask it to boot from 4.4.0-31, everything is fine.

My boot.log file:

  lvmetad is not active yet, using direct activation during sysinit
  Volume group "ubuntu-vg" not found
  Cannot process volume group ubuntu-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...
  Found volume group "ubuntu-vg" using metadata type lvm2
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  2 logical volume(s) in volume group "ubuntu-vg" now active
/dev/mapper/ubuntu--vg-root: recovering journal
/dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 blocks

It's unclear to me what is going wrong. There appears to be no activity on the computer. I let the boot sequence sit for 10 minutes (way longer than an average boot time) my laptop's fan is running full-tilt. But there was no hard-drive activity.

How can I find out what's going wrong?

I'm running Ubuntu 16.04 Linux on a Lenovo W530. I'm not certain what other information would be helpful for a bug report. I would be happy to submit whatever is deemed helpful.