tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-18_06-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: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_06-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.
tests ran: 19, failed: 7;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_06-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: 19, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_06-12-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_05-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: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_06-19-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 19, failed: 17;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_05-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-18_04-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.
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/1642821
Title:
Touchpad 3 button click no
Public bug reported:
After suspending the laptop, middle click) on Yoga 2 pro touch pad stops
working. Sometimes middle click emulation survives 3 or more suspends,
but usually not more than 5.
Only method to restore middle click is to reboot.
All other touch pad functionality works fine.
tests ran: 5, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_05-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_04-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: 5, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_05-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 5, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_05-19-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 3, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_04-05-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 2, failed: 2;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_04-54-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: hwe-next
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/1634607
** Changed in: hwe-next
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
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.
** Changed in: hwe-next
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
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.
tests ran: 10, failed: 10;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_04-23-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_04-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: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-18_02-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.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_03-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: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_04-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: 1, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_03-57-00/results-index.html
--
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/3.19.0-75.83~14.04.1-generic/modoc__3.19.0-75.83~14.04.1__2016-11-18_03-32-00/results-index.html
--
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.8.0-28.30-generic/s2lp4__4.8.0-28.30__2016-11-18_03-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.
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-18_02-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: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-18_02-19-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.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-18_01-11-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.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-18_00-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.
*** This bug is a duplicate of bug 1642241 ***
https://bugs.launchpad.net/bugs/1642241
The bug is in the nvidia driver 370, which appears to not exist in the
Ubuntu archive(?)
So this bug would be invalid for Ubuntu in general but it's also been
reported against Ubuntu proper using earlier
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/gonzo__4.9.0-1.2__2016-11-18_00-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.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/pepe__4.9.0-1.2__2016-11-18_00-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.
** 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/1612006
Title:
I2C touchpad does not work on AMD
tests ran: 19, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-18_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: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/gonzo__4.9.0-1.2__2016-11-18_00-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.
We'll take a look at this right away. Thanks for the quick integration.
--
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/1641139
Title:
Infiniband driver (kernel module) needed for Azure
tests ran: 31, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-17_22-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: 6, failed: 3;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/pepe__4.9.0-1.2__2016-11-17_22-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.
--- Comment From wil...@us.ibm.com 2016-11-17 19:00 EDT---
I can reproduce the problem using the following steps:
brctl addbr boom
brctl stp boom off
brctl addif boom enP2p1s0f3
brctl delif boom enP2p1s0f3
enP2p1s0f3 is a port on a bnx2.
The Oops will occur when "brctl delif" is run.
Repurposing this bug for a yakkety d-i refresh.
** This bug is no longer a duplicate of bug 1637520
Yakkety update to v4.8.5 stable release
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Yakkety)
** No longer
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1642774
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: 36, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-17_22-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: 2, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/gonzo__4.9.0-1.2__2016-11-17_23-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.
Public bug reported:
See this in the kernel logs:
[ 132.233601] mlx5_core 0005:01:00.0: 0005:01:00.0:wait_func:744:(pid 1353):
CREATE_EQ(0x301) timeout. Will cause a leak of a command resource
[ 132.245278] mlx5_core 0005:01:00.0: 0005:01:00.0:mlx5_start_eqs:505:(pid
1353): failed to create
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/gonzo__4.9.0-1.2__2016-11-17_22-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: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/amura__4.9.0-1.2__2016-11-17_22-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: 19, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onibi__3.19.0-75.83__2016-11-17_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.
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
--- 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
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.
** 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
@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
*** 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
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
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.
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
@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: 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.
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
@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.
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.
I'll let @jsalisbury comment on the status of his backported patches.
@jsalisbury, I'd also take this recently submitted patch from upstream
kernel as well. It ensures that the VSS driver doesn't timeout any long
running FREEZE operations too early. This should preclude the need for
faulpeltz's
@chih: Was helping a user in #ubuntu today with the same device ID
(413c:8143). But I think I'm a bit confused by this, I'm looking at the
upstream source and I see:
$ grep 413c drivers/bluetooth/btusb.c
{ USB_DEVICE(0x413c, 0x8197) },
{ USB_DEVICE(0x413c, 0x8126), .driver_info =
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-1.2-generic/gonzo__4.9.0-1.2__2016-11-17_20-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: 5, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/dwalin__3.19.0-75.83~14.04.1__2016-11-17_20-01-00/results-index.html
--
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-1.2-generic/fozzie__4.9.0-1.2__2016-11-17_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.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1635721
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
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: Fix Committed
** Changed in: linux (Ubuntu Zesty)
Status: Fix Committed => In
Unfortunately the bug exists on the newest mainline kernel. It was hard
to test because it made my system very unstable (which is expected) and
I had trouble to get couple straight wake-ups from suspend to be able to
tell if it freezes like it did before. But it did freeze on third or
fourth
Any news on this? Recently it seemed like a fix was found, but no update
for about a month now.
Thanks guys!
--
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]
** Tags added: kernel-bug-exists-upstream
--
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/1641244
Title:
Ubuntu 16.04 suspend works only twice or thrice in a row, freezes at
next
Hi Canonical, any update on this bug? It is an important fix for 14.04
IMO
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1607894
Title:
Unable to analyse vmcore/dump via crash due to
I have it both on a MacBook Air 2011 11" and a MacBook Pro 2015 13"
This is a bug in 16.10
It did not exist in 16.04
It appears to be for ALL 16.10 kernels to date, ie. from 8/27/2016 onwards
MacBook Pro:
uname --kernel-release --kernel-version
4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
Corruption no longer visible with 4.4.0-49-generic:
https://pastebin.canonical.com/171039/
Testing with Yakkety proper would be messy - what's the timeline for
getting an updated 4.8 kernel into Xenial? I currently only see
4.8.0-27.29~16.04.1.
** Tags removed: verification-needed-xenial
**
tests ran: 30, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/dwalin__3.19.0-75.83~14.04.1__2016-11-17_17-54-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-17_18-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.
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_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.
https://lists.ubuntu.com/archives/kernel-team/2016-November/081023.html
** Changed in: linux (Ubuntu Zesty)
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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
This seems to be a vanilla Linux kernel problem as I am experiencing
this on Fedora 24 as well.
--
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/159356
Title:
System freeze on high memory
** 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/1634271
Title:
arm64: kprobes disabled
Status in
I've reproduced this in a vm (more or less, my timestamps are different
but still wrong, but I'm guessing that's just due to different timezone
configurations).
Some relevant entries from /proc/mountinfo:
24 26 8:1 / /media/root-ro ro,relatime shared:2 - ext4 /dev/sda1 ro,data=ordered
25 26 0:20
https://lists.ubuntu.com/archives/kernel-team/2016-November/081021.html
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
I don't have a non-artificial test case for this since it involves
cloud images, but I can confirm that the mlx5_core module is in
linux-image-generic in xenial-proposed.
root@malefic:~# dpkg -L linux-image-4.4.0-49-generic | grep mlx
As above:
(yakkety-amd64)james@osageorange:~/x$ dpkg -c
linux-image-4.8.0-28-generic_4.8.0-28.30_amd64.deb | grep mlx
drwxr-xr-x root/root 0 2016-11-11 10:30
./lib/modules/4.8.0-28-generic/kernel/drivers/net/ethernet/mellanox/mlx4/
-rw-r--r-- root/root473742 2016-11-11 10:30
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.
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
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/modoc__4.4.0-49.70__2016-11-17_17-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.
** 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
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
Does somebody know if this fix in the kernel 4.9.0.rc5, once released, will be
back-ported to the previous kernel versions used by LTS linux distributions?
For example ubuntu 16.04 LTS uses kernel 4.4.x
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug was fixed in the package zfs-linux - 0.6.5.8-0ubuntu4.1
---
zfs-linux (0.6.5.8-0ubuntu4.1) yakkety; urgency=low
* Fix zpool import with vdev on zvol hang (LP: #1636517)
kernel commit 77adfdaff1901ced4f72496e61317779424ee653
("block_dev: Support checking inode
The verification of the Stable Release Update for zfs-linux 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 zfs-linux - 0.6.5.6-0ubuntu15
---
zfs-linux (0.6.5.6-0ubuntu15) xenial; urgency=medium
* Fix zpool import with vdev on zvol hang (LP: #1636517)
Xenial kernel commit 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee
("block_dev: Support checking
tests ran: 1, failed: 0;
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_17-18-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
1 - 100 of 193 matches
Mail list logo
