That indicates the bug is either already fixed in upstream 4.4.16 or
it's an Ubuntu specific bug.

To confirm it's now fixed upstream, can you test 4.4.15.  It should
contain the bug, since Ubuntu 4.4.0-34 had those stable updates and not
the 4.4.16 stable updates.

The 4.4.15 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.15/


Another testing option would be to test the Xenial -proposed kernel.
Xenial -proposed now does have the v4.4.16 stable updates.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.

Thank you in advance!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611831

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  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. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  rybu       4449 F.... pulseaudio
   /dev/snd/controlC0:  rybu       4449 F.... pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware                            1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611831/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to