[Kernel-packages] [Bug 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 17:26 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Stalled -- ready for review
  variant: debs

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

Title:
  precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 17:26 UTC
  reason:
promote-signing-to-proposed: Stalled -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846248/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[Richard Laager]

You have two datasets with mountpoint=/ (and canmount=on) which is going
to cause problems like this.

vms/roots/mate-1804 mountpoint  / local
vms/roots/mate-1804 canmountondefault
vms/roots/xubuntu-1804  mountpoint  / local
vms/roots/xubuntu-1804  canmountondefault

The normal setup for root-on-ZFS is for the initramfs to mount the root
filesystem, so it is supposed to be canmount=noauto.

You should do something like:
zfs set canmount=noauto vms/roots/mate-1804
zfs set canmount=noauto vms/roots/xubuntu-1804

Also, this too, though it isn't actually a problem here:
zfs set canmount=off vms/roots
zfs set mountpoint=none vms/roots

** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1845317] Re: Add new pci-id's for CML-S, ICL

[Timo Aaltonen]

the mesa part does what it says

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done 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/1845317

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1839557] Re: Hard Disk Freezing

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Hard Disk Freezing

Status in linux package in Ubuntu:
  Expired

Bug description:
  OS: Linux Mint 19.2
  Cinnamon Version: 4.2.3
  Kernel 4.15.0-55
  Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2
  Memory: 3.8 GB
  Hard disc 316.8 GB
  Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller.

  Issue Description: When I start the notebook and put the password in
  login screen and tap enter the computer doesn't responds and freeze
  the screen, sometimes the OS pass the screen login, but freeze and you
  cannot control or click anything. After it, I tried to change the
  version of Kernel to 5.0.0-23 and worked fine again. Please check it!
  The Kernel version 4.15.0-55 has serious problems with Hard Disc
  control.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839557/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[BertN45]

The output related to the mountpoints, see attachment

** Attachment added: "mountpoints"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+attachment/5295259/+files/mountpoints

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[BertN45]

Ignore the version numbers in the roots sub dataset, I did not change
the dataset names, but the system versions stored there is 19.10.

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

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

[Ubuntu Kernel Bot]

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

apport-collect 1847176

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

Title:
  [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No Sound on laptop speaker after upgrading ubuntu 19.04 a few days
  ago. Soundcard is found in alsamixer but only "dummy" is available in
  gnome settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 20:18:10 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.sku: 1KT13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847176/+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 1846016] Re: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive

[You-Sheng Yang]

Tried proposed patch https://patchwork.kernel.org/patch/11158395/ in
comment #38, still have this issue. However, that patch only removes -36
from the condition, and the firmware rev used for AC 3168 is -29. With
-29 removed from the conditions as well, there is no more errors.

** Tags added: ubuntu-certified

** Description changed:

  I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since
  yesterday.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.182
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:57:08 2019
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2019-07-23 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago)
+ 
+ --
+ Also found on Ubuntu-certified HP EliteDesk 800 G3 DM.

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

Title:
  iwlwifi regular scan timed out error sending statistics_cmd queue 0 is
  inactive

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

Bug description:
  I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since
  yesterday.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.182
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:57:08 2019
  Dependencies:

  InstallationDate: Installed on 2019-07-23 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago)

  --
  Also found on Ubuntu-certified HP EliteDesk 800 G3 DM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1846016/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[Richard Laager]

Can you provide the following details on your datasets' mountpoints.
zfs get mountpoint,canmount -t filesystem

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

[Daniel van Vugt]

It appears the kernel can't find any speaker outputs:

[   38.211994] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   38.211997] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   38.212000] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   38.212001] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   38.212002] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   38.212004] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
[   38.212006] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

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

** Also affects: alsa-driver (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/1847176

Title:
  [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  No Sound on laptop speaker after upgrading ubuntu 19.04 a few days
  ago. Soundcard is found in alsamixer but only "dummy" is available in
  gnome settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 20:18:10 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.sku: 1KT13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847176/+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 1847176] [NEW] [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago.
Soundcard is found in alsamixer but only "dummy" is available in gnome
settings.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  7 20:18:10 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-25 (681 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio 
fails to detect card
UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
dmi.bios.date: 08/07/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83A9
dmi.board.vendor: HP
dmi.board.version: KBC Version 39.32
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 13-ad1xx
dmi.product.sku: 1KT13UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco
-- 
[HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails 
to detect card
https://bugs.launchpad.net/bugs/1847176
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux 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 1846024] Re: bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags removed: block-proposed-bionic

** Tags removed: 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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
- phase: Ready for Testing
- phase-changed: Thursday, 03. October 2019 22:35 UTC
+ phase: Ready for Promote to Updates
+ phase-changed: Tuesday, 08. October 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Pending -- ready to copy
  replaces: bug 1844385
  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/1846024

Title:
  bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
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 Bionic:
  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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Promote to Updates
  phase-changed: Tuesday, 08. October 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  replaces: bug 1844385
  variant: debs

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

[Khaled El Mously]

I don't think cert-testing applies here (though I could easily be
wrong). Setting certification testing status to "invalid".

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

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

Title:
  bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
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 Bionic:
  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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Promote to Updates
  phase-changed: Tuesday, 08. October 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  replaces: bug 1844385
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846024/+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 1835138] Re: MKTME: make encrypted memory accessible by kernel

[quanxian]

** Changed in: intel
   Status: New => Won't Fix

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

Title:
  MKTME: make encrypted memory accessible by kernel

Status in intel:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Direct mapping is not good for accessing encrypted pages as all memory is 
mapped with KeyID 0.

  We need the temporary mapping with correct KeyID. kmap()/kmap_atomic()
  API seems fill our needs.

  Target Release: 19.10
  Target Kernel: 5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835138/+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 1846616] Re: eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846641
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:25 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  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: 1846641
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:25 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846616/+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 1834410] Re: iTCO watchdog No Reboot bit needs to move from side band to a TCOBASE register bit

[quanxian]

b84398d6d7f900805662b1619223fd644d862d7c
da23b6faa8bf0f1c50a0700440e9ff3f52b3bd9a

v5.4

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

Title:
  iTCO watchdog No Reboot bit needs to move from side band to a TCOBASE
  register bit

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

Bug description:
  Description:
  CDF has the WDT No Reboot bit as bit one of P2SB.SBREG_BAR64 +CFh + Ch 
which is cannot be read from the OS.

  This issue manifest itself in Linux by a -EBUSY error when loading the 
iTCO_wdt driver.
  [   23.060317] intel_rapl: Found RAPL domain package
  [   23.068017] intel_rapl: RAPL package 0 domain package locked by BIOS
  [   23.080641] FAT-fs (sdb1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
  [   23.203352] iTCO_vendor_support: vendor-support=0
  [   23.220844] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
  [   23.221060] iTCO_wdt iTCO_wdt: can't request region for resource [mem 
0x00c5fffc-0x00c5]
  [   23.221072] iTCO_wdt: probe of iTCO_wdt failed with error -16
  [   23.224465] Adding 4194300k swap on /dev/mapper/rhel-swap.  Priority:-2 
extents:1 across:4194300k SSFS
  [   24.614448] XFS (dm-2): Mounting V5 Filesystem
  [   24.632588] XFS (dm-2): Starting recovery (logdev: internal)
  [   24.642160] XFS (dm-2): Ending recovery (logdev: internal)
  [   24.754306] RPC: Registered named UNIX socket transport module.
  [   24.760402] RPC: Registered udp transport module.
   
  In systems that have a WDAT table, this is not an issue as such table 
contains the watchdog information. However, Jacobsville will not have a WDAT 
table. Therefore, when creating the iTCO_wdt platform device (in 
drivers/i2c/busses/i2c-i801.c), we need to take care of the updated location.
   
  Please see attached document.

  This update will be available in Cedar Fork B0.

   
  This issue is being tracked in the HSD 
https://hsdes.intel.com/appstore/article/#/2007770607.

  Target Kernel: TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834410/+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 1846024] Re: bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** 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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Testing
  phase-changed: Thursday, 03. October 2019 22:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
  replaces: bug 1844385
  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/1846024

Title:
  bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Testing
  phase-changed: Thursday, 03. October 2019 22:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
  replaces: bug 1844385
  variant: debs

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

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846026
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Testing
  phase-changed: Thursday, 03. October 2019 22:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
  replaces: bug 1844385
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846024/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1759285.

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


On 2019-10-07T18:32:51+00:00 ali.sherif10 wrote:

Description of problem:
After installing Fedora 30, I found that vertical sensitivity is much higher 
than horizontal sensitivity.

Version-Release number: 1.14.1.

How reproducible:
Always, because I got it in Kubuntu 19.04 too.

Steps to Reproduce:
1. Install Fedora 30.

Actual results:
Vertical sensitivity is higher than horizontal sensitivity and moving the 
cursor horizontally is slow.

Expected results:
Vertical and horizontal touchpad speeds are proper.

Additional info:
Laptop: HP Pavilion g6.
I didn't have the problem in previous versions of distributions. I don't know 
exactly when it started.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/comments/25


** Changed in: libinput (Fedora)
   Status: Unknown => Confirmed

** Changed in: libinput (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in libinput package in Fedora:
  Confirmed

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  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 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1825499/+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 1846007] Re: bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

