Patches submitted to kernel-team list:
Xenial - https://lists.ubuntu.com/archives/kernel-team/2019-April/099810.html
Bionic - https://lists.ubuntu.com/archives/kernel-team/2019-April/099813.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Kernel
Pa
** Changed in: linux (Ubuntu)
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/1822821
Title:
TSC clocksource not available in nested guests
Stat
This is easily verifiable on both Xenial and Bionic guests from uvt-kvm.
I've brought up both as nested instances, and TSC fails to show up as an
available clocksource:
== Xenial guest ==
$ uvt-kvm ssh bionic-l1
ubuntu@bionic-l1:~$ uvt-kvm ssh xenial-l2
ubuntu@xenial-l2:~$ uname -r
4.4.0-143-gen
Public bug reported:
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream cod
Tested on linux-generic 3.13.0.168.179 from trusty-proposed. Tried
reproducing according to test case from description, and verified that
ixgbe is fixed:
# uname -r
3.13.0-168-generic
# apt-cache madison linux-generic
linux-generic | 3.13.0.168.179 |
http://archive.ubuntu.com/ubuntu/trusty-propo
** Description changed:
[Impact]
- Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
+ Crash kernels include an obsolete "nousb" parameter by default, which can
cause confusion since it's been deprecated in newer kernel versions.
[Descriptio
** Patch removed: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
** Patch removed: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachm
Thanks for bringing that up, Cascardo. That was one scenario we didn't
consider, and you're right about it causing problems for users with
encrypted systems.
It does seem more sensible to just remove the 'nousb' option in this case,
since this parameter has no effect in recent kernels. I'll respi
** Description changed:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
Debdiffs for this bug were attached to LP#1800562
** Description changed:
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform
special activity in case this param
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to make
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile i
SRUv2 sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098451.htm
--
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/1815501
Title:
ixgbe: Kernel
** Description changed:
- Kernel has the "reset_devices" parameter that drivers can opt-in, and
- perform special activity in case this parameter is parsed from command-
- line. For example, in kdump kernels it hints the drivers that they
- (maybe) are booting from a non-healthy condition and need
** Description changed:
- Since kernel v4.5, the correct parameter to disable USB subsystem
- initialization is "usbcore.nousb" always (instead of "nousb" in case the
- subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb:
- make "nousb" a clear module parameter").
+ [Impact]
+ Cra
SRU request sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098444.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/1815501
Title:
ixgbe:
ete
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)
--
You received this bug notification because you are a memb
20 matches
Mail list logo
