[Kernel-packages] [Bug 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)

[Anthony Wong]

** No longer affects: linux (Ubuntu Xenial)

** Changed in: hwe-next
   Status: New => 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/1804588

Title:
  Power consumption during s2idle is higher than long idle (Intel
  SSDPEKKF)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF.

  Short idle: 6
  Long idle: 2
  S2I: 4.8

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the new Intel NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 2.8W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1804588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1813955] Re: CONFIG_TEST_BPF is disabled

[Stefan Bader]

** Changed in: linux (Ubuntu Cosmic)
   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/1813955

Title:
  CONFIG_TEST_BPF is disabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Our bpf testing will fail or be skipped without notice. So, real bpf failures 
might end up being missed.

  [Test case]
  Both ADT and SRU will end up testing the built module.

  [Regression potential]
  Our tests will start showing real failures we don't want to miss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813955/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)

[Gianfranco Costamagna]

Am I correct in saying that this is probably due to the kernel module
not being built correctly? I'm marking as duplicate

-- 
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/1818148

Title:
  virtualbox-guest-x11 does not work with 4.4.0-142-generic and with
  4.4.0-143-generic (from xenial-proposed)

Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have 16.04 LTS installed
  2. Enable xenial-proposed repository
  3. Install `virtualbox-guest-x11` package

  Expected results:
  * virtualbox-guest-x11 is working as before

  Actual results:
  * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: 
Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"
  * unable to use shared clipboard and drag and drop fuctionalty

  Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509
  ).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  1 00:38:30 2019
  InstallationDate: Installed on 2018-08-07 (205 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xenial 1850 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2018-01-04 (420 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: virtualbox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-143-generic N/A
   linux-backports-modules-4.4.0-143-generic  N/A
   linux-firmware 1.157.21
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-143-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xenial 1936 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: virtualbox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 

[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-166.216
/trusty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1814645

Title:
  linux: 3.13.0-166.216 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 01. March 2019 11:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

[Marcelo Cerri]

** Also affects: linux-oracle (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oracle (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux-oracle (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oracle (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux-oracle (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1815268

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oracle source package in Bionic:
  In Progress

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft 

[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

[Julian Andres Klode]

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-meta (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-hwe (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: apt (Ubuntu Trusty)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1787460

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Trusty:
  In Progress
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-hwe source package in Trusty:
  New
Status in apt source package in Xenial:
  In Progress
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1814813] Re: Bionic update: upstream stable patchset 2019-02-05

[Stefan Bader]

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Bionic)
   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/1814813

Title:
  Bionic update: upstream stable patchset 2019-02-05

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  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 from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-02-05 (ported from v4.14.59 and v4.17.11)
     from git://git.kernel.org/

  MIPS: ath79: fix register address in ath79_ddr_wb_flush()
  MIPS: Fix off-by-one in pci_resource_to_user()
  xen/PVH: Set up GS segment for stack canary
  drm/nouveau/drm/nouveau: Fix runtime PM leak in nv50_disp_atomic_commit()
  drm/nouveau: Set DRIVER_ATOMIC cap earlier to fix debugfs
  bonding: set default miimon value for non-arp modes if not set
  ip: hash fragments consistently
  ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull
  net/mlx4_core: Save the qpn from the input modifier in RST2INIT wrapper
  net: skb_segment() should not return NULL
  net/mlx5: Adjust clock overflow work period
  net/mlx5e: Don't allow aRFS for encapsulated packets
  net/mlx5e: Fix quota counting in aRFS expire flow
  net/ipv6: Fix linklocal to global address with VRF
  multicast: do not restore deleted record source filter mode to new one
  net: phy: consider PHY_IGNORE_INTERRUPT in phy_start_aneg_priv
  sock: fix sg page frag coalescing in sk_alloc_sg
  rtnetlink: add rtnl_link_state check in rtnl_configure_link
  vxlan: add new fdb alloc and create helpers
  vxlan: make netlink notify in vxlan_fdb_destroy optional
  vxlan: fix default fdb entry netlink notify ordering during netdev create
  tcp: fix dctcp delayed ACK schedule
  tcp: helpers to send special DCTCP ack
  tcp: do not cancel delay-AcK on DCTCP special ACK
  tcp: do not delay ACK in DCTCP upon CE status change
  staging: speakup: fix wraparound in uaccess length check
  usb: cdc_acm: Add quirk for Castles VEGA3000
  usb: core: handle hub C_PORT_OVER_CURRENT condition
  usb: dwc2: Fix DMA alignment to start at allocated boundary
  usb: gadget: f_fs: Only return delayed status when len is 0
  driver core: Partially revert "driver core: correct device's shutdown order"
  can: xilinx_can: fix RX loop if RXNEMP is asserted without RXOK
  can: xilinx_can: fix power management handling
  can: xilinx_can: fix recovery from error states not being propagated
  can: xilinx_can: fix device dropping off bus on RX overrun
  can: xilinx_can: keep only 1-2 frames in TX FIFO to fix TX accounting
  can: xilinx_can: fix incorrect clear of non-processed interrupts
  can: xilinx_can: fix RX overflow interrupt not being enabled
  can: peak_canfd: fix firmware < v3.3.0: limit allocation to 32-bit DMA addr 
only
  can: m_can.c: fix setup of CCCR register: clear CCCR NISO bit before checking 
can.ctrlmode
  turn off -Wattribute-alias
  net-next/hinic: fix a problem in hinic_xmit_frame()
  net/mlx5e: Refine ets validation function
  nfp: flower: ensure dead neighbour entries are not offloaded
  usb: gadget: Fix OS descriptors support
  ACPICA: AML Parser: ignore dispatcher error status during table load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814813/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1815234] Re: Bionic update: upstream stable patchset 2019-02-08

[Stefan Bader]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Bionic)
   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/1815234

Title:
  Bionic update: upstream stable patchset 2019-02-08

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  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 from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-02-08 (ported from v4.14.60 and v4.17.12)
     from git://git.kernel.org/

  fork: unconditionally clear stack on fork
  spi: spi-s3c64xx: Fix system resume support
  Input: elan_i2c - add ACPI ID for lenovo ideapad 330
  Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
  Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
  kvm, mm: account shadow page tables to kmemcg
  delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
  tracing: Fix double free of event_trigger_data
  tracing: Fix possible double free in event_enable_trigger_func()
  kthread, tracing: Don't expose half-written comm when creating kthreads
  tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
  tracing: Quiet gcc warning about maybe unused link variable
  arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
  mlxsw: spectrum_switchdev: Fix port_vlan refcounting
  kcov: ensure irq code sees a valid area
  xen/netfront: raise max number of slots in xennet_get_responses()
  skip LAYOUTRETURN if layout is invalid
  ALSA: emu10k1: add error handling for snd_ctl_add
  ALSA: fm801: add error handling for snd_ctl_add
  NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
  nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
  vfio: platform: Fix reset module leak in error path
  vfio/mdev: Check globally for duplicate devices
  vfio/type1: Fix task tracking for QEMU vCPU hotplug
  kernel/hung_task.c: show all hung tasks before panic
  mm: /proc/pid/pagemap: hide swap entries from unprivileged users
  mm: vmalloc: avoid racy handling of debugobjects in vunmap
  mm/slub.c: add __printf verification to slab_err()
  rtc: ensure rtc_set_alarm fails when alarms are not supported
  perf tools: Fix pmu events parsing rule
  netfilter: ipset: forbid family for hash:mac sets
  netfilter: ipset: List timing out entries with "timeout 1" instead of zero
  irqchip/ls-scfg-msi: Map MSIs in the iommu
  watchdog: da9063: Fix updating timeout value
  printk: drop in_nmi check from printk_safe_flush_on_panic()
  bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
  ceph: fix alignment of rasize
  e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
  powerpc/lib: Adjust .balign inside string functions for PPC32
  powerpc/64s: Add barrier_nospec
  powerpc/eeh: Fix use-after-release of EEH driver
  hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
  powerpc/64s: Fix compiler store ordering to SLB shadow area
  RDMA/mad: Convert BUG_ONs to error flows
  lightnvm: pblk: warn in case of corrupted write buffer
  netfilter: nf_tables: check msg_type before nft_trans_set(trans)
  pnfs: Don't release the sequence slot until we've processed layoutget on open
  disable loading f2fs module on PAGE_SIZE > 4KB
  f2fs: fix error path of move_data_page
  f2fs: fix to don't trigger writeback during recovery
  f2fs: fix to wait page writeback during revoking atomic write
  f2fs: Fix deadlock in shutdown ioctl
  f2fs: fix to detect failure of dquot_initialize
  f2fs: fix race in between GC and atomic open
  block, bfq: remove wrong lock in bfq_requests_merged
  usbip: usbip_detach: Fix memory, udev context and udev leak
  usbip: dynamically allocate idev by nports found in sysfs
  perf/x86/intel/uncore: Correct fixed counter index check in generic code
  perf/x86/intel/uncore: Correct fixed counter index check for NHM
  selftests/intel_pstate: Improve test, minor fixes
  selftests: memfd: return Kselftest Skip code for skipped tests
  selftests: intel_pstate: return Kselftest Skip code for skipped tests
  PCI: Fix devm_pci_alloc_host_bridge() memory leak
  iwlwifi: pcie: fix race in Rx buffer allocator
  Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning
  Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011
  ASoC: dpcm: fix BE dai not hw_free and shutdown
  mfd: cros_ec: Fail 

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[jespestana]

@dustya 
Thanks a lot for the feedback. I think that I will install both operating 
systems on the laptop, and check what happens.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM

[Stefan Bader]

** Changed in: linux-aws (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624

Title:
  PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
  was expected to be set in C-KVM

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-aws source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  In Progress
Status in linux-kvm source package in Cosmic:
  Fix Committed
Status in linux-aws source package in Disco:
  In Progress
Status in linux-azure source package in Disco:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  Issue reported by the kernel-security test:

    ==
    FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
    Ensure page poisoning is enabled (LP: #1783651)
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 2676, in 
test_420_config_page_poisoning
    self.assertKernelConfig('PAGE_POISONING', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
    self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
    '%s option was expected to be set in the kernel config' % name)
    AssertionError: PAGE_POISONING option was expected to be set in the kernel 
config

  
==
FAIL: test_421_config_page_poisoning_no_sanity 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2694, in 
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in 
the kernel config

==
FAIL: test_421_config_page_poisoning_zero 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2685, in 
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the 
kernel config


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:12:54 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812624/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818238] [NEW] fib_tests.sh net selftest is flaky when running carrier tests

[Thadeu Lima de Souza Cascardo]

Public bug reported:

[Impact]
The kernel net selftests include a fib_rules.sh that tests fib rules after 
carrier off. That test is flaky, which will cause false failures during ADT and 
SRU tests.

[Test case]
The carrier test has been run on a loop and the failure was noticed. After the 
fix, the failure does not appear.

[Regression potential]
This fix only applies to the selftests, not the kernel itself. The regression 
potential would be tests failing when they were not, but no regressions to 
users themselves.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1818238

Title:
  fib_tests.sh net selftest is flaky when running carrier tests

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The kernel net selftests include a fib_rules.sh that tests fib rules after 
carrier off. That test is flaky, which will cause false failures during ADT and 
SRU tests.

  [Test case]
  The carrier test has been run on a loop and the failure was noticed. After 
the fix, the failure does not appear.

  [Regression potential]
  This fix only applies to the selftests, not the kernel itself. The regression 
potential would be tests failing when they were not, but no regressions to 
users themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818237] [NEW] Xenial update: 4.4.171 upstream stable release

[Juerg Haefliger]

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 from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   4.4.171 upstream stable release
   from git://git.kernel.org/

Linux 4.4.171
sunrpc: use-after-free in svc_process_common()
ext4: fix a potential fiemap/page fault deadlock w/ inline_data
crypto: cts - fix crash on short inputs
i2c: dev: prevent adapter retries and timeout being set as minus value
ACPI: power: Skip duplicate power resource references in _PRx
PCI: altera: Move retrain from fixup to altera_pcie_host_init()
PCI: altera: Rework config accessors for use without a struct pci_bus
PCI: altera: Poll for link training status after retraining the link
PCI: altera: Poll for link up status after retraining the link
PCI: altera: Check link status before retrain link
PCI: altera: Reorder read/write functions
PCI: altera: Fix altera_pcie_link_is_up()
slab: alien caches must not be initialized if the allocation of the alien cache 
failed
USB: Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB
USB: storage: add quirk for SMI SM3350
USB: storage: don't insert sane sense for SPC3+ when bad sense specified
usb: cdc-acm: send ZLP for Telit 3G Intel based modems
cifs: Fix potential OOB access of lock element array
CIFS: Do not hide EINTR after sending network packets
btrfs: tree-checker: Fix misleading group system information
btrfs: tree-checker: Check level for leaves and nodes
btrfs: Verify that every chunk has corresponding block group at mount time
btrfs: Check that each block group has corresponding chunk at mount time
btrfs: validate type when reading a chunk
btrfs: tree-checker: Detect invalid and empty essential trees
btrfs: tree-checker: Verify block_group_item
btrfs: tree-check: reduce stack consumption in check_dir_item
btrfs: tree-checker: use %zu format string for size_t
btrfs: tree-checker: Add checker for dir item
btrfs: tree-checker: Fix false panic for sanity test
btrfs: tree-checker: Enhance btrfs_check_node output
btrfs: Move leaf and node validation checker to tree-checker.c
btrfs: Add checker for EXTENT_CSUM
btrfs: Add sanity check for EXTENT_DATA when reading out leaf
btrfs: Check if item pointer overlaps with the item itself
btrfs: Refactor check_leaf function for later expansion
btrfs: struct-funcs, constify readers
Btrfs: fix emptiness check for dirtied extent buffers at check_leaf()
Btrfs: memset to avoid stale content in btree leaf
Btrfs: kill BUG_ON in run_delayed_tree_ref
Btrfs: improve check_node to avoid reading corrupted nodes
Btrfs: memset to avoid stale content in btree node block
Btrfs: fix BUG_ON in btrfs_mark_buffer_dirty
Btrfs: check btree node's nritems
Btrfs: detect corruption when non-root leaf has zero item
Btrfs: fix em leak in find_first_block_group
Btrfs: check inconsistence between chunk and block group
Btrfs: add validadtion checks for chunk loading
btrfs: Enhance chunk validation check
btrfs: cleanup, stop casting for extent_map->lookup everywhere
ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Summary changed:

- Xenial update: v4.4.171 upstream stable release
+ Xenial update: 4.4.171 upstream stable release

** 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
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- 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 from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    4.4.171 upstream stable release
+    from git://git.kernel.org/
  
-v4.4.171 upstream stable release
-   

[Kernel-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199035.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-03-06T21:09:45+00:00 mathieutournier wrote:

Created attachment 274593
dmesg

Hi,
I'm currently running ubuntu 18.04 with a 4.15 kernel and i can observe very 
high cpu usage to the  systemd-udevd deamon.

removing the rule :
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

Solved the high CPU usage eventhough my bluetooth card is not available
anymore (as not in hci mode)

It seems that the command hid2hci creates a bind/unbind loop in udev
that is looping trying to set the device in hci mode. (that what udevadm
monitor seems to show, looping from bind to unbind for the device)

I suspect a0085f2510e8976614ad8f766b209448b385492f introduced a
regression (i have not tried to revert it yet).

Please not that there also seem to be a bug in hid2hci.c from bluez l148 :
if (err == 0) {
err = -1;
errno = EALREADY;
}
Correcting this and recompile bluez desn't solve the issue as cpu usage remains 
very high.

Using a 4.13 kernel result in a normal CPU usage, this seems a
regression in 4.14.

Other people seems to have the same issue, here is a bug report related to this 
:
https://dev.solus-project.com/T5224

Thanks a lot for your support,

Mathieu Tournier

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/0


On 2018-05-04T05:57:10+00:00 boro wrote:

I have the very same problem using the same distro (Ubuntu 18.04,
64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or
removing the aforementioned rule solves the problem but leaves BT
unusable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/1


On 2018-05-09T23:02:06+00:00 lucent wrote:

Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c: Broadcom Corp. 

Linux zontar 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64
GNU/Linux

May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
...repeating...

15632 root  20   0  233136 186656   2664 R  94.1%   4.7%  62:14.67 
systemd-udevd   
  
16222 root  20   0   88252   2432   1888 R  35.3%   0.1%  25:21.87 
systemd-udevd   
  

Looks like same problem affects this Dell Precision M6500 laptop.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/2


On 2018-05-20T07:57:41+00:00 f.dittmer wrote:

I observed the high cpu usage after upgrading from udev-233 to 
udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use 
newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as 
mentioned above.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/3


On 2018-06-13T16:50:40+00:00 rickfharris wrote:

As per https://patchwork.kernel.org/patch/10384111/ editing
97-hid2hci.rules as follows works around the new uevents added to the
kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65

-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"

Bluetooth now works with kernels above and below 4.14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/4


On 2018-06-14T00:32:13+00:00 

[Kernel-packages] [Bug 1818238] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1818238

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 comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** 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/1818238

Title:
  fib_tests.sh net selftest is flaky when running carrier tests

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The kernel net selftests include a fib_rules.sh that tests fib rules after 
carrier off. That test is flaky, which will cause false failures during ADT and 
SRU tests.

  [Test case]
  The carrier test has been run on a loop and the failure was noticed. After 
the fix, the failure does not appear.

  [Regression potential]
  This fix only applies to the selftests, not the kernel itself. The regression 
potential would be tests failing when they were not, but no regressions to 
users themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM

[Stefan Bader]

** Changed in: linux-kvm (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624

Title:
  PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
  was expected to be set in C-KVM

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux-azure source package in Cosmic:
  In Progress
Status in linux-kvm source package in Cosmic:
  Fix Committed
Status in linux-aws source package in Disco:
  In Progress
Status in linux-azure source package in Disco:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  Issue reported by the kernel-security test:

    ==
    FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
    Ensure page poisoning is enabled (LP: #1783651)
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 2676, in 
test_420_config_page_poisoning
    self.assertKernelConfig('PAGE_POISONING', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
    self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
    '%s option was expected to be set in the kernel config' % name)
    AssertionError: PAGE_POISONING option was expected to be set in the kernel 
config

  
==
FAIL: test_421_config_page_poisoning_no_sanity 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2694, in 
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in 
the kernel config

==
FAIL: test_421_config_page_poisoning_zero 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2685, in 
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the 
kernel config


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:12:54 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812624/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818238] Re: fib_tests.sh net selftest is flaky when running carrier tests

[Thadeu Lima de Souza Cascardo]

For some reason, I can't really reproduce the failure on cosmic 4.18
kernel, only on 5.0.

Cascardo.

-- 
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/1818238

Title:
  fib_tests.sh net selftest is flaky when running carrier tests

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The kernel net selftests include a fib_rules.sh that tests fib rules after 
carrier off. That test is flaky, which will cause false failures during ADT and 
SRU tests.

  [Test case]
  The carrier test has been run on a loop and the failure was noticed. After 
the fix, the failure does not appear.

  [Regression potential]
  This fix only applies to the selftests, not the kernel itself. The regression 
potential would be tests failing when they were not, but no regressions to 
users themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818238] Re: fib_tests.sh net selftest is flaky when running carrier tests

[Thadeu Lima de Souza Cascardo]

Not much luck on 4.19 either.

-- 
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/1818238

Title:
  fib_tests.sh net selftest is flaky when running carrier tests

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The kernel net selftests include a fib_rules.sh that tests fib rules after 
carrier off. That test is flaky, which will cause false failures during ADT and 
SRU tests.

  [Test case]
  The carrier test has been run on a loop and the failure was noticed. After 
the fix, the failure does not appear.

  [Regression potential]
  This fix only applies to the selftests, not the kernel itself. The regression 
potential would be tests failing when they were not, but no regressions to 
users themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)

[Gianfranco Costamagna]

*** This bug is a duplicate of bug 1818049 ***
https://bugs.launchpad.net/bugs/1818049

** This bug has been marked a duplicate of bug 1818049
   virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too 
many arguments to function ‘get_user_pages’]

-- 
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/1818148

Title:
  virtualbox-guest-x11 does not work with 4.4.0-142-generic and with
  4.4.0-143-generic (from xenial-proposed)

Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have 16.04 LTS installed
  2. Enable xenial-proposed repository
  3. Install `virtualbox-guest-x11` package

  Expected results:
  * virtualbox-guest-x11 is working as before

  Actual results:
  * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: 
Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"
  * unable to use shared clipboard and drag and drop fuctionalty

  Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509
  ).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  1 00:38:30 2019
  InstallationDate: Installed on 2018-08-07 (205 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xenial 1850 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2018-01-04 (420 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: virtualbox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-143-generic N/A
   linux-backports-modules-4.4.0-143-generic  N/A
   linux-firmware 1.157.21
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-143-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xenial 1936 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: virtualbox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1