** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: 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/1660704
Title:
linux: 4.4.0-63.84 -proposed tracker
For this kernel, no audio. Failure mode is like 4.4 mainline.
Just to understand: the strategy is to bisect between two mainline
kernels with different failure modes (4.4 final and 4.5rc1), with the
hope that between the two there will be a good kernel?
--
You received this bug notification
Public bug reported:
asdf
ProblemType: Package
DistroRelease: Kali 2016.2
Package: linux-base 4.5
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Jan 29 20:56:53 2017
Dependencies:
** Changed in: kernel-development-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
** Changed in:
** Changed in: kernel-development-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
--
You received this bug notification because
** Changed in: kernel-development-workflow/prepare-package-signed
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
** Description changed:
This bug
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660846
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660845
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660849
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Tested 4.2.0-19.23 kernel, same issue. Purging it off.
So, quick question... between "v4.4-wily" which worked and "linux-
image-4.4.0-1-generic", is the difference there the Ubuntu
customizations applied to the official Kernel build? Thus is something
in how Ubuntu customizes the Kernel source
Public bug reported:
When doing profile removal, the parent ns of the profiles is taken, but
the reference isn't being put, resulting in the ns never being freed
even after it is removed.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660842
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660840
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Public bug reported:
apparmor is leaking the parent ns ref count, by directly returning the
error
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Yakkety)
Public bug reported:
apparmor is leaking pinfs refcoutn when inode setup fails.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Yakkety)
Importance:
4.8.0-040800rc7 201701311526 failed
--
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/1659340
Title:
Linux kernel 4.8 hangs at boot up
Status in linux package in Ubuntu:
In Progress
Public bug reported:
The error condition of security_pin_fs() was not being checked which
will result can result in an oops or use after free, due to the fs pin
count not being incremented.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu
lightdm-gtk-greeter does not work fine... no visual countdown/other
display of the autologin timeout. See
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/902852/comments/31
XDM also does not allow to cancel autologin before the time elapses.
--
You received this bug notification because
** Changed in: apparmor
Status: In Progress => Invalid
--
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/1634753
Title:
srcname from mount rule corrupted under load
Status in
Public bug reported:
Bind mounts can oops when devname lookup fails because the devname is
unintialized and used in auditing the denial.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
When an fd is disallowed from being inherited during exec, instead of
closed it is duped to a special apparmor/.null file. This prevents the
fd from being reused by another file in case the application expects
the original file on a give fd
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660834
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660833
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660832
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660836
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Changed in: kernel-development-workflow/promote-to-release
Status: New => Fix Released
** Changed in: kernel-development-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-development-workflow/regression-testing
Status: Confirmed => Fix
Public bug reported:
@new does not have a reference taken locally and should not have its
reference put locally either.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
**
Public bug reported:
When using nested namespaces policy within the nested namespace is trying
to cross validate with policy outside of the namespace that is not
visible to it. This results the access being denied and with no way to
add a rule to policy that would
Public bug reported:
When a new label is created, it is created with a proxy in a circular
ref count that is broken by replacement. However if the label is not
used it will never be replaced and the circular ref count will never
be broken resulting in a leak.
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
This bug was fixed in the package linux - 4.9.0-15.16
---
linux (4.9.0-15.16) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1658101
* Zesty update to v4.9.5 stable release (LP: #1658099)
- Input: xpad - use correct product id for x360w controllers
** Tags added: block-proposed
--
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/1660738
Title:
linux: 4.9.0-16.17 -proposed tracker
Status in Kernel Development Workflow:
In Progress
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1660829
Title:
Undefined func on
Public bug reported:
Functions from mm/huge_memory.c is exported with include/linux/huge_mm.h header
but only when
context CONFIG_TRANSPARENT_HUGEPAGE is defined , when
CONFIG_TRANSPARENT_HUGEPAGE is not set
missing errors from compiler i expect this on include/linux/huge_mm.h bellow:
#ifdef
v4.8-rc7-201701311339 failed
v4.8-rc7-201701311526 failed
--
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/1659340
Title:
Linux kernel 4.8 hangs at boot up
Status in linux package in
** Tags removed: block-proposed
--
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/1660738
Title:
linux: 4.9.0-16.17 -proposed tracker
Status in Kernel Development Workflow:
In Progress
** 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.
https://bugs.launchpad.net/bugs/1660389
Title:
Netgear USB Wifi Adapter Model A6100 AC600 Dual Band
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811523/+files/ProcInterrupts.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
I did the apport-collect 1660389 but in the meantime I installed the driver
manually to get it to work. Do I need to uninstall the driver for this device
for further investigations?
The apport-collect 1660389 was done when I had the driver installed.
--
You received this bug notification
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811519/+files/Lspci.txt
--
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/1660389
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811520/+files/Lsusb.txt
--
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/1660389
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811522/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811515/+files/CRDA.txt
--
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/1660389
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811521/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811518/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811516/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1660389/+attachment/4811517/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected yakkety
** Description changed:
Bug #1462563 is the same but is closed. I have the device and can send logs.
Device will not work.
I could do the apport-collect
Description: Ubuntu 16.10
Release: 16.10
+ ---
+ ApportVersion:
I started a kernel bisect between 4.4 final and v4.5-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1289ace5b4f70f1e68ce785735b82c7e483de863
The test kernel can be downloaded from:
I built a Xenial test kernel with the patch mentioned in comment #3.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1654288/
Can you test this kernel and see if it resolves this bug? You would
need to install both the linux-image and linux-image-extra .deb
I built the next test kernel, up to the following commit:
1297667083d5442aafe3e337b9413bf02b114edb
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340/1297667083d5442aafe3e337b9413bf02b114edb
Can you test that kernel and report back if it has the bug or not? I
Can you test the 4.2.0-19.23 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8287821
--
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/1656605
Title:
No
Same defect with both the https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11923303 and
https://launchpad.net/ubuntu/+source/linux/4.3.0-7.18 kernel builds.
I am back booted to linux-image-4.4.0-59-generic and all other kernels
have been purged back off the server.
Please
Thanks for testing Yakkety. I reviewed the git logs between Xenail and
Yakkety and there are many drm commits. It would be easiest to perform
a Reverse bisect.
Commit 14de6c44d was added to Yakkety in Ubuntu-4.6.0-0.1. Can you test the
following kernel:
Yes, 4.4.0-21 is good, just like 4.4.0-59.
--
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/1657994
Title:
Regression: HDMI audio produces no sound (Skylake NUC)
Status in linux package
4.8.0-040800rc7.201701311339 failed
--
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/1659340
Title:
Linux kernel 4.8 hangs at boot up
Status in linux package in Ubuntu:
In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Tags removed: block-proposed
--
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/1658101
Title:
linux: 4.9.0-15.16 -proposed tracker
Status in Kernel Development Workflow:
In Progress
I built the next test kernel, up to the following commit:
6edf523
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326/6edf523
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same here. If it's not an issue, then something else definitely is, as i
can't access the Internet. Ping returns name or service not known. The
WiFi connection information does return an ipv4 address though.
--
You received this bug notification because you are a member of Kernel
Packages, which
I'll start putting test kernels in unique directories, so I don't remove them.
I built the next test kernel, up to the following commit:
7597cdc066313bfd211cca2f9252dfeb41271391
The test kernel can be downloaded from:
I'm unable to create a patched kernel - I'd try if I could
--
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/1310594
Title:
Lenovo Onelink Pro Dock - No audio via Dock-HDMI
Status in
My 4.4.0-42 kernel which booted fine and was my workaround for months
now hangs at boot like the later versions. I also discovered that I can
boot in 42 recovery mode and I get asked the luks password at boot. I
suspect a bad interaction with something else that got updated like
possibly the
Kees - there are archive shenanigans involved in getting a signed kernel
binary, hence the separate package.
Steve - I'm not sure about the rationale for grub booting unsigned
kernels. The foundations team might be able to explain it.
--
You received this bug notification because you are a
v4.8-rc7-201701311126 failed
--
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/1659340
Title:
Linux kernel 4.8 hangs at boot up
Status in linux package in Ubuntu:
In Progress
Status in
** Changed in: linux (Ubuntu Trusty)
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/1658270
Title:
Backport Dirty COW patch to prevent
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/1588529
Title:
Test bug 2. please ignore but do not close.
Status in linux
Mark - there is a 4.9 kernel in the Zesty release pocket with more
updates on the way. We should have a 4.10 kernel in the archive within a
couple of weeks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It was not possible to create or handle the tracking bugs for the following
packages (their tracking bugs based on this update must be handled manually):
linux-lts-zesty (16.04.1)
** Changed in: kernel-development-workflow/prepare-package
Status: New => Confirmed
** Changed in:
Can you test the 4.4.0-21 kernel next:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168
If it is good, we can bisect between 4.4.0-21 and 4.6.0-10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
This bug is for tracking the 4.9.0-16.17 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:
This either was never fixed or broke again, perf links neither against
libunwind or libdw:
$ ldd /usr/lib/linux-tools/4.8.0-37-generic/perf
linux-vdso.so.1 => (0x7ffee7766000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7efec8bb9000)
librt.so.1
I added the tag and marked the bug as confirmed. The upstream kernel is
one of the kernels I tried in my original bug report.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a
v4.8.0-040800rc7-201701311126 failed
--
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/1659340
Title:
Linux kernel 4.8 hangs at boot up
Status in linux package in Ubuntu:
In Progress
Public bug reported:
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
by originating either directly
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1660721
linux-snapdragon - bug 1660724
linux-aws - bug 1660727
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
I'll start putting test kernels in unique directories, so I don't remove
them.
I built the next test kernel, up to the following commit:
2507c856620cc7474e6101b0a05f82ac0ae5bf69
The test kernel can be downloaded from:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
--
You received this bug
Public bug reported:
This bug is for tracking the 4.4.0-63.84 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:
** 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/1625318
Title:
Ubuntu 16.10 KVM SRIOV: if enable sriov
** 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/1649718
Title:
Linux rtc self test fails in a VM under
** 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/1630924
Title:
Kdump through NMI SMP and single core not
** 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/1658270
Title:
Backport Dirty COW patch to prevent
@jj, any updates on the progress of the fixes?
--
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/1658625
Title:
linux i386 ADT apparmor self-tests OOM machine with linux-4.9.0-12.13
So I'm the OP on this bug report from what seems like ages ago...
While a lot of hard work as been done by some of the members posting
here to try and replicate it, it's been very difficult to track the
specific event that has been causing this.While we "fixed" our
problem a long time ago by
** Package changed: linux-meta-lts-xenial (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1660587
Title:
Dracut cannot be used to generate kernel initramfs image
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 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
1 - 100 of 155 matches
Mail list logo
