Yes, the fix was released with 4.4.0-96.119 (linux-image version) in
Xenial/16.04 and 4.10.0-35.39 in Zesty/17.04.
--
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/1708399
Title:
kernel
Because it was told those were important, the backports from Martin were
tested in a separate kernel and we included those and the Zesty cherry-
picks in re-spins that were made last week. And those kernels moved to
updates today.
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
The version number is that of the meta package (linux-image-generic).
But as long as uname -r returns 4.4.0-96-generic the correct kernel is
running. And it should have the fixes included.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Changed in: ubuntu-z-systems
Status: Incomplete => In Progress
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1708399
Title:
kernel panic -not syncing: Fatal
Moving to "incomplete", pending patches landing upstream.
** 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.
https://bugs.launchpad.net/bugs/1708399
** Description changed:
+ SRU justification:
+
+ Impact: A race in context flushing is causing a kernel panic on the
+ s390x architecture.
+
+ Fix: Using a set of 3 patches (all restricted to arch code), one already
+ upstream and the other 2 pending on linux-next. Regression risk should
+ be
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: ubuntu-z-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is
Replaced the packages at http://people.canonical.com/~smb/lp1708399/
with the latest kernel and the three suggested patche on top.
--
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/1708399
Ah ok, thanks. Will add some info to the commit message and prepare that
test kernel.
--
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/1708399
Title:
kernel panic -not syncing: Fatal
In fact hunk #3 of the original patch was also dropped which removed the
check in a different location. Yet, the last hunk removes the check for
that from the flush functions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
While preparing to provide a test kernel I noticed that the backport for
patch #1 introduces a test for MACHINE_HAS_TLB_LC which is not present
even in linux-next. Martin, is this really correct?
+ /* Reset TLB flush mask */
+ if (MACHINE_HAS_TLB_LC)
+
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** No longer affects: ubuntu-power-systems
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1708399
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Tags added: kernel-da-key
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception: panic_on_oops
Status in The Ubuntu-power-systems
Applied patch and build packages:
http://people.canonical.com/~smb/lp1708399/
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception:
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug
according to the logs it might affect more docker than the kernel:
- docker is used on that system (at least since Aug 1st)
- but I cannot find that docker.io is used - which docker version is in use?
dpkg log doesn't show me that docker.io got installed
- seems to be a docker issue that is
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
--
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/1708399
Title:
kernel panic -not syncing: Fatal exception: panic_on_oops
29 matches
Mail list logo
