kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.

Can you test the following kernels and post back?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt1-wily/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt2-wily/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt3-wily/

You don't have to test every kernel, just up until the first kernel that
has this bug.

Thanks in advance!

** Tags added: kernel-da-key wily

-- 
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/1548985

Title:
  After linux kernel update system won't boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try updating packages listed bellow via Software Updater,
  Ubuntu gets stuck on purple screen after restart. No key combination
  seems to do anything. I can login to desktop only via recovery and
  then normal boot option. I'm using Ubuntu 15.10.

  linux-generic 
  installed version 4.2.0.16.18
  available version 4.2.0.30.33

  linux-firmware
  Installed version: 1.149
  Available version: 1.149.3

  linux-headers-generic
  Installed version: 4.2.0.16.18
  Available version: 4.2.0.30.33

  linux-image-generic
  Installed version: 4.2.0.16.18
  Available version: 4.2.0.30.33

  linux-headers-4.2.0-30
  Installed version: None
  Available version: 4.2.0-30.35

  linux-image-extra-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  linux-libc-dev
  Installed version: 4.2.0-16.19
  Available version: 4.2.0-30.35

  linux-headers-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  linux-image-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  I'm not sure if all of them seams to cause the problem.

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