Title:
  bionic/linux-azure: 5.0.0-1022.23~18.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-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:
  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 Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Monday, 07. October 2019 21:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846007/+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 1847155] [NEW] Bionic update: upstream stable patchset 2019-10-07

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2019-10-07

Ported from the following upstream stable releases:
v4.14.147, v4.19.76
   v4.19.77

   from git://git.kernel.org/

Revert "Bluetooth: validate BLE connection interval updates"
powerpc/xive: Fix bogus error code returned by OPAL
IB/core: Add an unbound WQ type to the new CQ API
HID: prodikeys: Fix general protection fault during probe
HID: sony: Fix memory corruption issue on cleanup.
HID: logitech: Fix general protection fault caused by Logitech driver
HID: hidraw: Fix invalid read in hidraw_ioctl
mtd: cfi_cmdset_0002: Use chip_good() to retry in do_write_oneword()
crypto: talitos - fix missing break in switch statement
iwlwifi: mvm: send BCAST management frames to the right station
media: tvp5150: fix switch exit in set control handler
ASoC: fsl: Fix of-node refcount unbalance in fsl_ssi_probe_from_dt()
arm64: kpti: Whitelist Cortex-A CPUs that don't implement the CSV3 field
ALSA: hda - Add laptop imic fixup for ASUS M9V laptop
ALSA: hda - Apply AMD controller workaround for Raven platform
objtool: Clobber user CFLAGS variable
pinctrl: sprd: Use define directive for sprd_pinconf_params values
power: supply: sysfs: ratelimit property read error message
irqchip/gic-v3-its: Fix LPI release for Multi-MSI devices
f2fs: check all the data segments against all node ones
PCI: hv: Avoid use of hv_pci_dev->pci_slot after freeing it
blk-mq: move cancel of requeue_work to the front of blk_exit_queue
Revert "f2fs: avoid out-of-range memory access"
dm zoned: fix invalid memory access
f2fs: fix to do sanity check on segment bitmap of LFS curseg
drm: Flush output polling on shutdown
net: don't warn in inet diag when IPV6 is disabled
ACPI: video: Add new hw_changes_brightness quirk, set it on PB Easynote MZ35
xfs: don't crash on null attr fork xfs_bmapi_read
Bluetooth: btrtl: Additional Realtek 8822CE Bluetooth devices
f2fs: use generic EFSBADCRC/EFSCORRUPTED
arcnet: provide a buffer big enough to actually receive packets
cdc_ncm: fix divide-by-zero caused by invalid wMaxPacketSize
macsec: drop skb sk before calling gro_cells_receive
net/phy: fix DP83865 10 Mbps HDX loopback disable function
net: qrtr: Stop rx_worker before freeing node
net/sched: act_sample: don't push mac header on ip6gre ingress
net_sched: add max len check for TCA_KIND
openvswitch: change type of UPCALL_PID attribute to NLA_UNSPEC
ppp: Fix memory leak in ppp_write
sch_netem: fix a divide by zero in tabledist()
skge: fix checksum byte order
usbnet: ignore endpoints with invalid wMaxPacketSize
usbnet: sanity checking of packet sizes and device mtu
net/mlx5: Add device ID of upcoming BlueField-2
mISDN: enforce CAP_NET_RAW for raw sockets
appletalk: enforce CAP_NET_RAW for raw sockets
ax25: enforce CAP_NET_RAW for raw sockets
ieee802154: enforce CAP_NET_RAW for raw sockets
nfc: enforce CAP_NET_RAW for raw sockets
ALSA: hda: Flush interrupts on disabling
regulator: lm363x: Fix off-by-one n_voltages for lm3632 ldo_vpos/ldo_vneg
ASoC: sgtl5000: Fix charge pump source assignment
dmaengine: bcm2835: Print error in case setting DMA mask fails
leds: leds-lp5562 allow firmware files up to the maximum length
media: dib0700: fix link error for dibx000_i2c_set_speed
media: mtk-cir: lower de-glitch counter for rc-mm protocol
media: exynos4-is: fix leaked of_node references
media: hdpvr: Add device num check and handling
media: i2c: ov5640: Check for devm_gpiod_get_optional() error
sched/fair: Fix imbalance due to CPU affinity
sched/core: Fix CPU controller for !RT_GROUP_SCHED
x86/reboot: Always use NMI fallback when shutdown via reboot vector IPI fails
x86/apic: Soft disable APIC before initializing it
ALSA: hda - Show the fatal CORB/RIRB error more clearly
ALSA: i2c: ak4xxx-adda: Fix a possible null pointer dereference in 
build_adc_controls()
EDAC/mc: Fix grain_bits calculation
media: iguanair: add sanity checks
base: soc: Export soc_device_register/unregister APIs
ALSA: usb-audio: Skip bSynchAddress endpoint check if it is invalid
ia64:unwind: fix double free for mod->arch.init_unw_table
EDAC/altera: Use the proper type for the IRQ status bits
ASoC: rsnd: don't call clk_get_rate() under atomic context
md/raid1: end bio when the device faulty
md: don't call spare_active in md_reap_sync_thread if all member devices can't 
work
md: don't set In_sync if array is frozen
ACPI / processor: don't print errors for processorIDs == 0xff
EDAC, pnd2: Fix ioremap() size in dnv_rd_reg()
efi: cper: 

[Kernel-packages] [Bug 1846007] Re: bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Security
- phase-changed: Monday, 07. October 2019 20:01 UTC
+ phase: Promote to Security
+ phase-changed: Monday, 07. October 2019 21:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Pending -- ready to copy
+   promote-to-security: Ongoing -- packages not yet published
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

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

** 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: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Security
- phase-changed: Monday, 07. October 2019 21:35 UTC
+ phase: Complete
+ phase-changed: Monday, 07. October 2019 21:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  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 Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Monday, 07. October 2019 21:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846007/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Monday, 07. October 2019 13:55 UTC
+ phase: Testing
+ phase-changed: Monday, 07. October 2019 21:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 07. October 2019 21:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846078/+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 1846007] Re: bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  In Progress
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 Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Security
  phase-changed: Monday, 07. October 2019 21:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Ongoing -- packages not yet published
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846007/+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 1847151] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29),
  my laptop's touchpad is no longer detected as a device. This is a new
  problem.

  Contents of /proc/bus/input/devices attached.

  Following directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss3353 F pulseaudio
   /dev/snd/controlC0:  pss3353 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct  7 14:14:13 2019
  InstallationDate: Installed on 2019-04-24 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
  dmi.bios.date: 10/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17B7IMS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17B7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17B7IMS.10F:bd10/03/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS73 Stealth 8RF
  dmi.product.sku: 17B7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-04-25T10:50:34.601584

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847151/+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 1847151] [NEW] Touchpad not detected

[Paul S. Strauss]

Public bug reported:

After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29), my
laptop's touchpad is no longer detected as a device. This is a new
problem.

Contents of /proc/bus/input/devices attached.

Following directions from
https://wiki.ubuntu.com/DebuggingTouchpadDetection

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pss3353 F pulseaudio
 /dev/snd/controlC0:  pss3353 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Mon Oct  7 14:14:13 2019
InstallationDate: Installed on 2019-04-24 (166 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
dmi.bios.date: 10/03/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17B7IMS.10F
dmi.board.asset.tag: Default string
dmi.board.name: MS-17B7
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17B7IMS.10F:bd10/03/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GS
dmi.product.name: GS73 Stealth 8RF
dmi.product.sku: 17B7.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2019-04-25T10:50:34.601584

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


** Tags: amd64 apport-bug disco

** Attachment added: "Contents of /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1847151/+attachment/5295212/+files/devices

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29),
  my laptop's touchpad is no longer detected as a device. This is a new
  problem.

  Contents of /proc/bus/input/devices attached.

  Following directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss3353 F pulseaudio
   /dev/snd/controlC0:  pss3353 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct  7 14:14:13 2019
  InstallationDate: Installed on 2019-04-24 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
  

[Kernel-packages] [Bug 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Promote to Proposed
- phase-changed: Monday, 07. October 2019 14:01 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 07. October 2019 20:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Signing signed:building
+   promote-signing-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1846108

Title:
  bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 07. October 2019 20:32 UTC
  reason:
promote-signing-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/1846108/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** 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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Monday, 07. October 2019 15:11 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 07. October 2019 20:33 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Signing signed:building
+   promote-signing-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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1846122

Title:
  trusty/linux-azure: 4.15.0-1061.66~14.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 20:33 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

[Ubuntu Kernel Bot]

** 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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-to-proposed: Ongoing -- package copied to Signing signed:building
  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/1846108

Title:
  bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Signing signed:building
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+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 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC
  address pass through does not work with a Lenovo Thunderbolt 3
  Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  
  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+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 1845818] Re: arm64: system does not boot after installing linux-generic-hwe-18.04-edge/bionic-proposed

[Patricia Domingues]

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

adding console log

** Attachment added: "console_log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845818/+attachment/5295197/+files/gigabyte_bionic_hwe-edge-proposed_console_log

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

Title:
  arm64: system does not boot after installing linux-generic-
  hwe-18.04-edge/bionic-proposed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description: 
  system does not boot after installing 
linux-generic-hwe-18.04-edge/bionic-proposed

  System:
  Board Model:gbt-mt30
  Board name: MT30-GS1-00
  System name:R120-T33-00
  SKU:   CN8890-2000BG2601-AAP-Y-G

  1) Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-23-generic aarch64)
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  2) ((enable -proposed archive))
  linux-generic-hwe-18.04-edge:
    Installed: 5.0.0.23.79
    Candidate: 5.3.0.12.83
    Version table:
   5.3.0.12.83 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 
