got fixed with an updated release
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: ubuntu-z-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages,
Also, it might be good to test the latest mainline kernel to see if this
bug is already fixed. If it is fixed, we can instead perform a
"Reverse" bisect to identify the commit that fixes the bug.
The current mainline kernel can be downloaded from:
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?
v4.4.13:
** Tags added: kernel-da-key
** Tags added: performing-bisect
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16041
--
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/1607325
Title:
Ubuntu 16.04 running on z13 hardware is
7 matches
Mail list logo
