This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1642519
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 1642514
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
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-17_10-32-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_09-16-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: 31, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/dwalin__4.4.0-49.70__2016-11-17_08-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: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_09-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: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_08-49-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-28.30-generic/onibi__4.8.0-28.30__2016-11-17_08-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/modoc__3.19.0-75.83__2016-11-17_10-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.
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/modoc__3.19.0-75.83__2016-11-17_10-53-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Have the same problem at Ubuntu-16.04 fresh install.
Kernel version is 4.4.0-31-generic #50-Ubuntu.
dmesg of the failing xhci port is attached.
Is there anything I can additionally do to help with this?
** Attachment added: "dmesg of the failing xhci port"
** Changed in: hwe-next
Assignee: (unassigned) => Alex Hung (alexhung)
--
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/1642114
Title:
ThinkPad T460 hotkeys stop working in Ubuntu
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_07-57-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 1642510
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
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/dwalin__3.19.0-75.83__2016-11-17_07-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: 19, failed: 11;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-35-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_07-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.
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/onibi__4.8.0-28.30__2016-11-17_06-36-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-28.30-generic/modoc__4.8.0-28.30__2016-11-17_08-06-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 unable to run apport-collect 1639202 from the Precision 5510 after
the enlist stage fails.
--
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/1639202
Title:
Cannot enlist/commission
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1639202
Title:
Cannot enlist/commission machines in MAAS 2.1 with usb
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/ms10-35-mcdivittB0-kernel__4.4.0-49.70__2016-11-17_08-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.
Public bug reported:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: hwe-next
Importance: Undecided => Critical
** Changed in: hwe-next
Assignee: (unassigned) => Ying-Chun Liu (paulliu)
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
The following upstream fix is missing in xenial:
599b076d15ee ("i40e: fix call of ndo_dflt_bridge_getlink()")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=599b076d15ee
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
This is implemented in linux v4.5 by the following upstream patch:
1f211a1b929c ("net, sched: add clsact qdisc")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f211a1b929c
The backport is straightforward.
** Affects: linux (Ubuntu)
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_12-49-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: 4;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/modoc__3.19.0-75.83__2016-11-17_13-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.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/ms10-35-mcdivittB0-kernel__4.4.0-49.70__2016-11-17_14-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.
This should help:
https://forums.mageia.org/en/viewtopic.php?f=7=11220
http://www.linuxquestions.org/questions/linux-laptop-and-
netbook-25/can't-boot-into-hp-envy-15-ah150sa-radeon-after-
install-4175584667/
When installing remember to manually add acpi_no_static_ssdt
--
You received this
Hi Josh,
We missed your reply and now the folder is empty. Can you upload again
the test kernel so we can test it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1400319
Title:
tests ran: 31, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/dwalin__4.4.0-49.70__2016-11-17_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.
tests ran: 141, failed: 140;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_11-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: 64, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_11-40-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-28.30-generic/onibi__4.8.0-28.30__2016-11-17_10-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: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/ms10-35-mcdivittB0-kernel__4.4.0-49.70__2016-11-17_11-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.
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Luis Henriques (henrix)
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
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-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_11-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.
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Luis Henriques (henrix)
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
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.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_11-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-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_11-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.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** 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.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-17_11-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/modoc__3.19.0-75.83__2016-11-17_11-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: 5, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-17_12-18-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Can any one check if Queued TRIM issue is resolved in EXM03B6Q firmware
(available as of October 2016) for 850 Pro?
I'm not expecting Queued TRIM to work properly, but may be it is not advertised
as supported any more?
--
You received this bug notification because you are a member of Kernel
tests ran: 36, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/dwalin__4.4.0-49.70__2016-11-17_10-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.
Please ignore the comment from brad-figg as the above comment originated
from a bot.
That being said, I've had a bit of an opportunity to research this.
Initramfs-tools is responsible for updating the initramfs and including
modules in the initramfs. Unfortunately I don't think that adding
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-17_12-42-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/ms10-35-mcdivittB0-kernel__4.4.0-49.70__2016-11-17_12-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.
** 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/1642572
Title:
Xenial update to 4.4.31 stable release
** 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/1642573
Title:
Xenial update to 4.4.32 stable release
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1630554
Title:
QEMU throws failure msg while booting
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_12-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-28.30-generic/onibi__4.8.0-28.30__2016-11-17_12-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.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/modoc__3.19.0-75.83__2016-11-17_12-39-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
I've been running an on-off test on a couple of Power8 systems and have
been getting a failure of detection on the NVMe drives on Ubuntu 16.04.1
only. I've ran the same test on RHEL 7.2 and have not encountered this
proble. Once the problem occurs the OS
** Package changed: apport (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags removed: verification-done-yakkety verification-needed-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/1630554
Title:
QEMU throws failure msg while booting guest with
tests ran: 30, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onibi__3.19.0-75.83__2016-11-17_14-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.
** Changed in: linux (Ubuntu Yakkety)
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/1642606
Title:
Yakkety update to 4.8.7 stable release
** Changed in: linux (Ubuntu Yakkety)
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/1642607
Title:
Yakkety update to 4.8.8 stable release
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
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
tests ran: 19, failed: 10;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/ms10-35-mcdivittB0-kernel__4.4.0-49.70__2016-11-17_13-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:
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
Jean-Yves Avenard, to keep this relevant to upstream, one would want
check for, and test the latest mainline kernel (now 4.9-rc5) as it is
released.
Could you please advise?
** Tags removed: kernel-bug-exists-upstream latest-bios-fb07
** Tags added: bios-outdated-fb08 needs-upstream-testing
--
** Tags added: needs-reverse-bisect
--
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/1618600
Title:
Unclaimed register detected after reading register 0x65f10
Status in linux package in
Public bug reported:
Please backport libica upstream commit:
Fix msa level detection
Fixed problem in library constructor that was leading to false positive
msa level detection resulting in illegal instruction.
See also:
It is worth noting that I see the same warning ('WARNING: CPU: 1 PID: 1
at /build/linux-yFroJZ/linux-4.8.0/arch/x86/mm/dump_pagetables.c:225
note_page+0x6a1/0x880') with a 4.8 kernel. This is more likely a build
problem with modules, e.g.,
Nov 17 09:56:49 ubuntu kernel: [ 10.354579]
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_14-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.
Any e.t.a. on when it will be implemented?
Or can you let us know on this thread when it is?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1433906
Title:
Acer, Inc
This bug was fixed in the package linux-firmware - 1.157.5
---
linux-firmware (1.157.5) xenial; urgency=medium
* New firmware is required for some iwlwifi modules (LP: #1635091)
- iwlwifi: add new -17 firmware for iwlmvm devices
* Update linux-firmware in xenial for lts-y
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-firmware - 1.157.5
---
linux-firmware (1.157.5) xenial; urgency=medium
* New firmware is required for some iwlwifi modules (LP: #1635091)
- iwlwifi: add new -17 firmware for iwlmvm devices
* Update linux-firmware in xenial for lts-y
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
It seems like 14.04.0/1's kernel would still need this backport -- 3.13
base and the upstream fix went into 3.14.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
@faulpeltz
I agree. Your patch should also be included in case a FREEZE operation does
exceed the increased timeout.
I've attached a modified version of your patch that addresses some
concerns we had offline. Could you give it a try?
** Patch added:
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/fozzie__4.9.0-1.2__2016-11-17_20-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.
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/1642739
Title:
Kernel panic on shutdown
@Alex
The modified timeout should take care of the issue, but I think its a good idea
for the VSS daemon to issue a THAW before either exiting or trying to recover
--
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 1637520 ***
https://bugs.launchpad.net/bugs/1637520
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: debian-installer (Ubuntu)
** No longer affects: debian-installer (Ubuntu Yakkety)
--
You
tests ran: 3, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-17_20-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: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-17_19-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.
Public bug reported:
Since I have updated to Ubuntu 16.10 I have this problem where the
shutdown takes a long time (~30s) and ends with a (at least I think it
is) kernel panic with blinking harddrive- and battery status LEDs.
Nothing is visible on the screen.
This didnt happen on Ubuntu 16.04 so
** Description changed:
- Since I have updated to Ubuntu 16.10 I have this problem where the
- shutdown takes a long time (~30s) and ends with a (at least I think it
- is) kernel panic with blinking harddrive- and battery status LEDs.
- Nothing is visible on the screen.
+ Since I have updated to
tests ran: 19, failed: 11;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-35-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-17_20-13-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onibi__3.19.0-75.83__2016-11-17_19-56-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
I will try as soon as I have some spare time
@jsalisbury
Unfortunately I didnt have time to test the kernel from #341.
Including the #343 upstream commit should take care of our issue, and using the
patch from #345 (replacing my initial patch) should prevent any hv_vss_daemon
crashes in
--- Comment From craig.w...@us.ibm.com 2016-11-14 11:17 EDT---
dougmill-ibm commented 6 days ago
It appears that one of NVMe drives failed to function correctly during
boot/probe. The 'lspci' output does not show that drive, which means it was
taken after the failure but before recovery
Today I directly connected my computer through HDMI (with mini-
displayport adpater) to the projector and it works fine. It may be
important to note that my university has a console which is in-between
the projector and the computer that somehow controls what the device the
VGA is connected to. I
Beta version of the DKMS driver for FTE1001 touchpad (written by Brendan
McGrath, Victor Vlasenko and Frederik Wenigwieser) is available here:
https://github.com/vlasenko/hid-asus-fte-dkms
The driver seems to work well; everyone is welcome to try it out and
report any issues to github.
--
You
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onibi__3.19.0-75.83__2016-11-17_17-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.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/kernel02__4.8.0-28.30__2016-11-17_16-16-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 193 matches
Mail list logo
