Ubuntu

4.4.0-34 kernel booting bug, not certain how to report.

Asked by Ryan Budney

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 it sit for 10 minutes (way longer than an average boot time) and my laptop's fan was running full-tilt. But there was no hard-drive activity.

How can I find out what's going wrong? I'd like to know, and submit a proper bug report if it comes to that.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

If you boot the older kernel is it OK?

Revision history for this message
Ryan Budney (delooper) said : 		#2

Yes, the previous kernel runs flawlessly, as far as I can tell.

On Wed, Aug 10, 2016, 12:33 AM actionparsnip <
<email address hidden>> wrote:

> Your question #332444 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/332444
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> If you boot the older kernel is it OK?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/332444
>
> You received this question notification because you asked the question.
>

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Then I suggest you report a bug with the newer kernel. You can boot to the older kernel each time or even use GRUB to set the old kernel as default. If you get a new one you can try booting to it to see if the issue is resolved in the update.

Can you help with this problem?

Provide an answer of your own, or ask Ryan Budney for more information if necessary.

To post a message you must log in.