This patch is already in Yakkety kernel. It will also be released as a
part of the Xenial HWE kernel in Ubuntu Xenial 16.04.2.
Marking this bug as Invalid for Yakkety and Xenial and direct interested
parties to the Xenial HWE kernel.
Prior to its release in February 2017 it can be tested by
Yeah an official fix would be nice. I am tired of getting up early to
see if I have to reboot any vm's :)
--
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/1470250
Title:
[Hyper-V] Ubuntu
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
When rebooting Windows guest, it gets 0x5c BSOD
Impact to 3.13 ( trusty )
- no Impact to 4.x
+ no Impact to 4.x
[Fix]
Upstream development
4114c27d450bef228be9c7b0c40a888e18a3a636
("KVM: x86: reset RVI upon system reset")
** Tags added: sts
--
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/1660519
Title:
Windows guest got 0x5c BSOD when rebooting
Status in linux package in Ubuntu:
Incomplete
Bug
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660519
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:
[Impact]
When rebooting Windows guest, it gets 0x5c BSOD
Impact to 3.13 ( trusty )
no Impact to 4.x
[Fix]
Upstream development
4114c27d450bef228be9c7b0c40a888e18a3a636
("KVM: x86: reset RVI upon system reset")
6d2a0526b09e551d0f395cfb63e7cb965db825af
("KVM: x86: Emulator
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1660518
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:
The following changes was pulled into atleast the Ubuntu Xenail Kernel release.
http://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu-xenial.git/commit/mm?id=b56d2a75e1daae6ff6eedfb732eadf3c13df6090
>From b56d2a75e1daae6ff6eedfb732eadf3c13df6090 Mon Sep 17 00:00:00 2001
It's been more than 1.5 years!
When can we expect this fix to be released?
$ uname -a
Linux Server123 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu
tests ran: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_01-59-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Doing some more testing it looks like the systems without the firmware
udpate are not stable. I can sometimes, but not always, get them to boot
using either 4.4.0-59-generic #80 or 4.4.0-62-generic #83, but once
they're up, they don't last long. The longest I've seen is about 40
minutes before
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-31_00-47-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: 0;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_01-30-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: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-31_01-03-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: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_00-15-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: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-31_00-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.
So, I appear to have spoken too soon on exactly what fixes this.
We have two systems being tested with 4.4.0-62-generic #83 - one with the
firmware update and one without.
The one with the firmware updates has been up for over 6 hours now without
any issues.
The one without firmware updates has
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-31_00-29-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We found testing with the latest Xenial kernel (4.4.0.62.65) from
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11278866 fixes this issue - no firmware
updates required. We did also test with just the latest firmware
updates, and that did not fix the issue. Latest
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-30_23-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.
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_23-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.
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
--
You received this bug
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_23-03-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: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_23-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.
4.8.0-040800rc7-generic #201701301734 passed
--
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
*** This bug is a duplicate of bug 1655842 ***
https://bugs.launchpad.net/bugs/1655842
On Mon, 30 Jan 2017, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
Good thought.
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/1660485
Title:
Screen flicker with Intel
tests ran: 36, failed: 22;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_22-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.
Public bug reported:
After updating from 14.04 to 16.04 xenial, I am experiencing a screen
flickering issue. The screen periodically completely blanks out. I tried the
following kernels:
4.10.0 (daily from 1/30/2017)
4.4.0-59 (ships with 16.04)
4.1.21 (recommended from another random thread)
I built the next test kernel, up to the following commit:
4b8b0ff60f1d6553914a5fc17f16f9aa38a2036e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
tests ran: 16, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_22-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.
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-30_20-58-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: 23, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_20-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.
4.8.0-040800rc7.201701301041 failed [on Lenovo 710S (KabyLake i5-7200)]
4.10-rc6 failed [on Lenovo 710S (KabyLake i5-7200)]
--
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
tests ran: 36, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_20-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: 11, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_19-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.
Guys?!:-P
--
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/1475078
Title:
VirtIO (and probably other modules as well) is built-in, make it
modular...
Status in linux package in
--- Comment From rsche...@us.ibm.com 2017-01-30 16:37 EDT---
I have tried the attached path to kdump-config, and it fixes the problem for
me. Kdump to multipath root disk works correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I built the next test kernel, up to the following commit:
8d2c0d36d6826ddc3114801c599619d3f2932f0a
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
tests ran: 36, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_18-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.
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-30_18-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.
Hi Tim,
I have the C6320P back and running. Do you hae a new 4.9 kernel to try, or
should I apply the same one above?
--
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/1643087
Title:
It uses less RAM than 16.10 and 16.04. Difference is about 500 MB on start and
1Gb after launching different applications.
It's hard for me to compare 14.04 and 17.04, because it's 2.5 years passed. But
I think moving to systemd increased RAM usage anyway. And some new versions of
daemons and
tests ran: 8, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_18-47-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So you're saying that kernel 4.9.0 cuts ram usage to 14.04 levels which
would be a reduction of about 600-700 megabytes.
On 01/30/2017 12:59 PM, Сергей wrote:
> For me problem is gone since upgrading kernel to 4.9.0.
> You can try to get it from 17.04 repo.
>
--
You received this bug
For me problem is gone since upgrading kernel to 4.9.0.
You can try to get it from 17.04 repo.
--
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:
Ubuntu 16.04 Unity desktop
tests ran: 36, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/dwalin__4.8.0-37.39__2017-01-30_17-07-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 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/1660419
Title:
After multiple sleep/resume
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_17-35-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:
This is a thinkpad x1 yoga with a touchscreen, working great under
Ubuntu 16.04. Except that, after some sleep/resume cycles, the
touchscreen stops to respond altogether. Rebooting solves the issue but
it is not ideal by a mile.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660416
Title:
zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
Status in
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_17-37-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:
ms core ttf fonts fail to install
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu14
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_17-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.
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
--
You received this bug
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_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: 4, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-30_17-18-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: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_17-58-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: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_17-31-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: initramfs-tools (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
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/1653489
Title:
As this is "for our awareness", marking as incomplete.
** Changed in: linux (Ubuntu)
Status: New => 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/1658968
Title:
** Changed in: linux (Ubuntu)
Status: New => 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/1659111
Title:
UbuntuKVM guest crashed while running I/O stress test with
Kernel team is aware of this bug, removing Tasty Taco
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
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/1659111
Title:
UbuntuKVM guest crashed
tests ran: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_17-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.
tests ran: 38, failed: 6;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_16-23-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_16-59-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: 0;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_16-30-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: 4, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_16-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.
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_16-12-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: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_15-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.
tests ran: 38, failed: 6;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onibi__4.8.0-37.39__2017-01-30_15-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.
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1656112
Title:
Power S822LC (8335-GTB) failes KVM guest cert test with
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/ms10-35-mcdivittB0-kernel__4.8.0-37.39__2017-01-30_15-58-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hardware:
Lenovo L450 [Processor: Intel® Core™ i5-5200U CPU @ 2.20GHz × 4; Graphics:
Intel® HD Graphics 5500 (Broadwell GT2)]
### Factory delivery (as was) with Microsoft Windows 8 pre-installed on
HDD.
### HDD removed and replaced for new SDD: Samsung SSD 850 EVO 250GB.
### Additional RAM slot
tests ran: 38, failed: 6;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/dwalin__4.8.0-37.39__2017-01-30_15-30-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: regression-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_16-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.
** Bug watch added: Linux Kernel Bug Tracker #193661
http://bugzilla.kernel.org/show_bug.cgi?id=193661
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=193661
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_15-59-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: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1659381
Title:
linux: 4.8.0-37.39 -proposed
Yes, the top entry in GRUB is the one to boot.
Sorry about posting the amd64 link for Yakkety. The i386 link is:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11923303
Now that we know the bug is in the earlies 4.4 Ubuntu based kernel, it would be
good to know if it
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-30_15-12-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-30_15-41-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/ms10-35-mcdivittB0-kernel__4.8.0-37.39__2017-01-30_15-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.
@Alex,
Your ACPI DSDT contains the following ACPI code:
Name (GUID, ToUUID ("33db4d5b-1ff7-401c-9657-7441c03dd766") /* PCI
Host Bridge Device */)
Name (SUPP, Zero)
Name (CTRL, Zero)
Name (XCNT, Zero)
Method (_OSC, 4, Serialized) //
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
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
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-30_15-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.
** 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/1659918
Title:
On include/linux/init_task.h issue
Status in linux
** 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/1659905
Title:
On include/linux/ftrace.h issue.
Status in linux package
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
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
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
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
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
Dear again,
Sorry for the noise.
I use Debian 8.7 and the kernel 4.8.
I've upgraded acpidump and now I can provide you a log :
http://sprunge.us/HjIG
Best regards.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 135 matches
Mail list logo
