[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We can perform a "Reverse" kernel bisect to identify the commit that
fixes this in v4.9-rc7.
We first need to identify the last bad kernel and first good one. Can
you test the v4.9-rc1 kernel to try and narrow the affect versions down
further. It can be downloaded from:
I got the impression from my virtual server hoster (which runs the
hypervisor) that other customers don't have this issue.
I was also inquiried about my use of BTRFS as a filesystem, and I also
use Docker very heavily which makes heavy use of special BTRFS,
DeviceMapper and Cgroup features, which
I am now very confident that this bug is NOT present in 4.9-rc7,
therefore marking kernel-fixed-upstream.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
It appears as if the issue is NOT present in mainline 4.9-rc7. I will
wait a few more days to be sure before marking this 'kernel-fixed-
upstream', since the bug always appeared in a varying interval of 2-5
days, just to get a higher level of confidence.
--
You received this bug notification
For what it's worth, I am now running 4.9.0-040900rc7-generic since a
few minutes ago. The bug always hit me after 2-5 days but always under a
week, so I can tell you in at the earliest a week that the bug is or is
not in upstream with high certainty. (so around 9th of December)
--
You received
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
The kernel panic itself locks up the system instantly and therefore no
logging to disk happens of that error. Therefore, see the attached
screenshot of the qemu screen after the crash.
** Attachment added: "Screenshot of VM in Qemu after crashing"
10 matches
Mail list logo
