date:20190903

Public bug reported:

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 --
kernel-stable-master-bug: 1842546
variant: debs

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-azure (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1842546 kernel-sru-cycle-2019.09.02-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: bionic kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in:

[Kernel-packages] [Bug 1842546] [NEW] linux-azure: -proposed tracker

Public bug reported:

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 --
variant: debs

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-azure (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.09.02-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: disco kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

[Kernel-packages] [Bug 1842542] [NEW] linux-aws: -proposed tracker

Public bug reported:

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 --
variant: debs

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.09.02-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: disco kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-updates
   Importance: Undecided => Medium

[Kernel-packages] [Bug 1842540] [NEW] linux-raspi2: -proposed tracker

Public bug reported:

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 --
variant: debs

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-raspi2 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.09.02-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: disco kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-updates
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee:

[Kernel-packages] [Bug 1842532] Re: Touchpad stops working after resuming from s2idle

2019-09-03 Thread Chih-Hsyuan Ho

** Changed in: oem-priority
 Assignee: Shih-Yuan Lee (fourdollars) => You-Sheng Yang (vicamo)

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

Title:
  Touchpad stops working after resuming from s2idle

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  When enable s2i, found touchpad doesn't work after resuming from suspend(to 
idle).

  [Reproduce Steps]
  1. Install Ubuntu image
  2. let system enter s2i state
  3. press power button to resume the system

  [Results]
  Expected: System back to work without problem
  Actual: Found touchpad doesn't work after resuming

  [Additional Information]
  Dell Inspiron 5391
  Base Image: Ubuntu 18.04.3
  BIOS Version: 1.0.1
  Kernel Version: 5.0.0-1013-oem
  CPU: i5-10210U
  GPU: Nvidia(1d13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842532/+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 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard

2019-09-03 Thread quchunguang

same issues on my custom kernel based on 5.3.0-rc7

[7.034336] usb: port power management may be unreliable
[7.037182] platform eisa.0: EISA: Cannot allocate resource for mainboard
[7.037184] platform eisa.0: Cannot allocate resource for EISA slot 1
[7.037185] platform eisa.0: Cannot allocate resource for EISA slot 2
[7.037186] platform eisa.0: Cannot allocate resource for EISA slot 3
[7.037187] platform eisa.0: Cannot allocate resource for EISA slot 4
[7.037188] platform eisa.0: Cannot allocate resource for EISA slot 5
[7.037189] platform eisa.0: Cannot allocate resource for EISA slot 6
[7.037190] platform eisa.0: Cannot allocate resource for EISA slot 7
[7.037190] platform eisa.0: Cannot allocate resource for EISA slot 8

lsb_release -rd
Description:Ubuntu 19.04
Release:19.04

uname -a
Linux kevin6 5.3.0-qcg-0904+ #7 SMP Wed Sep 4 10:20:28 CST 2019 x86_64 x86_64 
x86_64 GNU/Linux

kernel .config based on kernel 5.0.0-27 from 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/1837326

Title:
  platform eisa.0: EISA: Cannot allocate resource for mainboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard
  [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1
  [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2
  [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3
  [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4
  [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5
  [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6
  [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7
  [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3028 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   3028 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 21 12:16:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (230 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+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 1832622] Re: QEMU - count cache flush Spectre v2 mitigation (CVE) (required for POWER9 DD2.3)

** Changed in: linux (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/1832622

Title:
  QEMU -  count cache flush Spectre v2 mitigation (CVE) (required for
  POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in qemu source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in qemu source package in Disco:
  Fix Committed
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * This belongs to the overall context of spectre mitigations and even 
 more the try to minimize the related performance impacts.
 On ppc64el there is a new chip revision (DD 2.3) which provides
 a facility that helps to better mitigate some of this.

   * Backport the patches that will make the feature (if supported by the 
 HW) will pass the capability to the guest - to allow guests that 
 support the improved mitigation to use it.

  [Test Case]

   * Start guests with and without this capability
 * Check if the capability is guest visible as intented
 * Check if there are any issues on pre DD2.3 HW
   * Test migrations (IBM outlined the intented paths that will work 
 below)
   * The problem with the above (and also the reasons I didn't add a list 
 of commands this time) is that it needs special HW (mentioned DD2.3 
 revision) of the chips which aren't available to us right now.
 Due to that testing / verification of this on all releases is on IBM

  [Regression Potential]

   * Adding new capabilities usually works fine, there are three common 
 pitfalls which here are the regression potential.
 - (severe) the code would announce a capability that isn't really 
   available. The guest tries to use it and crashes
 - (medium) several migration paths especially from systems with the 
   new cap to older (un-updated systems) will fail. But that applies 
   to any "from machine with Feature to machine without that feature" 
   and isn't really a new regression. As outlined by IBM below they 
   even tried to make it somewhat compatible (by being a new value in 
   an existing cap)
 - (low) the guest will see new caps and or facilities. A really odd
   guest could stumble due to that (would actually be a guest bug 
   then)
Overall all of the above was considered by IBM when developing this 
and should be ok. For archive wide SRU considerations, this has NO 
effect on non ppc64el.

  [Other Info]
   
   * n/a

  ---

  Power9 DD 2.3  CPUs  running updated firmware will use a new Spectre
  v2 mitigation. The new mitigation improves performance of branch heavy
  workloads, but also requires kernel support in order to be fully
  secure.

  Without the kernel support there is a risk of a Spectre v2 attack
  across a process context switch, though it has not been demonstrated
  in practice.

  QEMU portion - platform definition needs to account for this new
  mitigation action.. so attribute for this needs to be added.

  In terms of support for virtualisation there are 2 sides, kvm and qemu
  support. Patch list for each,

  KVM:
  2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
  This is part of LP1822870 already.

  QEMU:
  8ff43ee404 target/ppc/spapr: Add SPAPR_CAP_CCF_ASSIST
  399b2896d4 target/ppc/spapr: Add workaround option to SPAPR_CAP_IBS

  The KVM side is upstream as of v5.1-rc1.
  The QEMU side is upstream as of v4.0.0-rc0.

  In terms of migration the state is as follows.

  In order to specify to the guest to use the count cache flush
  workaround we use the spapr-cap cap-ibs (indirect branch speculation)
  with the value workaround. Previously the only valid values were
  broken, fixed-ibs (indirect branch serialisation) and fixed-ccd (count
  cache disabled). And add a new cap cap-ccf-assist (count cache flush
  assist) to specify the availability of the hardware assisted flush
  variant.

  Note the the way spapr caps work you can migrate to a host that supports a 
higher value, but not to one which doesn't support the current value (i.e. only 
supports lower values). Where for cap-ibs these are defined as:
  0 - Broken
  1 - Workaround
  2 - fixed-ibs
  3 - fixed-ccd

  So the following migrations would be valid for example:
  broken -> fixed-ccd, broken -> workaround, workaround -> fixed-ccd

  While the following would be invalid:
  fixed-ccd -> workaround, workaround ->broken, fixed-ccd -> broken

  This is done to maintain at least the level of

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

** Changed in: linux (Ubuntu Disco)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 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 Committed

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 1838477] Re: [regression] r8169 network device unable to detect link on x86 arch

The patches for this bug were applied to Bionic and Disco via stable
updates under 2 other bugs:

Bionic:  https://bugs.launchpad.net/bugs/1840378

Disco:  https://bugs.launchpad.net/bugs/1841994

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

** Changed in: linux (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  [regression] r8169 network device unable to detect link on x86 arch

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

Bug description:
  === SRU Justification ===
  [Impact]
  r8169 network device unable to detect link after boot.

  [Fix]
  Don't use MSI for older r8169 chips.

  [Test]
  User confirmed the issue is fixed with the patch applied.

  [Regression Potential]
  Low. This reverts affected r8169 device to use INTx, which is more
  reliable on older hardware.

  === Original Bug Report ===
  Since changes were introduced with 4.15.0-24 (LP #1752772), the r8169 driver 
became unusable on x86 machines (16.04 and 18.04 distributions). The device is 
always in link down state.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic i686
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A

[Kernel-packages] [Bug 1841911] Re: Kernel hangs during msm init

@Paolo: I'm just wondering if

a) There's some testing improvement we can do to catch this kind of thing 
pre-release
and
b) why that drm driver is getting this fix via stable updates but the driver 
itself would require "backport(ing) of the new msm dri driver (and all the 
relevant dependencies)".. Shouldn't that driver already be in our bionic tree 
if it's getting this fix via stable updates? (Although I just realized as I'm 
writing this that bionic gets updates from 4.16 too so maybe that's why.  Still 
easier to just ask :)  )

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

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

Title:
  Kernel hangs during msm init

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

Bug description:
  Impact:

  Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot around msm init.
  Sometimes we get the following stack trace, or the boot completes and the 
board hangs during reboot:

  ...
  [8.113018] msm_dsi_manager_register: failed to register mipi dsi host for 
DSI 0
  [8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops 
[msm]): -517
  [8.138234] msm 1a0.mdss: master bind failed: -517
  [8.145551] platform 1a01000.mdp: Dropping the link to 1ef.iommu
  [8.150545] iommu: Removing device 1a01000.mdp from group 1
  [8.157051] [ cut here ]
  [8.162369] WARNING: CPU: 1 PID: 1316 at 
/build/linux-snapdragon-t5G9R3/linux-snapdragon-4.15.0/drivers/iommu/qcom_iommu.c:336
 qcom_iommu_domain_free
  +0x74/0x88
  [8.167166] Modules linked in: adv7511_drm cec rc_core msm(+) mdt_loader
  [8.181137] CPU: 1 PID: 1316 Comm: systemd-udevd Not tainted 
4.15.0-1061-snapdragon #68-Ubuntu
  [8.188079] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
  [8.196501] pstate: 6045 (nZCv daif +PAN -UAO)
  [8.203356] pc : qcom_iommu_domain_free+0x74/0x88
  [8.207955] lr : qcom_iommu_domain_free+0x74/0x88
  [8.212727] sp : 0cbeb680
  [8.217412] x29: 0cbeb680 x28: 8000396d84b8
  [8.220713] x27: 8000396d84b0 x26: 8000396d84c0
  [8.226096] x25: 80003d057c10 x24: 8000396d8420
  [8.231391] x23: 0003 x22: 80003ce40258
  [8.236686] x21: 8203ad00 x20: 8203af30
  [8.241981] x19: 8203af00 x18: 
  [8.247275] x17:  x16: 0004
  [8.252570] x15: 09549c08 x14: 0720072007200720
  [8.257866] x13: 0720072007200720 x12: 0720072007200720
  [8.263161] x11: 09549e80 x10: 0871d340
  [8.268456] x9 : 0720072007200720 x8 : 0005
  [8.273751] x7 : 0720072d072d072d x6 : 014c
  [8.279046] x5 : 08610250 x4 : 
  [8.284345] x3 :  x2 : a59fa8ece8469a00
  [8.289637] x1 :  x0 : 0024
  [8.294932] Call trace:
  [8.300227]  qcom_iommu_domain_free+0x74/0x88
  [8.302400]  iommu_group_release+0x54/0x90
  [8.306914]  kobject_put+0x8c/0x1f0
  [8.310905]  kobject_del.part.0+0x3c/0x50
  [8.314292]  kobject_put+0x74/0x1f0
  [8.318455]  iommu_group_remove_device+0x10c/0x198
  [8.321756]  qcom_iommu_remove_device+0x58/0x70
  [8.326617]  iommu_bus_notifier+0xa8/0x120
  [8.331045]  notifier_call_chain+0x5c/0xa0
  [8.335210]  blocking_notifier_call_chain+0x64/0x88
  [8.339294]  device_del+0x234/0x368
  [8.344066]  platform_device_del.part.3+0x2c/0x98
  [8.347539]  platform_device_unregister+0x24/0x38
  [8.352410]  of_platform_device_destroy+0xb8/0xc0
  [8.357087]  device_for_each_child+0x58/0xb0
  [8.361775]  of_platform_depopulate+0x4c/0x68
  [8.366350]  msm_pdev_probe+0x2c4/0x388 [msm]
  [8.370369]  platform_drv_probe+0x60/0xc0
  [8.374707]  driver_probe_device+0x2ec/0x458
  [8.378701]  __driver_attach+0xdc/0x128
  [8.383042]  bus_for_each_dev+0x78/0xd8
  [8.386598]  driver_attach+0x30/0x40
  [8.390418]  bus_add_driver+0x20c/0x2a8
  [8.394237]  driver_register+0x6c/0x110
  [8.397797]  __platform_driver_register+0x54/0x60
  [8.401841]  msm_drm_register+0x54/0x80 [msm]
  [8.406481]  do_one_initcall+0x58/0x160
  [8.410818]  do_init_module+0x64/0x1d8
  [8.414463]  load_module+0x1378/0x15c8
  [8.418282]  SyS_finit_module+0x100/0x118
  [8.422016]  el0_svc_naked+0x30/0x34
  [8.426095] ---[ end trace 800d0885aa276bfd ]---

  Fix:

  During the Ubuntu-snapdragon-4.15.0-1061.68 cycle, we picked up one
  upstream patch that of_platform_depopulate() msm in case of probe
  deferral (or during the removal), but that patch triggers a WARN_ON()
  during the wind down of the IOMMU (and

[Kernel-packages] [Bug 1842532] Re: Touchpad stops working after resuming from s2idle

2019-09-03 Thread Chih-Hsyuan Ho

** Tags added: originate-from-1841723

** Tags added: oem-priority

** Tags added: somerville-dla

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

Title:
  Touchpad stops working after resuming from s2idle

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  When enable s2i, found touchpad doesn't work after resuming from suspend(to 
idle).

  [Reproduce Steps]
  1. Install Ubuntu image
  2. let system enter s2i state
  3. press power button to resume the system

  [Results]
  Expected: System back to work without problem
  Actual: Found touchpad doesn't work after resuming

  [Additional Information]
  Dell Inspiron 5391
  Base Image: Ubuntu 18.04.3
  BIOS Version: 1.0.1
  Kernel Version: 5.0.0-1013-oem
  CPU: i5-10210U
  GPU: Nvidia(1d13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842532/+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 1828166] Re: perf top problem on z with Ubuntu 18.04

Note: The fixes for this problem were applied under a different bug
number via stable updates:

For Bionic:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840520

For Disco:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841994


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

** Changed in: linux (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/1828166

Title:
  perf top problem on z with Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix
  s390 gap between kernel end and module start"

  * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix
  module size on s390"

  Disco needs also as prereq:

  * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix
  s390 missing module symbol and warning for non-root users

  
  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as medium since this
  happens only while using the perf top tool

  * and just 3 files are changed, and one of them is
  arch/s390/util/machine.c

  * but symbol and machine header in /tools/perf/util modified and
  several loc added

  [Other Info]

  * cherry-pick was possible to bionic-master-next and to disco-master-
  next (but used '--strategy=recursive -X theirs' for disco)

  * adding the patches to disco is to avoid regressions
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1842532] Missing required logs.

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

apport-collect 1842532

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
  Touchpad stops working after resuming from s2idle

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  When enable s2i, found touchpad doesn't work after resuming from suspend(to 
idle).

  [Reproduce Steps]
  1. Install Ubuntu image
  2. let system enter s2i state
  3. press power button to resume the system

  [Results]
  Expected: System back to work without problem
  Actual: Found touchpad doesn't work after resuming

  [Additional Information]
  Dell Inspiron 5391
  Base Image: Ubuntu 18.04.3
  BIOS Version: 1.0.1
  Kernel Version: 5.0.0-1013-oem
  CPU: i5-10210U
  GPU: Nvidia(1d13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842532/+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 1836396] Re: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

2019-09-03 Thread Daniel van Vugt

** Tags added: disco

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

Title:
  Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 19.04 on a Dell Inspiron Laptop that has Bluetooth
  enabled (visible, discoverable). Just bought a Tracfone MyFlip which
  uses KaiOS. Ideally, I should be able to transfer files back & forth.
  In fact, if a "send" a file from laptop to phone, I have no issues and
  the file appears. Means Bluetooth is more or less working ... devices
  are paired and some functionality.

  But if I try to send a file from phone to laptop - that does not work.
  There are messages on my phone, first: "File Transfer is Ready to
  Start". Then about 2 seconds latter: "File Transfer Fail." FYI: on
  KaiOS, via Files App... "Share" via "Bluetooth" and comes up with a
  list of paired devices, where my laptop is identified correctly.

  With laptop-->phone, phone bluetooth app displays messages and asks if OK to 
receive file.
  With phone-->laptop, no messages, nothing happens.

  Been knocking my head on this for two days now without resolution, so
  reaching out to community for help. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836396/+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 1842532] [NEW] Touchpad stops working after resuming from s2idle

2019-09-03 Thread Chih-Hsyuan Ho

Public bug reported:

[Summary]
When enable s2i, found touchpad doesn't work after resuming from suspend(to 
idle).

[Reproduce Steps]
1. Install Ubuntu image
2. let system enter s2i state
3. press power button to resume the system

[Results]
Expected: System back to work without problem
Actual: Found touchpad doesn't work after resuming

[Additional Information]
Dell Inspiron 5391
Base Image: Ubuntu 18.04.3
BIOS Version: 1.0.1
Kernel Version: 5.0.0-1013-oem
CPU: i5-10210U
GPU: Nvidia(1d13)

** Affects: oem-priority
 Importance: High
 Assignee: Shih-Yuan Lee (fourdollars)
 Status: New

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

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  Touchpad stops working after resuming from s2idle

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  When enable s2i, found touchpad doesn't work after resuming from suspend(to 
idle).

  [Reproduce Steps]
  1. Install Ubuntu image
  2. let system enter s2i state
  3. press power button to resume the system

  [Results]
  Expected: System back to work without problem
  Actual: Found touchpad doesn't work after resuming

  [Additional Information]
  Dell Inspiron 5391
  Base Image: Ubuntu 18.04.3
  BIOS Version: 1.0.1
  Kernel Version: 5.0.0-1013-oem
  CPU: i5-10210U
  GPU: Nvidia(1d13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842532/+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

Re: [Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend

2019-09-03 Thread Meir Levi

Thanks

> On 2 Sep 2019, at 22:10, Kai-Heng Feng  wrote:
> 
> Please use this test kernel for the interim:
> https://people.canonical.com/~khfeng/lp1833617/
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1833617
> 
> Title:
>  [amdgpu] screen freeze after suspend
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in linux source package in Disco:
>  New
> Status in xserver-xorg-video-amdgpu source package in Disco:
>  New
> Status in linux source package in Eoan:
>  Confirmed
> Status in xserver-xorg-video-amdgpu source package in Eoan:
>  Invalid
> 
> Bug description:
>  === SRU Justification ===
>  [Impact]
>  Screen freeze after S3 on AMD Stoney Ridge.
> 
>  [Fix]
>  Pin the VRAM so it won't contain garbage data after S3.
> 
>  [Test]
>  After applying this patch I can confirm the issue is gone on Dell
>  Inspiron 3180, a Stoney Ridge laptop.
> 
>  [Regression Potential]
>  Low. This patch only touched a small subset of amdgpu.
> 
>  === Original Bug Report ===
>  It's most likely amdgup driver needs an upgrade. Problem occurs since kernel 
> upgrade to 5.0
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: xorg 1:7.7+19ubuntu12
>  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
>  Uname: Linux 5.0.0-18-generic x86_64
>  ApportVersion: 2.20.10-0ubuntu27
>  Architecture: amd64
>  CompositorRunning: None
>  Date: Thu Jun 20 13:46:46 2019
>  DistUpgraded: Fresh install
>  DistroCodename: disco
>  DistroVariant: ubuntu
>  ExtraDebuggingInterest: Yes, if not too technical
>  GraphicsCard:
>   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
> [1002:98e4] (rev eb) (prog-if 00 [VGA controller])
> Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
>  InstallationDate: Installed on 2019-06-06 (14 days ago)
>  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>  MachineType: Dell Inc. Inspiron 3180
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
> root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
>  SourcePackage: xorg
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 03/09/2018
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: 1.3.0
>  dmi.board.name: 0918N8
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Dell Inc.
>  dmi.chassis.version: 1.3.0
>  dmi.modalias: 
> dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
>  dmi.product.family: Inspiron
>  dmi.product.name: Inspiron 3180
>  dmi.product.sku: 087E
>  dmi.product.version: 1.3.0
>  dmi.sys.vendor: Dell Inc.
>  version.compiz: compiz N/A
>  version.libdrm2: libdrm2 2.4.97-1ubuntu1
>  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
>  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
>  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions

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

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  New
Status in xserver-xorg-video-amdgpu source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Eoan:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Screen freeze after S3 on AMD Stoney Ridge.

  [Fix]
  Pin the VRAM so it won't contain garbage data after S3.

  [Test]
  After applying this patch I can confirm the issue is gone on Dell
  Inspiron 3180, a Stoney Ridge laptop.

  [Regression Potential]
  Low. This patch only touched a small subset of amdgpu.

  === Original Bug Report ===
  It's most likely amdgup driver needs an upgrade. Problem occurs since kernel 
upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
     Subsystem: Dell

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

2019-09-03 Thread Bug Watch Updater

** Changed in: linux
   Importance: Unknown => Critical

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2019-09-03 Thread Lakshminarayana-vudum

(In reply to Jani Saarinen from comment #5)
> ICL issue tracked on fdo 103167 and WIP there.

Accordingly, all the above details are set.

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840236/+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 1841132] Re: mpt3sas - storage controller resets under heavy disk io

2019-09-03 Thread Drew Woodard

Are there any plans to include this fix in the hwe kernel?
I tested today on the current 18.04 hwe kernel 5.0.0-27 and the bug appeared in 
18min.

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

Title:
  mpt3sas - storage controller resets under heavy disk io

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [summary]
  when a server running ubuntu 18.04 with an lsi sas controller experiences 
high disk io there is a chance the storage controller will reset
  this can take weeks or months, but once the controller resets it will keep 
resetting every few seconds or few minutes, dramatically degrading disk io
  the server must be rebooted to restore the controller to a normal state

  [hardware configuration]
  server: dell poweredge r7415, purchased 2019-02
  cpu/chipset: amd epyc naples
  storage controller: "dell hba330 mini" with chipset "lsi sas3008"
  drives: 4x samsung 860 pro 2TB ssd

  [software configuration]
  ubuntu 18.04 server
  mdadm raid6
  all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q)

  [what happened]
  server was operating as a vm host for months without issue
  one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag 
reset !!" and "Power-on or device reset occurred", along with unusably-slow 
disk io
  the server was removed from production and I looked for a way to reproduce 
the issue

  [how to reproduce the issue]
  there are probably many ways to product this issue, the hackish way I found 
to reliably reproduce it was:
  have the four ssds in a mdadm raid6 with ext4 filesystem
  create three 500GB files containing random data
  open three terminals. one calculates md5sum of file1 in a loop, another does 
the same for file2, the third does a copy of file3 to file3-temp in a loop
  the number of files is arbitrary, the goal is just to generate a lot of disk 
io on files too large to be cached in memory
  then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause 
even more drive thrashing
  within 1-15min the controller will enter the broken state. the longest I ever 
saw it take was 30min. I reproduced this several times
  rebooting the server restores the controller to a normal state
  if the server is not rebooted and the controller is left in this broken state 
eventually drives will fall out of the array, and sometimes array/filesystem 
corruption will occur

  [why this is being reported here]
  It's unlikely I am exceeding limits of the hardware since this server chassis 
can hold 24 drives and I am only using 4. The controller specs indicate I 
should not hit pcie bandwidth limits until at least 16 drives.
  My first thought was that the lsi controller firmware was at fault since they 
have been historically buggy, however I reproduced this with the newest 
firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be 
dell-specific).
  I then tried the most recent motherboard bios "1.9.3", and downgraded to 
"1.9.2", no change.
  I then wanted to eliminate the possibility of a bad drive. swapped out all 4 
drives with different ones of the same model, no change.
  I then upgraded from the standard 18.04 kernel to the newer backported hwe 
kernel, which also came with a newer mpt3sas driver, no change.
  I then ran the same test on the same array but with rhel 8, to my surprise I 
could no longer reproduce the issue.
  -
  tl;dr version:
  ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller 
breaks in 1-10min
  ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage 
controller breaks in 1-15min, max 30min
  rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same 
array for 19h, no errors

  [caveats]
  Server os misconfiguration is possible, however this is a rather basic vm 
host running kvm and no 3rd-party packages.
  I can't conclusively prove this isn't a hardware fault since I don't have a 
second unused identical server to test on right now, however the fact that the 
problem can be easily reproduced under ubuntu but not under rhel seems 
noteworthy.
  There is another bug (LP: #1810781) similar to this, I didn't post there 
because it's already marked as fixed.
  There is also a debian bug (Debian #926202) that encountered this on kernel 
4.19.0, but I'm unable to tell if it's the same issue.

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

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

[Kernel-packages] [Bug 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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 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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1832622] qemu-dd2.3-sanity.txt

--- Comment (attachment only) From faro...@br.ibm.com 2019-09-03 19:44 
EDT---


** Attachment added: "qemu-dd2.3-sanity.txt"
   
https://bugs.launchpad.net/bugs/1832622/+attachment/5286595/+files/qemu-dd2.3-sanity.txt

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

Title:
  QEMU -  count cache flush Spectre v2 mitigation (CVE) (required for
  POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in qemu source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in qemu source package in Disco:
  Fix Committed
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * This belongs to the overall context of spectre mitigations and even 
 more the try to minimize the related performance impacts.
 On ppc64el there is a new chip revision (DD 2.3) which provides
 a facility that helps to better mitigate some of this.

   * Backport the patches that will make the feature (if supported by the 
 HW) will pass the capability to the guest - to allow guests that 
 support the improved mitigation to use it.

  [Test Case]

   * Start guests with and without this capability
 * Check if the capability is guest visible as intented
 * Check if there are any issues on pre DD2.3 HW
   * Test migrations (IBM outlined the intented paths that will work 
 below)
   * The problem with the above (and also the reasons I didn't add a list 
 of commands this time) is that it needs special HW (mentioned DD2.3 
 revision) of the chips which aren't available to us right now.
 Due to that testing / verification of this on all releases is on IBM

  [Regression Potential]

   * Adding new capabilities usually works fine, there are three common 
 pitfalls which here are the regression potential.
 - (severe) the code would announce a capability that isn't really 
   available. The guest tries to use it and crashes
 - (medium) several migration paths especially from systems with the 
   new cap to older (un-updated systems) will fail. But that applies 
   to any "from machine with Feature to machine without that feature" 
   and isn't really a new regression. As outlined by IBM below they 
   even tried to make it somewhat compatible (by being a new value in 
   an existing cap)
 - (low) the guest will see new caps and or facilities. A really odd
   guest could stumble due to that (would actually be a guest bug 
   then)
Overall all of the above was considered by IBM when developing this 
and should be ok. For archive wide SRU considerations, this has NO 
effect on non ppc64el.

  [Other Info]
   
   * n/a

  ---

  Power9 DD 2.3  CPUs  running updated firmware will use a new Spectre
  v2 mitigation. The new mitigation improves performance of branch heavy
  workloads, but also requires kernel support in order to be fully
  secure.

  Without the kernel support there is a risk of a Spectre v2 attack
  across a process context switch, though it has not been demonstrated
  in practice.

  QEMU portion - platform definition needs to account for this new
  mitigation action.. so attribute for this needs to be added.

  In terms of support for virtualisation there are 2 sides, kvm and qemu
  support. Patch list for each,

  KVM:
  2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
  This is part of LP1822870 already.

  QEMU:
  8ff43ee404 target/ppc/spapr: Add SPAPR_CAP_CCF_ASSIST
  399b2896d4 target/ppc/spapr: Add workaround option to SPAPR_CAP_IBS

  The KVM side is upstream as of v5.1-rc1.
  The QEMU side is upstream as of v4.0.0-rc0.

  In terms of migration the state is as follows.

  In order to specify to the guest to use the count cache flush
  workaround we use the spapr-cap cap-ibs (indirect branch speculation)
  with the value workaround. Previously the only valid values were
  broken, fixed-ibs (indirect branch serialisation) and fixed-ccd (count
  cache disabled). And add a new cap cap-ccf-assist (count cache flush
  assist) to specify the availability of the hardware assisted flush
  variant.

  Note the the way spapr caps work you can migrate to a host that supports a 
higher value, but not to one which doesn't support the current value (i.e. only 
supports lower values). Where for cap-ibs these are defined as:
  0 - Broken
  1 - Workaround
  2 - fixed-ibs
  3 - fixed-ccd

  So the following migrations would be valid for example:
  broken -> fixed-ccd, broken -> workaround, workaround -> fixed-ccd

  While the

[Kernel-packages] [Bug 1832622] Comment bridged from LTC Bugzilla

--- Comment From faro...@br.ibm.com 2019-09-03 19:45 EDT---
I ran the tests mentioned in launchpad comment #40 on a DD2.3 witherspoon 
machine with GA firmware. Aside from the issue caused by the missing kernel 
patch, QEMU behaved as expected.

One thing of note is that the following firmware features are disabled:

ibm,opal/fw-features/fw-bcctrl-serialized
ibm,opal/fw-features/fw-count-cache-disabled

which means that 'cap-ibs=fixed-ibs' and 'cap-ibs=fixed-ccd' are always
refused by KVM in this machine.

I attached the test results as qemu-dd2.3-sanity.txt

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

Title:
  QEMU -  count cache flush Spectre v2 mitigation (CVE) (required for
  POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in qemu source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in qemu source package in Disco:
  Fix Committed
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * This belongs to the overall context of spectre mitigations and even 
 more the try to minimize the related performance impacts.
 On ppc64el there is a new chip revision (DD 2.3) which provides
 a facility that helps to better mitigate some of this.

   * Backport the patches that will make the feature (if supported by the 
 HW) will pass the capability to the guest - to allow guests that 
 support the improved mitigation to use it.

  [Test Case]

   * Start guests with and without this capability
 * Check if the capability is guest visible as intented
 * Check if there are any issues on pre DD2.3 HW
   * Test migrations (IBM outlined the intented paths that will work 
 below)
   * The problem with the above (and also the reasons I didn't add a list 
 of commands this time) is that it needs special HW (mentioned DD2.3 
 revision) of the chips which aren't available to us right now.
 Due to that testing / verification of this on all releases is on IBM

  [Regression Potential]

   * Adding new capabilities usually works fine, there are three common 
 pitfalls which here are the regression potential.
 - (severe) the code would announce a capability that isn't really 
   available. The guest tries to use it and crashes
 - (medium) several migration paths especially from systems with the 
   new cap to older (un-updated systems) will fail. But that applies 
   to any "from machine with Feature to machine without that feature" 
   and isn't really a new regression. As outlined by IBM below they 
   even tried to make it somewhat compatible (by being a new value in 
   an existing cap)
 - (low) the guest will see new caps and or facilities. A really odd
   guest could stumble due to that (would actually be a guest bug 
   then)
Overall all of the above was considered by IBM when developing this 
and should be ok. For archive wide SRU considerations, this has NO 
effect on non ppc64el.

  [Other Info]
   
   * n/a

  ---

  Power9 DD 2.3  CPUs  running updated firmware will use a new Spectre
  v2 mitigation. The new mitigation improves performance of branch heavy
  workloads, but also requires kernel support in order to be fully
  secure.

  Without the kernel support there is a risk of a Spectre v2 attack
  across a process context switch, though it has not been demonstrated
  in practice.

  QEMU portion - platform definition needs to account for this new
  mitigation action.. so attribute for this needs to be added.

  In terms of support for virtualisation there are 2 sides, kvm and qemu
  support. Patch list for each,

  KVM:
  2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
  This is part of LP1822870 already.

  QEMU:
  8ff43ee404 target/ppc/spapr: Add SPAPR_CAP_CCF_ASSIST
  399b2896d4 target/ppc/spapr: Add workaround option to SPAPR_CAP_IBS

  The KVM side is upstream as of v5.1-rc1.
  The QEMU side is upstream as of v4.0.0-rc0.

  In terms of migration the state is as follows.

  In order to specify to the guest to use the count cache flush
  workaround we use the spapr-cap cap-ibs (indirect branch speculation)
  with the value workaround. Previously the only valid values were
  broken, fixed-ibs (indirect branch serialisation) and fixed-ccd (count
  cache disabled). And add a new cap cap-ccf-assist (count cache flush
  assist) to specify the availability of the hardware assisted flush
  variant.

  Note the the way spapr caps work you can migrate to a host that supports a

[Kernel-packages] [Bug 1836396] Re: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

2019-09-03 Thread Tony Espy

snappy-hwe-snaps is a project used to track work related to system stack
snaps published by Canonical. Your bug most likely has to do with the
bluez (or related) Debian package from the Ubuntu archive.

** Project changed: snappy-hwe-snaps => bluez

** Project changed: bluez => bluez (Ubuntu)

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

Title:
  Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 19.04 on a Dell Inspiron Laptop that has Bluetooth
  enabled (visible, discoverable). Just bought a Tracfone MyFlip which
  uses KaiOS. Ideally, I should be able to transfer files back & forth.
  In fact, if a "send" a file from laptop to phone, I have no issues and
  the file appears. Means Bluetooth is more or less working ... devices
  are paired and some functionality.

  But if I try to send a file from phone to laptop - that does not work.
  There are messages on my phone, first: "File Transfer is Ready to
  Start". Then about 2 seconds latter: "File Transfer Fail." FYI: on
  KaiOS, via Files App... "Share" via "Bluetooth" and comes up with a
  list of paired devices, where my laptop is identified correctly.

  With laptop-->phone, phone bluetooth app displays messages and asks if OK to 
receive file.
  With phone-->laptop, no messages, nothing happens.

  Been knocking my head on this for two days now without resolution, so
  reaching out to community for help. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836396/+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 1836396] [NEW] Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

2019-09-03 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I'm using Ubuntu 19.04 on a Dell Inspiron Laptop that has Bluetooth
enabled (visible, discoverable). Just bought a Tracfone MyFlip which
uses KaiOS. Ideally, I should be able to transfer files back & forth. In
fact, if a "send" a file from laptop to phone, I have no issues and the
file appears. Means Bluetooth is more or less working ... devices are
paired and some functionality.

But if I try to send a file from phone to laptop - that does not work.
There are messages on my phone, first: "File Transfer is Ready to
Start". Then about 2 seconds latter: "File Transfer Fail." FYI: on
KaiOS, via Files App... "Share" via "Bluetooth" and comes up with a list
of paired devices, where my laptop is identified correctly.

With laptop-->phone, phone bluetooth app displays messages and asks if OK to 
receive file.
With phone-->laptop, no messages, nothing happens.

Been knocking my head on this for two days now without resolution, so
reaching out to community for help. Thanks in advance.

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

-- 
Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues 
https://bugs.launchpad.net/bugs/1836396
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

-- 
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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Description changed:

  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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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 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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 03. September 2019 21:38 UTC
+ phase: Promote to Proposed
+ phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  In Progress
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842459] Re: apparmor abi-feature pinning not working with Disco and Eoan kernels

2019-09-03 Thread John Johansen

Can you please attach the features file you are setting in
/etc/apparmor/apparmor.conf

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

Title:
  apparmor abi-feature pinning not working with Disco and Eoan kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When setting a features-file in /etc/apparmor/apparmor.conf (and using 
policies for this feature-set) certain operations are DENIED, although they 
should be allowed.
  This occurs for example when running an Ubuntu kernel with Debian Buster 
apparmor.

  Steps for reproducing:
  * Starting from a minimal Buster VM (apparmor 2.13.2-10)
  * Install unbound (one example) - apparmor confinement works as expected
  * Install a kernel from Ubuntu (tested with: 5.0.0-25.26 from disco and 
5.2.0-15.16 from eoan)
  * Reboot - unbound fails to start - the following messages are in `dmesg`:

  ```
  [3.109740] audit: type=1400 audit(1567527034.644:9): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [3.113969] audit: type=1400 audit(1567527034.652:10): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.322119] audit: type=1400 audit(1567527036.856:21): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.324621] audit: type=1400 audit(1567527036.860:22): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.326335] audit: type=1400 audit(1567527036.860:23): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="inet6" sock_type="dgram" protocol=0 requested_mask="create" 
denied_mask="create"
  ```

  The problem does not occur when:
  * booting the corresponding mainline kernels (5.0.18 and 5.29)
  * booting debian kernels (5.2.9-2 from testing+sid and 4.19.0-5-amd64 from 
buster)
  * the features-file is changed to reflect the features present in Ubuntu 
kernels
  * the features-file option is removed (commented out) in 
/etc/apparmor/apparmor.conf

  Opening the bug against linux and not apparmor, because it looks to me like 
the issue might be in
  the Ubuntu patches.

  Glad to provide further information and help testing!

  Thanks for all your great work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842459/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  In Progress
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker

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

** This bug has been marked a duplicate of bug 1842418
   bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

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

Title:
  bionic/linux-oem: 4.15.0-1051.60 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Monday, 19. August 2019 09:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 03. September 2019 13:21 UTC
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 03. September 2019 21:38 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  In Progress
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:50 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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-09-03 Thread Lei Zhao

Can confirm that after the latest BIOS update from ASUS, I'm also able
to boot OK into Ubuntu without the dis_ucode_ldr option.

-- 
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 i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  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

  WORKAROUND 3: upgrade BIOS
  Asus has released updated BIOSes, which probably include the newest 
microcode. After upgrading workarounds 1,2 are not needed. 
  Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be 
(easily) reverted. 

  ---
  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] [Bug 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+ replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  Confirmed
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:38 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  Confirmed
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 21:38 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+ replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+ replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+ replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

2019-09-03 Thread Seiichi Nakashima

at my Intel i3-7100 using CMS PC
I restore ubuntu 18.04.2 to /dev/sda2 that has pbr boot-loader.
I boot-up PC, and update to use software updater.
then partial update need to update message pop-up-window, and run.

my pc boot sequence is 
1. mbm039 from mbr, select boot partition
2. selected partition(/dev/sda2) run grub, display grub menu, select ubuntu top 
of one
but purple screen blink occur.

next one my pc boot sequence is
1. mbm039 from mbr, select boot partition
2. selected partition(/dev/sda2) run grub, display grub menu,
   select advanced options for ubuntu, and select ubuntu, with Linux 
5.0.0-27-generic
then normally boot up PC

I checked two boot sequence 2 or 3 times, same result.

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

Title:
  ubuntu 18.04.3 startup purple screen blink and could not start with
  kernel 5.0.0+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-05-31 (83 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (86 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1355 F pulseaudio
   /dev/snd/controlC1:  nakasima   1355 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (93 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=1c4b1b7d-1ae2-412e-ac5e-dca7d317b129 ro ipv6.disable=1 quiet splash 
ipv6.disable=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A

[Kernel-packages] [Bug 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1841086
  packages:
-   lrm: linux-restricted-modules-oem
-   main: linux-oem
-   meta: linux-meta-oem
-   signed: linux-signed-oem
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
+ replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
- replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842502] Missing required logs.

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

apport-collect 1842502

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
  TC filters are broken on Mellanox after upstream stable updates

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress

Bug description:
  The following upstream fix was missing from the latest upstream stable
  update (LP: # and LP1839376: #1839213):

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842502/+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 1842502] Re: TC filters are broken on Mellanox after upstream stable updates

2019-09-03 Thread Marcelo Cerri

** Summary changed:

- TC filters are broken on Mellanox with kernels -1030 and greater
+ TC filters are broken on Mellanox after upstream stable updates

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

** Description changed:

- Upstream fix:
+ The following upstream fix was missing from the latest upstream stable
+ update (LP: # and LP1839376: #1839213):
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3a80bb5a3eac311ddf28387402593977574460d

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

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

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

Title:
  TC filters are broken on Mellanox after upstream stable updates

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  The following upstream fix was missing from the latest upstream stable
  update (LP: # and LP1839376: #1839213):

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842502/+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 1842502] [NEW] TC filters are broken on Mellanox after upstream stable updates

2019-09-03 Thread Chris Johnston

Public bug reported:

The following upstream fix was missing from the latest upstream stable
update (LP: # and LP1839376: #1839213):

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

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

Title:
  TC filters are broken on Mellanox after upstream stable updates

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  The following upstream fix was missing from the latest upstream stable
  update (LP: # and LP1839376: #1839213):

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842502/+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 1836153] Re: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part

2019-09-03 Thread Dimitri John Ledkov

Please ignore the xenial verification request, as it was generated in
error. I can confirm this issue is resolved in bionic and up and calls
for no further actions. I apologise for any inconvenience caused.

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

Title:
  [18.04 FEAT] zKVM: Add hardware CPU Model - 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 Disco:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * New hardware is not supported by qemu and won't run run, due to
  missing hardware CPU model

  [Fix]

  * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add
  debug logging for cpu model subfunctions"

  * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390:
  implement subfunction processor calls"

  * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add
  vector enhancements facility 2 to cpumodel"

  * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add
  vector BCD enhancements facility to cpumodel"

  * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add
  MSA9 to cpumodel"

  * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide
  query function for instructions returning 32 byte"

  * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add
  enhanced sort facilty to cpu model"

  * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add
  deflate conversion facilty to cpu model"

  * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable
  MSA9 keywrapping functions depending on cpu model"

  [Test Case]

  * need to be tested by IBM on pre-rel. hardware or simulator

  [Regression Potential]

  * The regression potential can be considered as low since these
  changes are limited to arch/s390

  * changes are in support for new and upcoming hardware and shouldn't
  affect existing s390x systems

  [Other Info]

  * the first 2 commits are the key ones, the other 7 are needed to make
  them applly cleanly

  * these patches are already all included in upstream kernel 5.2, hence
  they are in eoan's kernel 5.2

  * qemu package SRU in LP 1836154 complements this SRU - for testing
  both need to be in place

  * I could apply the commit IDs cleanly with 'cherry-picks 
--strategy=recursive -X theirs' and checked that no patches on top were pulled 
in
  _

  Feature request to be applied to  Ubuntu 18.04 - kernel.

  The git commit information is already provided within
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239

  Once this feature is accepted all information for integration will be 
provided by IBM
  kernel 5.2 down to 4.15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836153/+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 1836153] Comment bridged from LTC Bugzilla

--- Comment From cborn...@de.ibm.com 2019-09-03 14:58 EDT---
This still has the verification-needed-xenial tag. Will this be backported or 
can we remove that tag? xenial-proposed does not seem to contain a kernel 
update and a backport to xenial was not requested. (It would be possible 
though).

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

Title:
  [18.04 FEAT] zKVM: Add hardware CPU Model - 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 Disco:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * New hardware is not supported by qemu and won't run run, due to
  missing hardware CPU model

  [Fix]

  * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add
  debug logging for cpu model subfunctions"

  * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390:
  implement subfunction processor calls"

  * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add
  vector enhancements facility 2 to cpumodel"

  * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add
  vector BCD enhancements facility to cpumodel"

  * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add
  MSA9 to cpumodel"

  * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide
  query function for instructions returning 32 byte"

  * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add
  enhanced sort facilty to cpu model"

  * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add
  deflate conversion facilty to cpu model"

  * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable
  MSA9 keywrapping functions depending on cpu model"

  [Test Case]

  * need to be tested by IBM on pre-rel. hardware or simulator

  [Regression Potential]

  * The regression potential can be considered as low since these
  changes are limited to arch/s390

  * changes are in support for new and upcoming hardware and shouldn't
  affect existing s390x systems

  [Other Info]

  * the first 2 commits are the key ones, the other 7 are needed to make
  them applly cleanly

  * these patches are already all included in upstream kernel 5.2, hence
  they are in eoan's kernel 5.2

  * qemu package SRU in LP 1836154 complements this SRU - for testing
  both need to be in place

  * I could apply the commit IDs cleanly with 'cherry-picks 
--strategy=recursive -X theirs' and checked that no patches on top were pulled 
in
  _

  Feature request to be applied to  Ubuntu 18.04 - kernel.

  The git commit information is already provided within
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239

  Once this feature is accepted all information for integration will be 
provided by IBM
  kernel 5.2 down to 4.15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836153/+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 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

2019-09-03 Thread Mario Limonciello

Alternatively this commit I suspect should help:

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=1ffdb51f28e8ec6be0a2b812c1765b5cf5c44a8f

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM:

[Kernel-packages] [Bug 1840335] Re: Xenial update: 4.4.189 upstream stable release

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

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

Title:
  Xenial update: 4.4.189 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  
  * arm64: cpufeature: Fix CTR_EL0 field definitions
  * arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG}
  * netfilter: nfnetlink_acct: validate NFACCT_QUOTA parameter
  * HID: Add quirk for HP X1200 PIXART OEM mouse
  * tcp: be more careful in tcp_fragment()
  * atm: iphase: Fix Spectre v1 vulnerability
  * net: bridge: delete local fdb on device init failure
  * net: fix ifindex collision during namespace removal
  * tipc: compat: allow tipc commands without arguments
  * net: sched: Fix a possible null-pointer dereference in dequeue_func()
  * net/mlx5: Use reversed order when unregister devices
  * bnx2x: Disable multi-cos feature.
  * compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
  * spi: bcm2835: Fix 3-wire mode if DMA is enabled
  * x86: cpufeatures: Sort feature word 7
  * x86/entry/64: Fix context tracking state warning when load_gs_index fails
  * Linux 4.4.189

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840335/+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 1842475] Missing required logs.

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

apport-collect 1842475

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

** Tags added: eoan

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

Title:
  [IOMMU]enable default domain

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Enable Default Domain

  
  fa954e683178949e3c50a7d40c176e7b951bb22d - v5.3-rc1

  Target Release: 19.10
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842475/+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 1842479] Re: timer_create will fail with invalid error code

https://lore.kernel.org/lkml/20190903171802.28314-1-casca...@canonical.com/T/#u

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

Title:
  timer_create will fail with invalid error code

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

Bug description:
  [Impact]
  On some OpenPower systems, RTC does not support set_alarm, and 
timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of 
EOPNOTSUPP. This will break some regression testing that expects the later 
value.

  [Test cases]
  Run LTP syscalls regression testing, which we do before releasing kernels.

  [Regression potential]
  This should not break any userspace, as none should be using/expecting 
ENOTSUPP for any call. In order to do so, they would have to go out of their 
way as it's not defined on libc headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+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 1841483] Re: Additional regression in CMA allocation rework

** Changed in: linux (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/1841483

Title:
  Additional regression in CMA allocation rework

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

Bug description:
  Introduced by the fixes for bug 1823753. Also related - bug 1839395.

  [Impact]
  There is an upstream report that the CMA allocation rework we backported to 
disco is breaking the ath10k wireless driver - and possibly other drivers - in 
certain configs. It is not clear if Ubuntu users have been impacted by this 
regression, I just noticed that it has a Fixes: reference in the git commit.

  [Test Case]
  Regression tested only.

  [Fix]
  90ae409f9eb3b dma-direct: fix zone selection after an unaddressable CMA 
allocation

  [Regression Risk]
  Regressions in this code generally cause drivers to fail due to unavailable 
memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841483/+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 1842418] Re: bionic/linux-oem: 4.15.0-1052.61 -proposed tracker

** Description changed:

  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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
+   promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  replaces: bug 1839980
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1052.61 -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-lrm 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:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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: 1841086
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 03. September 2019 13:21 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  replaces: bug 1839980
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842418/+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 1842479] [NEW] timer_create will fail with invalid error code

Public bug reported:

[Impact]
On some OpenPower systems, RTC does not support set_alarm, and 
timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of 
EOPNOTSUPP. This will break some regression testing that expects the later 
value.

[Test cases]
Run LTP syscalls regression testing, which we do before releasing kernels.

[Regression potential]
This should not break any userspace, as none should be using/expecting ENOTSUPP 
for any call. In order to do so, they would have to go out of their way as it's 
not defined on libc headers.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Triaged

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Triaged

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Triaged

** Affects: linux (Ubuntu Eoan)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1842479

Title:
  timer_create will fail with invalid error code

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

Bug description:
  [Impact]
  On some OpenPower systems, RTC does not support set_alarm, and 
timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of 
EOPNOTSUPP. This will break some regression testing that expects the later 
value.

  [Test cases]
  Run LTP syscalls regression testing, which we do before releasing kernels.

  [Regression potential]
  This should not break any userspace, as none should be using/expecting 
ENOTSUPP for any call. In order to do so, they would have to go out of their 
way as it's not defined on libc headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+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 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources

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

** Changed in: linux (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses
  shared power resources

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  When system goes to suspend-to idle, it's power consumption is around 4+ w.

  [Fix]
  Some TBT and other ACPI devices share the same power resource, when system 
goes to s2idle.
  PME polling thread continue bringing up devices to D0 mode.
  Use cached ACPI device power state will avoid this issue.

  [Test]
  Verified on 2 hardware. Tests result are good.

  [Regression Potential]
  Medium, upstream patches cherry-picked.

  Since these hareware is only supported by 5.0+ kernel, I set B-OEM-
  OSP1 and disco+ kernel tag.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840882/+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 1842473] [NEW] sched_getattr will return EFBIG

Public bug reported:

With the introduction of utilization clamps interface on
sched_[sg]etattr, sched_getattr will fail when used with the previous
smaller struct sched_attr. And instead of using E2BIG as documented, it
also ends up using EFBIG instead.

The interface change currently breaks userspace on 5.3 kernel.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Eoan)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  sched_getattr will return EFBIG

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  With the introduction of utilization clamps interface on
  sched_[sg]etattr, sched_getattr will fail when used with the previous
  smaller struct sched_attr. And instead of using E2BIG as documented,
  it also ends up using EFBIG instead.

  The interface change currently breaks userspace on 5.3 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842473/+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 1842459] Missing required logs.

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

apport-collect 1842459

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

** Tags added: disco

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

Title:
  apparmor abi-feature pinning not working with Disco and Eoan kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When setting a features-file in /etc/apparmor/apparmor.conf (and using 
policies for this feature-set) certain operations are DENIED, although they 
should be allowed.
  This occurs for example when running an Ubuntu kernel with Debian Buster 
apparmor.

  Steps for reproducing:
  * Starting from a minimal Buster VM (apparmor 2.13.2-10)
  * Install unbound (one example) - apparmor confinement works as expected
  * Install a kernel from Ubuntu (tested with: 5.0.0-25.26 from disco and 
5.2.0-15.16 from eoan)
  * Reboot - unbound fails to start - the following messages are in `dmesg`:

  ```
  [3.109740] audit: type=1400 audit(1567527034.644:9): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [3.113969] audit: type=1400 audit(1567527034.652:10): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.322119] audit: type=1400 audit(1567527036.856:21): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.324621] audit: type=1400 audit(1567527036.860:22): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.326335] audit: type=1400 audit(1567527036.860:23): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="inet6" sock_type="dgram" protocol=0 requested_mask="create" 
denied_mask="create"
  ```

  The problem does not occur when:
  * booting the corresponding mainline kernels (5.0.18 and 5.29)
  * booting debian kernels (5.2.9-2 from testing+sid and 4.19.0-5-amd64 from 
buster)
  * the features-file is changed to reflect the features present in Ubuntu 
kernels
  * the features-file option is removed (commented out) in 
/etc/apparmor/apparmor.conf

  Opening the bug against linux and not apparmor, because it looks to me like 
the issue might be in
  the Ubuntu patches.

  Glad to provide further information and help testing!

  Thanks for all your great work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842459/+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 1842475] [NEW] [IOMMU]enable default domain

2019-09-03 Thread quanxian

Public bug reported:

Description
Enable Default Domain


fa954e683178949e3c50a7d40c176e7b951bb22d - v5.3-rc1

Target Release: 19.10
Target Kernel: 5.3

** Affects: intel
 Importance: Undecided
 Status: Fix Committed

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


** Tags: intel-kernel-19.10

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

** Changed in: intel
   Status: New => Fix Committed

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

Title:
  [IOMMU]enable default domain

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Enable Default Domain

  
  fa954e683178949e3c50a7d40c176e7b951bb22d - v5.3-rc1

  Target Release: 19.10
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842475/+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 1842462] Missing required logs.

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

