** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1594569
Title:
package linux-headers-3.13.0-32 3.13.0-32.57~precise1 failed to
enable proposed, install the kernel update and see if it helps?
--
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/1553503
Title:
multi monitors - black flashes or black screen when the
It seems that the cpuset cgroup is causing this. Using the script below
I get this output:
In cgroup:
Cpus_allowed: f
Cpus_allowed_list: 0-3
Outside cgroup:
Cpus_allowed: e
Cpus_allowed_list: 1-3
The script:
#!/bin/bash
set -e
export CGDIR=/sys/fs/cgroup/cpuset/cpusets-$$
More test results:
v4.5 mainline build -> No oops, no problems
v4.5-rc1 mainline build -> No oops, no problems
v4.4.21 mainline build -> Same oops
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bump, anything new?
there are quite a number of peoples waiting here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1553503 ***
https://bugs.launchpad.net/bugs/1553503
Public bug reported:
When the mouse cursor leaves one of the screens, there is either :
- no problem
- the screen becomes black just below the position of the cursor and
instantly comes back to
Christopher M Penalver: There is an AskUbuntu issue for my particular
problem - something a lot like it - you can find it here:
http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
hangs I've asked if they also saw the CPU underrun - no answer yet.
FWIW, I just installed
I can confirm that trusty + linux-generic-lts-xenial from -proposed
looks good. I can now run sbuild with a tmpfs overlay, with
4.4.0-36-generic debconf would die with ESTALE during chroot setup.
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Tim: I have purged xautolock a long time ago (due to other reason) but
I am still having the freezes ( from which I recover by a keyboard key
combination that I mapped to: xrandr --auto )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
tests ran: 13, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-38.57/onza__4.4.0-38.57__2016-09-15_06-33-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/1620658
Verification-successful for shim-signed on precise --- all that is
required is there: the update-secureboot-policy script does what it
should and is run as expected.
However, it looks like MokManager.efi (which isn't something coming from
shim-signed) isn't installed on the system under
I have this bug since I installed Ubuntu 16.04 on my Dell Optiplex 980 with
Intel Graphics. My Kernel is, I think, "4.4.0-36-generic x86_64"
Is there any more info I could gather to help with it or I just need to
wait for the fix to come?
ps.: I am not an advanced user.
Thanks.
Em qui, 15 de
@penalvch , I've tested again on kernel 4.8-rc6, and from suspend button
and closing lid, the system is not suspending. It only blocks the
screen, and after unblocking the screen, I cannot open a new terminal,
or access internet, or shutdown the system neither.
When suspending with command 'sudo
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_15-10-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/s2lp6g002__4.8.0-9.10__2016-09-15_15-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.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1623804
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
The good news is that it looks like even though Cpus_allowed says CPU 0
is allowed the scheduler isn't going to actually schedule anything in
the cgroup to that CPU until something induces the cpuset code to
rebuild the scheduler domains. Primarily that would be writing to one of
the cpuset.cpus
You have been subscribed to a public bug:
I'm using Ubuntu 16.04 on a Lenovo ThinkPad T450s. This notebook has a
combined headphones/mic "headset"-jack as used by pretty much every
smartphone nowadays.
I have a Plantronics-Headset HW251/A - SupraPlus Monaural and a 4-pin
3,5mm jack cable, made
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp4__4.8.0-9.10__2016-09-15_15-28-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/dwalin__4.8.0-9.10__2016-09-15_15-20-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
https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions
suggests filing against the kernel.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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/1623820
Title:
USB devices routed into
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-38.57/onibi__4.4.0-38.57__2016-09-15_08-21-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/1620658
Yes but I have only one other account with another provider and that's
the one I don't want to put on the internet for everybody to see... why
are yahoo domain rejected??? that's insane, and the whole process is
just way too complicated even for tech savvy people. so my only option
is to open
mforonda, based on what has been seen and historically, bugzilla hasn't
been getting the attention one may expect. However, a message to the
mailing list typically leads the discussion for upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is
brandon211, could you please advise to the full details of that commit
number for this report (author, signed off by, etc.)?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => 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/1586195
Title:
Realtek 8153-based ethernet adapter on usb3
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
--
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/1620658
Title:
linux: 4.4.0-38.57 -proposed
tests ran: 4, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/kernel02__4.8.0-9.10__2016-09-15_15-42-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: 2, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-9.10/modoc__4.8.0-9.10__2016-09-15_16-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.
https://bugs.launchpad.net/bugs/1609913
yes, if you don't install the metapackage then you need to install
linux-image-extra-4.4.0-38-generic too
--
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/1553503
Title:
multi monitors -
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-9.10/onza__4.8.0-9.10__2016-09-15_15-24-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
@straber: I don't think this is a kernel bug after all.
You said that LXD will not alter the CPU pinning in any way. But it must
write _something_ to cpuset.cpus before you can add any tasks to the
cgroup. So I assume that by "not altering" you mean it just copies the
value from the parent
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
tests ran: 4, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-9.10/s2lp6g002__4.8.0-9.10__2016-09-15_15-38-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/1619756
Title:
backport support for userspace access of DP aux
** Description changed:
Testing failed on:
- ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20160831_110223@/log.gz
+ ppc64el:
My car (Renault, from April 2015, with built-in TomTom) does detect my BQ
Aquaris E5 Ubuntu ed (OTA-12) but does not pair or connect.
The phone's bluetooth works well with other bluetooth devices.
--
You received this bug notification because you are a member of Kernel
Packages, which is
RalinkRt3290 wifi broken after upgrade to kernel 4.4.0.36 Xenial 16.04
LTS. Network -manager reports device not ready.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1049466
** 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/1619552
Title:
Failed to acknowledge elog:
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-38.57/onza__4.4.0-38.57__2016-09-15_13-26-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/1620658
@tjaalton Thank you, I followed https://wiki.ubuntu.com/Testing/EnableProposed
to enable proposed and ran "sudo apt-get install linux-image-4.4.0-38-generic".
But after reboot I had a low screen resolution on my laptop and it did no
longer recognize my 2nd screen at all (did not turn on, xrandr
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1599924
Title:
embed derivative kernel target names in
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
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.
I thought of looking at Cpus_allowed from the status file of the current
task or of pid 1, but since both of those would be affected by the task
being in a non-root cgroup, we can't rely on that.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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/1624043
Title:
Call to fork/clone fails with
So the problem here is that LXD itself DOES NOT touch the cpuset
controller at all.
liblxc does have some initialization code in place which will copy the
parent value for cpuset.cpus and cpuset.mems if cgroup.clone_children
hasn't been set to 1 yet.
So I guess we'd need a change to the cgfsng
** 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
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.
Public bug reported:
I wrote a test program that forks processes until the fork calls start
to fail. It forks around 12000 processes and then the fork calls start
failing with EAGAIN. According to the fork man page, there are four
conditions that could cause EAGAIN to be returned:
- the
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.
** 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
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.
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: 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
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
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.
/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
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
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
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.
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: 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: 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.
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
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
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
@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
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
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
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
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.
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
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
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
@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
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
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:
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
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
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: 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
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
1 - 100 of 177 matches
Mail list logo
