kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

4.2-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc1-unstable/
4.2-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc4-unstable/
4.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/

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

Thanks in advance!

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: performing-bisect 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/1558764

Title:
  Sysrq trigger g cause system hang on Ubuntu 15.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I are using kgdb to debug kernel driver. The break point and sysrq
  work fine on Ubuntu 14.04. But when I upgrade Ubuntu from 14.04 to
  15.10, the sysrq trigger g (alt+sysrq+g) doesn't make gdb break and
  system hangs. It is a regression. The issue only happens after kernel
  booting up. It is OK during kernel booting.

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