[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-12 Thread Steve Langasek
Thanks for confirming.

> Should the shim-signed package have a dependency on a kernel that is
new enough?

For better or worse, there is no straightforward way to express such a
dependency.  But also, the fundamental problem here is not that shim-
signed has new requirements.  The fundamental problem is that you and
other users have been running a kernel that has had no security updates
for over 2 years and didn't know it.  While it was stated at the time
that these kernels would have security support for a limited time and
that users who had these kernels installed would not be automatically
rolled forward to the next series (as this might introduce regressions
in hardware support), evidently this information was not communicated in
a way that made it clear to users that they were out of security
support.

I will look into what can be done to improve the communication to users
in all the usual places that information about security updates are
communicated, to let users know they are running unsupported kernels.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread Steve Langasek
Other commenters, please confirm what kernel version you are seeing this
behavior with.  If this is not reproducible with either the linux-
generic 3.13 kernel or the linux-lts-xenial 4.4 kernel, then it is not
going to be fixed.

Note also that Ubuntu 14.04 has reached the end of standard support, so
in addition to the other *-lts-* kernels being out of security support
for a long time already, the rest of your system is also out of security
support unless you have ESM enabled.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-06-11 Thread Steve Langasek
@vandebo, your apport information shows the following:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-77-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27

That appears to be the last released version of the linux-lts-utopic
kernel.  That kernel is out of security support and has not been updated
since 2016.  You should upgrade to linux-lts-xenial immediately by
installing the linux-signed-generic-lts-xenial package.

@Lurchman, your comment also shows that you are running
3.19.0-82-generic, which is the last released version of the linux-
lts-*vivid* kernel, which is also out of security support and has not
been updated since February 2017.  You should also install linux-signed-
generic-lts-xenial immediately.

Please report if you are still experiencing issues once you have a
currently-supported version of the kernel on 14.04.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1831736] Re: [MIR] lz4 by default

2019-06-05 Thread Steve Langasek
Since these changes to the default initramfs compression are already
being uploaded, it's critical that there be follow-through on the
upgrader and on the sizing of /boot partitions to ensure that this is a
smooth transition for our users.

https://lists.ubuntu.com/archives/ubuntu-devel/2018-March/040265.html
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040729.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/1831736

Title:
  [MIR] lz4 by default

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Confirmed
Status in partman-auto package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+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 1831736] Re: [MIR] lz4 by default

2019-06-05 Thread Steve Langasek
** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

** Also affects: partman-auto (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: partman-auto (Ubuntu)
   Status: New => Triaged

** Changed in: partman-auto (Ubuntu)
   Importance: Undecided => High

** Changed in: partman-auto (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  [MIR] lz4 by default

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Confirmed
Status in partman-auto package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+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 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

2019-05-20 Thread Steve Langasek
Marking as an SRU regression and assigning to the Security Team uploader
for follow-up.

** Tags added: regression-security regression-update

** No longer affects: cryptsetup (Ubuntu)

** Changed in: intel-microcode (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with newer (Kaby lake) Intel CPU, intel-microcode

  
  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+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 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread Steve Langasek
Your comment describes an issue entirely unrelated to this bug report.
Please file a separate bug report against the cups package using ubuntu-
bug cups.

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

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+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 1821276] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for MAC address pass through on RTL8153-BD

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

Bug description:
  == SRU Justification ==

  * Impact:
  RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the 
whitelist of devices to activate MAC address passthrough.

  * Fix:
  Two commits in upstream need to be applied in order to support this feature. 
Both of them are in 5.0.

  commit 8e29d23e28ee7fb995a00c1ca7e1a4caf5070b12
  Author: David Chen david.ch...@dell.com
  Date: Sat Feb 16 17:16:42 2019 +0800

  r8152: Add support for MAC address pass through on RTL8153-BD

  commit c286909fe5458f69e533c845b757fd2c35064d26
  Author: David Chen david.ch...@dell.com
  Date: Wed Feb 20 13:47:19 2019 +0800

  r8152: Fix an error on RTL8153-BD MAC Address Passthrough support

  * Testcase:
  BIOS settings must be properly set before verifying.
  1.[Settings][POST Behavior][MAC Address Pass-Through]: Passthrough MAC Address
  2. There should be two MAC addresses in BIOS settings, ex: 
[Settings][General][System Information]
  Attach the dongle and see if MAC passthrough works.

  * Risk of Regression:
  Clean cherry-pick from mainline, and only add specific hardware to the 
whitelist. Risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1821276/+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 1822796] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux: 4.18.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822793 (linux-gcp), bug 1822794 
(linux-kvm), bug 1824771 (linux-aws), bug 1824841 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Release
  phase-changed: Tuesday, 23. April 2019 21:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822796/+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 1788432] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  4.15 s390x kernel BUG at /build/linux-
  Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!

Status in Ubuntu on IBM z Systems:
  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

Bug description:
  [SRU Justification]

  == Impact ==
  Several helper functions in the s390x code which handle accessing sysfs 
attributes were missing protection against races. Concurrent access would be 
able to trigger kernel bugs.

  == Fix ==
  The following two upstream commits (from v5.0 upstream) will fix the issue:

  78b1a52e05c9 virtio/s390: fix race in ccw_io_helper()
  2448a299ec41 virtio/s390: avoid race on vcdev->config

  == Testcase ==
  see below

  == Risk of Regression ==
  Changes are isolated to architecture code and are verified by running the 
stress testing, so overall should be low.


  uname -a
  Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 
s390x s390x s390x GNU/Linux

  and same for 4.15.0-29-generic and 4.17.0-8-generic

  Steps to reproduce this bug:

  git clone git://kernel.ubuntu.com/cking/stress-ng
  cd stress-ng
  make clean
  make

  And run with:

  ./stress-ng --sysfs 0 -t 60

  .. wait a few seconds and then:

  [  119.445891] [ cut here ]
  [  119.445898] kernel BUG at 
/build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
  [  119.446093] illegal operation: 0001 ilc:1 [#3] SMP
  [  119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk
  [  119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P  DO  
   4.15.0-33-generic #36-Ubuntu
  [  119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  119.446170] Krnl PSW : 12d313d3 405835bc 
(virtblk_cache_type_show+0x82/0x88 [virtio_blk])
  [  119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [  119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 
6545
  [  119.446196]03ff800058da 6546 6bf537c0 
6b60a100
  [  119.446198] 00690648 7cc3de40 
7a74b000
  [  119.446202]03ff80008210  03ff800058da 
7ac1bce8
  [  119.446210] Krnl Code: 03ff80005912: ebbff0a80004  lmg 
%r11,%r15,168(%r15)
  [  119.446210]03ff80005918: c0f40560  brcl
15,3ff800063d8
  [  119.446210]   #03ff8000591e: a7f40001  brc 
15,3ff80005920
  [  119.446210]   >03ff80005922: 0707  bcr 0,%r7
  [  119.446210]03ff80005924: 0707  bcr 0,%r7
  [  119.446210]03ff80005926: 0707  bcr 0,%r7
  [  119.446210]03ff80005928: c004  brcl
0,3ff80005928
  [  119.446210]03ff8000592e: eb6ff0480024  stmg
%r6,%r15,72(%r15)
  [  119.446226] Call Trace:
  [  119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 
[virtio_blk])
  [  119.446234]  [<00690684>] dev_attr_show+0x3c/0x80
  [  119.446240]  [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8
  [  119.446259]  [<003b048c>] seq_read+0xec/0x4c8
  [  119.446262]  [<003821ea>] vfs_read+0x8a/0x150
  [  119.446274]  [<00382786>] SyS_read+0x66/0xe0
  [  119.446278]  [<008e3028>] system_call+0xdc/0x2c8
  [  119.446279] Last Breaking-Event-Address:
  [  119.446281]  [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 
[virtio_blk]
  [  119.446283]
  [  119.446284] ---[ end trace 2c2403d726047e4a ]---

  For  4.17.0-8-generic:
  [   25.170715] kernel BUG at drivers/block/virtio_blk.c:574!
 

[Kernel-packages] [Bug 1818854] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev
  failures

Status in Ubuntu on IBM z Systems:
  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:
  SRU Justification:

  [Impact]

  * The vfio-ap driver will create a matrix device in sysfs without a
  subsystem link.

  * This causes failures in libudev that might also lead to libvirt
  errors.

  * A fix is upstream in master branch for kernel 5.1

  [Fix]

  * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap:
  link the vfio_ap devices to the vfio_ap bus subsystem"

  [Test Case]

  * An s390x machine with at least one CryptoExpress card,
where at least one AP and one 'Domain' is assigned to a particular LPAR.

  * Now running virsh nodedev-list before (and later after) construction
  the matrix device should expose the issue.

  * For details about how to setup a vfio-ap matrix device see: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
(see 2nd bullet: virtio-ap)

  [Regression Potential]

  * The regression potential can be considered as low since it only
  affects the s390x platform

  * and there it only affects the usage of AP (CryptoExpress) cards and
  it's driver/module

  * and again only affects the recently introduced virtual IO function
  of AP (vfio-ap).

  [Other Info]

  * It was already briefly discussed here:
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html
as well as reviewed and pushed.

  * Commit 3636065 from v5.1-rc1

  * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards!

  * For details on virtio-ap/vfio-ap see bullet #2 here: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
  _

  ---Problem Description---
  The vfio-ap driver will create a matrix device in sysfs without a subsystem 
link. This triggers failures in libudev that might also lead to libvirt errors 
(e.g. see 
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html)

  The proper fix is to add a subsystem link (e.g. by providing a dummy
  bus).

  A fix for that is upstream in master branch already for kernel 5.1

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99

  This  need to be applied to Bionic, Cosmic and Disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1818854/+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 1819881] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [CONFIG] please enable highdpi font FONT_TER16x32

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  The console font size on a high resolution screen is only suitable for
  eagles, although we can choose a bigger font by running:
sudo dpkg-reconfigure console-setup

  But that is not enough, the font size before video driver kicks in is
  still small. If we need to debug some early stage issues that will be a
  problem.

  
  == Fix ==
  ac8b6f14 (Fonts: New Terminus large console font)
  Config for this TER16x32 and the compiled-in fonts support needs to be
  enabled to keep engineers away from ophthalmologists.

  * Disco
It's already there. Just need to enable the configs.
  * Cosmic / Bionic
Patch can be cherry-picked.
  * Xenial
It needs an extra patch to make it a clean cherry-pick:
* 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together
  * Trusty
It needs two extra patches to make it a clean cherry-pick:
* fonts: Add 6x10 font (33ac9dba)
* lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826).
And a config entry for the 6x10 font.

  Commit "fonts: Add 6x10 font" is just adding a new font.
  Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is
  just a patch for context rearrangement.

  I think these two are safe to be pulled-in.

  
  == Test ==
  Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/

  Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
  /etc/default/grub, and follow these steps.

  * Disco
sudo update-grub; sudo reboot
  * Cosmic / Bionic
Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub
sudo update-grub; sudo reboot
  * Xenial
sudo update-grub; sudo reboot
  * Trusty
sudo update-grub; sudo reboot (I need the proprietary nvidia driver
to boot for my SUT - Dell Precision M3800)

  The font before the video driver kicks in will get bigger.

  == Regression potential ==
  Minimal, changes are limited to adding console fonts, turn on fonts
  related kernel configs.


  
  [CONFIG] please enable highdpi font FONT_TER16x32

  This is now available in v5.0

  config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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 1819546] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Avoid potential memory corruption on HiSilicon SoCs

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]
  There is a potential for memory corruption in MSI payloads. For reasons 
mentioned in the commit message, this happens to not be triggerable today, but 
is fragile, and could rear it's ugly head if a struct layout changes due to 
other backports in the future.

  [Test Case]
  Regression-only.

  [Fix]
  84a9a75774961 iommu/arm-smmu-v3: Avoid memory corruption from Hisilicon MSI 
payloads

  [Regression Risk]
  The fix is to add some explicit padding into an internal structure. This 
padding is already implicit today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819546/+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 1814892] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [19.04 FEAT] qeth: Enhanced link speed - kernel part

Status in Ubuntu on IBM z Systems:
  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

Bug description:
  SRU Justification:
  --

  * This is more a request (rather than a bug) to add support for the newest 
OSA-Express7S (network-) card,
so that even cosmic and bionic users should be able to benefit from it.

  * The support became upstream accepted with 4.20, mainly with commit

  [Test Case]

  * Due to the absence of that particular card in our (Canonical)
  system, the testing is up to IBM.

  * The recognition of the card type itself can be done via 'lsqeth |
  grep card_type',

  * and the functionality can be tested by network test tools, like
  stress-ng.

  * A regression test can of course be done on our (Canonical) system.

  [Regression Potential]

  * The regression potential can be considered as low since it only
  affects the s390x platform

  * and there only the qeth driver/module.

  * The patch itself is less complex and adds mainly lines and fields
  for the recognition of the new card.

  * The entire code needed is already included in disco and a sniff test was 
done based on disco's kernel 5.0.
  __

  Function:
  Provide enhanced link speed for OSA networks
  Business Case:
  Improved performance with OSA networks

  Available with kernel 4.20
  Git-Commit: s390/qeth: report 25Gbit link speed [54e049c227]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814892/+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 1823805] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  The following commit is being requested in the 18.04 4.18 based Bionic kernel 
for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  This is a critical issue.  The 4.18.0-1015 kernel immediately panics
  on boot without this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+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 1821064] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  hns3: fix oops in hns3_clean_rx_ring()

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