Packages
   *** 5.0.0.23.79 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.0.0.20.76 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 
Packages

  3)
  a. install linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 
[upgradable from: 5.0.0.23.79]
  b. reboot
  c. ssh into the system

  4)
  a. installed linux-generic-hwe-18.04-edge/bionic-proposed
  b. system does not boot

  ```
  linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 [upgradable 
from: 5.0.0.23.79]
    Complete Generic Linux kernel and headers
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845818/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-to-proposed: Ongoing -- package copied to Signing signed:building
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1061.66~14.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Signing signed:building
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846122/+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 1846007] Re: bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   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: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Security
- phase-changed: Monday, 07. October 2019 07:55 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 07. October 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1022.23~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  Confirmed
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 Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846009
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Security
  phase-changed: Monday, 07. October 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-azure-edge: bug 1846005
bionic/linux-azure/azure-kernel: bug 1846004
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846007/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846078/+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 1847139] [NEW] [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04

[Joseph Salisbury]

Public bug reported:

Microsoft would like to request the following mainline commit be added to 
linux-azure 16.04 and 18.04:
f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain 
numbers

This commit was added to mainline in v5.4-rc1~63^2~8^2

This was recommended by Azure host team, the bytes 4, 5 have more
uniqueness(info entropy) than bytes 8, 9, so we should use them as the
PCI domain numbers.

This patch should be added to both 16.04 and 18.04 images.

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

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

Title:
  [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04
  and 18.04

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Microsoft would like to request the following mainline commit be added to 
linux-azure 16.04 and 18.04:
  f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain 
numbers

  This commit was added to mainline in v5.4-rc1~63^2~8^2

  This was recommended by Azure host team, the bytes 4, 5 have more
  uniqueness(info entropy) than bytes 8, 9, so we should use them as the
  PCI domain numbers.

  This patch should be added to both 16.04 and 18.04 images.

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

[poprocks]

This driver (along with necessary alsa ucm files) as now included with
5.3.x is working on my system (vanilla 5.3.4). I'd recommend closing
this bug as FIXED.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1827822] Re: kernel null pointer dereference

[Darin]

Thanks for the response. What version of memtest did you run and how
long did you have to run it? You ended up having a bad stick of ram? Did
you have to test each one individually?

I just built this PC a few months ago and after building ran memtest for
a whole day without problem but maybe I'll have to try it again. My log
mentions amdgpu after the crash each time so it may be a problem with
the graphics card or amdgpu driver. There are a few similar bug posts
I've found indicating it might be an amdgpu driver issue. Here are a
few.

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

https://bugs.freedesktop.org/show_bug.cgi?id=106194

https://bugs.freedesktop.org/show_bug.cgi?id=111234

** Bug watch added: Linux Kernel Bug Tracker #204181
   https://bugzilla.kernel.org/show_bug.cgi?id=204181

** Bug watch added: freedesktop.org Bugzilla #106194
   https://bugs.freedesktop.org/show_bug.cgi?id=106194

** Bug watch added: freedesktop.org Bugzilla #111234
   https://bugs.freedesktop.org/show_bug.cgi?id=111234

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

Title:
  kernel null pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System started freezing up a couple days ago.  After the latest one, I
  looked at the syslog file and found what appears to be a kernel bug
  report.

  May  5 18:06:03 corbin-goul kernel: [ 4650.769677] BUG: unable to handle 
kernel NULL pointer dereference at 0008
  May  5 18:06:03 corbin-goul kernel: [ 4650.769694] IP: rm_hole+0x19/0x70 [drm]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769696] PGD 0 P4D 0 
  May  5 18:06:03 corbin-goul kernel: [ 4650.769698] Oops: 0002 [#1] SMP PTI
  May  5 18:06:03 corbin-goul kernel: [ 4650.769700] Modules linked in: 
nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_generic 
snd_hda_intel snd
  _hda_codec kvm snd_hda_core snd_hwdep snd_pcm irqbypass mei_me intel_cstate 
mei intel_rapl_perf snd_seq_midi input_leds snd_seq_midi_event serio_raw 
snd_rawmidi snd_seq snd_seq_device snd_timer lpc_ich snd shpchp soundcore 
mac_hid s
  ch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq a
  sync_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
i915
  May  5 18:06:03 corbin-goul kernel: [ 4650.769733]  aesni_intel i2c_algo_bit 
aes_x86_64 crypto_simd drm_kms_helper glue_helper cryptd syscopyarea 
sysfillrect sysimgblt r8169 fb_sys_fops ahci mii drm libahci sata_inic162x video
  May  5 18:06:03 corbin-goul kernel: [ 4650.769743] CPU: 0 PID: 8713 Comm: 
kworker/0:0 Not tainted 4.15.0-48-generic #51-Ubuntu
  May  5 18:06:03 corbin-goul kernel: [ 4650.769744] Hardware name: Gigabyte 
Technology Co., Ltd. H87M-D3H/H87M-D3H, BIOS F3 04/24/2013
  May  5 18:06:03 corbin-goul kernel: [ 4650.769770] Workqueue: events 
__i915_gem_free_work [i915]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769778] RIP: 
0010:rm_hole+0x19/0x70 [drm]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769779] RSP: 0018:95fb81f2bd20 
EFLAGS: 00010202
  May  5 18:06:03 corbin-goul kernel: [ 4650.769780] RAX:  RBX: 
89d51f1382c0 RCX: 
  May  5 18:06:03 corbin-goul kernel: [ 4650.769781] RDX:  RSI: 
89d765cf8b40 RDI: 89d51f138318
  May  5 18:06:03 corbin-goul kernel: [ 4650.769782] RBP: 95fb81f2bd28 R08: 
89d5e7b71bc0 R09: 
  May  5 18:06:03 corbin-goul kernel: [ 4650.769783] R10: 95fb81f2bde0 R11: 
0001 R12: 89d765cf8b00
  May  5 18:06:03 corbin-goul kernel: [ 4650.769784] R13:  R14: 
89d51f1382e0 R15: 89d75f6c37c8
  May  5 18:06:03 corbin-goul kernel: [ 4650.769786] FS:  
() GS:89d77e20() knlGS:
  May  5 18:06:03 corbin-goul kernel: [ 4650.769787] CS:  0010 DS:  ES: 
 CR0: 80050033
  May  5 18:06:03 corbin-goul kernel: [ 4650.769788] CR2: 0008 CR3: 
0002eac0a002 CR4: 001606f0
  May  5 18:06:03 corbin-goul kernel: [ 4650.769789] Call Trace:
  May  5 18:06:03 corbin-goul kernel: [ 4650.769797]  
drm_mm_remove_node+0x29d/0x360 [drm]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769801]  ? 
__internal_add_timer+0x1f/0x60
  May  5 18:06:03 corbin-goul kernel: [ 4650.769816]  
i915_vma_remove+0x3a/0x100 [i915]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769830]  
i915_vma_unbind+0x1cd/0x370 [i915]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769843]  i915_vma_close+0x7d/0xa0 
[i915]
  May  5 18:06:03 corbin-goul kernel: [ 4650.769856]  

[Kernel-packages] [Bug 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

[Seiichi Nakashima]

Today at i3-7100 PC, I update software-updater.
I update three partitions(sda1, sda2, sda3),
sda4 partition stayed ubuntu-18.04.2.

at sda1 and sda3 partitions, each ubuntu-18.04.3 
purple screen blink not occur to use software-updater.
but sda2 purple screen blink occur at reboot.

I use advancd options for ubuntu at grub,
ubuntu, with Linux 5.0.0-31-generic (recovery mode).
and next time reboot, start up normal.

I found purple screen occur that do not display mouse marker.
until dot changing red to white, mouse marker display at screen,
purple screen not occur.

-- 
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
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 

[Kernel-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Sherif]

** Bug watch added: Red Hat Bugzilla #1759285
   https://bugzilla.redhat.com/show_bug.cgi?id=1759285

** Also affects: libinput (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1759285
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in libinput package in Fedora:
  Unknown

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  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 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1825499/+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 1845355] Re: Support Hi1620 zip hw accelerator

[dann frazier]

Verification:

ubuntu@kreiken:~$ cat /proc/version
Linux version 5.0.0-32-generic (buildd@bos02-arm64-021) (gcc version 7.4.0 
(Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #34~18.04.1-Ubuntu SMP Wed Oct 2 
22:12:13 UTC 2019
ubuntu@kreiken:~$ dmesg | grep zip
[   30.558846] hisi_zip :75:00.0: enabling device ( -> 0002)
[   30.574972] hisi_zip :b5:00.0: enabling device ( -> 0002)

** Also affects: kunpeng920/upstream-kernel
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/ubuntu-18.04-hwe
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/ubuntu-19.04
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/ubuntu-19.10
   Importance: Undecided
   Status: New

** Tags removed: verification-needed-disco
** Tags added: verification-done-disco

** Changed in: kunpeng920/upstream-kernel
   Status: New => Fix Committed

** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.4

** Changed in: kunpeng920/ubuntu-19.10
   Status: New => Fix Committed

** Changed in: kunpeng920/ubuntu-19.04
   Status: New => Fix Committed

** Changed in: kunpeng920/ubuntu-19.10
Milestone: None => ubuntu-19.10-ga

** Changed in: kunpeng920/ubuntu-19.04
Milestone: None => ubuntu-19.04-sru-8

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: New => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.3-sru-4

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

Title:
  Support Hi1620 zip hw accelerator

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

  [Test Case]
  ubuntu@scobee:~$ dmesg | grep zip
  [   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
  [   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
  ubuntu@scobee:~$ lspci | grep ZIP
  75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)

  [Fix]
  263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon 
QM module
  dfed0098ab91f crypto: hisilicon - add hardware SGL support
  62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
  79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
  8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
  72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
  ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
  00ae05db583a7 crypto: hisilicon - fix kbuild warnings
  db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
  5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
  902f0babf5457 crypto: hisilicon - add missing single_release
  1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
  b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
  62a9d9fc7a210 crypto: hisilicon - Fix return value check in 
hisi_zip_acompress()
  bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning

  [Regression Risk]
  This is a new driver which will only load automatically on systems that 
expose a supported PCI device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1845355/+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 1846096] Re: bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846097
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 04. October 2019 05:51 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1846096

Title:
  bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846097
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 04. October 2019 05:51 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/1846096/+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 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

[Kai-Heng Feng]

Cleaned up patch to make it upstreamable. Only compiled tested.

** Patch added: "lenovo-dock-macpassthru.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+attachment/5295180/+files/lenovo-dock-macpassthru.patch

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

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC
  address pass through does not work with a Lenovo Thunderbolt 3
  Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  
  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+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 1845355] Re: Support Hi1620 zip hw accelerator

[dann frazier]

** Also affects: kunpeng920
   Importance: Undecided
   Status: New

** Changed in: kunpeng920
   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/1845355

Title:
  Support Hi1620 zip hw accelerator

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

Bug description:
  [Impact]
  The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

  [Test Case]
  ubuntu@scobee:~$ dmesg | grep zip
  [   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
  [   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
  ubuntu@scobee:~$ lspci | grep ZIP
  75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)

  [Fix]
  263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon 
QM module
  dfed0098ab91f crypto: hisilicon - add hardware SGL support
  62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
  79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
  8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
  72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
  ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
  00ae05db583a7 crypto: hisilicon - fix kbuild warnings
  db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
  5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
  902f0babf5457 crypto: hisilicon - add missing single_release
  1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
  b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
  62a9d9fc7a210 crypto: hisilicon - Fix return value check in 
hisi_zip_acompress()
  bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning

  [Regression Risk]
  This is a new driver which will only load automatically on systems that 
expose a supported PCI device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1845355/+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 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** 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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
- phase: Promote to Proposed
- phase-changed: Monday, 07. October 2019 15:25 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 07. October 2019 17:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Signing signed:depwait
+   promote-signing-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-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1846248

Title:
  precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 17:26 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846248/+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 1846219] Re: Revert ESE DASD discard support

[Frank Heimes]

Transferring comment #19 from LP 1830731 to this bug, too - mainly for 
sforshee's awareness:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830731

--- Comment From jan.hoepp...@de.ibm.com 2019-10-07 12:18 EDT---
(In reply to comment #24)
> Stefan, do you also plan to revert it from upstream - or what's the plan
> there?

I saw that you guys reverted the patch with LP1846219 already. But for
the sake of completeness, Stefan reverted the patch for upstream as
well:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=964ce509e2ded52c1a61ad86044cc4d70abd9eb8

Regards,
Jan

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

Title:
  Revert ESE DASD discard support

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * Under certain conditions, the discard operation on the new ESE DASD
  may lead to data corruption.

  [Test Case]

   * Internal IBM testing

  [Regression Potential]

   * ESE DASD / thin provisioning, is the a new subtype of DASD drives
  specific to s390 architecture. The fix is to not expose discard
  availability to the kernel, to prevent utilising discard.

  [Other Info]
   
   * Comments from the thin-provisioning feature bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830731

  
  Comment from Jan Hoeppner 2019-09-24 07:16:57 CDT

  The thin provisioning feature introduces an IOCTL and the discard
  support to allow userspace tools and filesystems to release unused and
  previously allocated space respectively.

  During some internal performance improvements and further tests, the
  release of allocated space revealed some issues that may lead to data
  corruption in some configurations when filesystems are mounted with
  discard support enabled.

  As we're working on a fix and trying to clarify the situation, it is highly 
recommended at this point to _not_ enable discard for any filesystem
  when working with ESE DASDs.
  mkfs should also be called with discard disabled for ESE DASDs
  (e.g. mkfs.ext4 -E nodiscard /dev/dasdX).

  Fixes and clarifications will be provided as soon as possible.

  Regards,
  Jan

  --- Comment From stefan.haberl...@de.ibm.com 2019-10-01 09:15
  EDT---

  In addition to Jan's update to _not_ enable discard support I would
  recommend to completely revert the patch:

  7e64db1597fe114b83fe17d0ba96c6aa5fca419a s390/dasd: Add discard
  support for ESE volumes

  to prevent the user from enabling the discard support for DASD devices.
  This patch will also be reverted upstream until further clarification.

  Regards,
  Stefan

   xnox 

  Ubuntu enables discard by default in all the installers, all
  filesystems, and all layers (e.g. mdadm/lvm/luks discard).

  Assumption until now, has been that it is harmless, when underlying
  storage doesn't support discard and always non-harmful when it is
  supported.

  I agree, we should revert discard support for ESE volumes in Ubuntu
  for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1846219/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846078/+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 1840161] Re: Very severe regression in ZFS 0.7.12 in 18.04.3

[Halfwalker]

I can confirm on a Lenovo M920S and Lenovo Thinkpad X1 Carbon, both with
18.04.3 and zfs package version 0.7.5-1ubuntu16.6

See https://github.com/zfsonlinux/zfs/issues/9147#issuecomment-539055281

** Bug watch added: Github Issue Tracker for ZFS #9147
   https://github.com/zfsonlinux/zfs/issues/9147

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

Title:
  Very severe regression in ZFS 0.7.12 in 18.04.3

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  ZFS version 0.7.12 has a documented very severe regression on sending
  and receiving datasets with dnodesize=auto set on the dataset (not
  present in 0.7.9 or 0.8.1). This manifests itself primarily when
  sending and receiving datasets with lots of files, such as happens if
  root is on ZFS. This issue has been documented on the ZFSonlinux git
  repositories in issues:

  https://github.com/zfsonlinux/zfs/issues/9147

  and

  https://github.com/zfsonlinux/zfs/issues/8458

  Since 0.7.12 was just brought into 18.04.3, this regression is now
  affecting LTS. I'm opening this issue in the hopes that the fix is
  backported to the LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1840161/+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 1830731] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From jan.hoepp...@de.ibm.com 2019-10-07 12:18 EDT---
(In reply to comment #24)
> Stefan, do you also plan to revert it from upstream - or what's the plan
> there?

I saw that you guys reverted the patch with LP1846219 already. But for
the sake of completeness, Stefan reverted the patch for upstream as
well:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=964ce509e2ded52c1a61ad86044cc4d70abd9eb8

Regards,
Jan

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

Title:
  [19.10 FEAT] Thin provisioning base support (kernel+390tools)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released

Bug description:
  Enable use of thin provisioned ECKD volumes.
  Efficient use of storage resources and reduced deployment time for ECKD 
volumes .

  Tentative Target is kernel 5.3 + s390tools
  Assumption from crystal balls
  merge window closes on Sunday, 2019-07-28 and release on Sunday, 2019-09-15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830731/+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 1838278] Re: zfs-initramfs wont mount rpool

[Server Team CI bot]

This bug is fixed with commit 489c0145 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=489c0145

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

Title:
  zfs-initramfs wont mount rpool

Status in curtin package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  1. Eoan

  2. http://archive.ubuntu.com/ubuntu eoan/main amd64 zfs-initramfs
  amd64 0.8.1-1ubuntu7 [23.1 kB]

  3. ZFS rootfs rpool is mounted at boot

  4. Booting an image with a rootfs rpool:

  [0.00] Linux version 5.2.0-8-generic (buildd@lgw01-amd64-015) (gcc 
version 9.1.0 (Ubuntu 9.1.0-6ubuntu2)) #9-Ubuntu SMP Mon Jul 8 13:07:27 UTC 
2019 (Ubuntu 5.2.0-8.9-generic 5.2.0)
  [0.00] Command line: 
BOOT_IMAGE=/ROOT/zfsroot@/boot/vmlinuz-5.2.0-8-generic 
root=ZFS=rpool/ROOT/zfsroot ro console=ttyS0

  
  Command: /sbin/zpool import -N   'rpool'
  Message: cannot import 'rpool': pool was previously in use from another 
system.
  Last accessed by ubuntu (hostid=d24775ba) at Mon Jul 29 05:21:19 2019
  The pool can be imported, use 'zpool import -f' to import the pool.
  Error: 1

  Failed to import pool 'rpool'.
  Manually import the pool and exit.

  
  Note, this works fine under Disco, 

  http://archive.ubuntu.com/ubuntu disco/main amd64 zfs-initramfs amd64
  0.7.12-1ubuntu5 [22.2 kB]

  [4.773077] spl: loading out-of-tree module taints kernel.  
  [4.777256] SPL: Loaded module v0.7.12-1ubuntu3
  [4.779433] znvpair: module license 'CDDL' taints kernel.
  [4.780333] Disabling lock debugging due to kernel taint
  [5.713830] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000, 
ZFS filesystem version 5
  Begin: Sleeping for ... done.
  Begin: Importing ZFS root pool 'rpool' ... Begin: Importing pool 'rpool' 
using defaults ... done.
  Begin: Mounting 'rpool/ROOT/zfsroot' on '/root//' ... done.

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

[Ubuntu Kernel Bot]

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

apport-collect 1847118

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

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

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

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

Title:
  PM / hibernate: fix potential memory corruption

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Disco:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  [Impact]

  A caching bug in the hibernation code can lead to potential memory
  corruptions on resume.

  The hibernation code is representing all the allocated pages in memory
  (pfn) using a list of extents, inside each extent it uses a radix tree
  and each node in the tree contains a bitmap. This structure is used to
  save the memory image to disk.

  To speed up lookups in this structure the kernel is caching the
  position of the previous lookup in the form (current_extent,
  current_node). However, if two consecutive lookups are distant enough
  from each other, the extent can change, but the kernel can still use
  the cached node (current_node), accessing the wrong bitmap and ending
  up saving to disk the wrong pfn's.

  [Test Case]

  Bug has been reproduced in Xenial and Bionic trying to hibernate a
  large instance with a lot of RAM (100GB+).

  But we also wrote a custom kernel module to better isolate the code
  that triggers the problem:
  https://code.launchpad.net/~arighi/+git/mybitmap

  This module has exactly the same code as the hibernation code, but it
  can be used as a fast test case to reproduce the problem without
  actually triggering a real hibernation/resume cycle.

  [Fix]

  This bug can be fixed by properly invalidating the cached pair
  (extent, node) when the next lookup falls in a different extent or a
  different node.

  [Regression Potential]

  The fix has been sent to the LKML for review/feedback
  (https://lkml.org/lkml/2019/9/25/393), we have not received any
  feedback so far, but the bug is pretty clear and well tested on the
  affected platforms. Moreover, the code is isolated to the hibernation
  area, so the overall regression potential is minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847118/+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 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker

[Dimitri John Ledkov]

** Also affects: debian-installer (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/1846641

Title:
  eoan/linux: 5.3.0-17.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Eoan:
  New
Status in linux source package in Eoan:
  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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 05. October 2019 01:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1846636
eoan/linux-aws: bug 1846613
eoan/linux-azure: bug 1846616
eoan/linux-gcp: bug 1846623
eoan/linux-kvm: bug 1846628
eoan/linux-oracle: bug 1846630
eoan/linux-raspi2: bug 1846611
eoan/linux-snapdragon: bug 1846634
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+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 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Stalled -- review FAILED
  replaces: bug 1844355
  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/1846018

Title:
  bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED
  replaces: bug 1844355
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+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 1846096] Re: bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker

[Ubuntu Kernel Bot]

** 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 --
  kernel-stable-master-bug: 1846097
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 04. October 2019 05:51 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa main:failed
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  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/1846096

Title:
  bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1846097
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 04. October 2019 05:51 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846096/+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 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

[Andy Whitcroft]

It seems that the binary packages coming out of linux-meta-oracle-edge
clash with those from linux-meta-oracle.

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => 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/1846018

Title:
  bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED
  replaces: bug 1844355
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+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 1847109] Re: [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number

[Frank Heimes]

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

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Status: Triaged => Confirmed

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Frank Heimes (frank-heimes)

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

Title:
  [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel:
  Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

  Description/Reproduction:
  The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

  # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
  event=0x00e9

  should be event=0x00e8

  Fix already available:
  commit 81507f38d427ebed3291a3c153a798937c998140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847109/+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 1847118] [NEW] PM / hibernate: fix potential memory corruption

[Andrea Righi]

Public bug reported:

[Impact]

A caching bug in the hibernation code can lead to potential memory
corruptions on resume.

The hibernation code is representing all the allocated pages in memory
(pfn) using a list of extents, inside each extent it uses a radix tree
and each node in the tree contains a bitmap. This structure is used to
save the memory image to disk.

To speed up lookups in this structure the kernel is caching the position
of the previous lookup in the form (current_extent, current_node).
However, if two consecutive lookups are distant enough from each other,
the extent can change, but the kernel can still use the cached node
(current_node), accessing the wrong bitmap and ending up saving to disk
the wrong pfn's.

[Test Case]

Bug has been reproduced in Xenial and Bionic trying to hibernate a large
instance with a lot of RAM (100GB+).

But we also wrote a custom kernel module to better isolate the code that
triggers the problem: https://code.launchpad.net/~arighi/+git/mybitmap

This module has exactly the same code as the hibernation code, but it
can be used as a fast test case to reproduce the problem without
actually triggering a real hibernation/resume cycle.

[Fix]

This bug can be fixed by properly invalidating the cached pair (extent,
node) when the next lookup falls in a different extent or a different
node.

[Regression Potential]

The fix has been sent to the LKML for review/feedback
(https://lkml.org/lkml/2019/9/25/393), we have not received any feedback
so far, but the bug is pretty clear and well tested on the affected
platforms. Moreover, the code is isolated to the hibernation area, so
the overall regression potential is minimal.

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

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

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

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

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

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

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

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

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

** Summary changed:

- PM / hibernate: fix potential memory corruption on hibernate
+ PM / hibernate: fix potential memory corruption

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

Title:
  PM / hibernate: fix potential memory corruption

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New

Bug description:
  [Impact]

  A caching bug in the hibernation code can lead to potential memory
  corruptions on resume.

  The hibernation code is representing all the allocated pages in memory
  (pfn) using a list of extents, inside each extent it uses a radix tree
  and each node in the tree contains a bitmap. This structure is used to
  save the memory image to disk.

  To speed up lookups in this structure the kernel is caching the
  position of the previous lookup in the form (current_extent,
  current_node). However, if two consecutive lookups are distant enough
  from each other, the extent can change, but the kernel can still use
  the cached node (current_node), accessing the wrong bitmap and ending
  up saving to disk the wrong pfn's.

  [Test Case]

  Bug has been reproduced in Xenial and Bionic trying to hibernate a
  large instance with a lot of RAM (100GB+).

  But we also wrote a custom kernel module to better isolate the code
  that triggers the problem:
  https://code.launchpad.net/~arighi/+git/mybitmap

  This module has exactly the same code as the hibernation code, but it
  can be used as a fast test case to reproduce the problem without
  actually triggering a real hibernation/resume cycle.

  [Fix]

  This bug can be fixed by properly invalidating the cached pair
  (extent, node) when the next lookup falls in a different extent or a
  different node.

  [Regression Potential]

  The fix has been sent to the LKML for review/feedback
  (https://lkml.org/lkml/2019/9/25/393), we have not received any
  feedback so far, but the bug is pretty clear and well tested on the
  affected platforms. Moreover, the code is isolated to the hibernation
  area, so the overall regression potential is minimal.

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

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

[Kernel-packages] [Bug 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:25 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Signing signed:depwait
  variant: debs

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

Title:
  precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:25 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Signing signed:depwait
  variant: debs

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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Promote to Proposed
- phase-changed: Friday, 04. October 2019 14:40 UTC
+ phase: Testing
+ phase-changed: Monday, 07. October 2019 15:52 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing 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/1846106

Title:
  bionic/linux-oem: 4.15.0-1058.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Monday, 07. October 2019 15:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846106/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1061.66~14.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

[gbhat]

Hi Tsuchiya/Verdre,

>- "cmd_timeout"
> This issue will occur after a second suspend like the dmesg log on
> >Comment#91 regardless of 2.4GHz/5GHz AP or power_save on/off


1. Command timeout after second suspend could be recreated in my Surface 4;

2. Logs were similar to the one in #91 & #92 by Verdre;

3. It is found that the command, which timed out did not reach the
firmware at all and am trying to understand more;

4. Once a command times out, driver dumps few scratch registers and also
it triggers the firmware dump; But I fail to get these in my device(I
don't know why, it is a different problem); So, I still fail to confirm
we are hitting same issue;

Note that, when the dump is uploaded to user-space, dmesg will say:
"== mwifiex dump information to /sys/class/devcoredump end"

Could you please share the dump(along with dmesg), which is saved in below 
file(it is automatically deleted after 5 minutes):

/sys/devices/virtual/devcoredump/devcd1/data


>- "Firmware wakeup failed"
This could also be recreated for the first time now; I kept Surface 4 connected 
to AP and PING overnight; But I have no much detail yet;

I will comeback soon on remaining two concerns you raised in comment#95;


Regards,
Ganapathi

Regards,
Ganapathi

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

[kitakar]

Created attachment 285391
[PATCH] mwifiex: debugfs: add entry for device_dump

This is a patch to add debugfs entry for device_dump.
Just to test device_dump functionality on Surface devices.

Usage:

  echo 1 | sudo tee /sys/kernel/debug/mwifiex/mlan0/device_dump

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1730924/+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 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 04. October 2019 17:41 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 07. October 2019 15:25 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:25 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

[kitakar]

> But I fail to get these in my device(I don't know why, it is a different
> problem); So, I still fail to confirm we are hitting same issue;

Yeah, the device_dump is also a problematic one on Surface devices.
It's reported that if_ops.device_dump() will cause lockups [1] (e.g. prevent 
system power off)

I also confirmed that by
1. adding debugfs entry for calling that function
2. and called the function via debugfs (echo 1 | sudo tee 
/sys/kernel/debug/mwifiex/mlan0/device_dump)
Sometimes I can get the device_dump log, sometimes I can't and it prevents 
system power off. I will post the patch which adds the debugfs entry to the 
next comment.

I will post the dump log (along with the dmesg log) as soon as I manage
to get the logs after wifi malfunctioning.

By the way, the user manual on
drivers/net/wireless/marvell/mwifiex/README describes that device_dump
can be obtained by `cat fw_dump` but the debugfs entry does not exist
anymore.


References:
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/comments/99
Comment #99 :  Bug #1730924 “Wifi does down “crash” in Surface Pro 4” : Bugs : 
linux package : 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/1730924

Title:
  Wifi does down "crash" in Surface Pro 4

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1730924/+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 1836261] Re: xfrm interface: several kernel panic

[Nicolas Dichtel]

root@dut-vm:~# ip netns add foo
root@dut-vm:~# ip netns add bar
root@dut-vm:~# ip -n foo netns set bar 0
root@dut-vm:~# ip -n foo link add xfrmi0 link-netnsid 0 type xfrm dev lo if_id 
23
root@dut-vm:~# ip -n bar link ls xfrmi0
Device "xfrmi0" does not exist.
root@dut-vm:~# ip -n foo link ls xfrmi0
2: xfrmi0@if1:  mtu 1500 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff link-netns bar

=> interface is correctly created and there is no backtrace in dmesg, OK


root@dut-vm:~# ip netns del foo
root@dut-vm:~# ip netns del bar
root@dut-vm:~# ip link add xfrm1 type xfrm dev lo if_id 1
root@dut-vm:~# ip link add xfrm2 type xfrm dev lo if_id 2
root@dut-vm:~# ip link set xfrm1 type xfrm dev lo if_id 2
RTNETLINK answers: File exists
root@dut-vm:~# ip -d link list dev xfrm1
7: xfrm1@lo:  mtu 1500 qdisc noop state DOWN mode DEFAULT group default 
qlen 1000
link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 
maxmtu 1500
xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 
65536 gso_max_segs 65535

=> if_id 0x1 and no backtrace in dmesg, OK


root@dut-vm:~# ip link add dummy type dummy
root@dut-vm:~# ip link add xfrm1 type xfrm dev dummy if_id 1
root@dut-vm:~# ip l d dummy
root@dut-vm:~# ip -d l ls xfrm1
10: xfrm1@if9:  mtu 1500 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
link/none 3a:90:dc:59:76:c6 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 
maxmtu 1500
xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 
65536 gso_max_segs 65535
root@dut-vm:~#

=> no refcnt pb, OK

Our internal tests suite is also OK.

** Tags removed: verification-needed-disco
** Tags added: verification-done-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/1836261

Title:
  xfrm interface: several kernel panic

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1836261

  [Impact]

  Upstream has recently received a number of bug fixes that resolve
  kernel panics, memory leaks, and list handling for virtual xfrm
  interfaces that were debuted in 4.19.

  [Test Case]

  3 of the 5 patches have test cases in their commit message for
  reproducing the fault they address.

  Another patch prevents including a stale name in the log files.

  And the other patch that doesn't have an explicit test case improves list
  handling.

  [Regression Potential]

  This patchset contains a nontrivial amount of changes. However, the
  heavier patches contain test cases that they resolve the regressions
  they were created for. They've been upstream since July and I don't
  see any follow up Fixes commits targeting these. The blast radius is
  "only" the xfrm interface but this is smoke tested and if any
  dependents rely on it for core functionality they might exercise it
  and would possibly notice any issues by now as well.

  Original bug description follows:
  

  There was several problems reported upstream:

  1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823

  2/ xfrm interface: avoid corruption on changelink
  http://patchwork.ozlabs.org/patch/1130240/

  3/ xfrm interface: ifname may be wrong in logs
  http://patchwork.ozlabs.org/patch/1130241/

  4/ xfrm interface: fix list corruption for x-netns
  http://patchwork.ozlabs.org/patch/1130385/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+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 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

[Matthias]

"Same Result" means it wakes up a few seconds after sleep. With
bluetooth disabled, it stays in sleep as expected.

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker

[Andy Whitcroft]

** 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-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1846248

Title:
  precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1846250
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:25 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

[Ubuntu Kernel Bot]

** 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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  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/1846108

Title:
  bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker

[Andy Whitcroft]

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

Title:
  trusty/linux-azure: 4.15.0-1061.66~14.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846122/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 04. October 2019 17:21 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1061.66~14.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1846123
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 15:11 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846122/+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 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Dave Chiluk]

@oddbjornk @cristofaro

Launchpad is not a forum.  Each bug is meant to solve one problem.  One
of you need to create a new bug for the new problem.  You are welcome to
reference or link this issue in that new bug though so whoever triages
it has a reference.

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1847109] [NEW] [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number

[bugproxy]

Public bug reported:

Kernel:
Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

Description/Reproduction:
The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

# cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
event=0x00e9

should be event=0x00e8

Fix already available:
commit 81507f38d427ebed3291a3c153a798937c998140

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-181639 severity-medium 
targetmilestone-inin18043

** Tags added: architecture-s39064 bugnameltc-181639 severity-medium
targetmilestone-inin18043

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel:
  Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

  Description/Reproduction:
  The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

  # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
  event=0x00e9

  should be event=0x00e8

  Fix already available:
  commit 81507f38d427ebed3291a3c153a798937c998140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847109/+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 1847109] [NEW] [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Kernel:
Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

Description/Reproduction:
The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

# cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
event=0x00e9

should be event=0x00e8

Fix already available:
commit 81507f38d427ebed3291a3c153a798937c998140

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-181639 severity-medium 
targetmilestone-inin18043
-- 
[Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number
https://bugs.launchpad.net/bugs/1847109
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux 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 1846616] Re: eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- eoan/linux-azure: 5.3.0-1001.1 -proposed tracker
+ eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

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

Title:
  eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  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: 1846641
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:25 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/1846616/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[BertN45]

I boot from ZFS so that datapool will be root mounted. That same
datapool has been used in the past exclusively for Virtual Machines,
later I added the datasets for the host OSes to the same datapool,
because they were at the begin of my SSHD. So that datapool contains
datasets with Virtualbox VMs and the root datasets for two Ubuntu OSes
Ubuntu Mate 19.10 and Xubuntu 19.10.

I plan to buy a NVME SSD (say 500 GB) and I would use that with a single
datapool also for both the Hosts OSes and  the Virtual Machines. The
other data (documents, movies, music etc) would remain on one or two
HDDs.

I have created the pools of course using the sudo or maybe even sudo -s, 
because I had to issue a number of privileged commands, since that creation 
time the datapools are mounted automatically by the system. 
I do not remember to have problems with the ZFS updates in 19.04 using the same 
datapools.

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1846616] Re: eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-eoan

** 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: 1846641
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 04. October 2019 17:41 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 07. October 2019 14:25 UTC
+ reason:
+   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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1846616

Title:
  eoan/linux-azure: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  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: 1846641
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:25 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/1846616/+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 1846106] Re: bionic/linux-oem: 4.15.0-1058.67 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Friday, 04. October 2019 14:40 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1846106

Title:
  bionic/linux-oem: 4.15.0-1058.67 -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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Friday, 04. October 2019 14:40 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846106/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

[Rik Mills]

Redditer trying an upgrade from disco -> eoan reported broken upgrade
due to this, and like in comment #34 I can reproduce this still.

So I think this a fix backported to 19,04 kernel is definitely required
before we release 19.10.

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in gcc-9 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Won't Fix
Status in xtables-addons package in Ubuntu:
  Won't Fix

Bug description:
  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1838921] Re: ability to install dkms without version checking and retire it when kernel fixed issue

[Alex Tu]

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

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

Title:
  ability to install dkms without version checking and retire it when
  kernel fixed issue

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  In Progress
Status in dkms source package in Bionic:
  Fix Committed
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  refer to https://github.com/dell/dkms/pull/98

  [Impact]
  to have a way for this case
  "user need to force install the dkms, but also would like to retire that dkms 
once kernel fixes the issue."
   - upstream patch : https://github.com/dell/dkms/pull/98

  [Test case]
  1. install the dkms package which already patched
  2. install a DKMS which has file content "{dkms name}_version-override" under 
/usr/share/dkms/modules_to_force_install/
 - the installation should ignore module version checking.

  3. update that installed DKMS to a new one which added OBSOLETE_BY in 
dkms.conf
 - on the kernel which version lower than OBSOLETE_BY, the dkms should be 
installed.
 - on the kernel which version higher than OBSOLETE_BY, the dkms should NOT 
be installed.

  [Regression potential]
  medium as it touched the version sanity. This change already there in 
upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+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 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 04. October 2019 23:17 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  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/1846108

Title:
  bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 07. October 2019 07:56 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

** 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

[Andy Whitcroft]

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

Title:
  bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846110
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 14:01 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

[Andy Whitcroft]

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

Title:
  bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1846079
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:55 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-azure-edge: bug 1846077
bionic/linux-azure/azure-kernel: bug 1846076
  variant: debs

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

[Ubuntu Kernel Bot]

** 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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Friday, 04. October 2019 14:40 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed 
signed:retry-needed
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  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/1846106

Title:
  bionic/linux-oem: 4.15.0-1058.67 -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: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Friday, 04. October 2019 14:40 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846106/+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 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 07. October 2019 03:50 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  replaces: bug 1844355
  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/1846018

Title:
  bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: bug 1844355
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+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 1847042] Re: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5

[monoi]

Possibly the same issue as this: https://lkml.org/lkml/2019/9/25/339

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

Title:
  Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP
  EliteBook 840 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Ubuntu 19.10 from 19.04.

  On first boot of 19.10, Kernel 5.3.0.13-generic crashed with an error
  in tpm_read_log_efi(), see screenshot. Disabling TPM in BIOS allowed
  successful boot of kernel 5.3.0.13-generic.

  Kernel 5.0.0-31-generic will boot 19.10 successfully, with or without
  TPM enabled in the BIOS.

  Hardware is HP EliteBook 840 G5. BIOS not most recent, cannot upgrade
  without installing Windows.

  ---

  $ lsb_release -rd

  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  $ apt-cache policy linux-generic

  linux-generic:
Installed: 5.3.0.13.14
Candidate: 5.3.0.13.14
Version table:
   *** 5.3.0.13.14 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847042/+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 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

[Andy Whitcroft]

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

Title:
  bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1846019
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Monday, 07. October 2019 13:35 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: bug 1844355
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02

[Colin Ian King]

The error: "zfs[9317]: cannot mount '/': directory is not empty" seems
to suggest that this is a root mounted zfs.  Is that so?

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

Title:
  19.10 ZFS Update failed on 2019-10-02

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb 
failed the same is true for zfs-zed and zfsutils-linux.
  The system still runs on 0.8.1-1ubuntu11_amd64.
  The first error message was about a failing mount and at the end it announced 
that all 3 modules were not updated.
  I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M 
and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1846012] Re: bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1846015
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Sunday, 06. October 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1846011
bionic/linux-gcp/gcp-kernel: bug 1846010
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846012/+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 1846012] Re: bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** 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: 1846015
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Sunday, 06. October 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1846011
bionic/linux-gcp/gcp-kernel: bug 1846010
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1846015
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Sunday, 06. October 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1846011
bionic/linux-gcp/gcp-kernel: bug 1846010
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846012/+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 1846019] Re: disco/linux-oracle: 5.0.0-1004.8 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** 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: 1846026
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 04. October 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1846018
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1004.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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: 1846026
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 04. October 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1846018
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846019/+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 1846019] Re: disco/linux-oracle: 5.0.0-1004.8 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  disco/linux-oracle: 5.0.0-1004.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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: 1846026
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 04. October 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1846018
  variant: debs

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

[Mauricio Faria de Oliveira]

Disco is now fix released with linux 5.0.0-31.33 (bionic: linux-hwe
5.0.0-31.33~18.04.1).

** Changed in: linux (Ubuntu Disco)
   Status: Fix Committed => 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/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:
  Fix Released
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 1841148] Re: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver

[Mauricio Faria de Oliveira]

Disco is now fix released with linux 5.0.0-31.33 (linux-hwe
5.0.0-31.33~18.04.1).

** Changed in: linux (Ubuntu Disco)
   Status: Fix Committed => 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/1841148

Title:
  Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and
  82579V using e1000e driver

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
Status in linux source package in Eoan:
  Fix Released

Bug description:
  Since linux-image-4.15.0-58-generic my ethernet connection fails to
  get a connection.

  The network connection constantly goes up and down. The issue has been
  reported by another user:

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

  Snippet from kern.log showing that the connection constantly goes up
  and down:

  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: 
up
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: 
attached
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent 
link down event.
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent 
link up event.
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: 
disabling the bridge on dev down
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: 
down
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: 
detached
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent 
link down event.
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent 
link up event.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: 
up
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: 
attached
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent 
link down event.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent 
link up event.
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: 
disabling the bridge on dev down
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: 
down
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: 
detached
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent 
link down event.
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent 
link up event.
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: 
up
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: 
attached
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent 
link down event.
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent 
link up event.
  Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: 
disabling the bridge on dev down
  Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: 
down
  Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: 
detached
  Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent 
link down event.
  Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent 
link up event.
  Aug 20 10:06:20 martijn-ThinkPad-P50 

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

[bugproxy]

--- Comment From cborn...@de.ibm.com 2019-10-07 08:31 EDT---
Same test (auxv) also works with bionic-proposed.
Linux t35lp61 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:22:41 UTC 2019 
s390x s390x s390x GNU/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/1842774

Title:
  Enhanced Hardware Support - Finalize Naming

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in qemu source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Fix Committed
Status in qemu source package in Disco:
  Triaged

Bug description:
  SRU Justification Kernel:
  =

  [Impact]

  * Add / activate support for IBM z15 and LinuxONE III systems

  [Fix]

  * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support
  for IBM z15 machines"

  [Test Case]

  * check and verify cpuinfo - regression testing is possible by
  Canonical/me

  * functional testing is currently only doable by IBM

  [Regression Potential]

  * There is regression potential with having new code in and the flags
  added/active

  * but the code changes are pretty straight forward, just add config,
  cases and defs

  * and are not used on existing systems, just on the new generation
  that is not yet out in the field

  [Other Info]

  * SRU of LP 1842916 merged with (this) LP 1842774

  
  ---

  SRU Template for qemu as the impact/scope is different
  ==

  [Impact]

  * Update naming of the new HW Generation

  * Now that the systems are released people might look for types matching 
the name and no one really knows "IBM 8561 GA1".

  * Help users to identify the cpu type by backporting the fix that sets the 
defined name.

  [Fix]

  * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca

  [Test Case]

  * qemu-system-s390x -cpu ? | grep gen15
  s390 gen15a-base IBM 8561 GA1(static, 
migration-safe)
  s390 gen15a  IBM 8561 GA1(migration-safe)
  s390 gen15b-base IBM 8562 GA1(static, 
migration-safe)
  s390 gen15b  IBM 8562 GA1(migration-safe)

  * With the fix gen15a should be called "IBM z15 GA1"

  [Regression Potential]

  * The only thing changing (for qemu) are some texts e.g. when showing CPU 
types. The cpu type itself that is used in e.g. scripts / commands will 
not change. Therefore the regression risk of the qemu change is next to 
none. The only I can think of is people grepping for the old ID in text 
output, but that seems theoretical and not important.

  [Other Info]

  * For an SRU perspective this is "nice to have" we will only do this 
"along" other higher impact SRUs.

  
  __

  This feature request will provide the final naming of the next machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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 1833474] Re: Radom & frequent total crashes since upgrade to 19.04

[G.M.]

Hi all,

I've managed to track down where the problem comes from.

CONTEXT

- I use one of my neighbors' access point/portal to access internet
(based on FON principle: https://en.wikipedia.org/wiki/Fon_(company)).

- Since the access point is not that close from my apartment, I baught and use 
an external Wifi adapter with a (supposed to be) 5DBi antenna. This is the 
exact following "ALFA" model:
https://www.dx.com/p/alfa-awus036nh-network-ralink-3070l-wifi-network-card-2000mw-alfa-wireless-wifi-usb-adapter-with-5dbi-antenna-white-2053330.html

- In order to be able to put this device outside my window, I plug it to my 
computer via a 2m USB armored cable, similar to this one (with the 
characteristic little bump / fuse?)
https://mpshop.tn/3035-thickbox_default/rallonge-usb-male-femelle.jpg
I tried with several cables (non-armored ones or longer cables, armored or 
not). All lead to kernel not recognizing the device or intermittent 
disconnection from the AP or disappearing of the device after a few minutes.  

The chipset is apparently detected as a RaLink and the kernel tells me it uses 
the 'rt2870.bin' firmware:
[27393.587771] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[27393.753513] usb 1-1: New USB device found, idVendor=148f, idProduct=3070, 
bcdDevice= 1.01
[27393.753519] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27393.753523] usb 1-1: Product: 802.11 n WLAN
[27393.753526] usb 1-1: Manufacturer: Ralink
[27393.753528] usb 1-1: SerialNumber: 1.0
[27393.883944] usb 1-1: reset high-speed USB device number 6 using xhci_hcd
[27394.044554] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 
detected
[27394.055744] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 0005 detected
[27394.056214] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[27394.098722] rt2800usb 1-1:1.0 wlx000f0032e9c8: renamed from wlan0
[27394.150888] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading 
firmware file 'rt2870.bin'
[27394.150937] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware 
detected - version: 0.36
[27395.779361] wlx000f0032e9c8: authenticate with e4:9e:12:cf:e8:09
[27395.790695] wlx000f0032e9c8: send auth to e4:9e:12:cf:e8:09 (try 1/3)
[27395.792593] wlx000f0032e9c8: authenticated
[27395.798527] wlx000f0032e9c8: associate with e4:9e:12:cf:e8:09 (try 1/3)
[27395.801965] wlx000f0032e9c8: RX AssocResp from e4:9e:12:cf:e8:09 
(capab=0x401 status=0 aid=1)
[27395.804884] wlx000f0032e9c8: associated
[27395.805216] IPv6: ADDRCONF(NETDEV_CHANGE): wlx000f0032e9c8: link becomes 
ready 

Under Linux (XUbuntu 19.04), everything works fine (detection of
networks/connection to networks/upload), apart the fact that
the computer totally freezes/crashes in less than 2 hours as soon as the
ALFA device is plugin. When I use the computer without the ALFA device
plugged, everything works fine (tested reaching a 12 days uptime!)

Under windows (10 1903) everything works fine whatever the conditions
(there's no crashes, even with the ALFA device plugged, tested reaching
24hrs uptime - sorry, I'm not able to use Windows more than that ;)...).

So my (informed) guess is that there's a bug either in Linux's RaLink
module or 'rt2870.bin' firmware.

How can I provide more details, so that the bug is corrected ?


PS: I don't see how this is not a security issue: a computer that freezes 
brutally and in a non recoverable manner (CTRL-ALT-DEL & SysReq are useless)
1) reflects a very big problem in some module/firmware code, that probably can 
be related to a buffer overflow of some kind which could be exploited 
locally/remotely to take control of the machine
2) has a very strong probability to lead to data corruption (as it is clear 
that apps/fs/disks are not shutdown correctly)
3) even if it is not the case, being potentially able to voluntarily (locally 
or remotely) execute the part of the code that crashes the machine, i.e. 
perform a Denial of Service, is very serious problem...

PS2: I'm aware that I use potentially chinese non-guenuine
devices/chipsets/cables and that can be the source of many problems.
However, the Linux kernel should, at worse, refuse to recognize/use the
device, but crashing after woking correctly a few hours is not an
acceptable 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/1833474

Title:
  Radom & frequent total crashes since upgrade to 19.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I'm using an ASUS X751L laptop for several years with no (=a few
  manageable) problem(s).

  Two weeks ago, I switched to Xunbuntu 19.04, by:
  - changing the lines in the /etc/sources.list
  - running apt-get dist-upgrade

  Since then, the computer randomly totally freezes ~twice a day. Even
  after another dist-upgrade this morning...

  
  When I say "totally freezes", I mean:
  - Mouse is 

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

[bugproxy]

--- Comment From cborn...@de.ibm.com 2019-10-07 08:11 EDT---
Functionality successfully tested fine on disco-proposed 5.0.0-32-generic 
#34-Ubuntu SMP Wed Oct 2 02:06:00 UTC 2019 s390x s390x s390x GNU/Linux

I can see z15 in the aux vector:

# gdb --quiet ls
Reading symbols from ls...
(No debugging symbols found in ls)
(gdb) start
Temporary breakpoint 1 at 0x45ae
Starting program: /usr/bin/ls

Temporary breakpoint 1, 0x02aa45ae in main ()
(gdb) info auxv
33   AT_SYSINFO_EHDR  System-supplied DSO's ELF header 0x3fffdffe000
16   AT_HWCAP Machine-dependent CPU capability hints 0x7
6AT_PAGESZSystem page size   4096
17   AT_CLKTCKFrequency of times()   100
3AT_PHDR  Program headers for program0x2aa0040
4AT_PHENT Size of program header entry   56
5AT_PHNUM Number of program headers  9
7AT_BASE  Base address of interpreter0x3fffdf8
8AT_FLAGS Flags  0x0
9AT_ENTRY Entry point of program 0x2aa6320
11   AT_UID   Real user ID   0
12   AT_EUID  Effective user ID  0
13   AT_GID   Real group ID  0
14   AT_EGID  Effective group ID 0
23   AT_SECUREBoolean, was exec setuid-like? 0
25   AT_RANDOMAddress of 16 random bytes 0x3fff73c
31   AT_EXECFNFile name of executable0x3ec 
"/usr/bin/ls"
15   AT_PLATFORM  String identifying platform0x3fff74c "z15"
0AT_NULL  End of vector  0x0

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

Title:
  Enhanced Hardware Support - Finalize Naming

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in qemu source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Fix Committed
Status in qemu source package in Disco:
  Triaged

Bug description:
  SRU Justification Kernel:
  =

  [Impact]

  * Add / activate support for IBM z15 and LinuxONE III systems

  [Fix]

  * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support
  for IBM z15 machines"

  [Test Case]

  * check and verify cpuinfo - regression testing is possible by
  Canonical/me

  * functional testing is currently only doable by IBM

  [Regression Potential]

  * There is regression potential with having new code in and the flags
  added/active

  * but the code changes are pretty straight forward, just add config,
  cases and defs

  * and are not used on existing systems, just on the new generation
  that is not yet out in the field

  [Other Info]

  * SRU of LP 1842916 merged with (this) LP 1842774

  
  ---

  SRU Template for qemu as the impact/scope is different
  ==

  [Impact]

  * Update naming of the new HW Generation

  * Now that the systems are released people might look for types matching 
the name and no one really knows "IBM 8561 GA1".

  * Help users to identify the cpu type by backporting the fix that sets the 
defined name.

  [Fix]

  * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca

  [Test Case]

  * qemu-system-s390x -cpu ? | grep gen15
  s390 gen15a-base IBM 8561 GA1(static, 
migration-safe)
  s390 gen15a  IBM 8561 GA1(migration-safe)
  s390 gen15b-base IBM 8562 GA1(static, 
migration-safe)
  s390 gen15b  IBM 8562 GA1(migration-safe)

  * With the fix gen15a should be called "IBM z15 GA1"

  [Regression Potential]

  * The only thing changing (for qemu) are some texts e.g. when showing CPU 
types. The cpu type itself that is used in e.g. scripts / commands will 
not change. Therefore the regression risk of the qemu change is next to 
none. The only I can think of is people grepping for the old ID in text 
output, but that seems theoretical and not important.

  [Other Info]

  * For an SRU perspective this is "nice to have" we will only do this 
"along" other higher impact SRUs.

  
  __

  This feature request will provide the final naming of the next machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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 1797753] Re: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)

[laulau]

projects on github seems to work, maybe concider integrating into ubuntu
/ kernel if possible, so that we don't have to reinstall module with
each new kernel update.

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

Title:
  I have lenevo ideapad 130-131KB and in that there is not support for
  wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad
  doing xinput)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after 
installation there is no wifi adapter and also touchpad not working 
  firstly id lspci and in that the output i found of chip :

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter

  secondly id did xinput but there was not device dected as touchpad

  after that i dual boot centos 7 along side ubunt in that touchpad is
  working but again wifi adapter not found

  please solve this issue for both ubuntu (wifi adapter  not found and touchpad 
not detected) and centos
  (wifi adapter not found)

  i searched and read regarding this issue and tried all of the but
  didn't find any solution so at last i have hopes only on u all

  Thank you

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

[Ubuntu Kernel Bot]

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

apport-collect 1847063

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

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

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

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

Title:
  Fix non-working Realtek USB ethernet after system resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Incomplete
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work
  under the following steps:
  1. Connect to a Dell dock
  2. Suspend the system
  3. Re-plug the dock 
  4. Resume the system
  5. Ethernet stops working

  [Fix]
  The USB port lose its power when the dock gets replugged, so we need to
  re-write the MAC address at reset_resume callback.

  [Test]
  The fix is succesfully tested on Dell WD15 dock and TB16 dock.

  [Regression Potential]
  Low. The fix limits to one single device and only take affect when MAC
  passthrough is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1847063/+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 1847063] [NEW] Fix non-working Realtek USB ethernet after system resume

[Kai-Heng Feng]

Public bug reported:

[Impact]
If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work
under the following steps:
1. Connect to a Dell dock
2. Suspend the system
3. Re-plug the dock 
4. Resume the system
5. Ethernet stops working

[Fix]
The USB port lose its power when the dock gets replugged, so we need to
re-write the MAC address at reset_resume callback.

[Test]
The fix is succesfully tested on Dell WD15 dock and TB16 dock.

[Regression Potential]
Low. The fix limits to one single device and only take affect when MAC
passthrough is enabled.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

** Affects: linux-oem-osp1 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: linux-oem-osp1 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

** Affects: linux-oem (Ubuntu Disco)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-osp1 (Ubuntu Disco)
 Importance: Undecided
 Status: Won't Fix

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

** Affects: linux-oem (Ubuntu Eoan)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-osp1 (Ubuntu Eoan)
 Importance: Undecided
 Status: Won't Fix


** Tags: oem-priority originate-from-1846190 somerville

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

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

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

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

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

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: linux-oem (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: New => Won't Fix

** Tags added: oem-priority originate-from-1846190 somerville

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

Title:
  Fix non-working Realtek USB ethernet after system resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Incomplete
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work
  under the following steps:
  1. Connect to a Dell dock
  2. Suspend the system
  3. Re-plug the dock 
  4. Resume the system
  5. Ethernet stops working

  [Fix]
  The USB port lose its power when the dock gets replugged, so we need to
  re-write the MAC address at reset_resume callback.

  [Test]
  The fix is succesfully tested on Dell WD15 dock and TB16 dock.

  [Regression Potential]
  Low. The fix limits to one single device and only take affect when MAC
  passthrough is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1847063/+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 1847042] Re: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5

[monoi]

apport-collect report sent.

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

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

Title:
  Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP
  EliteBook 840 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Ubuntu 19.10 from 19.04.

  On first boot of 19.10, Kernel 5.3.0.13-generic crashed with an error
  in tpm_read_log_efi(), see screenshot. Disabling TPM in BIOS allowed
  successful boot of kernel 5.3.0.13-generic.

  Kernel 5.0.0-31-generic will boot 19.10 successfully, with or without
  TPM enabled in the BIOS.

  Hardware is HP EliteBook 840 G5. BIOS not most recent, cannot upgrade
  without installing Windows.

  ---

  $ lsb_release -rd

  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  $ apt-cache policy linux-generic

  linux-generic:
Installed: 5.3.0.13.14
Candidate: 5.3.0.13.14
Version table:
   *** 5.3.0.13.14 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

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