apport-collect 1842462

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
  [IOMMU] xsaves support for pasid

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  context switch support for pasid using xsaves method.

  Target Release: 20.04
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842462/+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 1842473] Re: sched_getattr will return EFBIG

https://lore.kernel.org/lkml/20190903171645.28090-1-casca...@canonical.com/T/#t

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

Title:
  sched_getattr will return EFBIG

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  With the introduction of utilization clamps interface on
  sched_[sg]etattr, sched_getattr will fail when used with the previous
  smaller struct sched_attr. And instead of using E2BIG as documented,
  it also ends up using EFBIG instead.

  The interface change currently breaks userspace on 5.3 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842473/+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 1842473] Re: sched_getattr will return EFBIG

This breaks ltp syscalls regression testing on 5.3. The EFBIG versus
E2BIG should not happen in practice unless the other bug is also
present, so I wouldn't bother fixing it on older versions.

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

Title:
  sched_getattr will return EFBIG

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  With the introduction of utilization clamps interface on
  sched_[sg]etattr, sched_getattr will fail when used with the previous
  smaller struct sched_attr. And instead of using E2BIG as documented,
  it also ends up using EFBIG instead.

  The interface change currently breaks userspace on 5.3 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842473/+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 1836910] Re: br_netfilter: namespace sysctl operations

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

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

