Due to the wireguard breakage noted in Comment #1, the patch "net: Fix
CONFIG_NET_CLS_ACT=n and CONFIG_NFT_FWD_NETDEV={y, m} build" will be
deferred.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18701
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870142
Title:
Focal update: v5.4.29 upstream stable release
To manage
Issue resolved: The wireguard breakage was fixed by wireguard-linux-
compat 1.0.20200401-1ubuntu1, and the upstream stable commit mentioned
in comment #1 has now been merged into focal along with the rest of this
patch set.
--
You received this bug notification because you are a member of Ubuntu
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870571
Title:
Focal update: v5.4.30 upstream stable release
To manage
pen()
+ net: ip_gre: Separate ERSPAN newlink / changelink callbacks
+ net: ip_gre: Accept IFLA_INFO_DATA-less configuration
+ tcp: repair: fix TCP_QUEUE_SEQ implementation
+ s390/qeth: handle error when backing RX buffer
+ ahci: Add Intel Comet Lake H RAID PCI ID
+ UBUNTU: upstream stable to v4.14.17
o use new variables for port ranges in bpf hook
UBUNTU: upstream stable to v4.19.102, v5.4.18
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progres
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
dle: teo: Avoid using "early hits" incorrectly
dm thin: fix use-after-free in metadata_pre_commit_callback
ASoC: topology: fix soc_tplg_fe_link_create() - link->dobj initialization order
UBUNTU: upstream stable to v4.19.102, v5.4.18
** Affects: linux (Ubuntu)
Importance: Undec
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Luis Henriques (henrix) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 4.4.0-1019.22 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 4.4.0-1
*** This bug is a duplicate of bug 1596012 ***
https://bugs.launchpad.net/bugs/1596012
** This bug has been marked a duplicate of bug 1596012
linux-lts-trusty: 3.13.0-91.138~precise1 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1595990 ***
https://bugs.launchpad.net/bugs/1595990
** This bug has been marked a duplicate of bug 1595990
linux-lts-vivid: 3.19.0-64.72~14.04.1 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Patch set submitted for kernel team review:
https://lists.ubuntu.com/archives/kernel-team/2016-June/078598.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592429
Title:
trusty kernel crash in OO
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592429
Title:
trusty kernel crash in OOM killer related to cgroups
To
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The "out of the normal cycle" kernel versions released yesterday were
for a security fix, and so do _not_ include the fix for this bug.
The "normal cycle" kernel versions that we're preparing this week _do_
include this fix. A note will be posted here as soon as those kernels
reach the -proposed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596635
Title:
KVM system crashes after starting guest
To manage notif
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592114
Title:
Device shutdown notification for CAPI Flash cards
To ma
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Also affects: linux (Ubuntu Yakkety)
Importance: Medium
Assignee: Alex Hung (alexhung)
Status: Confirmed
--
You received
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596469
Title:
[Bug]tpm initialization fails on x86
To manage notifica
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596557
Title:
Upstream patch "crypto: vmx - IV size failing on skciphe
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588056
Title:
cgroupfs mounts can hang
To manage notifications about
Public bug reported:
This bug is for tracking the 4.4.0-29.48 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workfl
Public bug reported:
This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-s
Public bug reported:
This bug is for tracking the 3.13.0-92.139 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-work
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587089
Title:
Hide "ballooned" memory from /proc in guest Ubuntu
To m
Public bug reported:
This bug is for tracking the 3.2.0-106.147 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-work
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days from
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
Affected users: As noted above, the kernel versions available in the
-proposed include this fix now. Since the problem can't be positively
verified, we'll consider the problem "verified" as long as we do not get
any reports to the contrary in the next few days.
So, if you install the -proposed ke
Moritz, its understood that this can only be "verified" as a long-term
stability issue. Please install the -proposed kernel on some of your
servers as a smoke test, and we'll consider if verified if you don't see
problems in the next few days.
--
You received this bug notification because you ar
Thanks for posting the handy instructions, Tim.
It isn't really necessary for all previously affected users to post
"positive" results (since they will necessarily be inconclusive anyway).
As long as we get at least a couple of folks (including myself) to
report no further instance of the problem
This has now been committed to Xenial, scheduled to be released in
4.4.0-30.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Summary changed:
- linux-ti-omap4: -proposed tracker
+ linux-ti-omap4: 3.2.0-1484.111 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 3.2.0-1484
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.2.0-1034.44 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 4.2.0-1034.44 u
Public bug reported:
This bug is for tracking the 4.4.0-30.49 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workfl
*** This bug is a duplicate of bug 1597897 ***
https://bugs.launchpad.net/bugs/1597897
** This bug has been marked a duplicate of bug 1597897
linux: 4.4.0-30.49 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567602
Title:
FCP devices are not detected correctly nor deterministic
We've bumped the current -proposed Xenial version number (to -30) for an
unrelated issue. This fix is still scheduled to be released in the next
Xenial cycle. A note will be posted here once it reaches -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
*** This bug is a duplicate of bug 1597902 ***
https://bugs.launchpad.net/bugs/1597902
** This bug has been marked a duplicate of bug 1597902
linux-raspi2: -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
*** This bug is a duplicate of bug 1597903 ***
https://bugs.launchpad.net/bugs/1597903
** This bug has been marked a duplicate of bug 1597903
linux-snapdragon: -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1597904 ***
https://bugs.launchpad.net/bugs/1597904
** This bug has been marked a duplicate of bug 1597904
linux-lts-xenial: 4.4.0-30.49~14.04.1 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.4.0-1017.23 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 4.4.0-1017.23 u
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 4.4.0-1020.23 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 4.4.0-1
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 verification is not done by 5 working days from t
** Changed in: linux-kvm (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux-kvm (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux-kvm (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux-kvm (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just FYI folks: This fix does not yet appear in the kernels which just
landed in -proposed (which are respins for an unrelated issue). The fix
is still queued up for the next cycle (currently 4.4.0-123.147).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
anged in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760672
Title:
test_regression_testsuite in ubuntu_qrt_appa
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received th
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Also affects: linux-kvm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Xenial)
Assignee: (unassigned) => Po-H
** Changed in: linux-kvm (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760646
Title:
test_072_config_debug_set_module_ronx in kernel sec
Verified fixed in all affected -proposed kernels:
trusty 3.13.0-146.195
xenial 4.4.0-123.147
artful 4.13.0-40.45
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
verification-done
701 - 800 of 3471 matches
Mail list logo
