tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-16_04-34-00/results-index.html
--
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/1609913
tests ran: 83, failed: 32;
http://kernel.ubuntu.com/testing/4.8.0-9.10/dwalin__4.8.0-9.10__2016-09-16_00-44-00/results-index.html
--
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/1609913
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-16_03-52-00/results-index.html
--
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/1609913
tests ran: 19, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-16_03-54-00/results-index.html
--
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/1609913
Same as before with this one:
>This one was broken but not in the same way. With this >one, right
after the PC booted it gets stuck in a console >(only a blinking cursor
in the upper left corner) right >before plymouth is supposed to load.
>The keyboard and everything else is unresponsive. I had
** Changed in: kernel-development-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-development-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-development-workflow/prepare-package-signed
Status: New => Confirmed
**
*** This bug is a duplicate of bug 1624198 ***
https://bugs.launchpad.net/bugs/1624198
** This bug has been marked a duplicate of bug 1624198
linux: 4.6.0-13.15 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1624198 ***
https://bugs.launchpad.net/bugs/1624198
** This bug has been marked a duplicate of bug 1624198
linux: 4.6.0-13.15 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
This bug is for tracking the 4.6.0-13.15 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
kernel-phase-changed:Friday,
Public bug reported:
This bug is for tracking the 4.6.0-13.15 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: linux (Ubuntu)
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-16_03-17-00/results-index.html
--
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/1609913
Anton Polukhin, to clarify, what version of 802.11 are you using (ex.
802.11n)?
** Tags added: latest-firmware
--
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/1622293
Title:
rtl8821ae
brandon211, to keep this relevant to upstream, one would want check for,
and test the latest mainline kernel (now 4.8-rc6) as it is released.
Could you please advise?
** Tags added: bisect-done regression-update
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
** Tags removed: kernel-bug-exists-upstream-4.7-rc4
** Tags added: kernel-bug-exists-upstream-4.8-rc6
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tobias Suchy, if you are still having a sound issue, it will help immensely if
you filed a new report with the Ubuntu via a terminal:
ubuntu-bug audio
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
** Changed in: linux
Jean-Yves Avenard, it will help immensely if you filed a new report with the
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You
Aditya Duggal, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received
David DIDIER, to advise, I don't maintain those resources. I'm only
providing a suggestion to WORKAROUND the issue, and move this forward.
This is as you like.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
zwpwjwtz, could you please plug the Realtek device in, and post the results of
the following terminal command:
usb-devices
** Tags removed: regression-potential
** Tags added: needs-bisect regression-release vivid wily
--
You received this bug notification because you are a member of Kernel
tests ran: 19, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-16_02-17-00/results-index.html
--
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/1609913
tests ran: 22, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-16_01-09-00/results-index.html
--
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/1609913
Public bug reported:
The 'shareiscsi' property for ZFS volumes is listed in the manpage for
the 'zfs' command, but the property cannot be set on ZFS volumes.
root@monremonda:~# zfs create -V 25g zpt/eridian-zv
root@monremonda:~# zfs set shareiscsi=on zpt/eridian-zv
cannot set property for
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-16_00-51-00/results-index.html
--
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/1609913
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/dwalin__4.8.0-9.10__2016-09-15_23-13-00/results-index.html
--
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/1609913
Public bug reported:
Also: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for
module i915_bpo
Ubuntu 16.04 Xenial
Packages:
ii linux-firmware1.157.3 all Firmware for
Linux kernel drivers
ii linux-image-generic 4.4.0.36.38 amd64
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-15_21-22-00/results-index.html
--
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/1609913
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-15_20-50-00/results-index.html
--
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/1609913
Hi Joseph --
I installed the linux-image and -extra debs, rebooted, chose 4.4.0-36
from the advanced menu, and things work as expected. Installation was
fine as well.
Testing performed:
* No frequency polling errors in kern.log (notice nothing since Sep 12
when I was running the ubuntu
The issue still appears on the linked upstream kernel
(4.8.0-040800rc6-generic) and the kernel from xenial (linux-
image-4.4.0-36-generic).
** Tags added: kernel-bug-exists-upstream xenial
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
I built a Xenial test kernel with the patch you posted. The test kernel
can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1622763/
Can you test this kernel and see if it resolves this bug? If it does, I
can send the patch upstream and SRU it to the Ubuntu kernels.
You just need
tests ran: 19, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/dwalin__4.8.0-9.10__2016-09-15_21-45-00/results-index.html
--
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/1609913
Just installed the new Ubuntu base that arrived as an OS update and
contained a compiz upgrade - no discernible improvement.
--
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/1572801
Title:
Did you nuke xscreensaver and or light lock. If you disabled all else
(for testing) the last option should apply prior to resuming.
Blinking Green power = Suspend
No light on power = Hibernate
Solid green power = xautolock, screensaver, or equivalent
Prior - I could make hibernate and suspend
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-15_21-32-00/results-index.html
--
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/1609913
** Changed in: dkms (Ubuntu Xenial)
Status: New => In Progress
** Changed in: dkms (Ubuntu Yakkety)
Status: Triaged => In Progress
** Changed in: dkms (Ubuntu Trusty)
Status: New => In Progress
** Changed in: dkms (Ubuntu Trusty)
Assignee: (unassigned) => Brian Murray
** Description changed:
- The apport package hook for dkms packages seems to have an error in its
- supported kernel check. If the kernel is an unsupported one, the hook
- should exit with a return code of 1. However, in the Ubuntu Error
- Tracker we can see some crashes with unsupported kernel
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-15_18-48-00/results-index.html
--
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/1609913
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-15_21-01-00/results-index.html
--
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/1609913
tests ran: 35, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-9.10/dwalin__4.8.0-9.10__2016-09-15_19-48-00/results-index.html
--
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/1609913
Well, it is good to know that others have the same problem as myself,
but the comments do not all add any new information in order to help
address the issue. The problem CANNOT just be a straight memory leak or
CPU usage issue. I am running 16.04.1 on a 64-bit Dell I with Radeon
graphics and
I built the next test kernel, up to the following commit:
dcf9fa00268dd24d9ecaa4f84cc6d07de8bd86a7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1608236
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
** Summary changed:
- dkms_packages.py supported kernel check seems wrong
+ dkms_packages.py supported kernel check is wrong
** Summary changed:
- dkms_packages.py supported kernel check is wrong
+ dkms_packages.py supported kernel check is not working
--
You received this bug notification
It looks like we can perform a reverse bisect between 4.4 final and
4.5-rc1. Can you give 4.4 final a test, just to confirm it exhibits the
bug and it wasn't introduced in on of the stable updates in 4.4? 4.4
final can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-15_18-05-00/results-index.html
--
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/1609913
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
We can also perform a kernel bisect to identify the commit that
introduced this regression.
--
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/1621699
Title:
Upgrade to 16.04.1 LTS
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1624043
Title:
Call to
** Changed in: dkms (Ubuntu)
Status: New => Triaged
** Changed in: dkms (Ubuntu)
Importance: Undecided => Medium
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Also affects: dkms (Ubuntu Trusty)
Importance: Undecided
Status: New
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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
You can install the .deb packages by using the dpkg command from a
terminal. For example:
sudo dpkg -i linux-
image-3.13.0-95-generic_3.13.0-95.142~lp1470250faulpeltzPatchBAckported_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Yes, there is no need to install the headers.
--
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/1609242
Title:
Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Status in linux
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.8
The issue is the ValueError string content changed or was never correct.
*** ValueError: package linux-headers-4.6.1-040601-lowlatency does not
exist
vs.
try:
supported_kernel = apport.packaging.is_distro_package(kernel_package)
except ValueError as e:
if str(e) ==
Well, it changed in 2012...
$ bzr log -r 1369.34.701 -p
revno: 1369.34.701
committer: Martin Pitt
branch nick: apport
timestamp: Tue 2012-09-18 12:12:33 +0200
message:
* packaging-apt-dpkg.py: When
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.8
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.8
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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
@Timo Aaltonen (tjaalton): after reading your comment, I decided to
install kernel 4.4.0-23.41, but it isn't available on the repo anymore,
so I installed kernel 4.4.0-24 (if "that revert is already in the xenial
kernel since Ubuntu-4.4.0-23.41", then installing kernel 4.4.0-24
shouldn't be a
Hi David,
Do you plan on sending the patch upstream?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Can you see if this issue also happens with the latest daily image? It can be
downloaded from:
http://cdimage.ubuntu.com/daily-live/current/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in: linux
Would it be possible for you to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8
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
This bug does not exist in kernels prior to v4.4.0-30? If that is the
case, we might be able to perform a kernel bisect to identify the commit
that introduced the regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_19-25-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 83, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_18-44-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This could be a hardware issue with the touchpad due to the fact a
previous kernel that once worked no longer works.
It might be worth trying a LiveCD from one of the prior releases to see
if the issue still happens.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed
Please add a note when these patches show up in linux-next.
--
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/1623750
Title:
Request to backport cxlflash patches to Xenial SRU stream
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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
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.8
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.8
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.8
Also, does this issue go away if you boot back into the prior kernel
version?
** Tags added: kernel-da-key yakkety
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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.8
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_19-04-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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.8
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.8
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.8
On Thu, Sep 15, 2016 at 06:21:33PM -, Stéphane Graber wrote:
> I'm assuming you have a system that's booted with the right kernel
> option.
>
> Can you check if /sys/devices/system/cpu/possible includes the isolated
> CPU?
>
> If not, then we could copy that value instead of having to parse
tests ran: 19, failed: 8;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-15_18-55-00/results-index.html
--
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/1609913
Hi Joshua-
Before applying this, we'd like more details about the "additional SR-
IOV issues" you noted in comment #15. Can you clarify what those issues
are, and what level of testing has been done to validate the ixgbevf
changes? Thanks!
--
You received this bug notification because you are
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_19-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/dwalin__4.8.0-9.10__2016-09-15_17-02-00/results-index.html
--
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/1609913
tests ran: 83, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_18-27-00/results-index.html
--
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: New => 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/1624037
Title:
Xenial update to v4.4.21 stable release
Status in
@Shankey or @daniel philips,
Would it be possible for you to open a new bug? There have been many
comments in this bug report. Having a new bug will allow for easier
tracking. It sounds like this is a regression, so we should be able to
perform a bisect with the new bug report and identify the
tests ran: 136, failed: 27;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_17-51-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 35, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-15_17-14-00/results-index.html
--
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/1609913
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-15_17-05-00/results-index.html
--
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/1609913
tests ran: 136, failed: 27;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_18-00-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm assuming you have a system that's booted with the right kernel
option.
Can you check if /sys/devices/system/cpu/possible includes the isolated
CPU?
If not, then we could copy that value instead of having to parse the CPU
ranges from /sys/devices/system/cpu/isolated and substract that from
That error is not seen with 4.8 kernels
** Tags removed: wily
--
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/1504441
Title:
[4.2.0-16.19] kernel: nf_conntrack: automatic helper
This is the check for kptr_restrct functioning correctly failing. It's
failing on the contents of /proc/self/stack, which apprently in the run-
under-root case contains only the following line:
[<>] (null)
for ppc64el/3.19 (aka vivid). Given that there's no valid
Vendor Netgear
Hardware VersionWNDR4000
Firmware VersionV1.0.2.4_9.1.86
GUI Language VersionV1.0.2.4_2.1.17.1
Firmware is up-to-date, I've updated it a few days ago.
--
You received this bug notification because you are a member of Kernel
Packages, which is
/sys/devices/system/cpu/isolated tells you which cpus are isolated.
--
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/1623143
Title:
Linux container does not take same cpu configuration as
This bug was fixed in the package shim-signed - 1.18~12.04.1
---
shim-signed (1.18~12.04.1) precise; urgency=medium
* update-secureboot-policy: If /proc/sys/kernel/moksbstate_disabled is
present, prefer this unconditionally over MokSBStateRT. LP: #1604873.
-- Steve Langasek
tests ran: 18, failed: 7;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_17-51-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 18, failed: 7;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_17-43-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 32, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_17-01-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 32, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_16-48-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onibi__4.8.0-9.10__2016-09-15_16-08-00/results-index.html
--
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/1609913
** Changed in: linux (Ubuntu Xenial)
Status: New => 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/1621113
Title:
Xenial update to v4.4.20 stable release
Status in
1 - 100 of 177 matches
Mail list logo