Title:
  br_netfilter: namespace sysctl operations

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

Bug description:
  SRU Justification

  Impact: Currently, the /proc/sys/net/bridge folder is only created in
  the initial network namespace. This blocks use-cases where users would
  like to e.g. not do bridge filtering for bridges in a specific network
  namespace while doing so for bridges located in another network
  namespace.

  Fix: The patches linked below ensure that the /proc/sys/net/bridge
  folder is available in each network namespace if the module is loaded
  and disappears from all network namespaces when the module is
  unloaded.

  In doing so the patch makes the sysctls:

  bridge-nf-call-arptables
  bridge-nf-call-ip6tables
  bridge-nf-call-iptables
  bridge-nf-filter-pppoe-tagged
  bridge-nf-filter-vlan-tagged
  bridge-nf-pass-vlan-input-dev

  apply per network namespace.

  Regression Potential: Low since it is limited to the br_netfilter module. I 
tested the patchset extensively by compiling a kernel with the patches applied. 
I loaded and unloaded the module and verified that it works correctly for the 
container usecase and does not crash. The Google ChromeOS team has also 
backported this patchset to their kernel and has not seen any issues so far: 
https://bugs.chromium.org/p/chromium/issues/detail?id=878034
  Security considerations around netfilter rules are also low. The netfilter 