Bug description:
  [Impact]
  kernel oops

  [Test Case]
  Run netperf between two hosts. Doesn't 100% cause a crash, but works as a 
regression test.

  [Fix]
  d394d33bee224 net: hns3: add dma_rmb() for rx description

  [Regression Risk]
  Restricted to a driver specific to the hi1620 SoC. Since this adds a new read 
barrier, there is a potential performance regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821064/+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 1821378] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
  in Azure kernel

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  This is a request to include the following two commits in 16.04 and
  18.04 linux-azure:

  fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for 
unopened channels")
  ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")

  Both commits are fixes to prior commits and have been cc'd to upstream
  stable.

  Commit fc96df16a1ce is in mainline as of v4.20
  Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4

  The problem these commits fix is that some of the code for displaying
  values for entries in /sys/bus/vmbus don't have appropriate locking to
  prevent reading an entry while it is being created or being freed.
  The result is accessing a bogus memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+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 1816669] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp33s0f0  no wireless extensions.
   
   lono wireless extensions.
   
   enp33s0f1  no wireless extensions.
  MachineType: AMD Corporation DAYTONA_X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RDY0071B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DAYTONA_X
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: DAYTONA_X
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1816669/+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 1826171] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux: 4.18.0-19.20 -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 verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826170 (bionic/linux-hwe)
  derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 
(linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 10:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826171/+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 1786013] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Committed
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  New

Bug description:
  Ongoing packing resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1821395] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
     commit c5a94f434c82 ("fscache: fix race between enablement and
     dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case,
     but these are the conditions to hit the problem:

     1) The active dataset size is equal to the cache disk size.
    The application reads the data over and over again.
     2) Disk is near full (90%+)
     3) cachefilesd in userspace is trying to cull the old objects
    while new objects are being looked up.
     4) new cachefiles are created and some fail with no disk space.
     5) race in dropping object state machine and
    deferred lookup state machine causes the hang.
     6) HUNG in fscache_wait_for_deferred_lookup for
    clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

  [Regression Potential]

   * Low; contained in fscache; no further fixes applied upstream.

   * This patch is applied in a stable tree (linux-4.4.y).

  [Original Description]

  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.

  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

  This patch is required in Bionic and Cosmic, and it's applied in
  Xenial (via stable) and Disco.

  Apparently there's no simple test case, but these are the conditions
  to hit the problem:

  1) The active dataset size is equal to the cache disk size.
     The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
     while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
  5) race in dropping object state machine and
     deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
     clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+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 1826165] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1017.17~18.04.1 -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:
  Invalid
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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1826164 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 10:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826165/+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 1820990] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference

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

Bug description:
  [Impact]
  When no acpi hid match the device, there will be a NULL dereference in amd 
iommu.
  It will make system hang.

  [Fix]
  Check NULL pointer before using it.

  [Test]
  Tested on several AMD platforms, bugs are fixed with this patch.

  [Regression Potential]
  Low, upstream fix, Verified on several platforms.
  It should be safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1820990/+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 1824879] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: Add the Catapult FPGA Driver

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  Add the Catapult FPGA Driver to the custom linux-azure kernel while a
  version is not available upstream.

  [Test Case]

  The catapult driver must be present as a module in the linux-modules
  package (not in the linux-modules-extra).

  [Regression Potential]

  Low risk of regression since that's a new driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1824879/+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 1820153] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU][B/C/OEM]IOMMU: add kernel dma protection

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  SRU justification:

  [Impact]
  Recent systems shipping with "kernel DMA protection" = "enabled" by default 
in BIOS. This setting option changed "Thunderbolt Security Level" = "No 
Security (SL0)".
  With this setting systems will be vulnerable to a DMA attack by a thunderbolt 
device.

  OS can use IOMMU to defend against DMA attacks from a PCI device like 
thunderbolt one.
  Intel adds DMA_CTRL_PLATFORM_OPT_IN_FLAG flag in DMAR ACPI table.
  Use this flag to enable IOMMU and use _DSD to identify untrusted PCI devices.

  [Fix]
  Enable IOMMU when BIOS supports DMA opt in flag and ExternalFacingPort in 
_DSD.
  Disable ATS on the untrusted PCI device.

  [Test]
  Tested on 2 Intel platforms that supports DMA opt in flag with a thunderbolt 
dock station.
  iommu enabled as expected with this fix.

  Verified by QA's full test with a temporary build of bionic-oem kernel.
  All test passed on one supported "DMA protection" system and one
  non-supported "DMA protection" system.

  [Regression Potential]
  Upstream fix, Verified on supported platforms, no affection on not supported 
platforms.
  Backported changes are fairly minimal.

  These patches are included in 5.0 kernel, disco is good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1820153/+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 1824333] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autofs kernel module missing

Status in autofs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in autofs source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in autofs source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Fix Released
Status in autofs source package in Disco:
  Invalid
Status in linux source package in Disco:
  Fix Released

Bug description:
  linux-modules-4.18.0-17-generic misses the autofs module whereas
  linux-modules-4.15.0-47-generic contains it:

  root@files07:~# find /lib/modules -name '*autofs*'
  /lib/modules/4.15.0-46-generic/kernel/fs/autofs4
  /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko
  /lib/modules/4.15.0-47-generic/kernel/fs/autofs4
  /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko
  root@files07:~# dpkg -l|grep linux-modules
  ii  linux-modules-4.15.0-46-generic 4.15.0-46.49  amd64   
 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-47-generic 4.15.0-47.50  amd64   
 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1  amd64   
 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP
  ii  linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1  amd64   
 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP
  ii  linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1  amd64   
 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP

  This make it impossible to install and use the autofs package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+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 1821934] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293.
  However, due to a recently discovered security issue,
  CONFIG_HOTPLUG_CPU needs to be re-enabled.

  There are some patches on LKML to address this security issue, but
  they are not in the Azure kernel yet, and may not be accepted upstream
  in their current form.  If your interested, those two patches are
  available here:

  https://lkml.org/lkml/2019/3/26/893
  https://lkml.org/lkml/2019/3/26/894
  https://lkml.org/lkml/2019/3/26/895

  To mitigate this security issue, the nosmt option needs to be passed
  on the boot line.  However, the nosmt option will not work if
  CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs
  to be turned back on at this time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934/+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 1817786] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  tcm_loop.ko: move from modules-extra into main modules package

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-gcp source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-gcp source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Please move the tcm_loop.ko module from the linux-modules-extra-* to
  main linux-modules-* package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817786/+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 1820187] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Huawei Hi1822 NIC has poor performance

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]
  Connect Hi1822 NIC with 10G switch but the performance is only 1-2Gb/s
  $ iperf -c 10.228.68.133
  
  Client connecting to 10.228.68.133, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.228.68.116 port 56810 connected with 10.228.68.133 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  1.53 GBytes  1.32 Gbits/sec

  [Test Case]
  iperf -c 

  [Fix]
  Backporting all patches from mainline for drivers/net/ethernet/huawei solves 
this issue.

  [Regression Risk]
  Only modify codes in drivers/net/ethernet/huawei. Lowest risk to other 
devices and platform without it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820187/+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 1822791] Update Released

2019-05-14 Thread Steve Langasek
*** This bug is a duplicate of bug 1826166 ***
https://bugs.launchpad.net/bugs/1826166

The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 17:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822791/+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 1821271] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
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] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1821271/+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 1812809] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests
  failed on B PowerPC

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Justification ==
  When running the ftrace in ubunut_kernel_selftests, the "Kprobe event 
argument syntax" will fail on Bionic PowerPC.

  This is because PowerPC was not supported by this test.

  == Fix ==
  9855c462 (selftests/ftrace: Add ppc support for kprobe args tests)
  This patch can be cherry-picked for Bionic and Xenial.
  Although we don't run this ftrace test in Xenial, it will still be a plus to 