rules are already per network namespace so it should be safe for users to 
specify whether bridge devices inside a network namespace are supposed to go 
through iptables et al. or not. Also, this can already be done per-bridge by 
setting an option for each individual bridge via Netlink. It should also be 
possible to do this for all bridges in a network namespace via sysctls.

  Test Case: Tested with LXD on a kernel with the patches applied and
  per-network namespace iptables.

  Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the
  patchset upstream.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836910/+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 1842465] Re: Watchdog error about hard lockup

2019-09-03 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

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

Title:
  Watchdog error about hard lockup

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Got a message from Watchdog about self-detected hard LOCKUP
   
  ---uname output---
  Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  4
  Core(s) per socket:  16
  Socket(s):   2
  NUMA node(s):6
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-63
  NUMA node8 CPU(s):   64-127
  NUMA node252 CPU(s):
  NUMA node253 CPU(s):
  NUMA node254 CPU(s):
  NUMA node255 CPU(s):
  ---
  free
totalusedfree  shared  buff/cache   
available
  Mem: 1071807104 5110016   985192768 622944081504320  
1056273664
  Swap:   2097088   0 2097088
  --
  lsblk
  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda   8:01 894.3G  0 disk
  ??sda18:11 7M  0 part
  ??sda28:21 894.3G  0 part /
  sdb   8:16   1 894.3G  0 disk
  nvme0n1 259:10   2.9T  0 disk /nvmdisk1
  ---
   
  Machine Type = AC922, bare metal 
   
  ---Steps to Reproduce---
   This problem I encountered when running customer workload and I switched SMT 
levels from SMT2 to SMT1 and I got a 
  lockup error right away!! this seems to be a different one... postgresql DB 