fix this.

  It's already been applied in C/D.

  == Test ==
  Patch tested with Bionic P8. Test passed as expected:
  [23] Kprobe event argument syntax [PASS]

  == Regression potential ==
  None.
  This patch is just for the kernel testing tool.

  == Original bug report ==
  This issue was not spotted on the other arches.

  Failure:
  [23] Kprobe event argument syntax [FAIL]

  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] event tracing - enable/disable with event level files [PASS]
  [6] event tracing - restricts events based on pid [PASS]
  [7] event tracing - enable/disable with subsystem level files [PASS]
  [8] event tracing - enable/disable with top level files   [PASS]
  [9] ftrace - function graph filters with stack tracer [PASS]
  [10] ftrace - function graph filters  [PASS]
  [11] ftrace - function glob filters   [PASS]
  [12] ftrace - function pid filters[PASS]
  [13] ftrace - test for function event triggers[PASS]
  [14] ftrace - function profiler with function tracing [PASS]
  [15] ftrace - test reading of set_ftrace_filter   [PASS]
  [16] ftrace - test for function traceon/off triggers  [PASS]
  [17] Test creation and deletion of trace instances while setting an event 
[PASS]
  [18] Test creation and deletion of trace instances[PASS]
  [19] Kprobe dynamic event - adding and removing   [PASS]
  [20] Kprobe dynamic event - busy event check  [PASS]
  [21] Kprobe dynamic event with arguments  [PASS]
  [22] Kprobe event string type argument[UNTESTED]
  [23] Kprobe event argument syntax [FAIL]
  [24] Kprobes event arguments with types   [PASS]
  [25] Kprobe event auto/manual naming  [PASS]
  [26] Kprobe dynamic event with function tracer[PASS]
  [27] Kprobe dynamic event - probing module[PASS]
  [28] Kretprobe dynamic event with arguments   [PASS]
  [29] Kretprobe dynamic event with maxactive   [PASS]
  [30] Register/unregister many kprobe events   [PASS]
  [31] Kprobe events - probe points [PASS]
  [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED]
  [33] event trigger - test event enable/disable trigger[PASS]
  [34] event trigger - test trigger filter  [PASS]
  [35] event trigger - test histogram modifiers [PASS]
  [36] event trigger - test histogram trigger   [PASS]
  [37] event trigger - test multiple histogram triggers [PASS]
  [38] event trigger - test snapshot-trigger[PASS]
  [39] event trigger - test stacktrace-trigger  [PASS]
  [40] event trigger - test traceon/off trigger [PASS]
  [41] (instance)  Basic test for tracers   [PASS]
  [42] (instance)  Basic trace clock test   [PASS]
  [43] (instance)  event tracing - enable/disable with event level files
[PASS]
  [44] (instance)  event tracing - restricts events based on pid[PASS]
  [45] (instance)  event tracing - enable/disable with subsystem level files
[PASS]
  [46] (instance)  ftrace - test for function event triggers[PASS]
  [47] (instance)  ftrace - test for function traceon/off triggers  [PASS]
  [48] (instance)  event trigger - test event enable/disable trigger[PASS]
  [49] (instance)  event trigger - test trigger filter  [PASS]
  [50] (instance)  event trigger - test histogram modifiers [PASS]
  [51] (instance)  event trigger - test histogram trigger   [PASS]
  [52] (instance)  event trigger - test multiple histogram triggers [PASS]

  # of passed:  49
  # of 

[Kernel-packages] [Bug 1824841] Update Released

2019-05-14 Thread Steve Langasek
*** This bug is a duplicate of bug 1826166 ***
https://bugs.launchpad.net/bugs/1826166

The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1016.16 -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:
  Invalid
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:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Signoff
  phase-changed: Tuesday, 23. April 2019 08:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824841/+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 1822790] Update Released

2019-05-14 Thread Steve Langasek
*** This bug is a duplicate of bug 1826165 ***
https://bugs.launchpad.net/bugs/1826165

The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+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 1819689] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [linux-azure] Commit To Improve NVMe Performance

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to
  be enabled in the linux-azure kernels(currently 4.15 and 4.18) in
  order to increase NVME disks performance.

  To achieve the peak IOPs we are seeing in testing, the following commit is 
also needed:
  7ac257b862f2c (“blk-mq: remove the request_list usage”)

  This commit cleans up unused code in block-mq (mq uses pre-allocated
  tags to allocate request, not request_list as it's used only in legacy
  queue).  The commit saves a bunch of rcu locks on I/O queuing path,
  which increases the achievable IOPs seen in testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+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 1779756] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

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

Bug description:
  [Impact]
  The i40e driver can get stalled on tx timeouts. This can happen when
  DCB is enabled on the connected switch. This can also trigger a
  second situation when a tx timeout occurs before the recovery of
  a previous timeout has completed due to CPU load, which is not
  handled correctly. This leads to networking delays, drops and
  application timeouts and hangs. Note that the first tx timeout
  cause is just one of the ways to end up in the second situation.

  This issue was seen on a heavily loaded Kafka broker node running
  the 4.15.0-38-generic kernel on Xenial.

  Symptoms include messages in the kernel log of the form:

  ---
  [4733544.982116] i40e :18:00.1 eno2: tx_timeout: VSI_seid: 390, Q 6, NTC: 
0x1a0, HWB: 0x66, NTU: 0x66, TAIL: 0x66, INT: 0x0
  [4733544.982119] i40e :18:00.1 eno2: tx_timeout recovery level 1, 
hung_queue 6
  

  With the test kernel provided in this LP bug which had these
  two commits compiled in, the problem has not been seen again,
  and has been running successfully for several months:

  "i40e: Fix for Tx timeouts when interface is brought up if
   DCB is enabled"
  Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee

  "i40e: prevent overlapping tx_timeout recover"
  Commit: d5585b7b6846a6d0f9517afe57be3843150719da

  * The first commit is already in Disco, Cosmic
  * The second commit is already in Disco
  * Bionic needs both patches and Cosmic needs the second

  [Test Case]
  * We are considering the case of both issues above occurring.
  * Seen by reporter on a Kafka broker node with heavy traffic.
  * Not easy to reproduce as it requires something like the
    following example environment and heavy load:

    Kernel: 4.15.0-38-generic
    Network driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
    NIC: Intel 40Gb XL710
    DCB enabled

  [Regression Potential]
  Low, as the first only impacts i40e DCB environment, and has
  been running for several months in production-load testing
  successfully.

  --- Original Description
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to 
the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+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 1824827] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

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

Bug description:
  [Impact]

   * Tasks of a multi-threaded workload doing write() and fsync()
 might deadlock in write_cache_pages(), preventing progress.

   * The fix addresses a corner case in write_cache_pages() on
 the range_cyclic implementation which allows the deadlock.

   * Patch:
 - commit 64081362e8ff4587b4554087f3cfc73d3e0a4cd7
   ("mm/page-writeback.c: fix range_cyclic writeback vs
   writepages deadlock"), present in v4.20-rc1~92^2~19.

  [Test Case]

   * This issue originally has been hit by the 'perforce' (p4d)
 tool in a XFS filesystem, but it's difficult/rare to occur.

   * We've written an userspace + kernel module (kprobes-based)
 to reproduce this problem and verify the test kernel/patch.

   * The kprobes are strictly tied to particular kernel versions
 because of the assembly instruction offsets.  We'll provide
 updated versions for -updates and -proposed for verification.

   * Steps 
 (see output examples in comments):

 - Userspace part:
 $ gcc -o test test.c -pthread

 - Kernel part:
 $ touch Makefile 
 $ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o clean
 $ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o 
modules 

 - Shorter hung task timeout and higher console logging level
   to notice the deadlocked tasks sooner, and watch progress:
 $ echo 10 | sudo tee /proc/sys/kernel/hung_task_timeout_secs
 $ echo 9 | sudo tee /proc/sys/kernel/printk 

 - Load module / Run userspace part (logging to kernel log) in XFS:
 $ sudo insmod kprobe-test.ko
 $ cd /path/to/xfs-mountpoint && sudo sh -c 'stdbuf -oL /path/to/test 
>/dev/kmsg'
 $ sudo rmmod kprobe-test

 You may need to ctrl-z with the original kernel as 'test' doesn't
  finish.

 - Check kernel log or watch the system console:
 $ dmesg

 Check threads in D state.
 $ ps -eLo pid,tid,state,comm | grep D | grep -e test -e kworker

  
  [Regression Potential] 

   * The patch is small but changes core writeback infrastructure,
 so there's a chance this may _affect_ some or other behavior
 that has not been validated with our regression testing; not
 exactly _break_ it.  Please note our regression testing.

   * This has been verified with 'xfstests' (not only for XFS fs,
 despite its original name), used by major Linux filesystems
 for regression testing during development. It's been tested
 on systems with 24 and 4 CPUs (to exercise differences in
 scalability, parallelism, and workload) and XFS and ext4
 (reporter's environment + Ubuntu's default).
 No regressions were observed (the set of failed tests is
 the same in each system and tests failed in the same way).
 
   * This has also been verified with 'iozone' for write intensive
 tests, to exercise the writeback mechanism and no errors were
 observed.

   * The reporter has been running the test kernel with the patch
 for weeks and has not observed any other issues/regressions.

  [Other Info]
   
   * This is only required in Cosmic (for the Bionic HWE kernel),
 and is already applied in Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+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 1824839] Update Released

2019-05-14 Thread Steve Langasek
*** This bug is a duplicate of bug 1826165 ***
https://bugs.launchpad.net/bugs/1826165

The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1016.16~18.04.1 -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:
  Invalid
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:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Ready for Signoff
  phase-changed: Wednesday, 24. April 2019 14:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824839/+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 1818204] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Released
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1826166] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-azure: 4.18.0-1017.17 -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:
  Invalid
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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826165 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Ready for Signoff
  phase-changed: Monday, 13. May 2019 10:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826166/+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 1820930] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  some codecs stop working after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem 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:

  To fix this bug, B/OEM-B/C needs only 1 patch, while v5.0-rc1 introduced
  a new patch which affect this issue, so the DISCO needs 2 patches.

  [Impact]
  After S3, some codecs (alc236, alc255, alc891 and some HDMI codec) stop
  working, they can't detect jack plugging/unplugging or the audio device
  can't show up in the gnome-sound-setting

  [Fix]
  After S3, if it runs runtime_resume(), the codec works again. We change
  the driver to let system_resume() trigger runtime_resume()

  [Test Case]
  This issue is reported from OEM project, some codecs can't detect
  jack pluggin/unplugging, some codecs can't show up in the UI, after
  applying this patch, all related bugs are fixed.

  [Regression Potential]
  Low. have tested on many machines (with this issue or without this issue),
  all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1820930/+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 1812845] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
  triggers system hang on i386

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  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:
  SRU Justification:

  [Impact]

   * Parity page in btrfs raid56 is incorrectly unmapped, allowing to
  easily trigger a reference counter bug on i386 causing a kernel panic

   * The fix unmaps the right rbio pages and adds the proper kunmap()
  call for the parity page

  [Test Case]

   * create a raid5 btrfs filesystem:
     # mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde

   * mount it:
     # mount /dev/sdb /mnt

   * run btrfs scrub in a loop:
     # while :; do btrfs scrub start -BR /mnt; done

  [Fix]

   *
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3897b6f0a859288c22fb793fad11ec2327e60fcd

  kunmap(p_page) was completely left out, so we never
  did an unmap for the p_page and the loop unmapping the rbio page was
  iterating over the wrong number of stripes: unmapping should be done
  with nr_data instead of rbio->real_stripes.

  [Regression Potential]

   * This is an upstream fix, tested on the affected platform. The bug
  is affecting only btrfs raid5/6 users on architectures where kunamp()
  is not a no-op (like i386). It is also a very small patch, so backport
  changes are minimal.

  [Original bug report]

  This issue was not spotted on AMD64

  Reproduce rate: 100%

  The following command is the key to trigger this:
  btrfs scrub start -BR $MNT

  Steps:
  # (Install necessary packages)
  # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  # TMP=/tmp/tmp MNT=/tmp/mnt
  # mkdir -p $TMP; mkdir -p $MNT
  # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes
  # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh

  Trace:
   [  494.357824] [ cut here ]
   [  494.357828] kernel BUG at 
/build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350!
   [  494.365079] invalid opcode:  [#1] SMP
   [  494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif 
gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas 
intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich 
ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid 
sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas 
pata_acpi wmi
   [  494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 
4.15.0-43-generic #46-Ubuntu
   [  494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 
09/18/2012
   [  494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper 
[btrfs]
   [  494.453657] EIP: kunmap_high+0xaa/0xb0
   [  494.457571] EFLAGS: 00010246 CPU: 2
   [  494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: 
   [  494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40
   [  494.474264]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
   [  494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0
   [  494.486353] Call Trace:
   [  494.488967]  kunmap+0x3e/0x50
   [  494.492140]  finish_parity_scrub+0x24d/0x570 [btrfs]
   [  494.497226]  ? update_load_avg+0x64f/0x830
   [  494.501528]  validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs]
   [  494.507527]  raid56_parity_scrub_end_io+0x53/0x70 [btrfs]
   [  494.513058]  bio_endio+0xb9/0x110
   [  494.516574]  ? end_workqueue_fn+0x2c/0x40 [btrfs]
   [  494.521435]  end_workqueue_fn+0x33/0x40 [btrfs]
   [  494.526139]  normal_work_helper+0x7d/0x2f0 [btrfs]
   [  494.531087]  btrfs_endio_raid56_helper+0x10/0x20 [btrfs]
   [  494.536621]  process_one_work+0x1b9/0x3d0
   [  494.540799]  worker_thread+0x37/0x420
   [  494.544628]  kthread+0xf0/0x110
   [  

[Kernel-packages] [Bug 1811815] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

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:
  === SRU Justification ===

  [Impact]
  Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.

  [Test]
  User confirm it fixes the issue.
   
  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===

  The issue here is that the drivers/platform/x86/ideapad_laptop.c
  module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill
  switch, reads the I/O port for its state, gets a zero, and therefore
  reports to the kernel that RFkill is hard-blocked.

  The current workaround is to blacklist the module to stop it being
  loaded.

  I've attached a simple patch for the module that teaches it that this
  model does not have a hardware RF kill switch.

   Original Report -

  Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165
  card, specifically on a Lenovo ideapad 330 laptop.

  A current workaround:

  - Blacklist the "ideapad-laptop" module.
  - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or 
something similar (if it does not already exist), and append "blacklist 
ideapad-laptop" to the file. Save and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dustin 1948 F pulseaudio
   /dev/snd/pcmC0D0p:   dustin 1948 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 04:08:20 2019
  InstallationDate: Installed on 2019-01-15 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210e Acer, Inc
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 3938:1047
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FK
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 
2012" quiet splash nouveau.modeset=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH:
  dmi.product.family: ideapad 330-15ICH
  dmi.product.name: 81FK
  dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH
  dmi.product.version: Lenovo ideapad 330-15ICH
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+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 1813244] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd cause kernel trace "BUG: unable to handle kernel paging
  request at 6db23a14" on Cosmic i386

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * Flow action buffer can be incorrectly resized to contain the newly
  added action entries: the buffer is always resized multiplying the
  previous size by 2, but this might be not enough if the requested size
  is bigger than previous_size*2, causing a buffer overflow

   * The fix correctly resizes the buffer to prevent the buffer overflow

   * Despite the subject this bug can be triggered potentially on any
  architecture, but it is very likely to happen on i386 running the
  following test case

  [Test Case]

   * run this openvswitch test case:
  https://launchpadlibrarian.net/416589265/lp1262692

  [Fix]

   * Instead of resizing the buffer by a factor of 2, use
  max(current_size * 2, current_size + requested_size)

  [Regression Potential]

   * Fix has been tested on the affected platform and verified using
  slub_debug. The patch has been queued up for -stable by David Miller,
  it will be included upstream for the next merge window. It is also a
  very small patch (a one-liner basically), so backport changes are
  minimal.

  [Original bug report]

  This issue was found after leaving a SUT to run overnight (was testing
  the ubuntu_cts_kernel test 13 hours ago before this happens). Can't
  tell if this is a regression, as I haven't find a way to reproduce it.
  But I do see similar reports on the Internet [1]

  After checking the systemd service timers, it looks like this is
  caused by the logrotate.service:

  $ sudo systemctl list-timers --all
  NEXT LEFT  LAST 
PASSEDUNIT ACTIVATES
  Fri 2019-01-25 06:18:58 UTC  1h 40min left Thu 2019-01-24 06:34:15 UTC  22h 
ago   apt-daily-upgrade.timer  apt-daily-upgrade.service
  Fri 2019-01-25 09:15:54 UTC  4h 37min left Fri 2019-01-25 03:43:24 UTC  55min 
ago apt-daily.timer  apt-daily.service
  Fri 2019-01-25 17:02:47 UTC  12h left  Fri 2019-01-25 04:20:17 UTC  18min 
ago motd-news.timer  motd-news.service
  Sat 2019-01-26 00:00:00 UTC  19h left  Fri 2019-01-25 00:00:37 UTC  4h 
38min ago  logrotate.timer  logrotate.service
  Sat 2019-01-26 04:02:38 UTC  23h left  Fri 2019-01-25 04:02:38 UTC  36min 
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv
  Mon 2019-01-28 00:00:00 UTC  2 days left   Wed 2019-01-23 10:44:18 UTC  1 day 
17h ago fstrim.timer fstrim.service
  n/a  n/a   n/a  n/a   
snapd.snap-repair.timer  snapd.snap-repair.service

  7 timers listed.

  After this happens, you won't be able to reboot it with the command.
  $ sudo reboot
  sudo: unable to resolve host onza: Resource temporarily unavailable
  Killed

  Here is the error message, please refer to the attachment for a
  complete syslog:

  Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files...
  Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel 
paging request at 6db23a14
  Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = 

  Jan 25 00:00:37 onza kernel: [45282.968650] Oops:  [#1] SMP
  Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: 
systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu
  Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
  Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240
  Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 
f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 
45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 
85 3f 01
  Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 
350d EDX: 350c
  Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 

[Kernel-packages] [Bug 1818294] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  HiSilicon HNS ethernet broken in 4.15.0-45

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]
  The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:

308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
  after rmmod.")

  While that fixed an issue with phys after reloading the driver, it
  caused an issue with some phys on initial load.

  [Test Case]
  dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
  (With enahisic2i2 properly wired up)

  [Fix]
  This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.

  [Regression Risk]
  Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1812123] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-azure 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812123/+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 1822760] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Bionic: Sync to Xenial (Spectre)

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

Bug description:
  == SRU Justification ==

  There are a couple of Spectre related commits in Xenial that never
  landed in Bionic. Fix that to prevent a regression when upgrading from
  Xenial to Bionic.

  == Regression Potential ==

  Low. These are not very intrusive commits that have been in upstream
  for quite a while.

  == Fix ==

  Backport the relevant commits from upstream.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822760/+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 1825074] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems with video cards using amdgpu driver may fail to resume due to 
resource leakage.

  [Fix]
  73469585510d drm/amdgpu: fix for wb_clear

  [Test Case]
  Verified with fwts for a thounsand runs.

  [Regression Risk]
  Low. This patch has been included in stable kernel v4.16.y and on, and
  it's mostly a trivial bug fix.

   Original Bug Report 
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu 

[Kernel-packages] [Bug 1818490] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  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:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd 

[Kernel-packages] [Bug 1825487] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1825487/+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 1825058] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

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

Bug description:
  [Impact]
  Kernel NULL pointer dereference in mac80211_hwsim.

  [Fix]
  a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device 
registered

  This fix has been included in 4.19.9 or above.

  [Test Case]
  $ git clone https://github.com/aircrack-ng/aircrack-ng
  # Tested with 69a406c
  $ cd aircrack-ng
  $ grep 'sudo apt' README.md | bash
  $ autoreconf -i
  $ ./configure --with-experimental
  $ make check
  $ sudo bash scripts/airmon-ng.linux check kill
  $ sudo make integration

  # Run integration test again and check dmesg
  $ sudo bash scripts/airmon-ng.linux check kill
  $ sudo make integration

  Verified with VMs setup locally.

  [Regression Risk]
  Low. Move forward data structure initialization only. This patch has
  also been included in LTS stable kernel.

   Original Bug Report 

  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.

  Output:

  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim 

[Kernel-packages] [Bug 1822821] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [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 code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822821/+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 1814874] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  NULL pointer dereference when using z3fold and zswap

Status in Linux:
  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

Bug description:
  == Justification ==
  When using z3fold and zswap on a VM under overcommitted memory stress,
  z3fold will complains about an "unknown buddy id 0" and fail to get a
  pointer to the mapped allocation in z3fold_map().

   z3fold: unknown buddy id 0
   WARNING: CPU: 2 PID: 1584 at mm/z3fold.c:971 z3fold_zpool_map+0xce/0x100 
[z3fold]

  And it will leads to a null pointer dereference in zswap

   BUG: unable to handle kernel NULL pointer dereference at 
   PGD 0 P4D 0
   Oops:  [#1] SMP PTI
   CPU: 2 PID: 1584 Comm: stress Tainted: GW 4.18.0-17-generic 
#18-Ubuntu
   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 
04/01/2014
   RIP: 0010:zswap_writeback_entry+0x4d/0x360

  == Fix ==
  ca0246bb (z3fold: fix possible reclaim races)

  This patch has already in Disco, and can be cherry-picked into B/C.
  Not needed for Xenial and older kernels as z3fold is not supported.

  == Test ==
  Test kernels for Bionic / Cosmic could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Bionic/
  http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/

  This issue can be reproduced easily in a KVM with the following setup:
   * 8G disk, 4G RAM, 4 CPUs
   * 1G swap
   * "zswap.enabled=1 zswap.zpool=z3fold zswap.max_pool_percent=7" added to grub
   * "z3fold" module added into /etc/initramfs-tools/modules

  Stress it with two childs running:
   * stress --vm-bytes 512M --vm 4 --vm-hang 3
   * stress --vm-bytes 512M --vm 4 --vm-hang 7

  The VM is expected to crash within 5 minutes.

  With the patched kernel, the VM can withstand this stress for over an
  hour with crashing with this issue

  == Regression potential ==
  Small.

  Fix limited to z3fold. User needs to enable it explicitly for this
  feature.

  
  == Original Bug Report ==
  Under memory pressure, my VM locks up. This has been reported upstream though 
I don't know how far any solution has progressed.

  https://bugzilla.kernel.org/show_bug.cgi?id=201603

  Feb  6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0
  Feb  6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle 
kernel NULL pointer dereference at 0008

  The little bit of log I managed to salvage is attached.

  This has happened to two identical VMs. Unusually it has not occurred
  on a third VM which is configured the same but has less RAM (fingers
  crossed it won't).

  Irrelevant information:
  I thought the lock-ups were due to me using a BTRFS filesystem, however I 
swapped over to NILFS2 and this still occurs. The only difference seems to be 
that I am now able to grab some of the kernel output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:55:05 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1814874/+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 1819786] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  4.15 kernel ip_vs --ops causes performance and hang problem

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  From the commit message:
  "Connections in One-packet scheduling mode (-o, --ops) are
  removed with refcnt=0 because they are not hashed in conn table."

  [Fix]
  From the commit message:
  "To avoid refcount_dec reporting this as error, change them to be
  removed with refcount_dec_if_one as all other connections."

  [Test]
  The bug reporter has a reproducer and confirmed this commit fixes the
  issue.

  [Regression Potential]
  Low. Fix for a specific use case, and it's in upstream for a while.

  === Original Bug Report ===
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.

  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.

  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.

  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***

  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:

  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342

  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.

  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:

  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up

  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is left to the tester.  I just added alias 10.129.131.x
  addresses on my "outbound" interface and a static route for 172.16.5.1 to my
  client system so the test packets arrived on the "inbound" interface.

  I set up routing and addresses on my 2 NIC test such that packets arrived
  on 

[Kernel-packages] [Bug 1823056] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autopkgtests run too often, too much and don't skip enough

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * linux autopkgtest should only execute either rebuild tests, when triggered 
by toolchain.
 or execute regression suite when triggered by meta
 but never both. As otherwise, it results in false negative results for the 
kernel

  [Test Case]

   * Trigger adt test of linux with a matching linux-meta. Check that
  rebuild test is skipped, and that the regression suite test runs.

   * trigger adt test of linux with triggered by gcc-6/7/8 (as
  appropriate) and observe that rebuild test runs, and regression suite
  test is skipped.

   * (when this is applied to flavours) trigger adt test of linux-* with
  a matching flavour meta, and check that regression test-suite is
  skipped on kernels that cannot boot in scaling stack (e.g. gcp, azure,
  aws, etc)

  [Fix]

   * debian/tests/* are modified to pay more attention as to what they
  are triggered by, and raise appropriate skipped error codes

  [Regression Potential]

   * incorrect tests may run at incorrect time is the regression
  potential here, hence the two test cases verify that the right tests
  are executed when expected.

   * care was taken to take into account all linux kernel flavours,
  hence the third test case need to be reverified on flavoured kernels.

  [Other Info]

   * affects all stable series xenial and up, across all kernel flavours

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056/+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 1821663] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem 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]
  After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM 
is
  enabled, on some codecs or for some hw design, there is noise with the codec
  runtime PM enabled.

  
  [Fix]
  put the machine in the power_save_black_list, this will set the power_save=0

  [Test Case]
  just boot up and do some audio operations, there is no noise anymore

  [Regression Risk]
  Low. this patch ony applies to the specific machines.


  
  I'm experiencing a repeating crackling noise after 19.04 upgrade that start 
just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+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 1825272] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  headset-mic doesn't work on two Dell laptops.

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  the headset-mic can't be detected after we plug the headset into the audio 
jack

  [Fix]
  Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE.

  [Test Case]
  Boot up the system
  plug the headset into the audio jack
  The audio device selecting dialogue will show up
  selecting headset-mic icon, then rerord sound from headset-mic, it works well.

  [Regression Risk]
  Low. this patch only applies to specific dell machines which have the same 
pin config
  as defined in the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1825272/+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 1820868] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  bionic: fork out linux-snapdragon into its own topic kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux-meta source package in Bionic:
  Fix Released
Status in linux-snapdragon source package in Bionic:
  Fix Released

Bug description:
  Impact:

  During the Bionic cycle, a decision was made to incorporate the 
linux-snapdragon
  kernel into the master branch, thus reducing the number of topic kernels and 
the
  stable maintenance burden.

  But as time passed and new patches were produced by Qualcomm, incorporating 
them
  into master while avoiding to destabilize generic became more and more
  problematic, down to the point where it was not a viable approach
  anymore.

  At that point, the decision was made to fork out linux-snapdragon into its own
  topic kernel (e.g. linux-raspi2), giving more room to incorporate new code
  coming from the Qualcomm tree and avoiding to destabilize any other target in
  generic.

  Fix:

  This is a three step process:

  1) disable building linux-snapdragon from master by applying the attached 
patch
  to bionic/master

  2) create a new bionic/linux-snapdragon branch and reset hard to my
  lp:snapdragon-topic-kernel branch  (see below)

  3) update bionic-meta to point to the new bionic/linux-snapdragon
  kernel

  Regression potential

  From the point of view of bionic/master, this pull request doesn't introduce 
any
  substantial change, and in the future will let us purge generic from several
  external patches.

  While from the point of view of linux-snapdragon, with ~600 code commits and 
~4k
  config changes, this represent a brand new kernel and while great care was 
used
  while putting together this branch, there's clearly a regression potential 
here
  but we can't leave linux-snapdragon stagnate behind the curve, so the sooner 
we
  bite the bullet, the better we can the deal with the eventual fallout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+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 1819921] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] [B/OEM] Fix ACPI bug that causes boot failure

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  V2:
  Fix non-x86 building error.

  [Impact]
  Some lenovo laptops failed to boot at a very early stage, only blackscreen 
shown.

  [Fix]
  Some system BIOS set definition in if statement, it would be deferred to
  be loaded.
  Some devices would not work properly and cause a system lockup.
  add a quirk for these laptops to execute all acpi tables and
  make system work properly.

  [Test]
  Tested on several laptops, the laptop that failed to boot boots well.
  Other laptops still works fine.

  [Regression Potential]
  SAUCE patch.Low, specific changes depends on hardware.

  Upstream fix:

  commit 5a8361f7ecceaed64b4064000d16cb703462be49
  Author: Schmauss, Erik 
  Date:   Thu Feb 15 13:09:30 2018 -0800

  ACPICA: Integrate package handling with module-level code

  Due to the lots of changes in this commit and other regressions concern
  So made a sauce patch in Bionic kernel with the specific BIOS series.
  Verified on several laptops. Fix boot failure and no regression found.

  The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1819921/+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 1822870] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Fix Committed
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

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+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 1823972] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  (please see got log without --oneline for stable@ details)

  However both bionic and xenial/hwe has much less fuse patches applied:

[Kernel-packages] [Bug 1821290] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

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

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1821290/+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 1824553] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Bionic update: upstream stable patchset for fuse 2019-04-12

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

Bug description:
  SRU Justification:

  [Impact]
 This stable patchset update affects only the FUSE filesystem, since
 we have received bug reports about FUSE causing problems with the
 Bionic kernel, see also bug #1823972.

 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-04-12 (ported from v4.15 .. v5.0)
 from git://git.kernel.org/

  fuse: decrement NR_WRITEBACK_TEMP on the right page
  fuse: call pipe_buf_release() under pipe lock
  fuse: handle zero sized retrieve correctly
  fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS
  fuse: fix use-after-free in fuse_direct_IO()
  fuse: fix possibly missed wake-up after abort
  fuse: fix leaked notify reply 
  fuse: fix blocked_waitq wakeup
  fuse: set FR_SENT while locked 
  fuse: Fix use-after-free in fuse_dev_do_write()
  fuse: Fix use-after-free in fuse_dev_do_read()
  fuse: Don't access pipe->buffers without pipe_lock()
  fuse: Fix oops at process_init_reply()
  fuse: umount should wait for all requests 
  fuse: fix unlocked access to processing queue
  fuse: fix double request_end()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+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 1822247] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification, BIONIC ==

  [Impact]

  Running the autotest regression test ubuntu_nbd_smoke occasionally
  trips I/O errors such as:

  [  700.668758] print_req_error: I/O error, dev nbd0, sector 0
  [  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read

  This happens when the nbd client detaches and the backing store is
  removed. The fix is to ensure a rescan occurs.

  [Fix]

  Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set 
bd_invalidated"). If a disconnect action happens the
  partition table gets invalidated and rescanned properly.

  [Test]

  Without the fix running the Ubuntu Kernel Team nbd smoke test will
  occasionally trip the bug and the error message from the kernel
  appears and the test fails. With the fix, this test has been run tens
  of times without showing the failure.

  To test run:
  autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control

  [Regression Potential]

  This fix touches just the NBD driver and has been upstream since May
  2018 without any subsequent bug reports against it, so it is a known
  good fix. At most it sets the bd_invalidated flag more aggressively,
  so the rescan will occur, so I believe the regression potential is
  very limited just to ndb client connect/disconnect activity.

  -

  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.

    * Command:
    
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
    _test.sh
    Exit status: 1
    Duration: 7.90551400185

    stdout:
    creating backing nbd image /tmp/nbd_image.img

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-13924
    Date:  Fri Mar 29 06:06:04 UTC 2019
    Host:  baltar
    Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
    Machine:   baltar ppc64le ppc64le
    CPUs online:   160
    CPUs total:160
    Page size: 65536
    Pages avail:   1904339
    Pages total:   2089666
    Free space:
    Filesystem  Size  Used Avail Use% Mounted on
    udev 61G 0   61G   0% /dev
    tmpfs13G   12M   13G   1% /run
    /dev/sda2   1.8T   11G  1.7T   1% /
    tmpfs64G 0   64G   0% /dev/shm
    tmpfs   5.0M 0  5.0M   0% /run/lock
    tmpfs64G 0   64G   0% /sys/fs/cgroup
    tmpfs13G 0   13G   0% /run/user/1000
    


    NBD device /dev/nbd0 created
    found nbd export
    NBD exports found:
    test
    starting client with NBD device /dev/nbd0
    Negotiation: ..size = 128MB
    creating ext4 on /dev/nbd0
    mkfs on /dev/nbd0 succeeded after 0 attempt(s)
    checking ext4 on /dev/nbd0
    fsck from util-linux 2.31.1
    /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

    mount:
    /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered)
    mounted on /dev/nbd0

    free:
    Filesystem 1K-blocks  Used Available Use% Mounted on
    /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-13924

    creating large file /mnt/nbd-test-13924/largefile
    -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile

    free:
    Filesystem 1K-blocks   Used Available Use% Mounted on
    /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-13924

    removing file /mnt/nbd-test-13924/largefile
    unmounting /mnt/nbd-test-13924
    stopping client
    disconnect, sock, done
    Found kernel warning, IO error and/or call trace
    echo
    [  694.662746] creating backing nbd image /tmp/nbd_image.img
    [  695.821047] NBD device /dev/nbd0 created
    [  696.271555] found nbd export
    [  697.318393] starting client with NBD device /dev/nbd0
    [  697.323210] creating ext4 on /dev/nbd0
    [  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)

[Kernel-packages] [Bug 1826338] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-aws: 4.15.0-1038.40 -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:
  Invalid
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 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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826337 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 10:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826338/+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 1826358] Update Released

2019-05-14 Thread Steve Langasek
The verification of the Stable Release Update for linux-aws 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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux: 4.15.0-49.53 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 10:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826358/+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 1827697] Re: Enroll key whiptail prompt blocks kernel header package upgrades

2019-05-04 Thread Steve Langasek
ok based on the process tree I've identified the source of the trouble,
/etc/kernel/header_postinst.d/dkms invokes dkms_autoinstaller with
>/dev/null.  So this is a similar symptom to other bugs that have been
fixed, but is a separate unfixed bug.

Note that a workaround for this problem is to run 'sudo update-
secureboot-policy --enroll-key' outside of apt.

** Also affects: dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: shim-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: shim-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Disco)
   Importance: Undecided
   Status: New

** No longer affects: shim-signed (Ubuntu)

** No longer affects: shim-signed (Ubuntu Xenial)

** No longer affects: shim-signed (Ubuntu Bionic)

** No longer affects: shim-signed (Ubuntu Cosmic)

** No longer affects: shim-signed (Ubuntu Disco)

** No longer affects: shim-signed (Ubuntu Eoan)

** Changed in: dkms (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: dkms (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: dkms (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: dkms (Ubuntu Disco)
   Status: New => Triaged

** Changed in: dkms (Ubuntu Eoan)
   Status: New => Triaged

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

Title:
  Enroll key whiptail prompt blocks kernel header package upgrades

Status in dkms package in Ubuntu:
  Triaged
Status in dkms source package in Xenial:
  Triaged
Status in dkms source package in Bionic:
  Triaged
Status in dkms source package in Cosmic:
  Triaged
Status in dkms source package in Disco:
  Triaged
Status in dkms source package in Eoan:
  Triaged

Bug description:
  I noticed that sometimes the system upgrade is blocked in the kernel
  header package's configure phase, in the process manager I found that
  it is blocked by the "Configuring Secure Boot" whiptail prompt started
  by `update-secureboot-policy --enroll-key` which doesn't surface to
  the terminal and hence not interactable.

  Refer the attached screenshot for the process status at the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+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 1827752] Re: Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when using Ubuntu 19.04

2019-05-04 Thread Steve Langasek
** Tags removed: regression-update

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

Title:
  Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when
  using Ubuntu 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04 this laptop no longer suspends to RAM
  correctly (and it would resume by itself in previous versions of
  Ubuntu). It does not matter if the lid is closed or trying to suspend
  from GUI/CLI, the laptop tries to suspend but immediately resumes back
  to the lock screen.

  Below I attached the information necessary to debug such problem
  followed from the wiki, this logs were made using the Linux mainline
  non-daily kernel 5.0.12 from the Ubuntu kernel repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827752/+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 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server

2019-05-01 Thread Steve Langasek
Based on the analysis in the log, there does not appear to be a bug in
systemd - which is behaving as intended, and defaulting to the best
available cpufreq governor for low power consumption - but there may be
a bug in the kernel resulting in the wrong scaling driver being used on
the hardware in question.  Reassigning to the kernel.

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  set-cpufreq: 'powersave' governor configuration sanity on ubuntu
  server

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  Whilst debugging 'slow instance performance' on a Ubuntu Bionic based
  cloud, I observed that the default cpu governor configuration was set
  to 'powersave'; toggling this to 'performance' (while in not anyway a
  particularly green thing todo) resulted in the instance slowness
  disappearing and the cloud performance being as expected (based on a
  prior version of the deploy on Ubuntu Xenial).

  AFAICT Xenial does the same thing albeit in a slight different way,
  but we definitely did not see the same performance laggy-ness under a
  Xenial based cloud.

  Raising against systemd (as this package sets the governor to
  'powersave') - I feel that the switch to 'performance' although
  appropriate then obscures what might be a performance/behavioural
  difference in the underlying kernel when a machine is under load.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:05:46 2018
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt 
intel_iommu=on
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 02C2CP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806012/+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 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate

2019-05-01 Thread Steve Langasek
The last outstanding open task for sysvinit/xenial is also invalid, to
my understanding.  Both /etc/init.d/ondemand in <= xenial and
/lib/systemd/set-cpufreq in >= bionic implement the intended default
policy of interactive/ondemand/powersave, not performance.

** Changed in: sysvinit (Ubuntu Xenial)
   Status: Triaged => Invalid

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

Title:
  Keep powersave CPU frequency scaling governor for CPUs that support
  intel_pstate

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in sysvinit source package in Xenial:
  Invalid

Bug description:
  Hi,

  With the new Ubuntu archive servers, we saw constantly high load and
  after some tinkering, we found that it was mostly CPUs being woken up
  to see if they should enter idle states. Changing the CPU frequency
  scaling governor to "performance" saw a considerable drop.

  Perf report using the following commands:

  | perf record -g -a sleep 10
  | perf report

  | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906
  |   Children  Self  Command  Shared Object Symbol
  | +   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  | +   53.51% 0.00%  swapper  [kernel.kallsyms] [k] 
start_secondary
  | +   53.02% 0.08%  swapper  [kernel.kallsyms] [k] 
call_cpuidle
  | +   52.94% 0.02%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter
  | +   31.81% 0.67%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter_state
  | +   29.59% 0.12%  swapper  [kernel.kallsyms] [k] 
acpi_idle_enter
  | +   29.45% 0.05%  swapper  [kernel.kallsyms] [k] 
acpi_idle_do_entry
  | +   29.43%29.43%  swapper  [kernel.kallsyms] [k] 
acpi_processor_ffh_cstate_enter
  | +   20.51% 0.04%  swapper  [kernel.kallsyms] [k] 
ret_from_intr
  | +   20.47% 0.12%  swapper  [kernel.kallsyms] [k] do_IRQ
  | +   19.30% 0.07%  swapper  [kernel.kallsyms] [k] 
irq_exit
  | +   19.18% 0.07%  apache2  [kernel.kallsyms] [k] 
entry_SYSCALL_64_fastpath
  | +   18.80% 0.17%  swapper  [kernel.kallsyms] [k] 
__do_softirq
  | +   16.45% 0.11%  swapper  [kernel.kallsyms] [k] 
net_rx_action
  | +   16.25% 0.43%  swapper  [kernel.kallsyms] [k] be_poll
  | +   14.74% 0.21%  swapper  [kernel.kallsyms] [k] 
be_process_rx
  | +   13.61% 0.07%  swapper  [kernel.kallsyms] [k] 
napi_gro_frags
  | +   12.58% 0.04%  swapper  [kernel.kallsyms] [k] 
netif_receive_skb_internal
  | +   12.48% 0.03%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb
  | +   12.42% 0.24%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb_core
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f27983b5028
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f2798369028
  | +   11.49% 0.16%  swapper  [kernel.kallsyms] [k] ip_rcv
  | +   11.29% 0.09%  swapper  [kernel.kallsyms] [k] 
ip_rcv_finish
  | +   10.77% 0.05%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver
  | +   10.70% 0.06%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver_finish
  | +   10.55% 0.22%  swapper  [kernel.kallsyms] [k] 
tcp_v4_rcv
  | +   10.10% 0.00%  apache2  [unknown] [k] 

  | +   10.01% 0.04%  swapper  [kernel.kallsyms] [k] 
tcp_v4_do_rcv

  Expanding in a few of those, you'll see:

  | -   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  |- 55.04% cpu_startup_entry
  |   - 52.98% call_cpuidle
  |  + 52.93% cpuidle_enter
  |  + 0.00% ret_from_intr
  |0.00% cpuidle_enter_state
  |0.00% irq_entries_start
  |   + 1.14% cpuidle_select
  |   + 0.47% schedule_preempt_disabled
  | 0.10% rcu_idle_enter
  | 0.09% rcu_idle_exit
  |   + 0.05% ret_from_intr
  |   + 0.05% tick_nohz_idle_enter
  |   + 0.04% arch_cpu_idle_enter
  | 0.02% cpuidle_enter
  | 0.02% tick_check_broadcast_expired
  |   + 0.01% cpuidle_reflect
  | 0.01% menu_reflect
  | 0.01% atomic_notifier_call_chain
  | 0.01% local_touch_nmi
  | 0.01% cpuidle_not_available
  | 0.01% menu_select
  | 0.01% 

[Kernel-packages] [Bug 1826993] [NEW] rebuild autopkgtest never succeeds

2019-04-29 Thread Steve Langasek
Public bug reported:

The linux-oracle package never succeeds its rebuild autopkgtest.

  HOSTCC  scripts/selinux/genheaders/genheaders
In file included from /tmp/autopkgtest.vlURUK/build.51y/src/scripts/selinux/genh
eaders/genheaders.c:19:
/tmp/autopkgtest.vlURUK/build.51y/src/security/selinux/include/classmap.h:247:2:
 error: #error New address family defined, please update secclass_map.
 #error New address family defined, please update secclass_map.
  ^
make[6]: *** [scripts/Makefile.host:90: scripts/selinux/genheaders/genheaders] E
rror 1
make[2]: Leaving directory 
'/tmp/autopkgtest.vlURUK/build.51y/src/debian/build/build-oracle'
make[1]: Leaving directory '/tmp/autopkgtest.vlURUK/build.51y/src'
make[5]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/scripts/Makefile.build:604: 
scripts/selinux/genheaders] Error 2
make[4]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/scripts/Makefile.build:604: 
scripts/selinux] Error 2
make[3]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/Makefile:589: scripts] 
Error 2
make[2]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/Makefile:278: 
__build_one_by_one] Error 2

(http://autopkgtest.ubuntu.com/packages/l/linux-oracle/eoan/amd64)

Since this test is skipped when linux-meta-oracle is the trigger, these
failures show up as regressions and clog proposed-migration.

Either the test should be fixed so that the package can actually be
rebuilt via the autopkgtest, or the autopkgtest should always be skipped
for this custom kernel.

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

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

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

Title:
  rebuild autopkgtest never succeeds

Status in linux-oracle package in Ubuntu:
  Confirmed

Bug description:
  The linux-oracle package never succeeds its rebuild autopkgtest.

HOSTCC  scripts/selinux/genheaders/genheaders
  In file included from 
/tmp/autopkgtest.vlURUK/build.51y/src/scripts/selinux/genh
  eaders/genheaders.c:19:
  
/tmp/autopkgtest.vlURUK/build.51y/src/security/selinux/include/classmap.h:247:2:
   error: #error New address family defined, please update secclass_map.
   #error New address family defined, please update secclass_map.
^
  make[6]: *** [scripts/Makefile.host:90: 
scripts/selinux/genheaders/genheaders] E
  rror 1
  make[2]: Leaving directory 
'/tmp/autopkgtest.vlURUK/build.51y/src/debian/build/build-oracle'
  make[1]: Leaving directory '/tmp/autopkgtest.vlURUK/build.51y/src'
  make[5]: *** 
[/tmp/autopkgtest.vlURUK/build.51y/src/scripts/Makefile.build:604: 
scripts/selinux/genheaders] Error 2
  make[4]: *** 
[/tmp/autopkgtest.vlURUK/build.51y/src/scripts/Makefile.build:604: 
scripts/selinux] Error 2
  make[3]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/Makefile:589: scripts] 
Error 2
  make[2]: *** [/tmp/autopkgtest.vlURUK/build.51y/src/Makefile:278: 
__build_one_by_one] Error 2

  (http://autopkgtest.ubuntu.com/packages/l/linux-oracle/eoan/amd64)

  Since this test is skipped when linux-meta-oracle is the trigger,
  these failures show up as regressions and clog proposed-migration.

  Either the test should be fixed so that the package can actually be
  rebuilt via the autopkgtest, or the autopkgtest should always be
  skipped for this custom kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1826993/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-04-18 Thread Steve Langasek
Hello fossfreedom, or anyone else affected,

Accepted dkms into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dkms (Ubuntu Disco)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  No wireless networks displayed for broadcom BCM43142

Status in dkms package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Invalid
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  The dkms version available in disco regressed in behavior in
  comparison to earlier series, causing `dkms uninstall` removing the
  module from the built tree instead of only uninstalling it. Per the
  dkms manpage, an uninstall operation should leave the module in the
  'built' state, while currently it ends up only in the 'added' state.

  This breaks our current shim-signed logic, since on postinst we're
  uninstalling every dkms module, checking if we uninstalled it
  correctly by making sure it's in the 'built' state and then signing it
  if everything is ok. And this is now broken.

  This seemed to have been introduced unintentionally as the manpage still 
notes for `dkms uninstall`:
  "Uninstalls an installed module/module-version combo from the kernel/arch 
passed in the -k option, or the current kernel if the -k option was not passed 
upon. After uninstall completion, the driver will be left in the built state.
  To completely remove a driver, the remove action should be utilized."

  The bug has been made visible with the bcmwl-kernel-source driver,
  which, if installed before shim-signed, will then become uninstalled
  and not reinstalled again (because of the failed status check before
  signing).

  [Test Case]

  An easy way of checking if the uninstall logic has been reverted:

   1. On a disco system, install the dkms and bcmwl-kernel-source packages 
(-proposed disabled).
   2. Check the version of the module installed `dkms status`.
   3. Once the installation completes, uninstall the bcmwl dkms module from the 
system:
   `dkms uninstall bcmwl/`
   4. Checks that the status is not reported as 'built' (should be something 
like 'added' only):
   `dkms status bcmwl`
   5. Enable disco-proposed and upgrade dkms.
   6. Re-install the bcmwl-kernel-source package.
   7. Once again uninstall the bcmwl dkms module:
   `dkms uninstall bcmwl/`
   8. Check the status and notice that it is now reported as 'built':
   `dkms status bcmwl`

  Another way would be checking on a secureboot-enabled system that has
  Broadcom wireless installing the -proposed dkms, then bcmwl-kernel-
  source and finally shim-signed (reinstalling if necessary). This
  operation should result in the broadcom dkms module still being
  installed and active. But this test should be counted as an optional
  'additional test'.

  [Regression Potential]

  Since this does change the dkms uninstall behavior, there is always
  some risk involved. One of the potential regressions could be related
  to kernel uninstallation, as we are reverting parts of the kernel
  prerm scripts along with the revert - but the risk should be low as
  we're actually reverting to the state we had in all series prior to
  disco. In overall the uninstall command of dkms might have regressed
  its behavior in case some other place started assuming the removals of
  modules from the built directory, but seeing the disco diff it's
  highly improbable.

  [Original Description]

  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that 

[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

2019-04-12 Thread Steve Langasek
initramfs-tools uploaded for disco.  Thadeu, do you want to prepare a
separate debdiff for bionic and cosmic?

** Changed in: initramfs-tools (Ubuntu Disco)
   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/1778844

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in initramfs-tools source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.


  -

  
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   

[Kernel-packages] [Bug 1824177] Re: dmesg spammed with nvidia-nvlink messages during install

2019-04-10 Thread Steve Langasek
This looks like a problem with the integration in the nvidia drivers
package, which should not be trying to load modules immediately after
installation and prior to a reboot.  Reassigning for investigation.

** Package changed: ubiquity (Ubuntu) => nvidia-graphics-drivers-410
(Ubuntu)

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

Title:
  dmesg spammed with nvidia-nvlink messages during install

Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop.
  I've selected the 3rd party driver option in ubiquity and now my dmesg
  is spammed 10x per second with this chunk. This appears to be slowing
  down the install.

  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major 
device number 235
  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 235
  [Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 
1 device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: 
 NVRM: nouveau, rivafb, nvidiafb or rivatv 
 NVRM: was loaded and obtained ownership of the 
NVIDIA device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module 
(and/or
 NVRM: reconfigure your kernel without the 
conflicting
 NVRM: driver(s)), then try loading the NVIDIA 
kernel module
 NVRM: again.
  [Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 16:29:38 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-410/+bug/1824177/+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 1822786] Re: linux-raspi2: 4.18.0-1012.14 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-raspi2: 4.18.0-1012.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 12:32 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822786/+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 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-kvm: 4.18.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 13:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822794/+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 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-gcp: 4.18.0-1009.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822792 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 14:03 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822793/+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 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-azure: 4.18.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 17:34 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822791/+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 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-aws: 4.18.0-1013.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 16:32 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822788/+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 1822796] Re: linux: 4.18.0-18.19 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux: 4.18.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822788 (linux-aws), bug 1822791 
(linux-azure), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm)

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 08:30 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822796/+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 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux: 4.15.0-48.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 
1822981 (linux)

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 17:31 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+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 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

2019-04-03 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux: 4.4.0-146.172 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 03. April 2019 17:31 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+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 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)

2019-04-02 Thread Steve Langasek
This is because the raspi2 kernel package does not Provides:  zfs-dkms,
zfs-modules, as expected for Ubuntu kernel packages which include ZFS
support.  So if you try to install the zfs-initramfs package, apt will
try to pull in something which satisfies the dependencies if nothing
else is already installed which does, and it doesn't know that the
kernel image it's pulling is not an appropriate provider of zfs for the
running system.

If there is a bug here, it's that the Ubuntu zfs sauce patches are not
enabled on the raspi2 arm64 kernel build.

However, given the memory limitations of the raspi3 family of devices,
I'm not sure it's at all advisable to try to run zfs on such a system.

** Package changed: ubuntu => linux-raspi2 (Ubuntu)

** Changed in: linux-raspi2 (Ubuntu)
   Status: New => Triaged

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

Title:
  ZFS module is installed for wrong kernel on arm64-raspi3 systems
  (19.04 beta)

Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled-
  server-arm64+raspi3.img

  Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP
  PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64
  GNU/Linux)

  Problem: The ZFS module is installed for a kernel that can not be
  used.

  apt-get install zfs-initramfs 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux
  Suggested packages:
fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools
linux-headers-5.0.0-8-snapdragon nfs-kernel-server
samba-common-bin
  The following NEW packages will be installed:
libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
linux-image-unsigned-5.0.0-8-snapdragon
linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed
zfsutils-linux
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 55.7 MB of archives.
  After this operation, 305 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 
linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux 
arm64 0.7.12-1ubuntu5 [42.8 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux 
arm64 0.7.12-1ubuntu5 [50.7 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux 
arm64 0.7.12-1ubuntu5 [498 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux 
arm64 0.7.12-1ubuntu5 [121 kB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux 
arm64 0.7.12-1ubuntu5 [267 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs 
arm64 0.7.12-1ubuntu5 [22.2 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 
0.7.12-1ubuntu5 [57.5 kB]
  Fetched 55.7 MB in 37s (1486 kB/s)   
  Selecting previously unselected package linux-modules-5.0.0-8-snapdragon.
  (Reading database ... 61671 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package 
linux-image-unsigned-5.0.0-8-snapdragon.
  Preparing to unpack 
.../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ...
  Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ...
  Selecting previously unselected package libnvpair1linux.
  Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libnvpair1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libuutil1linux.
  Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libuutil1linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzpool2linux.
  Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzpool2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package libzfs2linux.
  Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking libzfs2linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfsutils-linux.
  Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ...
  Unpacking zfsutils-linux (0.7.12-1ubuntu5) ...
  Selecting previously unselected package zfs-initramfs.
  

[Kernel-packages] [Bug 1794055] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   

[Kernel-packages] [Bug 1808389] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello James, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | 

[Kernel-packages] [Bug 1817817] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello AceLan, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  To add power setting bin file for SAR support (QCA6174)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  To meet the policy requirement of the RF radiation, we need to reduce the 
power of the device.

  [Fix]
  Qualcomm provides a new firmware for this.
  97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

  [Test]
  We can't verify it.

  [Regression Potential]
  Low, it's a fix from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1817817/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-03-13 Thread Steve Langasek
ok, so can someone who's experiencing this bug run the requested command
so we can collect more information?

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Incomplete

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-03-13 Thread Steve Langasek
There's a reasonable chance this is an issue with the lockdown kernel
patches in Ubuntu 14.04, so opening a task on linux also.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Incomplete

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1748983] Re: Generate per-machine MOK for dkms signing

2019-03-11 Thread Steve Langasek
I have asked for additional information on that bug.

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-03-11 Thread Steve Langasek
Please run 'apport-collect -p shim-signed 1818134' to provide further
information about the state of SecureBoot on your system.

** Changed in: shim-signed (Ubuntu)
   Status: New => Incomplete

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in shim-signed package in Ubuntu:
  Incomplete

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-03-01 Thread Steve Langasek
Seth, my only preference here is that the test cases be appropriate for
what's being updated.  If there are going to be updates affecting
multiple series of chips, then I think the test case should also cover
testing across multiple series.  Otherwise, if that testing is onerous,
I think withdrawing this SRU and changing only the firmware for the
series we know is affected by this bug would be better.

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Incomplete
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Incomplete

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  

[Kernel-packages] [Bug 1817072] Re: WiFi connnectivity loses

2019-02-21 Thread Steve Langasek
** Package changed: shim-signed (Ubuntu) => linux (Ubuntu)

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

Title:
  WiFi connnectivity loses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I installed ubuntu 18.04 mate, randomly loses wifi connectivity
  and I must constantly disconnect from the wifi network and reconnect
  to have connectivity. From the same machine but booting windows that
  situation does not happen, only when booting Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817072/+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 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly

2019-02-17 Thread Steve Langasek
That is unlikely to be true.  Please file a new bug report and describe
in your own words what is happening and why you believe it is a bug.

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

Title:
  18.10 kernel does not appear to validate kernel module signatures
  correctly

Status in linux package in Ubuntu:
  In Progress
Status in shim package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released
Status in shim source package in Cosmic:
  Invalid

Bug description:
  SRU Justification

  Impact: An bug in the secure boot lockdown patches in the 18.10 kernel
  causes the results of module signature verification to be ignored,
  allowing modules with no signature or an invalid signature to be
  loaded. A second bug results in the MOK not being trusted for signing
  modules, but this bug has been masked by the first bug.

  Fix: These bugs should be fixed together to avoid regressions in dkms
  module loading under secure boot. First, fix the latter bug by
  trusting keys in the kernel's secondary keyring for module signing.
  Then fix the former bug by removing code related to trusting IMA
  signatures for loading modules under kernel lockdown.

  Test Case: Confirm the following behavior under kernel lockdown:

1) Unsigned modules cannot be loaded.

2) Modules signed with an untrusted key cannot be loaded.

3) Modules signed with the kernel's ephemeral build-time key can be
  loaded.

4) Modules signed with a MOK which has been enrolled with shim can
  be loaded.

  I have tested to verify these conditions with the proposed fixes.

  Regression Potential: This restores the behavior from previous Ubuntu
  releases, so no regressions are expected wrt those releases. In some
  cases modules that were loading under lockdown might no longer load,
  but this is the intended behavior.

  ---

  On a system with Ubuntu 18.10, with secure boot enabled, and a key
  enrolled in the MOK database, I am observing the following peculiar
  behaviors:

  * Signature verification appears to be disabled, and cannot be enabled again. 
It appeared to be enabled previously, as loading of unsigned modules was 
failing, and `mokutil --enable-validation` runs without incident; however, upon 
the next boot when attempting to confirm the change, MokManager prints an error 
message "Unable to delete Secure Boot state" after completing the password 
challenge.
  * As a result of signature verification being disabled, modules signed with 
untrusted keys taint the kernel instead of failing to load outright.
  * Regardless of signature verification being enabled or not, it seems that 
the key enrolled in the MOK is not being used for validating kernel module 
signatures. Modules signed with the key still fail the signature verification 
test and taint the kernel, even though the key is visible in the output of 
`mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows 
that it's enrolled. Also, a message acknowledging the key appears in dmesg: 
Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 
90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring
  * Also, somewhat strangely, in this state with module signature verification 
not being enforced, attempting to load a completely unsigned kernel module 
suceeds, and doesn't even log a kernel message about a missing/invalid 
signature, or taint the kernel.

  Apport report attached, which includes dmesg log showing the kernel
  acknowledging the key enrolled in the MOK database, and a signature
  verification failure and subsequent successful loading of a module
  signed with that key:

   [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated 
signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys 
keyring
  ...
   [6.628452] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
  ...
   [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 238
   [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007)
   [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
   [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  410.66  Wed 
Oct 10 12:01:53 CDT 2018 (using threaded interrupts)

  This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 
18.04, signatures made with the same key are recognized as valid. Hence, I 
suspect that something changed in the Ubuntu 18.10 kernel which is causing 
signature verification to function in an unexpected way.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danix  1729 F pulseaudio
  DistroRelease: Ubuntu 18.10
  

Re: [Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Steve Langasek
On Thu, Feb 14, 2019 at 10:44:34PM -, Marek Hák wrote:
> The output of 'efibootmgr -v' showed me where the EFI partition is, but
> I have no idea where it's mounted or how to get to it.

> Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
> 84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

OK, this should be either sda2 or sdb2 depending on which order your disks
were detected.  So you should be able to do sudo mount /dev/sda2 /boot/efi
to mount it (or /dev/sdb2, depending).

Then once you have replaced that grubx64.efi with the one that allows
booting unsigned kernels, you should run 'sudo umount /boot/efi' to make
sure the disk is cleanly unmounted.  After this, you should have a
secureboot-enabled grub on the internal disk which allows you to boot to a
different unsigned kernel on the flash drive in order to reset the firmware
state.

> Thanks again for any help! I'd really love to sort this out :)

Sorry this is such a mess.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  
  If you have applied updates, and find that you can not boot the above fixed 
kernel because of Secure Boot and that the kernel is unsigned, but can still 
boot another kernel for your system; here's what you can do:

  1) Download 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed:
  $ wget 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed

  
  2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
  $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

  3) Reboot; you should now be able to load the new unsigned kernel that
  allows fixing firmware / SPI.

  4) Once you're satisfied that things work; boot to Ubuntu with a
  standard, signed kernel, and re-install the right GRUB version for
  your system:

  $ sudo grub-install

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Steve Langasek
Marek, Secure Boot is a UEFI feature.  It is not possible for you to
have Secure Boot blocking a kernel boot if you do not have UEFI.

It is possible that your EFI System Partition is not mounted at
/boot/efi, if you have modified your /etc/fstab since installation.  For
the system to boot at all under UEFI, you must have an EFI System
Partition.  For you to have a grub that refuses to boot unsigned
kernels, you must have updated the contents on that EFI System Partition
rather recently.

The output of 'efibootmgr -v' may help you locate the partition so that
you can mount it.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  
  If you have applied updates, and find that you can not boot the above fixed 
kernel because of Secure Boot and that the kernel is unsigned, but can still 
boot another kernel for your system; here's what you can do:

  1) Download 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed:
  $ wget 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed

  
  2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
  $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

  3) Reboot; you should now be able to load the new unsigned kernel that
  allows fixing firmware / SPI.

  4) Once you're satisfied that things work; boot to Ubuntu with a
  standard, signed kernel, and re-install the right GRUB version for
  your system:

  $ sudo grub-install

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in 

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-02-08 Thread Steve Langasek
This SRU claims for regression-potential:

> Low. The quirk uses strict DMI to match affected systems.

This doesn't appear to be true for the changes to upower, which include
no DMI quirking whatsoever.  Please clarify this.

** Changed in: upower (Ubuntu Bionic)
   Status: Fix Committed => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-02-08 Thread Steve Langasek
I think the test and regression potential templates on this bug are not
up to the normal SRU standard.  There are a number of firmware blobs
updated, what is the set of chips that make use of these firmware blobs
that could potentially be affected by this update?  Why is this complete
range of firmware blobs being updated, if there is a bug being reported
with only a single chip?

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: Fix Committed => Incomplete

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Incomplete

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

2019-02-07 Thread Steve Langasek
** Package changed: plymouth (Ubuntu) => linux (Ubuntu)

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

Title:
  kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

Status in linux package in Ubuntu:
  New

Bug description:
  A few days ago, I let update-manager upgrade my kernel from 4.18.0-13
  to 4.18.0-14. Since then, my system is unable to boot. It freezes
  after printing

fb: switching to inteldrmfb from VESA VGA

  but before it gets around to asking me the passphrase for my encrypted
  main partition. (At first I thought it was a problem with cryptsetup
  because it never got to that prompt, but now I'm pretty sure it's
  something to do with changing video mode.)

  However, if I use the grub menu to select the older 4.18.0-13, the
  system boots just fine. It looks very much like a bug introduced
  between 4.18.0-13 and 4.18.0-14.

  Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel
  modesetting does not happen, and the system boots just fine. (Except
  for the 1980s-style low-res video, that is.) This seems like good
  evidence that it's a problem with setting the video mode.

  I'll test with some mainline builds, but I want to get this bug report opened 
before I start rebooting.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=fb24f9f1-0e89-4ef6-a88a-fb9fc5d776c7
  InstallationDate: Installed on 2018-09-05 (155 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/lubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-14-generic N/A
   linux-backports-modules-4.18.0-14-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-14-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2019-01-23 (16 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815152/+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 1814241] Re: linux-oem: 4.15.0-1033.38 -proposed tracker

2019-02-04 Thread Steve Langasek
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-oem: 4.15.0-1033.38 -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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1813779
  phase: Release
  phase-changed: Monday, 04. February 2019 16:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+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 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2019-01-28 Thread Steve Langasek
** Changed in: grub2 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  grub or kernel update broke Secure Boot by putting grubx64.efi instead
  of shimx64.efi in EFI boot order

Status in One Hundred Papercuts:
  Confirmed
Status in grub2 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've been running Ubuntu on a Lenovo ThinkPad X240.  I initially
  installed 14.10 when I got the machine in January.  I then upgraded to
  15.04, and on Monday evening (late December 14) I upgraded to 15.10.
  I rebooted once right after the update to make sure some postfix and
  opendkim configuration changes I made worked correctly after
  rebooting.

  Then between Monday evening and Friday evening (December 19) there
  were a bunch of system updates that I installed.  On Friday evening I
  decided to reboot to boot into the updated kernel.  (There were also
  grub updates in that interval.)

  When I rebooted, the laptop said:

  Secure Boot
  Image failed to verify with *ACCESS DENIED*
  Press any key to continue.

  See the image (posted by somebody else) of this error in
  http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-
  image-failed-to-verify-with-access-denied-on-st

  I had to disable secure boot to make the system boot.

  
  Based on the discussion in 
http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-image-failed-to-verify-with-access-denied-on-st
 it appears that the problem is that the updates caused it to try to boot 
directly to grub (File(\EFI‌​\ubuntu\grubx64.efi)) rather than via the shim 
(File(\EFI‌​\ubuntu\shimx64.efi)).  I don't know for sure what sequence of 
events caused that, nor did I verify for certain that it was booting via the 
shim before.  However, I know that this reboot on Friday was the first time I 
had a secure boot failure since installing Ubuntu on the laptop (and using only 
Ubuntu; no other OSes involved) in January.

  I'll attach a list of the system updates that were applied in the
  interval between the successful boot and the failed one from
  /var/log/dpkg.log .  Note that the log is in UTC but my description
  above ("evening", etc., is in UTC-8, so the evening of December 14 is
  actually around 07:00 UTC on December 15).  Note that this log
  contains a grub update, two kernel updates, and the removal of the
  first of those kernel updates via apt-get autoremove.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grub-common 2.02~beta2-29ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 21 15:39:21 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-25 (330 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: grub2
  UpgradeStatus: Upgraded to wily on 2015-12-15 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1528345/+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


  1   2   3   4   5   6   7   8   9   10   >