daemon was running on the system.
   
  Stack trace output:
   [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ 
_raw_spin_lock+0x54/0xe0
  [756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat 
TB:387337108856720 (13812ms ago)
  [756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd 
ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm 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 mlx5_ib ib_uverbs ib_core ast 
crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper 
syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci 
tls mlxfw devlink tg3 drm_panel_orientation_quirks
  [756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 
5.0.0-23-generic #24~18.04.1-Ubuntu
  [756383.688088] NIP:  c0e0fcc4 LR: c015fd90 CTR: 
c0600460
  [756383.688089] REGS: c07fffb3bd70 TRAP: 0900   Not tainted  
(5.0.0-23-generic)
  [756383.688089] MSR:  90009033   CR: 
28242824  XER: 
  [756383.688091] CFAR: c0e0fcec IRQMASK: 1 
  [756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 
c00020732ea49100 
  [756383.688093] GPR04: c000206f2cdf7a38  c000206f2cdf7b00 
0001 
  [756383.688095] GPR08: 0003 807d 8035 
fffd 
  [756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 
0f495eee0d68 
  [756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 
7fffc0eb2a74 
  [756383.688098] GPR20:  0001 0001 
 
  [756383.688099] GPR24:  c000206f2cdf7a38 c1349100 
20732d70 
  [756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 
c00020732ea49100 
  [756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0
  [756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150
  [756383.688102] Call Trace:
  [756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 
(unreliable)
  [756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818
  [756383.688104] [c000206f2cdf7a10] [c01649c0]

[Kernel-packages] [Bug 1842465] [NEW] Watchdog error about hard lockup

Public bug reported:

---Problem Description---
Got a message from Watchdog about self-detected hard LOCKUP
 
---uname output---
Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
Architecture:ppc64le
Byte Order:  Little Endian
CPU(s):  128
On-line CPU(s) list: 0-127
Thread(s) per core:  4
Core(s) per socket:  16
Socket(s):   2
NUMA node(s):6
Model:   2.2 (pvr 004e 1202)
Model name:  POWER9, altivec supported
CPU max MHz: 3800.
CPU min MHz: 2300.
L1d cache:   32K
L1i cache:   32K
L2 cache:512K
L3 cache:10240K
NUMA node0 CPU(s):   0-63
NUMA node8 CPU(s):   64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
---
free
  totalusedfree  shared  buff/cache   available
Mem: 1071807104 5110016   985192768 622944081504320  1056273664
Swap:   2097088   0 2097088
--
lsblk
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:01 894.3G  0 disk
??sda18:11 7M  0 part
??sda28:21 894.3G  0 part /
sdb   8:16   1 894.3G  0 disk
nvme0n1 259:10   2.9T  0 disk /nvmdisk1
---
 
Machine Type = AC922, bare metal 
 
---Steps to Reproduce---
 This problem I encountered when running customer workload and I switched SMT 
levels from SMT2 to SMT1 and I got a 
lockup error right away!! this seems to be a different one... postgresql DB 
daemon was running on the system.
 
Stack trace output:
 [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ 
_raw_spin_lock+0x54/0xe0
[756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat 
TB:387337108856720 (13812ms ago)
[756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd 
ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm 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 mlx5_ib ib_uverbs ib_core ast 
crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper 
syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci 
tls mlxfw devlink tg3 drm_panel_orientation_quirks
[756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 5.0.0-23-generic 
#24~18.04.1-Ubuntu
[756383.688088] NIP:  c0e0fcc4 LR: c015fd90 CTR: 
c0600460
[756383.688089] REGS: c07fffb3bd70 TRAP: 0900   Not tainted  
(5.0.0-23-generic)
[756383.688089] MSR:  90009033   CR: 28242824  
XER: 
[756383.688091] CFAR: c0e0fcec IRQMASK: 1 
[756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 
c00020732ea49100 
[756383.688093] GPR04: c000206f2cdf7a38  c000206f2cdf7b00 
0001 
[756383.688095] GPR08: 0003 807d 8035 
fffd 
[756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 
0f495eee0d68 
[756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 
7fffc0eb2a74 
[756383.688098] GPR20:  0001 0001 
 
[756383.688099] GPR24:  c000206f2cdf7a38 c1349100 
20732d70 
[756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 
c00020732ea49100 
[756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0
[756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150
[756383.688102] Call Trace:
[756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 
(unreliable)
[756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818
[756383.688104] [c000206f2cdf7a10] [c01649c0] try_to_wake_up+0x380/0x710
[756383.688105] [c000206f2cdf7aa0] [c0164de0] wake_up_q+0x70/0xd0
[756383.688105] [c000206f2cdf7ae0] [c05fab54] do_semtimedop+0x474/0xcc0
[756383.688106] [c000206f2cdf7d60] [c05fc634] ksys_semtimedop+0xd4/0xf0
[756383.688107] [c000206f2cdf7dc0] [c060047c] sys_ipc+0x14c/0x470
[756383.688107] [c000206f2cdf7e20] [c000b288] system_call+0x5c/0x70
[756383.688108] Instruction dump:
[756383.688108] 40c20010 7d40192d 40c2fff0 7c2004ac 2fa9 4d9e0020 fbc1fff0 
3fc20004 
[756383.688110] 3bde9578 fbe1fff8 7c7f1b78 f821ffd1 <7c210b78> e93e 
75290010 41820014 
[756386.336267] watchdog: CPU 53 became unstuck TB:387345536789288
[756386.336292] CPU: 53 PID: 330 Comm:

[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose

2019-09-03 Thread Fingerless Gloves

Tested using the docker-compose.yml with original docker-compose.yml
with every container but unbound using -dns.

Test1: Crashed (took less than 1 minutes to crash)
Fully updated ubuntu, using Scaleway's ubuntu image. (4.15.0-60-generic)
Crash: https://gist.github.com/FingerlessGlov3s/f829642cfc6390c975ca89be3b0d685a

Test2: Crashed (took less than 5 seconds to crash)
Fully updated ubuntu, using Scaleway's ubuntu image. (4.15.0-60-generic)
Also turned off appamour, SELinux not installed (systemctl disable
apparmor.service and rebooted)
Crash: https://gist.github.com/FingerlessGlov3s/fe3b5e6b89986b397e20bc5474049584

Test3: Working
Fully updated ubuntu, using Scaleway's ubuntu image. using old kernel
(4.15.0-58-generic)

Just ask if you want any more information or testing.

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

Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
nameserver in docker-compose

Status in linux package in Ubuntu:
Confirmed

Bug description:
Hello,

there are multiple inquries in the mailcow GitHub issues over at
https://github.com/mailcow/mailcow-dockerized/issues/2904 that the
latest kernel linux-image-4.15.0-60-generic causes kernel panics when
"- dns" setting is used within the docker-compose.yml file, for yet
some unclear reasons.

Multiple users on different systems (e.g. virtualized ones on VMware
ESXi and KVM) were able to reproduce the same issue. I was also able
to reproduce this constantly on a completely new deployed Ubuntu 18.04
VM (KVM) with a fresh mailcow installation.

Steps to reproduce:
1. Install a clean Ubuntu 18.04(.03) machine
2. Upgrade the installation to linux-image-4.15.0-60-generic
3. Setup mailcow as instructed at
https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes
less than a minute, easy to reproduce)
4. Start mailcow with "dns"-settings specified in docker-compose file (Make
sure using the older docker-compose version with dns settings:
https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears

Using this workaround it appears to be stable again:
https://github.com/mailcow/mailcow-
dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2

I've attached the apport file to this bug. Please let me know if you
need any kind of further information. (As this is my first bug report
here, I hope I have included all required information helping you
finding the cause.)

Kind regards,
Patrik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1836910] Re: br_netfilter: namespace sysctl operations

The tag verification-needed-bionic has been wrongly added by the bot,
the fixes for this bug hasn't been merged yet. I'm removing the tag.

** Tags removed: verification-done-bionic

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

Title:
  br_netfilter: namespace sysctl operations

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

Bug description:
  SRU Justification

  Impact: Currently, the /proc/sys/net/bridge folder is only created in
  the initial network namespace. This blocks use-cases where users would
  like to e.g. not do bridge filtering for bridges in a specific network
  namespace while doing so for bridges located in another network
  namespace.

  Fix: The patches linked below ensure that the /proc/sys/net/bridge
  folder is available in each network namespace if the module is loaded
  and disappears from all network namespaces when the module is
  unloaded.

  In doing so the patch makes the sysctls:

  bridge-nf-call-arptables
  bridge-nf-call-ip6tables
  bridge-nf-call-iptables
  bridge-nf-filter-pppoe-tagged
  bridge-nf-filter-vlan-tagged
  bridge-nf-pass-vlan-input-dev

  apply per network namespace.

  Regression Potential: Low since it is limited to the br_netfilter module. I 
tested the patchset extensively by compiling a kernel with the patches applied. 
I loaded and unloaded the module and verified that it works correctly for the 
container usecase and does not crash. The Google ChromeOS team has also 
backported this patchset to their kernel and has not seen any issues so far: 
https://bugs.chromium.org/p/chromium/issues/detail?id=878034
  Security considerations around netfilter rules are also low. The netfilter 
rules are already per network namespace so it should be safe for users to 
specify whether bridge devices inside a network namespace are supposed to go 
through iptables et al. or not. Also, this can already be done per-bridge by 
setting an option for each individual bridge via Netlink. It should also be 
possible to do this for all bridges in a network namespace via sysctls.

  Test Case: Tested with LXD on a kernel with the patches applied and
  per-network namespace iptables.

  Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the
  patchset upstream.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836910/+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 1842462] [NEW] [IOMMU] xsaves support for pasid

2019-09-03 Thread quanxian

Public bug reported:

Description
context switch support for pasid using xsaves method.

Target Release: 20.04
Target Kernel: 5.3

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-19.10

** 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842462

Title:
  [IOMMU] xsaves support for pasid

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  context switch support for pasid using xsaves method.

  Target Release: 20.04
  Target Kernel: 5.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1842462/+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 1842459] [NEW] apparmor abi-feature pinning not working with Disco and Eoan kernels

2019-09-03 Thread Stoiko Ivanov

Public bug reported:

When setting a features-file in /etc/apparmor/apparmor.conf (and using policies 
for this feature-set) certain operations are DENIED, although they should be 
allowed.
This occurs for example when running an Ubuntu kernel with Debian Buster 
apparmor.

Steps for reproducing:
* Starting from a minimal Buster VM (apparmor 2.13.2-10)
* Install unbound (one example) - apparmor confinement works as expected
* Install a kernel from Ubuntu (tested with: 5.0.0-25.26 from disco and 
5.2.0-15.16 from eoan)
* Reboot - unbound fails to start - the following messages are in `dmesg`:

```
[3.109740] audit: type=1400 audit(1567527034.644:9): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
[3.113969] audit: type=1400 audit(1567527034.652:10): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
[5.322119] audit: type=1400 audit(1567527036.856:21): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
[5.324621] audit: type=1400 audit(1567527036.860:22): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
[5.326335] audit: type=1400 audit(1567527036.860:23): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="inet6" sock_type="dgram" protocol=0 requested_mask="create" 
denied_mask="create"
```

The problem does not occur when:
* booting the corresponding mainline kernels (5.0.18 and 5.29)
* booting debian kernels (5.2.9-2 from testing+sid and 4.19.0-5-amd64 from 
buster)
* the features-file is changed to reflect the features present in Ubuntu kernels
* the features-file option is removed (commented out) in 
/etc/apparmor/apparmor.conf

Opening the bug against linux and not apparmor, because it looks to me like the 
issue might be in
the Ubuntu patches.

Glad to provide further information and help testing!

Thanks for all your great work!

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


** Tags: apparmor

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

Title:
  apparmor abi-feature pinning not working with Disco and Eoan kernels

Status in linux package in Ubuntu:
  New

Bug description:
  When setting a features-file in /etc/apparmor/apparmor.conf (and using 
policies for this feature-set) certain operations are DENIED, although they 
should be allowed.
  This occurs for example when running an Ubuntu kernel with Debian Buster 
apparmor.

  Steps for reproducing:
  * Starting from a minimal Buster VM (apparmor 2.13.2-10)
  * Install unbound (one example) - apparmor confinement works as expected
  * Install a kernel from Ubuntu (tested with: 5.0.0-25.26 from disco and 
5.2.0-15.16 from eoan)
  * Reboot - unbound fails to start - the following messages are in `dmesg`:

  ```
  [3.109740] audit: type=1400 audit(1567527034.644:9): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [3.113969] audit: type=1400 audit(1567527034.652:10): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=516 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.322119] audit: type=1400 audit(1567527036.856:21): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.324621] audit: type=1400 audit(1567527036.860:22): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create" addr=none
  [5.326335] audit: type=1400 audit(1567527036.860:23): apparmor="DENIED" 
operation="create" profile="/usr/sbin/unbound" pid=549 comm="unbound" 
family="inet6" sock_type="dgram" protocol=0 requested_mask="create" 
denied_mask="create"
  ```

  The problem does not occur when:
  * booting the corresponding mainline kernels (5.0.18 and 5.29)
  * booting debian kernels (5.2.9-2 from testing+sid and 4.19.0-5-amd64 from 
buster)
  * the features-file is changed to reflect the features present in Ubuntu 
kernels
  * the features-file option is removed (commented out) in 
/etc/apparmor/apparmor.conf

[Kernel-packages] [Bug 1842465] [NEW] Watchdog error about hard lockup

2019-09-03 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

---Problem Description---
Got a message from Watchdog about self-detected hard LOCKUP
 
---uname output---
Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
Architecture:ppc64le
Byte Order:  Little Endian
CPU(s):  128
On-line CPU(s) list: 0-127
Thread(s) per core:  4
Core(s) per socket:  16
Socket(s):   2
NUMA node(s):6
Model:   2.2 (pvr 004e 1202)
Model name:  POWER9, altivec supported
CPU max MHz: 3800.
CPU min MHz: 2300.
L1d cache:   32K
L1i cache:   32K
L2 cache:512K
L3 cache:10240K
NUMA node0 CPU(s):   0-63
NUMA node8 CPU(s):   64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
---
free
  totalusedfree  shared  buff/cache   available
Mem: 1071807104 5110016   985192768 622944081504320  1056273664
Swap:   2097088   0 2097088
--
lsblk
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:01 894.3G  0 disk
??sda18:11 7M  0 part
??sda28:21 894.3G  0 part /
sdb   8:16   1 894.3G  0 disk
nvme0n1 259:10   2.9T  0 disk /nvmdisk1
---
 
Machine Type = AC922, bare metal 
 
---Steps to Reproduce---
 This problem I encountered when running customer workload and I switched SMT 
levels from SMT2 to SMT1 and I got a 
lockup error right away!! this seems to be a different one... postgresql DB 
daemon was running on the system.
 
Stack trace output:
 [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ 
_raw_spin_lock+0x54/0xe0
[756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat 
TB:387337108856720 (13812ms ago)
[756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 
xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay 
vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd 
ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm 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 mlx5_ib ib_uverbs ib_core ast 
crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper 
syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci 
tls mlxfw devlink tg3 drm_panel_orientation_quirks
[756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 5.0.0-23-generic 
#24~18.04.1-Ubuntu
[756383.688088] NIP:  c0e0fcc4 LR: c015fd90 CTR: 
c0600460
[756383.688089] REGS: c07fffb3bd70 TRAP: 0900   Not tainted  
(5.0.0-23-generic)
[756383.688089] MSR:  90009033   CR: 28242824  
XER: 
[756383.688091] CFAR: c0e0fcec IRQMASK: 1 
[756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 
c00020732ea49100 
[756383.688093] GPR04: c000206f2cdf7a38  c000206f2cdf7b00 
0001 
[756383.688095] GPR08: 0003 807d 8035 
fffd 
[756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 
0f495eee0d68 
[756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 
7fffc0eb2a74 
[756383.688098] GPR20:  0001 0001 
 
[756383.688099] GPR24:  c000206f2cdf7a38 c1349100 
20732d70 
[756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 
c00020732ea49100 
[756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0
[756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150
[756383.688102] Call Trace:
[756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 
(unreliable)
[756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818
[756383.688104] [c000206f2cdf7a10] [c01649c0] try_to_wake_up+0x380/0x710
[756383.688105] [c000206f2cdf7aa0] [c0164de0] wake_up_q+0x70/0xd0
[756383.688105] [c000206f2cdf7ae0] [c05fab54] do_semtimedop+0x474/0xcc0
[756383.688106] [c000206f2cdf7d60] [c05fc634] ksys_semtimedop+0xd4/0xf0
[756383.688107] [c000206f2cdf7dc0] [c060047c] sys_ipc+0x14c/0x470
[756383.688107] [c000206f2cdf7e20] [c000b288] system_call+0x5c/0x70
[756383.688108] Instruction dump:
[756383.688108] 40c20010 7d40192d 40c2fff0 7c2004ac 2fa9 4d9e0020 fbc1fff0 
3fc20004 
[756383.688110] 3bde9578 fbe1fff8 7c7f1b78 f821ffd1 <7c210b78> e93e 
75290010 41820014 
[756386.336267] watchdog: CPU 53 became unstuck TB:387345536789288
[756386.336292]

[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket

** Changed in: linux (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/1834465

Title:
  ipv6: fix neighbour resolution with raw socket

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==

  IPv6 packets may be dropped during the neighbor resolution when a
  userspace program uses IPv6 raw sockets. The commit that introduces
  this bug has not been identified, but it's here at least from Xenial (4.4).
  This was fixed in the requested backport (from 5.2).

  == Fix ==

  Backport the requested patches to Disco (5.0), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regregression ==

  The change slightly modifies the target IPv6 address in neighbor
  resolution engine. Risk should be low and limited to ipv6.

  ---

  With an IPv6 raw socket, packets may be dropped during the neighbour
  resolution. It is fixed upstream by these patches:

  9b1c1ef13b35 ipv6: constify rt6_nexthop()
  2c6b55f45d53 ipv6: fix neighbour resolution with raw socket

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f

  The detail of the bug is explained in the second patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+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 1830756] Re: tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

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

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

Title:
  tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

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

Bug description:
  [SRU Justification]

  == Impact ==

  1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
  kernel v4.5 introduced an issue where userspace processes might not
  get notified if a link comes up after initially being down. This was
  fixed in the requested backport (from 4.17).

  == Fix ==

  Backport the requested patch to Bionic (4.15). Xenial (4.4) is not
  affected and Disco and later already contain that fix.

  == Risk of Regregression ==

  The change only slightly modifies a very specific protocol function.
  Risk should be low and limited to tuntap.

  ---

  The upstream commit 2f3ab6221e4c ("tuntap: correctly set 
SOCKWQ_ASYNC_NOSPACE") is missing.
  Without this patch, userspace apps that use tuntap may be blocked.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

** Changed in: linux (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/1838133

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

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

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose

2019-09-03 Thread jkrakenda

** Also affects: linux
Importance: Undecided
Status: New

** No longer affects: linux

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

Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
nameserver in docker-compose

Status in linux package in Ubuntu:
Confirmed

Bug description:
Hello,

Using this workaround it appears to be stable again:
https://github.com/mailcow/mailcow-
dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2

Kind regards,
Patrik

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

[Kernel-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

2019-09-03 Thread Colin Ian King

The ZFS destroy checks the reference count on the dataset with
zfs_refcount_count(>ds_longholds) != expected_holds and returns
EBUSY in dsl_destroy_head_check_impl.

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Triaged
Status in lxc source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  New
Status in lxc source package in Disco:
  New
Status in linux source package in Eoan:
  Triaged
Status in lxc source package in Eoan:
  Confirmed

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name: milhouse

  $ lxc delete --force b1
  Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

  Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

   | short version is that something unshared a mount namespace causing
   | them to get a copy of the mount table at the time that dataset was
   | mounted, which then prevents zfs from being able to destroy it)

  The work around provided was

   | you can unstick this particular issue by doing:
   |  grep default/containers/b1 /proc/*/mountinfo
   | then for any of the hits, do:
   |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
   | then try the delete again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smoser31412 F pulseaudio
   /dev/snd/controlC2:  smoser31412 F pulseaudio
   /dev/snd/controlC0:  smoser31412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 10:42:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1071 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
  dmi.board.asset.tag: �
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
  dmi.product.family: �
  dmi.product.name: �
  dmi.product.version: �
  dmi.sys.vendor: �

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

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

[Kernel-packages] [Bug 1838619] Re: Turn off nvme driver on raspi2

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

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

Title:
  Turn off nvme driver on raspi2

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

Bug description:
  Impact:

  We recently adjusted CONFIG_NVM to fix a build failure. The change
  causing this was actually a mis-merge and will be reverted. However
  the question came up whether it makes sense at all to build any
  raspberry kernel with NVME support at all. There currently is no way
  to attach any NVME to a raspberry pi, so lets turn off driver support
  for it for that kernel in total.

  Fix:

  Disable the relevant config options:

  # CONFIG_NVM is not set
  ...
  # CONFIG_NVME_FC is not set
  # CONFIG_NVME_TARGET is not set

  
  Regression potential:

  None, we are disabling support for a piece of hardware that doesn't
  exist on the RaspberryPi boards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838619/+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 1840846] Re: Disco update: upstream stable patchset 2019-08-20

** Changed in: linux (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/1840846

Title:
  Disco update: upstream stable patchset 2019-08-20

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-20

  Ported from the following upstream stable releases:
  v4.19.60, v5.1.19,
  v4.19.61, v5.1.20

     from git://git.kernel.org/

  Revert "e1000e: fix cyclic resets at link up with active tx"
  e1000e: start network tx queue only when link is up
  Input: synaptics - enable SMBUS on T480 thinkpad trackpad
  nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header
  drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT
  firmware: improve LSM/IMA security behaviour
  irqchip/gic-v3-its: Fix command queue pointer comparison bug
  clk: ti: clkctrl: Fix returning uninitialized data
  efi/bgrt: Drop BGRT status field reserved bits check
  perf/core: Fix perf_sample_regs_user() mm check
  ARM: dts: gemini Fix up DNS-313 compatible string
  ARM: omap2: remove incorrect __init annotation
  afs: Fix uninitialised spinlock afs_volume::cb_break_lock
  x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz
  be2net: fix link failure after ethtool offline test
  ppp: mppe: Add softdep to arc4
  sis900: fix TX completion
  ARM: dts: imx6ul: fix PWM[1-4] interrupts
  pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order
  dm table: don't copy from a NULL pointer in realloc_argv()
  dm verity: use message limit for data block corruption message
  x86/boot/64: Fix crash if kernel image crosses page table boundary
  x86/boot/64: Add missing fixup_pointer() for next_early_pgt access
  HID: chicony: add another quirk for PixArt mouse
  pinctrl: mediatek: Ignore interrupts that are wake only during resume
  cpu/hotplug: Fix out-of-bounds read when setting fail state
  pinctrl: mediatek: Update cur_mask in mask/mask ops
  linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL
  genirq: Delay deactivation in free_irq()
  genirq: Fix misleading synchronize_irq() documentation
  genirq: Add optional hardware synchronization for shutdown
  x86/ioapic: Implement irq_get_irqchip_state() callback
  x86/irq: Handle spurious interrupt after shutdown gracefully
  x86/irq: Seperate unused system vectors from spurious entry again
  ARC: hide unused function unw_hdr_alloc
  s390: fix stfle zero padding
  s390/qdio: (re-)initialize tiqdio list entries
  s390/qdio: don't touch the dsci in tiqdio_add_input_queues()
  crypto: talitos - move struct talitos_edesc into talitos.h
  crypto: talitos - fix hash on SEC1.
  crypto/NX: Set receive window credits to max number of CRBs in RxFIFO
  drm/udl: introduce a macro to convert dev to udl.
  drm/udl: move to embedding drm device inside udl device.
  x86/entry/32: Fix ENDPROC of common_spurious
  irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus
  arm64: dts: ls1028a: Fix CPU idle fail.
  selftests/powerpc: Add test of fork with mapping above 512TB
  x86/efi: fix a -Wtype-limits compilation warning
  pinctrl: ocelot: fix gpio direction for pins after 31
  pinctrl: ocelot: fix pinmuxing for pins after 31
  mm/oom_kill.c: fix uninitialized oc->constraint
  fork,memcg: alloc_thread_stack_node needs to set tsk->stack
  UBUNTU: upstream stable to v4.19.60, v5.1.19
  MIPS: ath79: fix ar933x uart parity mode
  MIPS: fix build on non-linux hosts
  arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly
  scsi: iscsi: set auth_protocol back to NULL if CHAP_A value is not supported
  dmaengine: imx-sdma: fix use-after-free on probe error path
  wil6210: fix potential out-of-bounds read
  ath10k: Do not send probe response template for mesh
  ath9k: Check for errors when reading SREV register
  ath6kl: add some bounds checking
  ath10k: add peer id check in ath10k_peer_find_by_id
  wil6210: fix spurious interrupts in 3-msi
  ath: DFS JP domain W56 fixed pulse type 3 RADAR detection
  regmap: debugfs: Fix memory leak in regmap_debugfs_init
  batman-adv: fix for leaked TVLV handler.
  media: dvb: usb: fix use after free in dvb_usb_device_exit
  media: spi: IR LED: add missing of table registration
  crypto: talitos - fix skcipher failure due to

[Kernel-packages] [Bug 1840373] Re: Disco update: upstream stable patchset 2019-08-15

** Changed in: linux (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/1840373

Title:
  Disco update: upstream stable patchset 2019-08-15

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-15

  Ported from the following upstream stable releases:
  v4.19.56, v5.1.15

     from git://git.kernel.org/

  tracing: Silence GCC 9 array bounds warning
  gcc-9: silence 'address-of-packed-member' warning
  ovl: support the FS_IOC_FS[SG]ETXATTR ioctls
  ovl: fix wrong flags check in FS_IOC_FS[SG]ETXATTR ioctls
  ovl: make i_ino consistent with st_ino in more cases
  ovl: detect overlapping layers
  ovl: don't fail with disconnected lower NFS
  ovl: fix bogus -Wmaybe-unitialized warning
  mmc: sdhci: sdhci-pci-o2micro: Correctly set bus width when tuning
  mmc: core: API to temporarily disable retuning for SDIO CRC errors
  mmc: core: Add sdio_retune_hold_now() and sdio_retune_release()
  mmc: core: Prevent processing SDIO IRQs when the card is suspended
  scsi: ufs: Avoid runtime suspend possibly being blocked forever
  usb: chipidea: udc: workaround for endpoint conflict issue
  xhci: detect USB 3.2 capable host controllers correctly
  usb: xhci: Don't try to recover an endpoint if port is in error state.
  IB/hfi1: Validate fault injection opcode user input
  IB/hfi1: Silence txreq allocation warnings
  iio: temperature: mlx90632 Relax the compatibility check
  Input: synaptics - enable SMBus on ThinkPad E480 and E580
  Input: uinput - add compat ioctl number translation for UI_*_FF_UPLOAD
  Input: silead - add MSSL0017 to acpi_device_id
  apparmor: enforce nullbyte at end of tag string
  brcmfmac: sdio: Disable auto-tuning around commands expected to fail
  brcmfmac: sdio: Don't tune while the card is off
  ARC: fix build warnings
  dmaengine: dw-axi-dmac: fix null dereference when pointer first is null
  dmaengine: sprd: Fix block length overflow
  ARC: [plat-hsdk]: Add missing multicast filter bins number to GMAC node
  ARC: [plat-hsdk]: Add missing FIFO size entry in GMAC node
  fpga: dfl: afu: Pass the correct device to dma_mapping_error()
  fpga: dfl: Add lockdep classes for pdata->lock
  parport: Fix mem leak in parport_register_dev_model
  parisc: Fix compiler warnings in float emulation code
  IB/rdmavt: Fix alloc_qpn() WARN_ON()
  IB/hfi1: Insure freeze_work work_struct is canceled on shutdown
  IB/{qib, hfi1, rdmavt}: Correct ibv_devinfo max_mr value
  IB/hfi1: Validate page aligned for a given virtual address
  MIPS: uprobes: remove set but not used variable 'epc'
  xtensa: Fix section mismatch between memblock_reserve and mem_reserve
  kselftest/cgroup: fix unexpected testing failure on test_memcontrol
  kselftest/cgroup: fix unexpected testing failure on test_core
  kselftest/cgroup: fix incorrect test_core skip
  selftests: vm: install test_vmalloc.sh for run_vmtests
  net: dsa: mv88e6xxx: avoid error message on remove from VLAN 0
  mdesc: fix a missing-check bug in get_vdev_port_node_info()
  sparc: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD
  net: ethernet: mediatek: Use hw_feature to judge if HWLRO is supported
  net: ethernet: mediatek: Use NET_IP_ALIGN to judge if HW RX_2BYTE_OFFSET is 
enabled
  drm/arm/mali-dp: Add a loop around the second set CVAL and try 5 times
  drm/arm/hdlcd: Actually validate CRTC modes
  drm/arm/hdlcd: Allow a bit of clock tolerance
  nvmet: fix data_len to 0 for bdev-backed write_zeroes
  scripts/checkstack.pl: Fix arm64 wrong or unknown architecture
  scsi: ufs: Check that space was properly alloced in copy_query_response
  scsi: smartpqi: unlock on error in pqi_submit_raid_request_synchronous()
  net: ipvlan: Fix ipvlan device tso disabled while NETIF_F_IP_CSUM is set
  s390/qeth: fix VLAN attribute in bridge_hostnotify udev event
  hwmon: (core) add thermal sensors only if dev->of_node is present
  hwmon: (pmbus/core) Treat parameters as paged if on multiple pages
  arm64: Silence gcc warnings about arch ABI drift
  nvme: Fix u32 overflow in the number of namespace list calculation
  btrfs: start readahead also in seed devices
  can: xilinx_can: use correct bittiming_const for CAN FD core
  can: flexcan: fix timeout when set small bitrate
  can: purge socket error

[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot

2019-09-03 Thread Alistair Buxton

Reloading the module does clear the error for me.

I have never seen the problem where the link comes up but it won't
receive packets.

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

Title:
  r8169 ethernet sometimes doesn't work after cold boot/boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever the computer is rebooted there is a roughly 50% chance that
  the r8169 ethernet cannot negotiate a link. There is no relevant
  information in dmesg except for the "link down" message. The work
  around is to just keep rebooting the computer until it eventually
  works; sometimes this may take up to 7 reboots.

  The first set of attached log files were generated while the ethernet
  was working.

  The second set are generated on the 5.0 HWE kernel when the ethernet
  was NOT working.

  Note that this is a regression. Ubuntu 16.04 ran on this computer for
  three years without the ethernet doing this even once.

  Unloading and loading the r8169 module will eventually make it work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-58-generic 4.15.0-58.64
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Thu Aug 22 10:05:17 2019
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  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.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.173.9
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  al14985 F pulseaudio
   /dev/snd/controlC0:  al14985 F pulseaudio
   /dev/snd/controlC1:  al14985 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
  InstallationDate: Installed on 2013-12-22 (2068 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.173.9
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER

[Kernel-packages] [Bug 1841121] Re: Disco update: upstream stable patchset 2019-08-22

** Changed in: linux (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/1841121

Title:
  Disco update: upstream stable patchset 2019-08-22

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-22

  Ported from the following upstream stable releases:
  v4.19.63, v5.2.5

     from git://git.kernel.org/

  hvsock: fix epollout hang from race condition
  drm/panel: simple: Fix panel_simple_dsi_probe
  iio: adc: stm32-dfsdm: manage the get_irq error case
  iio: adc: stm32-dfsdm: missing error case during probe
  staging: vt6656: use meaningful error code during buffer allocation
  usb: core: hub: Disable hub-initiated U1/U2
  tty: max310x: Fix invalid baudrate divisors calculator
  pinctrl: rockchip: fix leaked of_node references
  tty: serial: cpm_uart - fix init when SMC is relocated
  drm/amd/display: Fill prescale_params->scale for RGB565
  drm/amdgpu/sriov: Need to initialize the HDP_NONSURFACE_BAStE
  drm/amd/display: Disable ABM before destroy ABM struct
  drm/amdkfd: Fix a potential memory leak
  drm/amdkfd: Fix sdma queue map issue
  drm/edid: Fix a missing-check bug in drm_load_edid_firmware()
  PCI: Return error if cannot probe VF
  drm/bridge: tc358767: read display_props in get_modes()
  drm/bridge: sii902x: pixel clock unit is 10kHz instead of 1kHz
  gpu: host1x: Increase maximum DMA segment size
  drm/crc-debugfs: User irqsafe spinlock in drm_crtc_add_crc_entry
  drm/crc-debugfs: Also sprinkle irqrestore over early exits
  memstick: Fix error cleanup path of memstick_init
  tty/serial: digicolor: Fix digicolor-usart already registered warning
  tty: serial: msm_serial: avoid system lockup condition
  serial: 8250: Fix TX interrupt handling condition
  drm/amd/display: Always allocate initial connector state state
  drm/virtio: Add memory barriers for capset cache.
  phy: renesas: rcar-gen2: Fix memory leak at error paths
  drm/amd/display: fix compilation error
  powerpc/pseries/mobility: prevent cpu hotplug during DT update
  drm/rockchip: Properly adjust to a true clock in adjusted_mode
  serial: imx: fix locking in set_termios()
  tty: serial_core: Set port active bit in uart_port_activate
  usb: gadget: Zero ffs_io_data
  mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width
  powerpc/pci/of: Fix OF flags parsing for 64bit BARs
  drm/msm: Depopulate platform on probe failure
  serial: mctrl_gpio: Check if GPIO property exisits before requesting it
  PCI: sysfs: Ignore lockdep for remove attribute
  i2c: stm32f7: fix the get_irq error cases
  kbuild: Add -Werror=unknown-warning-option to CLANG_FLAGS
  genksyms: Teach parser about 128-bit built-in types
  PCI: xilinx-nwl: Fix Multi MSI data programming
  iio: iio-utils: Fix possible incorrect mask calculation
  powerpc/cacheflush: fix variable set but not used
  powerpc/xmon: Fix disabling tracing while in xmon
  recordmcount: Fix spurious mcount entries on powerpc
  mfd: madera: Add missing of table registration
  mfd: core: Set fwnode for created devices
  mfd: arizona: Fix undefined behavior
  mfd: hi655x-pmic: Fix missing return value check for devm_regmap_init_mmio_clk
  mm/swap: fix release_pages() when releasing devmap pages
  um: Silence lockdep complaint about mmap_sem
  powerpc/4xx/uic: clear pending interrupt after irq type/pol change
  RDMA/i40iw: Set queue pair state when being queried
  serial: sh-sci: Terminate TX DMA during buffer flushing
  serial: sh-sci: Fix TX DMA buffer flushing and workqueue races
  IB/mlx5: Fixed reporting counters on 2nd port for Dual port RoCE
  powerpc/mm: Handle page table allocation failures
  IB/ipoib: Add child to parent list only if device initialized
  arm64: assembler: Switch ESB-instruction with a vanilla nop if !ARM64_HAS_RAS
  PCI: mobiveil: Fix PCI base address in MEM/IO outbound windows
  PCI: mobiveil: Fix the Class Code field
  kallsyms: exclude kasan local symbols on s390
  PCI: mobiveil: Initialize Primary/Secondary/Subordinate bus numbers
  PCI: mobiveil: Use the 1st inbound window for MEM inbound transactions
  perf test mmap-thread-lookup: Initialize variable to suppress memory 
sanitizer warning
  perf stat: Fix use-after-freed pointer detected by the smatch tool
  perf top: Fix potential NULL

[Kernel-packages] [Bug 1840961] Re: Disco update: upstream stable patchset 2019-08-21

** Changed in: linux (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/1840961

Title:
  Disco update: upstream stable patchset 2019-08-21

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-21

  Ported from the following upstream stable releases:
  v4.19.62, v5.1.21, v5.2.4

     from git://git.kernel.org/

  bnx2x: Prevent load reordering in tx completion processing
  caif-hsi: fix possible deadlock in cfhsi_exit_module()
  hv_netvsc: Fix extra rcu_read_unlock in netvsc_recv_callback()
  igmp: fix memory leak in igmpv3_del_delrec()
  ipv4: don't set IPv6 only flags to IPv4 addresses
  ipv6: rt6_check should return NULL if 'from' is NULL
  ipv6: Unlink sibling route in case of failure
  net: bcmgenet: use promisc for unsupported filters
  net: dsa: mv88e6xxx: wait after reset deactivation
  net: make skb_dst_force return true when dst is refcounted
  net: neigh: fix multiple neigh timer scheduling
  net: openvswitch: fix csum updates for MPLS actions
  net: phy: sfp: hwmon: Fix scaling of RX power
  net: stmmac: Re-work the queue selection for TSO packets
  nfc: fix potential illegal memory access
  r8169: fix issue with confused RX unit after PHY power-down on RTL8411b
  rxrpc: Fix send on a connected, but unbound socket
  sctp: fix error handling on stream scheduler initialization
  sky2: Disable MSI on ASUS P6T
  tcp: be more careful in tcp_fragment()
  tcp: fix tcp_set_congestion_control() use from bpf hook
  tcp: Reset bytes_acked and bytes_received when disconnecting
  vrf: make sure skb->data contains ip header to make routing
  net/mlx5e: IPoIB, Add error path in mlx5_rdma_setup_rn
  macsec: fix use-after-free of skb during RX
  macsec: fix checksumming after decryption
  netrom: fix a memory leak in nr_rx_frame()
  netrom: hold sock when setting skb->destructor
  net_sched: unset TCQ_F_CAN_BYPASS when adding filters
  net/tls: make sure offload also gets the keys wiped
  sctp: not bind the socket in sctp_connect
  net: bridge: mcast: fix stale nsrcs pointer in igmp3/mld2 report handling
  net: bridge: mcast: fix stale ipv6 hdr pointer when handling v6 query
  net: bridge: don't cache ether dest pointer on input
  net: bridge: stp: don't cache eth dest pointer before skb pull
  dma-buf: balance refcount inbalance
  dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc
  gpio: davinci: silence error prints in case of EPROBE_DEFER
  MIPS: lb60: Fix pin mappings
  perf/core: Fix exclusive events' grouping
  perf/core: Fix race between close() and fork()
  ext4: don't allow any modifications to an immutable file
  ext4: enforce the immutable flag on open files
  mm: add filemap_fdatawait_range_keep_errors()
  jbd2: introduce jbd2_inode dirty range scoping
  ext4: use jbd2_inode dirty range scoping
  ext4: allow directory holes
  KVM: nVMX: do not use dangling shadow VMCS after guest reset
  KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested
  mm: vmscan: scan anonymous pages on file refaults
  net: sched: verify that q!=NULL before setting q->flags
  selftests: txring_overwrite: fix incorrect test of mmap() return value
  net/tls: reject offload of TLS 1.3
  net/mlx5e: Rx, Fix checksum calculation for new hardware
  gpiolib: of: fix a memory leak in of_gpio_flags_quirks()
  sd_zbc: Fix report zones buffer allocation
  block: Limit zone array allocation size
  bnxt_en: Fix VNIC accounting when enabling aRFS on 57500 chips.
  mlxsw: spectrum_dcb: Configure DSCP map as the last rule is removed
  mlxsw: spectrum: Do not process learned records with a dummy FID
  Revert "kvm: x86: Use task structs fpu field for user"
  UBUNTU: upstream stable to v4.19.62, v5.1.21, v5.2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840961/+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 1840521] Re: Disco update: upstream stable patchset 2019-08-16

** Changed in: linux (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/1840521

Title:
  Disco update: upstream stable patchset 2019-08-16

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-16

  Ported from the following upstream stable releases:
  v4.19.57, v5.1.16

     from git://git.kernel.org/

  arm64: Don't unconditionally add -Wno-psabi to KBUILD_CFLAGS
  Revert "x86/uaccess, ftrace: Fix ftrace_likely_update() vs. SMAP"
  qmi_wwan: Fix out-of-bounds read
  fs/proc/array.c: allow reporting eip/esp for all coredumping threads
  mm/mempolicy.c: fix an incorrect rebind node in mpol_rebind_nodemask
  fs/binfmt_flat.c: make load_flat_shared_library() work
  clk: socfpga: stratix10: fix divider entry for the emac clocks
  mm: soft-offline: return -EBUSY if set_hwpoison_free_buddy_page() fails
  mm: hugetlb: soft-offline: dissolve_free_huge_page() return zero on !PageHuge
  dm log writes: make sure super sector log updates are written in order
  scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()
  x86/speculation: Allow guests to use SSBD even if host does not
  x86/microcode: Fix the microcode load on CPU hotplug for real
  x86/resctrl: Prevent possible overrun during bitmap operations
  NFS/flexfiles: Use the correct TCP timeout for flexfiles I/O
  cpu/speculation: Warn on unsupported mitigations= parameter
  irqchip/mips-gic: Use the correct local interrupt map registers
  af_packet: Block execution of tasks waiting for transmit to complete in 
AF_PACKET
  bonding: Always enable vlan tx offload
  ipv4: Use return value of inet_iif() for __raw_v4_lookup in the while loop
  net/packet: fix memory leak in packet_set_ring()
  net: remove duplicate fetch in sock_getsockopt
  net: stmmac: fixed new system time seconds value calculation
  net: stmmac: set IC bit when transmitting frames with HW timestamp
  sctp: change to hold sk after auth shkey is created successfully
  team: Always enable vlan tx offload
  tipc: change to use register_pernet_device
  tipc: check msg->req data len in tipc_nl_compat_bearer_disable
  tun: wake up waitqueues after IFF_UP is set
  bpf: simplify definition of BPF_FIB_LOOKUP related flags
  bpf: lpm_trie: check left child of last leftmost node for NULL
  bpf: fix nested bpf tracepoints with per-cpu data
  bpf: fix unconnected udp hooks
  bpf: udp: Avoid calling reuseport's bpf_prog from udp_gro
  bpf: udp: ipv6: Avoid running reuseport's bpf_prog from __udp6_lib_err
  arm64: futex: Avoid copying out uninitialised stack in failed cmpxchg()
  bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd
  futex: Update comments and docs about return values of arch futex code
  RDMA: Directly cast the sockaddr union to sockaddr
  tipc: pass tunnel dev as NULL to udp_tunnel(6)_xmit_skb
  arm64: insn: Fix ldadd instruction encoding
  clk: tegra210: Fix default rates for HDA clocks
  mm, swap: fix THP swap out
  mm: fix page cache convergence regression
  efi/memreserve: deal with memreserve entries in unmapped memory
  net: aquantia: fix vlans not working over bridged network
  UBUNTU: upstream stable to v4.19.57, v5.1.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840521/+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 1840718] Re: Disco update: upstream stable patchset 2019-08-19

** Changed in: linux (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/1840718

Title:
  Disco update: upstream stable patchset 2019-08-19

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-19

  Ported from the following upstream stable releases:
  v4.19.58, v5.1.17,
  v4.19.59, v5.1.18

     from git://git.kernel.org/

  Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
  Bluetooth: Fix regression with minimum encryption key size alignment
  Bluetooth: Fix faulty expression for minimum encryption key size check
  netfilter: nf_flow_table: ignore DF bit setting
  netfilter: nft_flow_offload: set liberal tracking mode for tcp
  netfilter: nft_flow_offload: don't offload when sequence numbers need 
adjustment
  netfilter: nft_flow_offload: IPCB is only valid for ipv4 family
  ASoC : cs4265 : readable register too low
  ASoC: ak4458: add return value for ak4458_probe
  ASoC: soc-pcm: BE dai needs prepare when pause release after resume
  ASoC: ak4458: rstn_control - return a non-zero on error only
  spi: bitbang: Fix NULL pointer dereference in spi_unregister_master
  drm/mediatek: fix unbind functions
  drm/mediatek: unbind components in mtk_drm_unbind()
  drm/mediatek: call drm_atomic_helper_shutdown() when unbinding driver
  drm/mediatek: clear num_pipes when unbind driver
  drm/mediatek: call mtk_dsi_stop() after mtk_drm_crtc_atomic_disable()
  ASoC: max98090: remove 24-bit format support if RJ is 0
  ASoC: sun4i-i2s: Fix sun8i tx channel offset mask
  ASoC: sun4i-i2s: Add offset to RX channel select
  x86/CPU: Add more Icelake model numbers
  usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]
  usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC
  ALSA: hdac: fix memory release for SST and SOF drivers
  SoC: rt274: Fix internal jack assignment in set_jack callback
  scsi: hpsa: correct ioaccel2 chaining
  drm: panel-orientation-quirks: Add quirk for GPD pocket2
  drm: panel-orientation-quirks: Add quirk for GPD MicroPC
  platform/x86: intel-vbtn: Report switch events when event wakes device
  platform/x86: mlx-platform: Fix parent device in i2c-mux-reg device 
registration
  platform/mellanox: mlxreg-hotplug: Add devm_free_irq call to remove flow
  i2c: pca-platform: Fix GPIO lookup code
  cpuset: restore sanity to cpuset_cpus_allowed_fallback()
  scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE
  mm/mlock.c: change count_mm_mlocked_page_nr return type
  tracing: avoid build warning with HAVE_NOP_MCOUNT
  module: Fix livepatch/ftrace module text permissions race
  ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()
  crypto: user - prevent operating on larval algorithms
  crypto: cryptd - Fix skcipher instance memory leak
  ALSA: seq: fix incorrect order of dest_client/dest_ports arguments
  ALSA: firewire-lib/fireworks: fix miss detection of received MIDI messages
  ALSA: line6: Fix write on zero-sized buffer
  ALSA: usb-audio: fix sign unintended sign extension on left shifts
  ALSA: hda/realtek: Add quirks for several Clevo notebook barebones
  ALSA: hda/realtek - Change front mic location for Lenovo M710q
  lib/mpi: Fix karactx leak in mpi_powm
  fs/userfaultfd.c: disable irqs for fault_pending and event locks
  tracing/snapshot: Resize spare buffer if size changed
  ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node
  arm64: kaslr: keep modules inside module region when KASAN is enabled
  drm/amd/powerplay: use hardware fan control if no powerplay fan table
  drm/amdgpu/gfx9: use reset default for PA_SC_FIFO_SIZE
  drm/etnaviv: add missing failure path to destroy suballoc
  drm/imx: notify drm core before sending event during crtc disable
  drm/imx: only send event on crtc disable if kept disabled
  ftrace/x86: Remove possible deadlock between register_kprobe() and 
ftrace_run_update_code()
  mm/vmscan.c: prevent useless kswapd loops
  btrfs: Ensure replaced device doesn't have pending chunk allocation
  tty: rocket: fix incorrect forward declaration of 'rp_init()'
  net/smc: move unhash before release of clcsock
  media: s5p-mfc: fix incorrect bus assignment in virtual child device
  drm/fb-helper: generic:

[Kernel-packages] [Bug 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -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:
  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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  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
  kernel-stable-master-bug: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841534/+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 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -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:
  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:
  Fix Released
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:
  Fix Released
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 Xenial:
  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
  kernel-stable-master-bug: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 15:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841533/+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 1841994] Re: Disco update: upstream stable patchset 2019-08-29

** Changed in: linux (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/1841994

Title:
  Disco update: upstream stable patchset 2019-08-29

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-29

  Ported from the following upstream stable releases:
  v4.19.66, v5.2.8,
  v4.19.67, v5.2.9,
  v4.19.68, v5.2.10

     from git://git.kernel.org/

  scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
  gcc-9: don't warn about uninitialized variable
  driver core: Establish order of operations for device_add and device_del via 
bitflag
  drivers/base: Introduce kill_device()
  libnvdimm/bus: Prevent duplicate device_unregister() calls
  libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
  libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
  HID: wacom: fix bit shift for Cintiq Companion 2
  HID: Add quirk for HP X1200 PIXART OEM mouse
  atm: iphase: Fix Spectre v1 vulnerability
  bnx2x: Disable multi-cos feature.
  ife: error out when nla attributes are empty
  ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
  ip6_tunnel: fix possible use-after-free on xmit
  ipip: validate header length in ipip_tunnel_xmit
  mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()
  mvpp2: fix panic on module removal
  mvpp2: refactor MTU change code
  net: bridge: delete local fdb on device init failure
  net: bridge: mcast: don't delete permanent entries when fast leave is enabled
  net: fix ifindex collision during namespace removal
  net/mlx5e: always initialize frag->last_in_page
  net/mlx5: Use reversed order when unregister devices
  net: phylink: Fix flow control for fixed-link
  net: qualcomm: rmnet: Fix incorrect UL checksum offload logic
  net: sched: Fix a possible null-pointer dereference in dequeue_func()
  net sched: update vlan action for batched events operations
  net: sched: use temporary variable for actions indexes
  net/smc: do not schedule tx_work in SMC_CLOSED state
  NFC: nfcmrvl: fix gpio-handling regression
  ocelot: Cancel delayed work before wq destruction
  tipc: compat: allow tipc commands without arguments
  tun: mark small packets as owned by the tap sock
  net/mlx5: Fix modify_cq_in alignment
  net/mlx5e: Prevent encap flow counter update async to user query
  r8169: don't use MSI before RTL8168d
  compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
  cgroup: Call cgroup_release() before __exit_signal()
  cgroup: Implement css_task_iter_skip()
  cgroup: Include dying leaders with live threads in PROCS iterations
  cgroup: css_task_iter_skip()'d iterators must be advanced before accessed
  cgroup: Fix css_task_iter_advance_css_set() cset skip condition
  spi: bcm2835: Fix 3-wire mode if DMA is enabled
  ALSA: usb-audio: Sanity checks for each pipe and EP types
  ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
  drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
  net: phylink: don't start and stop SGMII PHYs in SFP modules twice
  net: phy: mscc: initialize stats array
  bpf: fix XDP vlan selftests test_xdp_vlan.sh
  selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
  selftests/bpf: reduce time to execute test_xdp_vlan.sh
  net: fix bpf_xdp_adjust_head regression for generic-XDP
  hv_sock: Fix hang when a connection is closed
  UBUNTU: upstream stable to v4.19.66, v5.2.8
  iio: cros_ec_accel_legacy: Fix incorrect channel setting
  iio: adc: max9611: Fix misuse of GENMASK macro
  staging: gasket: apex: fix copy-paste typo
  staging: android: ion: Bail out upon SIGKILL when allocating memory.
  crypto: ccp - Fix oops by properly managing allocated structures
  crypto: ccp - Add support for valid authsize values less than 16
  crypto: ccp - Ignore tag length when decrypting GCM ciphertext
  usb: usbfs: fix double-free of usb memory upon submiturb error
  usb: iowarrior: fix deadlock on disconnect
  sound: fix a memory leak bug
  mmc: cavium: Set the correct dma max segment size for mmc_host
  mmc: cavium: Add the missing dma unmap when the dma has finished.
  loop: set PF_MEMALLOC_NOIO for the worker thread
  Input: usbtouchscreen - initialize PM mutex before using it
  Input: elantech - enable SMBus on new (2018+) systems
  Input: synaptics -

[Kernel-packages] [Bug 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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
  kernel-stable-master-bug: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841539/+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 1841681] Re: Disco update: upstream stable patchset 2019-08-27

** Changed in: linux (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/1841681

Title:
  Disco update: upstream stable patchset 2019-08-27

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-27

  Ported from the following upstream stable releases:
  v4.19.64, v5.2.6,
  v4.19.65, v5.2.7

     from git://git.kernel.org/

  hv_sock: Add support for delayed close
  vsock: correct removal of socket from the list
  ISDN: hfcsusb: checking idx of ep configuration
  media: au0828: fix null dereference in error path
  ath10k: Change the warning message string
  media: cpia2_usb: first wake up, then free in disconnect
  media: pvrusb2: use a different format for warnings
  NFS: Cleanup if nfs_match_client is interrupted
  media: radio-raremono: change devm_k*alloc to k*alloc
  Bluetooth: hci_uart: check for missing tty operations
  sched/fair: Don't free p->numa_faults with concurrent readers
  sched/fair: Use RCU accessors consistently for ->numa_group
  /proc//cmdline: remove all the special cases
  /proc//cmdline: add back the setproctitle() special case
  drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl
  Fix allyesconfig output.
  ceph: hold i_ceph_lock when removing caps for freeing inode
  ip_tunnel: allow not to count pkts on tstats by setting skb's dev to NULL
  xfrm: policy: fix bydst hlist corruption on hash rebuild
  nvme: fix multipath crash when ANA is deactivated
  UBUNTU: upstream stable to v4.19.64, v5.2.6
  ARM: riscpc: fix DMA
  ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
  ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
  ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
  ftrace: Enable trampoline when rec count returns back to one
  dmaengine: tegra-apb: Error out if DMA_PREP_INTERRUPT flag is unset
  arm64: dts: rockchip: fix isp iommu clocks and power domain
  kernel/module.c: Only return -EEXIST for modules that have finished loading
  firmware/psci: psci_checker: Park kthreads before stopping them
  MIPS: lantiq: Fix bitfield masking
  dmaengine: rcar-dmac: Reject zero-length slave DMA requests
  clk: tegra210: fix PLLU and PLLU_OUT1
  fs/adfs: super: fix use-after-free bug
  clk: sprd: Add check for return value of sprd_clk_regmap_init()
  btrfs: fix minimum number of chunk errors for DUP
  btrfs: qgroup: Don't hold qgroup_ioctl_lock in btrfs_qgroup_inherit()
  cifs: Fix a race condition with cifs_echo_request
  ceph: fix improper use of smp_mb__before_atomic()
  ceph: return -ERANGE if virtual xattr value didn't fit in buffer
  ACPI: blacklist: fix clang warning for unused DMI table
  scsi: zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized
  perf version: Fix segfault due to missing OPT_END()
  x86: kvm: avoid constant-conversion warning
  ACPI: fix false-positive -Wuninitialized warning
  be2net: Signal that the device cannot transmit during reconfiguration
  x86/apic: Silence -Wtype-limits compiler warnings
  x86: math-emu: Hide clang warnings for 16-bit overflow
  mm/cma.c: fail if fixed declaration can't be honored
  lib/test_overflow.c: avoid tainting the kernel and fix wrap size
  lib/test_string.c: avoid masking memset16/32/64 failures
  coda: add error handling for fget
  coda: fix build using bare-metal toolchain
  uapi linux/coda_psdev.h: move upc_req definition from uapi to kernel side 
headers
  drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate some strings
  ipc/mqueue.c: only perform resource calculation if user valid
  xen/pv: Fix a boot up hang revealed by int3 self test
  x86/kvm: Don't call kvm_spurious_fault() from .fixup
  x86/paravirt: Fix callee-saved function ELF sizes
  x86, boot: Remove multiple copy of static function sanitize_boot_params()
  drm/nouveau: fix memory leak in nouveau_conn_reset()
  kconfig: Clear "written" flag to avoid data loss
  kbuild: initialize CLANG_FLAGS correctly in the top Makefile
  Btrfs: fix incremental send failure after deduplication
  Btrfs: fix race leading to fs corruption after transaction abort
  mmc: dw_mmc: Fix occasional hang after tuning on eMMC
  mmc: meson-mx-sdio: Fix misuse of GENMASK macro
  gpiolib: fix incorrect IRQ requesting of an

[Kernel-packages] [Bug 1841536] Re: xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-raspi2: 4.4.0-1120.129 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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
  kernel-stable-master-bug: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841536/+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 1842128] Re: Disco update: upstream stable patchset 2019-08-30

** Changed in: linux (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/1842128

Title:
  Disco update: upstream stable patchset 2019-08-30

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-30

  Ported from the following upstream stable releases:
  v4.19.69, v5.2.11

     from git://git.kernel.org/

  selftests/bpf: fix sendmsg6_prog on s390
  net: mvpp2: Don't check for 3 consecutive Idle frames for 10G links
  selftests: forwarding: gre_multipath: Enable IPv4 forwarding
  selftests: forwarding: gre_multipath: Fix flower filters
  can: mcp251x: add error check when wq alloc failed
  can: gw: Fix error path of cgw_module_init
  ASoC: rockchip: Fix mono capture
  mac80211_hwsim: Fix possible null-pointer dereferences in 
hwsim_dump_radio_nl()
  netfilter: ipset: Actually allow destination MAC address for hash:ip,mac sets 
too
  netfilter: ipset: Copy the right MAC address in bitmap:ip,mac and hash:ip,mac 
sets
  rxrpc: Fix potential deadlock
  rxrpc: Fix the lack of notification when sendmsg() fails on a DATA packet
  net: phy: phy_led_triggers: Fix a possible null-pointer dereference in 
phy_led_trigger_change_speed()
  NFS: Fix regression whereby fscache errors are appearing on 'nofsc' mounts
  HID: quirks: Set the INCREMENT_USAGE_ON_DUPLICATE quirk on Saitek X52
  drm/rockchip: Suspend DP late
  SMB3: Fix potential memory leak when processing compound chain
  s390: put _stext and _etext into .text section
  net: stmmac: Fix issues when number of Queues >= 4
  net: stmmac: tc: Do not return a fragment entry
  block, bfq: handle NULL return value by bfq_init_rq()
  KVM: arm64: Don't write junk to sysregs on reset
  KVM: arm: Don't write junk to CP15 registers on reset
  clk: socfpga: stratix10: fix rate caclulationg for cnt_clks
  ceph: clear page dirty before invalidate page
  Drivers: hv: vmbus: Fix virt_to_hvpfn() for X86_PAE
  dm integrity: fix a crash due to BUG_ON in __journal_read_write()
  dm raid: add missing cleanup in raid_ctr()
  xfs: don't trip over uninitialized buffer on extent read of corrupted inode
  xfs: always rejoin held resources during defer roll
  rxrpc: Fix local endpoint refcounting
  rxrpc: Fix read-after-free in rxrpc_queue_local()
  rxrpc: Fix local endpoint replacement
  rxrpc: Fix local refcounting
  regulator: axp20x: fix DCDCA and DCDCD for AXP806
  regulator: axp20x: fix DCDC5 and DCDC6 for AXP803
  HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
  MIPS: kernel: only use i8253 clocksource with periodic clockevent
  mips: fix cacheinfo
  netfilter: ebtables: fix a memory leak bug in compat
  ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks
  spi: pxa2xx: Balance runtime PM enable/disable on error
  bpf: sockmap, sock_map_delete needs to use xchg
  bpf: sockmap, synchronize_rcu before free'ing map
  bpf: sockmap, only create entry if ulp is not already enabled
  ASoC: dapm: fix a memory leak bug
  bonding: Force slave speed check after link state recovery for 802.3ad
  can: dev: call netif_carrier_off() in register_candev()
  ASoC: Fail card instantiation if DAI format setup fails
  st21nfca_connectivity_event_received: null check the allocation
  st_nci_hci_connectivity_event_received: null check the allocation
  {nl,mac}80211: fix interface combinations on crypto controlled devices
  ASoC: ti: davinci-mcasp: Fix clk PDIR handling for i2s master mode
  ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
  net: usb: qmi_wwan: Add the BroadMobi BM818 card
  qed: RDMA - Fix the hw_ver returned in device attributes
  isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in 
start_isoc_chain()
  net: stmmac: manage errors returned by of_get_mac_address()
  netfilter: ipset: Fix rename concurrency with listing
  nvmem: Use the same permissions for eeprom as for nvmem
  iwlwifi: mvm: avoid races in rate init and rate perform
  iwlwifi: dbg_ini: move iwl_dbg_tlv_load_bin out of debug override ifdef
  iwlwifi: dbg_ini: move iwl_dbg_tlv_free outside of debugfs ifdef
  iwlwifi: fix locking in delayed GTK setting
  iwlwifi: mvm: send LQ command always ASYNC
  isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack
  perf bench numa: Fix cpu0 binding

[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Description changed:

  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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Ready for Signoff
- phase-changed: Monday, 02. September 2019 15:11 UTC
+ phase: Ready for Promote to Updates
+ phase-changed: Tuesday, 03. September 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Holding -- stakeholder signoff not verified
-   stakeholder-signoff: Stalled -- waiting for signoff
+   promote-to-updates: Pending -- ready to copy
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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 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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff 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 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Promote to Updates
  phase-changed: Tuesday, 03. September 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+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 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

Update of xenial/linux-deeplens tested successfully. Marking
Stakeholder-Signoff as 'Fix Released'.

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

Title:
  xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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 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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff 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 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Promote to Updates
  phase-changed: Tuesday, 03. September 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose

2019-09-03 Thread Patrik Kernstock

** Summary changed:

- Kernel Panic with linux-image-4.15.0-60-generic when using docker-compose 
with dns setting
+ Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in 
docker-compose

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

Title:
  Kernel Panic with linux-image-4.15.0-60-generic when specifying
  nameserver in docker-compose

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  there are multiple inquries in the mailcow GitHub issues over at
  https://github.com/mailcow/mailcow-dockerized/issues/2904 that the
  latest kernel linux-image-4.15.0-60-generic causes kernel panics when
  "- dns" setting is used within the docker-compose.yml file, for yet
  some unclear reasons.

  Multiple users on different systems (e.g. virtualized ones on VMware
  ESXi and KVM) were able to reproduce the same issue. I was also able
  to reproduce this constantly on a completely new deployed Ubuntu 18.04
  VM (KVM) with a fresh mailcow installation.

  Steps to reproduce:
  1. Install a clean Ubuntu 18.04(.03) machine
  2. Upgrade the installation to linux-image-4.15.0-60-generic
  3. Setup mailcow as instructed at 
https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes 
less than a minute, easy to reproduce)
  4. Start mailcow with "dns"-settings specified in docker-compose file (Make 
sure using the older docker-compose version with dns settings: 
https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
  5. Wait a few minutes, then kernel crash appears

  Using this workaround it appears to be stable again:
  https://github.com/mailcow/mailcow-
  dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2

  I've attached the apport file to this bug. Please let me know if you
  need any kind of further information. (As this is my first bug report
  here, I hope I have included all required information helping you
  finding the cause.)

  Kind regards,
  Patrik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1840002] Re: xenial/linux-azure: 4.15.0-1056.61 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-azure: 4.15.0-1056.61 -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:
  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:
  Fix Released
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:
  Fix Released
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 Xenial:
  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
  kernel-stable-master-bug: 1841086
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 14:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-azure: bug 1840001
xenial/linux-azure-edge: bug 184
xenial/linux-azure/azure-kernel: bug 183
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840002/+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 1839996] Re: xenial/linux-oracle: 4.15.0-1022.25~16.04.1 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-oracle: 4.15.0-1022.25~16.04.1 -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:
  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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  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
  kernel-stable-master-bug: 1839997
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 14:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839996/+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 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux-gcp: 4.15.0-1041.43 -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:
  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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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
  kernel-stable-master-bug: 1841086
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 14:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1840672
xenial/linux-gcp/gke-kernel: bug 1840673
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+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 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  xenial/linux: 4.4.0-161.189 -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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
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:
  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 Xenial:
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 03. September 2019 14:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841544/+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 1842114] Re: Bionic update: upstream stable patchset 2019-08-30

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

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

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

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-30

  Ported from the following upstream stable releases:
  v4.14.141, v4.19.69

     from git://git.kernel.org/

  HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
  MIPS: kernel: only use i8253 clocksource with periodic clockevent
  mips: fix cacheinfo
  netfilter: ebtables: fix a memory leak bug in compat
  ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks
  bonding: Force slave speed check after link state recovery for 802.3ad
  can: dev: call netif_carrier_off() in register_candev()
  ASoC: Fail card instantiation if DAI format setup fails
  st21nfca_connectivity_event_received: null check the allocation
  st_nci_hci_connectivity_event_received: null check the allocation
  ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
  net: usb: qmi_wwan: Add the BroadMobi BM818 card
  qed: RDMA - Fix the hw_ver returned in device attributes
  isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in 
start_isoc_chain()
  netfilter: ipset: Fix rename concurrency with listing
  isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack
  perf bench numa: Fix cpu0 binding
  can: sja1000: force the string buffer NULL-terminated
  can: peak_usb: force the string buffer NULL-terminated
  net/ethernet/qlogic/qed: force the string buffer NULL-terminated
  NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
  HID: input: fix a4tech horizontal wheel custom usage
  SMB3: Kernel oops mounting a encryptData share with CONFIG_DEBUG_VIRTUAL
  net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
  net: hisilicon: make hip04_tx_reclaim non-reentrant
  net: hisilicon: fix hip04-xmit never return TX_BUSY
  net: hisilicon: Fix dma_map_single failed on arm64
  libata: have ata_scsi_rw_xlat() fail invalid passthrough requests
  libata: add SG safety checks in SFF pio transfers
  x86/lib/cpu: Address missing prototypes warning
  drm/vmwgfx: fix memory leak when too many retries have occurred
  perf ftrace: Fix failure to set cpumask when only one cpu is present
  perf cpumap: Fix writing to illegal memory in handling cpumap mask
  perf pmu-events: Fix missing "cpu_clk_unhalted.core" event
  selftests: kvm: Adding config fragments
  HID: wacom: correct misreported EKR ring values
  HID: wacom: Correct distance scale for 2nd-gen Intuos devices
  Revert "dm bufio: fix deadlock with loop device"
  ceph: don't try fill file_lock on unsuccessful GETFILELOCK reply
  libceph: fix PG split vs OSD (re)connect race
  drm/nouveau: Don't retry infinitely when receiving no data on i2c over AUX
  gpiolib: never report open-drain/source lines as 'input' to user-space
  userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx
  x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386
  x86/apic: Handle missing global clockevent gracefully
  x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
  x86/boot: Save fields explicitly, zero out everything else
  x86/boot: Fix boot regression caused by bootparam sanitizing
  dm kcopyd: always complete failed jobs
  dm btree: fix order of block initialization in btree_split_beneath
  dm space map metadata: fix missing store of apply_bops() return value
  dm table: fix invalid memory accesses with too high sector number
  dm zoned: improve error handling in reclaim
  dm zoned: improve error handling in i/o map code
  dm zoned: properly handle backing device failure
  genirq: Properly pair kobject_del() with kobject_add()
  mm, page_owner: handle THP splits correctly
  mm/zsmalloc.c: migration can leave pages in ZS_EMPTY indefinitely
  mm/zsmalloc.c: fix race condition in zs_destroy_pool
  xfs: fix missing ILOCK unlock when xfs_setattr_nonsize fails due to EDQUOT
  dm zoned: fix potential NULL dereference in dmz_do_reclaim()
  powerpc: Allow flush_(inval_)dcache_range to work across ranges >4GB
  can: mcp251x: add error check when wq alloc failed
  netfilter: ipset: Actually allow destination MAC address for hash:ip,mac sets 
too
  netfilter:

[Kernel-packages] [Bug 1840520] Re: Bionic update: upstream stable patchset 2019-08-16

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

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

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

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-16

  Ported from the following upstream stable releases:
  v4.14.139, v4.19.67

     from git://git.kernel.org/

  iio: adc: max9611: Fix misuse of GENMASK macro
  crypto: ccp - Fix oops by properly managing allocated structures
  crypto: ccp - Ignore tag length when decrypting GCM ciphertext
  usb: usbfs: fix double-free of usb memory upon submiturb error
  usb: iowarrior: fix deadlock on disconnect
  sound: fix a memory leak bug
  mmc: cavium: Set the correct dma max segment size for mmc_host
  mmc: cavium: Add the missing dma unmap when the dma has finished.
  loop: set PF_MEMALLOC_NOIO for the worker thread
  Input: synaptics - enable RMI mode for HP Spectre X360
  lkdtm: support llvm-objcopy
  crypto: ccp - Validate buffer lengths for copy operations
  crypto: ccp - Add support for valid authsize values less than 16
  perf annotate: Fix s390 gap between kernel end and module start
  perf db-export: Fix thread__exec_comm()
  perf record: Fix module size on s390
  usb: host: xhci-rcar: Fix timeout in xhci_suspend()
  usb: yurex: Fix use-after-free in yurex_delete
  can: rcar_canfd: fix possible IRQ storm on high load
  can: peak_usb: fix potential double kfree_skb()
  netfilter: nfnetlink: avoid deadlock due to synchronous request_module
  vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn
  netfilter: Fix rpfilter dropping vrf packets by mistake
  netfilter: nft_hash: fix symhash with modulus one
  scripts/sphinx-pre-install: fix script for RHEL/CentOS
  iscsi_ibft: make ISCSI_IBFT dependson ACPI instead of ISCSI_IBFT_FIND
  mac80211: don't warn about CW params when not using them
  hwmon: (nct6775) Fix register address and added missed tolerance for nct6106
  drm: silence variable 'conn' set but not used
  cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init()
  s390/qdio: add sanity checks to the fast-requeue path
  ALSA: compress: Fix regression on compressed capture streams
  ALSA: compress: Prevent bypasses of set_params
  ALSA: compress: Don't allow paritial drain operations on capture streams
  ALSA: compress: Be more restrictive about when a drain is allowed
  perf tools: Fix proper buffer size for feature processing
  perf probe: Avoid calling freeing routine multiple times for same pointer
  drbd: dynamically allocate shash descriptor
  ACPI/IORT: Fix off-by-one check in iort_dev_find_its_id()
  ARM: davinci: fix sleep.S build error on ARMv4
  scsi: megaraid_sas: fix panic on loading firmware crashdump
  scsi: ibmvfc: fix WARN_ON during event pool release
  scsi: scsi_dh_alua: always use a 2 second delay before retrying RTPG
  test_firmware: fix a memory leak bug
  tty/ldsem, locking/rwsem: Add missing ACQUIRE to read_failed sleep loop
  perf/core: Fix creating kernel counters for PMUs that override event->cpu
  HID: sony: Fix race condition between rumble and device remove.
  can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices
  can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices
  hwmon: (nct7802) Fix wrong detection of in4 presence
  drm/i915: Fix wrong escape clock divisor init for GLK
  ALSA: firewire: fix a memory leak bug
  ALSA: hda - Don't override global PCM hw info flag
  ALSA: hda - Workaround for crackled sound on AMD controller (1022:1457)
  mac80211: don't WARN on short WMM parameters from AP
  SMB3: Fix deadlock in validate negotiate hits reconnect
  smb3: send CAP_DFS capability during session setup
  NFSv4: Only pass the delegation to setattr if we're sending a truncate
  NFSv4: Fix an Oops in nfs4_do_setattr
  KVM: Fix leak vCPU's VMCS value into other pCPU
  mwifiex: fix 802.11n/WPA detection
  iwlwifi: don't unmap as page memory that was mapped as single
  iwlwifi: mvm: fix an out-of-bound access
  iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41
  iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT support
  iio: cros_ec_accel_legacy: Fix incorrect channel setting
  staging: android: ion: Bail out upon SIGKILL when allocating memory.
  x86/purgatory: Use

[Kernel-packages] [Bug 1841652] Re: Bionic update: upstream stable patchset 2019-08-27

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

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

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

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-08-27

  Ported from the following upstream stable releases:
  v4.14.140, v4.19.68

     from git://git.kernel.org/

  sh: kernel: hw_breakpoint: Fix missing break in switch statement
  mm/usercopy: use memory range to be accessed for wraparound check
  mm/memcontrol.c: fix use after free in mem_cgroup_iter()
  bpf: get rid of pure_initcall dependency to enable jits
  bpf: restrict access to core bpf sysctls
  bpf: add bpf_jit_limit knob to restrict unpriv allocations
  xtensa: add missing isync to the cpu_reset TLB code
  ALSA: hda - Apply workaround for another AMD chip 1022:1487
  ALSA: hda - Fix a memory leak bug
  ALSA: hda - Add a generic reboot_notify
  ALSA: hda - Let all conexant codec enter D3 when rebooting
  HID: holtek: test for sanity of intfdata
  HID: hiddev: avoid opening a disconnected device
  HID: hiddev: do cleanup in failure of opening a device
  Input: kbtab - sanity check for endpoint type
  Input: iforce - add sanity checks
  net: usb: pegasus: fix improper read if get_registers() fail
  netfilter: ebtables: also count base chain policies
  clk: at91: generated: Truncate divisor to GENERATED_MAX_DIV + 1
  clk: renesas: cpg-mssr: Fix reset control race condition
  xen/pciback: remove set but not used variable 'old_state'
  irqchip/gic-v3-its: Free unused vpt_page when alloc vpe table fail
  irqchip/irq-imx-gpcv2: Forward irq type to parent
  perf header: Fix divide by zero error if f_header.attr_size==0
  perf header: Fix use of unitialized value warning
  libata: zpodd: Fix small read overflow in zpodd_get_mech_type()
  drm/bridge: lvds-encoder: Fix build error while CONFIG_DRM_KMS_HELPER=m
  scsi: hpsa: correct scsi command status issue after reset
  scsi: qla2xxx: Fix possible fcport null-pointer dereferences
  ata: libahci: do not complain in case of deferred probe
  kbuild: modpost: handle KBUILD_EXTRA_SYMBOLS only for external modules
  arm64/efi: fix variable 'si' set but not used
  arm64: unwind: Prohibit probing on return_address()
  arm64/mm: fix variable 'pud' set but not used
  IB/core: Add mitigation for Spectre V1
  IB/mad: Fix use-after-free in ib mad completion handling
  drm: msm: Fix add_gpu_components
  ocfs2: remove set but not used variable 'last_hash'
  asm-generic: fix -Wtype-limits compiler warnings
  UBUNTU: [Packaging] update retpoline for get_order rework
  KVM: arm/arm64: Sync ICH_VMCR_EL2 back when about to block
  staging: comedi: dt3000: Fix signed integer overflow 'divider * base'
  staging: comedi: dt3000: Fix rounding up of timer divisor
  iio: adc: max9611: Fix temperature reading in probe
  USB: core: Fix races in character device registration and deregistraion
  usb: gadget: udc: renesas_usb3: Fix sysfs interface of "role"
  usb: cdc-acm: make sure a refcount is taken early enough
  USB: CDC: fix sanity checks in CDC union parser
  USB: serial: option: add D-Link DWM-222 device ID
  USB: serial: option: Add support for ZTE MF871A
  USB: serial: option: add the BroadMobi BM818 card
  USB: serial: option: Add Motorola modem UARTs
  bpf: fix bpf_jit_limit knob for PAGE_SIZE >= 64K
  arm64: ftrace: Ensure module ftrace trampoline is coherent with I-side
  netfilter: conntrack: Use consistent ct id hash calculation
  Input: psmouse - fix build error of multiple definition
  iommu/amd: Move iommu_init_pci() to .init section
  bnx2x: Fix VF's VLAN reconfiguration in reload.
  net/mlx4_en: fix a memory leak bug
  net/packet: fix race in tpacket_snd()
  sctp: fix the transport error_count check
  xen/netback: Reset nr_frags before freeing skb
  net/mlx5e: Only support tx/rx pause setting for port owner
  net/mlx5e: Use flow keys dissector to parse packets for ARFS
  team: Add vlan tx offload to hw_enc_features
  bonding: Add vlan tx offload to hw_enc_features
  mmc: sdhci-of-arasan: Do now show error message in case of deffered probe
  xfrm: policy: remove pcpu policy cache
  mm/hmm: fix bad subpage pointer in try_to_unmap_one
  mm: mempolicy: make the behavior consistent when MPOL_MF_MOVE* and

[Kernel-packages] [Bug 1840378] Re: Bionic update: upstream stable patchset 2019-08-15