[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1865197, bug 1864744
+   trusty/linux-azure: bug 1864744, bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  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/1865198

Title:
  xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1864744, bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+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 1864729] Re: bionic/linux-snapdragon: 4.15.0-1074.81 -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: 1865109
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 27. February 2020 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1864727
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1074.81 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1865109
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 27. February 2020 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1864727
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864729/+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 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -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: 1865106
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1134.142 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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: 1865106
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

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

[Gavin Lin]

Hardware Certification have completed testing this -proposed kernel. No 
regressions were observed, results are available here:
https://certification.canonical.com/hardware/201901-26783/submission/163123/

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  bionic/linux-snapdragon: 4.15.0-1074.81 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1865109
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 27. February 2020 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1864727
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864729/+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 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker

[Gavin Lin]

Hardware Certification have completed testing this -proposed kernel. No 
regressions were observed, results are available here:
https://certification.canonical.com/hardware/201611-25221/submission/163061/

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-snapdragon: 4.4.0-1134.142 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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: 1865106
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863329/+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 1857459] Re: audio doesn't work

[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/1857459

Title:
  audio doesn't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  Kernel: 
  Linux version 5.4.6-050406-generic (kernel@kathleen) (gcc version 9.2.1 
20191130 (Ubuntu 9.2.1-21ubuntu1)) #201912211140 SMP Sat Dec 21 11:43:01 UTC 
2019

  In 5.3.18 audio was ok.

  Now in the setting there is written "Dummy output" and alsamixer
  doesn't show any devices.

  
  Hardware: 

   sudo lspci -vnvn (see the log)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857459/+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 1857956] Re: package linux-image-5.3.0-24-generic 5.3.0-24.26 failed to install/upgrade: installed linux-image-5.3.0-24-generic package pre-removal script subprocess returned er

[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/1857956

Title:
  package linux-image-5.3.0-24-generic 5.3.0-24.26 failed to
  install/upgrade: installed linux-image-5.3.0-24-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Sorry, not sure what happened in this case.  I just got a pop-up
  saying an error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mjb3226 F pulseaudio
   /dev/snd/pcmC0D0c:   mjb3226 F...m pulseaudio
  Date: Tue Dec 31 01:54:41 2019
  ErrorMessage: installed linux-image-5.3.0-24-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=none
  MachineType: Dell Inc. XPS 15 7590
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=ZFS=ubuntu/root 
ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-5.3.0-24-generic 5.3.0-24.26 failed to 
install/upgrade: installed linux-image-5.3.0-24-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857956/+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 1857938] Re: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state

[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/1857938

Title:
  Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening
  from suspended state

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using Ubuntu 19.10 with kernel 5.3.0 on my HP Envy X360
  13-ag0xxx. The touchpad works fine under most conditions, however
  whenever the system wakes up from a suspended state (on startup) in
  the first 15-20 seconds the touchpad is extremely laggy (everything
  else is smooth) and nearly impossible to use. I am using Libinput
  1.14.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857938/+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 1798615] Re: suspend does not lock in 18.04

[John Crown]

I'm changing the status to "Fix Released", based on current behavior.
(This is 18.04 with all available current updates.)  (I can no longer
reproduce this problem, so somebody must have fixed it!)

I probably should have done this status change on 2019-01-10 along with
the note I added then, but I didn't know I had the juice.


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

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

Title:
  suspend does not lock in 18.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  To reproduce from the command-line (this is ubuntu 18.04):

  % gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend  true
  % gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend   
  true

  % systemctl suspend

  Now the monitors go black and report "no signal" (good), and it will
  stay that way for hours (good) ...  but if I tap "shift" key a few
  times, Ubuntu 18.04 comes back without asking my password.  (I
  expected rather that the system would be locked, i.e. I should see a
  dialog box that would require a password before anything else!)

  Same thing if I suspend by using the upper-right-of-screen "power" icon 
(click-and-hold, then click on the suspend icon).
  Same thing if I let 20 minutes go by.  (A msg comes up ~~ "system will 
suspend soon...", and it does suspend, but doesn't lock).

  I have left the ubuntu-lock-on-suspend setting at "true" through
  several re-boots, but it still doesn't take effect.

  I get the same behavior whether ubuntu-lock-on-suspend is set to
  "true" or "false".

  Other info:
  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: N/A

  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  Codename:   bionic

  % uname -a
  Linux ucbvax 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I just upgraded from 16.04 a couple of weeks ago.  I think (90%) it
  was locking in 16.04, but now not locking in 18.04.

  If I click on the  upper-right-of-screen padlock icon, then the system
  does lock (password required).

  While it's locked in that way, I can click on the upper-right-of-
  screen "suspend" (from drop-down), and then my system is both
  suspended and locked. But the question is ...

  How can I make my system lock (automatically) every time a "suspend"
  happens?  (Or even "every time kbd and mouse are idle for 15
  minutes"?)

  Please advise.
  thanks

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 7633 F pulseaudio
   /dev/snd/controlC1:  ubuntu 7633 F pulseaudio
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp2s0no wireless extensions.
   
   enp7s5no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  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=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-fips: bug 1865419, bug 1864732
+   bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1063.67 -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 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+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 1865109] Re: bionic/linux: 4.15.0-91.92 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1864737, bug 1865247
+   bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1865480, bug 1863339
+   bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1865482] Re: eoan/linux-aws: 5.3.0-1013.14 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865111
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 00:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1865481
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1013.14 -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 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865111
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 00:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1865481
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865482/+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 1865106] Re: xenial/linux: 4.4.0-176.206 -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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
-   xenial/linux-fips: bug 1865199, bug 1863331
+   xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  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/1865106

Title:
  xenial/linux: 4.4.0-176.206 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865106/+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 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Maheshwaran]

Any update on this issue? Dell latitude 7540 still reporting this issue.

Kernel : Linux 5.3.18-050318-generic

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in Gaming Edition:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
  [   13.414976] iwlwifi :01:00.0: 0x | umac branchlink1
  [   13.414977] iwlwifi :01:00.0: 0xC008CC3C | umac branchlink2
  [   13.414978] iwlwifi :01:00.0: 0xC0087660 | umac interruptlink1
  [   

Re: [Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys

[Jared Young]

I installed from the .deb files and this did not make a difference for the
backlight, however the volume keys on the keyboard no longer work.

I am not experienced in testing different kernels so it is possible that I
messed up the install. I did not apply the .patch files.


On Tue, Mar 3, 2020 at 11:50 PM Kai-Heng Feng 
wrote:

> Can you please test kernel here:
> https://people.canonical.com/~acelan/bugs/lp1861521/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860303
>
> Title:
>   Backlight brightness cannot be adjusted using keys
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I cannot adjust the screen brightness using the keyboard keys or
>   changing /sys/call/backlight/intel_backlight/brightness values. I've
>   only been able to adjust the backlight using xrandr.
>
>   Followed bug report on
> https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques
> and attached files. Additional information:
>   1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not
> change the screen brightness
>   2. video.use_bios_initial_backlight=0 does not enable brightness to be
> changed
>   3. Cannot login to when using kernel paramater acpi_osi=. Login does not
> work and on one boot "y"s were being continuously typed without any keys
> being depressed. It was odd.
>   4. video.use_native_backlight=1 does not enabel brightness to be changed
>   5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had
> no impact
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: linux-image-5.3.0-26-generic 5.3.0-26.28
>   ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
>   Uname: Linux 5.3.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  jaredy 1649 F pulseaudio
>/dev/snd/pcmC0D0p:   jaredy 1649 F...m pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 19 19:51:45 2020
>   InstallationDate: Installed on 2020-01-03 (16 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   MachineType: HP HP Spectre x360 Convertible 13t-aw100
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic
> root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash
> acpi_backlight=vendor vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-5.3.0-26-generic N/A
>linux-backports-modules-5.3.0-26-generic  N/A
>linux-firmware1.183.3
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/15/2019
>   dmi.bios.vendor: AMI
>   dmi.bios.version: F.10
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 86FA
>   dmi.board.vendor: HP
>   dmi.board.version: 87.43
>   dmi.chassis.type: 31
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Spectre
>   dmi.product.name: HP Spectre x360 Convertible 13t-aw100
>   dmi.product.sku: 6YG70AV
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions
>

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

Title:
  Backlight brightness cannot be adjusted using keys

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot adjust the screen brightness using the keyboard keys or
  changing /sys/call/backlight/intel_backlight/brightness values. I've
  only been able to adjust the backlight using xrandr.

  Followed bug report on 
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and 
attached files. Additional information:
  1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change 
the screen brightness
  2. video.use_bios_initial_backlight=0 does not enable brightness to be changed
  3. Cannot login to when using kernel paramater acpi_osi=. Login does not work 
and on one boot "y"s were being continuously typed without any keys being 
depressed. It was odd. 
  4. video.use_native_backlight=1 does not enabel brightness to be changed
  5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no 
impact

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  

[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Rex Tsai]

It's the same issue happens on Dell XPS 13 9300[1], the solution[2] has
been proposed to kernel mailing list by Acelan. It's expected to be land
in the next SRU cycle (05-Apr).

[1] Bug #1865962 “Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fail...” : Bugs 
: linux package : Ubuntu - https://bugs.launchpad.net/bugs/1865962
[2] [PATCH 0/6][SRU][Focal] Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails 
to load firmware - 
https://lists.ubuntu.com/archives/kernel-team/2020-March/107993.html

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  Laptop: Dell XPS 13 7390 2-in-1
  Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz

  iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
  Firmware crashes after loading and interface doesn't show up.

  This is with:
  linux-image-5.4.0-9-generic   5.4.0-9.12
  linux-firmware 1.184

  I've noticed the driver was trying to load a more recent firmware:
  Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2

  I've downloaded this file from upstream iwlwifi firmware git and tried
  unloading/reloading iwlwifi. Driver crashes as well, but with a
  different error code.

  Best,
  - LM

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lool   1579 F pulseaudio
   /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 15:02:08 2020
  InstallationDate: Installed on 2019-12-02 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago)
  dmi.bios.date: 11/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865111
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.3: bug 1865492
  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/1865493

Title:
  eoan/linux-oracle: 5.3.0-1011.12 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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: 1865111
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.3: bug 1865492
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865493/+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 1866427] [NEW] bluetooth mouse wheel not working after suspend/reconnect

[SHHyun]

Public bug reported:

1) Description: Ubuntu 18.04.4 LTS
Release:18.04

2) bluez:
  Installed: 5.50-0ubuntu0ppa1
  Candidate: 5.50-0ubuntu0ppa1
  Version table:
 *** 5.50-0ubuntu0ppa1 500
500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 
Packages
100 /var/lib/dpkg/status
 5.48-0ubuntu3.3 500
500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages
 5.48-0ubuntu3 500
500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages

3) My bluetooth mouse(Surface Precision Mouse) wheel is not working
after suspended. It's working fine at first. This phenomenon occurs
after suspended. It's not only for pc suspended but also mouse power
on/off. Both the mouse cursor and click are normal. Only the wheels do
not work.

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

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

Title:
  bluetooth mouse wheel not working after suspend/reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 18.04.4 LTS
  Release:  18.04

  2) bluez:
Installed: 5.50-0ubuntu0ppa1
Candidate: 5.50-0ubuntu0ppa1
Version table:
   *** 5.50-0ubuntu0ppa1 500
  500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3.3 500
  500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages
   5.48-0ubuntu3 500
  500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages

  3) My bluetooth mouse(Surface Precision Mouse) wheel is not working
  after suspended. It's working fine at first. This phenomenon occurs
  after suspended. It's not only for pc suspended but also mouse power
  on/off. Both the mouse cursor and click are normal. Only the wheels do
  not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1866427/+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 1866423] 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 1866423

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

Title:
  [arm64] Enable USB support on Amlogic Meson GXL & GXM platforms

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please enable the following configs in Ubuntu Focal to fully enable
  USB support for the Amlogic Meson GXL & GXM (Amlogic S805X, S905X,
  S912) in Linux 5.4

  CONFIG_PHY_MESON_GXL_USB2
  CONFIG_PHY_MESON_GXL_USB3
  CONFIG_USB_DWC3_OF_SIMPLE

  Some devices rely on USB support in order to load additional files to
  boot the system and installer.

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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865111
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-5.3: bug 1865488
bionic/linux-gke-5.3: bug 1865490
  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/1865491

Title:
  eoan/linux-gcp: 5.3.0-1014.15 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1865111
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-5.3: bug 1865488
bionic/linux-gke-5.3: bug 1865490
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865491/+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 1866423] [NEW] [arm64] Enable USB support on Amlogic Meson GXL & GXM platforms

[Da Xue]

Public bug reported:

Please enable the following configs in Ubuntu Focal to fully enable USB
support for the Amlogic Meson GXL & GXM (Amlogic S805X, S905X, S912) in
Linux 5.4

CONFIG_PHY_MESON_GXL_USB2
CONFIG_PHY_MESON_GXL_USB3
CONFIG_USB_DWC3_OF_SIMPLE

Some devices rely on USB support in order to load additional files to
boot the system and installer.

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

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

Title:
  [arm64] Enable USB support on Amlogic Meson GXL & GXM platforms

Status in linux package in Ubuntu:
  New

Bug description:
  Please enable the following configs in Ubuntu Focal to fully enable
  USB support for the Amlogic Meson GXL & GXM (Amlogic S805X, S905X,
  S912) in Linux 5.4

  CONFIG_PHY_MESON_GXL_USB2
  CONFIG_PHY_MESON_GXL_USB3
  CONFIG_USB_DWC3_OF_SIMPLE

  Some devices rely on USB support in order to load additional files to
  boot the system and installer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866423/+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 1865269] Re: bionic/linux-aws: 4.15.0-1063.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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-fips: bug 1864732, bug 1865419
+   bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1063.67 -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 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+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 1865109] Re: bionic/linux: 4.15.0-91.92 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1865247, bug 1864737
+   bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1864744, bug 1865197
+   trusty/linux-azure: bug 1865197, bug 1864744
xenial/linux-azure/azure-kernel: bug 1865196
  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/1865198

Title:
  xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1865197, bug 1864744
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+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 1865170] Re: lid close simply turns off laptop screen

[Alex Hung]

There are a few s2idle fixes and workaround in mainline kernel, and it
may worth a try. If it can fix your problem, fixes can be backported to
bionic

latest mainline kernel: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.6-rc4/

instructions: https://askubuntu.com/questions/879888/how-do-i-update-
kernel-to-the-latest-mainline-version

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware   1.173.15
  Tags:  bionic
  Uname: Linux 4.15.0-1073-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.

[Kernel-packages] [Bug 1865106] Re: xenial/linux: 4.4.0-176.206 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1865199, bug 1863331
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  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/1865106

Title:
  xenial/linux: 4.4.0-176.206 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1865199, bug 1863331
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  variant: debs

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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865110
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 02. March 2020 16:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1865192
  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/1865193

Title:
  bionic/linux-azure: 5.0.0-1034.36 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  In Progress
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: 1865110
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 02. March 2020 16:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1865192
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865193/+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 1866407] Re: GPU Driver extension issue (NVIDIA)

[Joseph Salisbury]

The following can be used as a work around:

For new VM:
Build VM without Nvidia Extension
sudo apt-get -o Dpkg::Options::="--force-overwrite" install -y nvidia-440
Apply Nvidia Extension for Linux to VM
Continue with setup

For existing VM with failed installation:
sudo apt-get -o Dpkg::Options::="--force-overwrite" install -y nvidia-440
sudo 
/var/lib/waagent/Microsoft.HpcCompute.NvidiaGpuDriverLinux-1.2.0.0/scripts/enable.sh
 Reboot
Continue with remaining setup

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

Title:
  GPU Driver extension issue (NVIDIA)

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but
  it is correctly installed for Standard_NV6.  This is happening on
  Ubuntu Server 18.04 LTS.


  To repro this issue:

  1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and
  size Standard_NC6

  2. Add extension NvidiaGpuDriver and wait for it to fail

  3. Connect to the VM and try to install following package sudo apt
  install -y xubuntu-desktop

  4. You'll see how it is unable to install it and it suggests to run
  apt --fix-broken install but it doesn't work either.

  
  It should work accordingly to this doc 
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux

  This may be related to an older bug for an older Nvidia version: bug
  1753796

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1866407/+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 1866407] [NEW] GPU Driver extension issue (NVIDIA)

[Joseph Salisbury]

Public bug reported:

The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but
it is correctly installed for Standard_NV6.  This is happening on Ubuntu
Server 18.04 LTS.


To repro this issue:

1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and size
Standard_NC6

2. Add extension NvidiaGpuDriver and wait for it to fail

3. Connect to the VM and try to install following package sudo apt
install -y xubuntu-desktop

4. You'll see how it is unable to install it and it suggests to run apt
--fix-broken install but it doesn't work either.


It should work accordingly to this doc 
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux

This may be related to an older bug for an older Nvidia version: bug
1753796

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

Title:
  GPU Driver extension issue (NVIDIA)

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but
  it is correctly installed for Standard_NV6.  This is happening on
  Ubuntu Server 18.04 LTS.


  To repro this issue:

  1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and
  size Standard_NC6

  2. Add extension NvidiaGpuDriver and wait for it to fail

  3. Connect to the VM and try to install following package sudo apt
  install -y xubuntu-desktop

  4. You'll see how it is unable to install it and it suggests to run
  apt --fix-broken install but it doesn't work either.

  
  It should work accordingly to this doc 
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux

  This may be related to an older bug for an older Nvidia version: bug
  1753796

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

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

Re: [Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Ramon, which hardware is yours? Razer?

Enviado via ProtonMail móvel

 Mensagem Original 
Ativo 6 de mar de 2020 16:34, Ramon Fontes escreveu:

> BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't
> work.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746340
>
> Title:
> Samsung SSD corruption (fsck needed)
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Ubuntu 4.13.0-21.24-generic 4.13.13
>
> I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
> 17.04, which gave me this error after 2 weeks of usage. After that, I 
> installed 16.04 and used it for MONTHS without any problems, until it 
> produced the same error this week. I think it has to do with the ubuntu 
> updates, because I did one recently and one today, just before this problem. 
> Could be a coincidence though.
>
> I notice the error when I try to save something on disk and it says me
> that the disk is in read-only mode:
>
> lz@lz:/var/log$ touch something
> touch: cannot touch 'something': Read-only file system
>
> lz@lz:/var/log$ cat syslog
> Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
> ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
> directory block 0
>
> lz@lz:/var/log$ dmesg
> [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.377374] Aborting journal on device nvme0n1p2-8.
> [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
> [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
> #26607929: comm updatedb.mlocat: checksumming directory block 0
> [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
> operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
> capability=12 capname="net_admin"
>
> Rebooting the ubuntu will give me a black terminal where I can run
> fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
> orphaned inodes. The majority of time it boots back to the Ubuntu
> working good, but some times it boots to a broken ubuntu (no images,
> lots of things broken). I have to reinstall ubuntu then.
>
> Every time I reinstall my Ubuntu, I have to try lots of times until it
> installs without an Input/Output error. When it installs, I can use it
> for some hours without having the problem, but if I run the software
> updates, it ALWAYS crashes and enters in read-only mode, specifically
> in the part that is installing kernel updates.
>
> I noticed that Ubuntu installs updates automatically when they're for
> security reasons. Could this be the reason my Ubuntu worked for months
> without the problem, but then an update was applied and it broke?
>
> I thought that this bug was happening:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
> different nvme_core.default_ps_max_latency_us= combinations, all them
> gave errors. I just changed to 0 and I had no error while using ubuntu
> (however I didn't test for a long time) but I still had the error
> after trying to update my ubuntu.
>
> My Samsung 512gb SSD is:
>
> SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q
>
> on a Razer Blade Stealth.
>
> I also asked this on ask ubuntu, without success:
> https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
> corruption-fsck-needed-probably-samsung-ssd-bug-afte
>
> Please help me, as I need this computer to work on lots of things :c
> ---
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: lz 1088 F pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 17.10
> InstallationDate: Installed on 2018-01-30 (0 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
> 

[Kernel-packages] [Bug 1866403] [NEW] Eoan update: upstream stable patchset 2020-03-06

[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 2020-03-06

Ported from the following upstream stable releases:
v4.19.101, v5.4.17,
v4.19.102, v5.4.18

   from git://git.kernel.org/

orinoco_usb: fix interface sanity check
rsi_91x_usb: fix interface sanity check
usb: dwc3: pci: add ID for the Intel Comet Lake -V variant
USB: serial: ir-usb: add missing endpoint sanity check
USB: serial: ir-usb: fix link-speed handling
USB: serial: ir-usb: fix IrLAP framing
usb: dwc3: turn off VBUS when leaving host mode
staging: most: net: fix buffer overflow
staging: wlan-ng: ensure error return is actually returned
staging: vt6656: correct packet types for CTS protect, mode.
staging: vt6656: use NULLFUCTION stack on mac80211
staging: vt6656: Fix false Tx excessive retries reporting.
serial: 8250_bcm2835aux: Fix line mismatch on driver unbind
component: do not dereference opaque pointer in debugfs
mei: me: add comet point (lake) H device ids
iio: st_gyro: Correct data for LSM9DS0 gyro
crypto: chelsio - fix writing tfm flags to wrong place
cifs: Fix memory allocation in __smb2_handle_cancelled_cmd()
ath9k: fix storage endpoint lookup
brcmfmac: fix interface sanity check
rtl8xxxu: fix interface sanity check
zd1211rw: fix storage endpoint lookup
net_sched: ematch: reject invalid TCF_EM_SIMPLE
net_sched: fix ops->bind_class() implementations
arc: eznps: fix allmodconfig kconfig warning
HID: Add quirk for Xin-Mo Dual Controller
HID: ite: Add USB id match for Acer SW5-012 keyboard dock
HID: Add quirk for incorrect input length on Lenovo Y720
drivers/hid/hid-multitouch.c: fix a possible null pointer access.
phy: qcom-qmp: Increase PHY ready timeout
phy: cpcap-usb: Prevent USB line glitches from waking up modem
watchdog: max77620_wdt: fix potential build errors
watchdog: rn5t618_wdt: fix module aliases
spi: spi-dw: Add lock protect dw_spi rx/tx to prevent concurrent calls
drivers/net/b44: Change to non-atomic bit operations on pwol_mask
net: wan: sdla: Fix cast from pointer to integer of different size
gpio: max77620: Add missing dependency on GPIOLIB_IRQCHIP
atm: eni: fix uninitialized variable warning
HID: steam: Fix input device disappearing
platform/x86: dell-laptop: disable kbd backlight on Inspiron 10xx
PCI: Add DMA alias quirk for Intel VCA NTB
iommu/amd: Support multiple PCI DMA aliases in IRQ Remapping
ARM: OMAP2+: SmartReflex: add omap_sr_pdata definition
usb-storage: Disable UAS on JMicron SATA enclosure
rsi: fix use-after-free on probe errors
rsi: fix memory leak on failed URB submission
rsi: fix non-atomic allocation in completion handler
crypto: af_alg - Use bh_lock_sock in sk_destruct
Bluetooth: btusb: fix non-atomic allocation in completion handler
usb: host: xhci-tegra: set MODULE_FIRMWARE for tegra186
usb: typec: wcove: fix "op-sink-microwatt" default that was in mW
serial: imx: fix a race condition in receive path
debugfs: Return -EPERM when locked down
mei: hdcp: bind only with i915 on the same PCH
iio: adc: stm32-dfsdm: fix single conversion
driver core: Fix test_async_driver_probe if NUMA is disabled
CIFS: Fix task struct use-after-free on reconnect
cifs: set correct max-buffer-size for smb2_ioctl_init()
net_sched: walk through all child classes in tc_bind_tclass()
net: socionext: fix possible user-after-free in netsec_process_rx
net: socionext: fix xdp_result initialization in netsec_process_rx
udp: segment looped gso packets correctly
mlxsw: minimal: Fix an error handling path in 'mlxsw_m_port_create()'
net: include struct nhmsg size in nh nlmsg size
rxrpc: Fix use-after-free in rxrpc_receive_data()
HID: asus: Ignore Asus vendor-page usage-code 0xff events
HID: intel-ish-hid: ipc: add CMP device id
HID: wacom: add new MobileStudio Pro 13 support
HID: wacom: Recognize new MobileStudio Pro PID
ASoC: SOF: fix fault at driver unload after failed probe
ASoC: SOF: Intel: hda: hda-dai: fix oops on hda_link .hw_free
ASoC: fsl_audmix: add missed pm_runtime_disable
ASoC: topology: Prevent use-after-free in snd_soc_get_pcm_runtime()
HID: intel-ish-hid: ipc: Add Tiger Lake PCI device ID
usb: musb: jz4740: Silence error if code is -EPROBE_DEFER
net: Google gve: Remove dma_wmb() before ringing doorbell
iommu/dma: fix variable 'cookie' set but not used
drm/amd/display: Reduce HDMI pixel encoding if max clock is exceeded
extcon-intel-cht-wc: Don't reset USB data connection at probe
ASoC: Intel: cht_bsw_rt5645: Add quirk for boards using pmc_plt_clk_0
libbpf: Fix BTF-defined map's __type macro handling of 

[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1063.67 -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 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1864737, bug 1865247
+   bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1834875] Re: cloud-init growpart race with udev

[Michael Hudson-Doyle]

Can someone from CPC confirm that this has fixed the issues in the Azure
tests?

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  Fix Committed
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-utils package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1865111] Re: eoan/linux: 5.3.0-42.34 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  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/1865111

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865111/+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 1746340] Re: Samsung SSD corruption (fsck needed)

[Ramon Fontes]

BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't
work.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 

[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1865197, bug 1864744
+   trusty/linux-azure: bug 1864744, bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  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/1865198

Title:
  xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1864744, bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+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 1865109] Re: bionic/linux: 4.15.0-91.92 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1865247, bug 1864737
+   bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1863339, bug 1865480
+   bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1746340] Re: Samsung SSD corruption (fsck needed)

[Ramon Fontes]

Hello all!

I'm experiencing the same problem with an adata SU800NS38. My SSD works
fine with the 4.17.0-041700-generic kernel version but unfortunately
this is the only kernel version it works perfectly. In addition to try
other kernel versions such as 4.x, I also tried 5.0 - 5.5. The disk
becomes read-only during use and I need to use fsck whenever I start the
system.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  

[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan

[Francis Ginther]

This looks likely to be the same bug:
https://bugzilla.kernel.org/show_bug.cgi?id=206259

Both patches are in linux upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/linux/hid.h?id=84a4062632462c4320704fcdf8e99e89e94c0aba
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hid/hid-core.c?id=5ebdffd25098898aff1249ae2f7dbfddd76d8f8f

That's all I have at the moment. Will look at this some more when I have
time again.

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

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

Title:
  Touchscreen Unresponsive in Focal, but Works in Eoan

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  After upgrading my Surface Go to Focal from Eoan, the touchscreen has
  stopped working.

  A snippet from journalctl:

  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event4 13:68 fd 28 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" 
"none"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) selected scheme none/0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration factor: 2.000
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration threshold: 4
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/mouse0)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, 
ignoring this device.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been 
added with another device file.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/event5)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
Applying InputClass "libinput tablet catchall"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 
'libinput' for 'ELAN9038:00 04F3:261A'
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event5 13:69 fd 29 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) 

[Kernel-packages] [Bug 1865025] Re: focal/linux: 5.4.0-17.21 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Sunday, 01. March 2020 12:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
focal/linux-aws: bug 1865020
focal/linux-azure: bug 1865021
focal/linux-gcp: bug 1865022
focal/linux-kvm: bug 1865023
focal/linux-oem-5.4: bug 1865019
focal/linux-oem-5.6: bug 1865018
focal/linux-oracle: bug 1865024
focal/linux-raspi2: bug 1865017
focal/linux/pc-kernel: bug 1865029
focal/linux/pc-lowlatency-kernel: bug 1865030
  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/1865025

Title:
  focal/linux: 5.4.0-17.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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: Sunday, 01. March 2020 12:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
focal/linux-aws: bug 1865020
focal/linux-azure: bug 1865021
focal/linux-gcp: bug 1865022
focal/linux-kvm: bug 1865023
focal/linux-oem-5.4: bug 1865019
focal/linux-oem-5.6: bug 1865018
focal/linux-oracle: bug 1865024
focal/linux-raspi2: bug 1865017
focal/linux/pc-kernel: bug 1865029
focal/linux/pc-lowlatency-kernel: bug 1865030
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865025/+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 1865023] Re: focal/linux-kvm: 5.4.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1865025
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1865023

Title:
  focal/linux-kvm: 5.4.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Focal:
  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: 1865025
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865023/+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 1865111] Re: eoan/linux: 5.3.0-42.34 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  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/1865111

Title:
  eoan/linux: 5.3.0-42.34 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865111/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Harry W. Haines, III]

Urgent cut in!!
Testing today on a daily build of Kubuntu 20.04 I observed the same issue.
Linux version 5.4.0-14-generic, linux-firmware/focal,now 1.186.

I did a CRC check on the oland_rlc.bin file in linux-firmware 1.186 and
it was the same as from the one in linux-firmware/bionic-updates
1.173.15

Please make the necessary adjustments so this issue will not occur in
the LTS release of 20.04.

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  

[Kernel-packages] [Bug 1865023] Re: focal/linux-kvm: 5.4.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865025
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1865023

Title:
  focal/linux-kvm: 5.4.0-1003.3 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Focal:
  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: 1865025
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865023/+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 1866195] Re: Can not resume after suspend on HP Spectre x360 13 aw0xxx (late 2019)

[Séverin Lemaignan]

Tested on Fedora 31 (linux 5.3.7) from a Live session, works ok.

What has been specifically tested:

echo freeze | sudo tee /sys/power/state

-> goes to soft suspend mode; power led turns off; on pressing the power
button, resumes without error

echo mem | sudo tee /sys/power/state

-> goes to suspend mode; power led turns off; on pressing the power
button, resumes without error

echo disk | sudo tee /sys/power/state

-> fails to hibernate (power led remains on, had to hard shutdown the
laptop)

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

Title:
  Can not resume after suspend on HP Spectre x360 13 aw0xxx (late 2019)

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  After attempting a suspend, the laptop does not resume. The power
  button LED remains on.

  Impossible to switch to different console (ctrl+alt+Fx).

  Only option is a forced shutdown.
   
  Same issue on Ubuntu 19.10 (with kernel 5.3).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Mar  5 14:27:57 2020
  InstallationDate: Installed on 2020-02-28 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4934ba68-d847-4a31-8844-10f79fcaab92 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-03-04 (0 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1866195/+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 1865025] Re: focal/linux: 5.4.0-17.21 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Sunday, 01. March 2020 12:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
focal/linux-aws: bug 1865020
focal/linux-azure: bug 1865021
focal/linux-gcp: bug 1865022
focal/linux-kvm: bug 1865023
focal/linux-oem-5.4: bug 1865019
focal/linux-oem-5.6: bug 1865018
focal/linux-oracle: bug 1865024
focal/linux-raspi2: bug 1865017
focal/linux/pc-kernel: bug 1865029
focal/linux/pc-lowlatency-kernel: bug 1865030
  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/1865025

Title:
  focal/linux: 5.4.0-17.21 -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-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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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: Sunday, 01. March 2020 12:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
focal/linux-aws: bug 1865020
focal/linux-azure: bug 1865021
focal/linux-gcp: bug 1865022
focal/linux-kvm: bug 1865023
focal/linux-oem-5.4: bug 1865019
focal/linux-oem-5.6: bug 1865018
focal/linux-oracle: bug 1865024
focal/linux-raspi2: bug 1865017
focal/linux/pc-kernel: bug 1865029
focal/linux/pc-lowlatency-kernel: bug 1865030
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865025/+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 1865571] Re: Sound card not detected on HP Spectre x360 13-aw0xxx

[Séverin Lemaignan]

Tested on Fedora 31 (linux 5.3.7), sounds work ok (using the
snd_sof_intel_hda driver).

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

Title:
  Sound card not detected on HP Spectre x360 13-aw0xxx

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0
  (via proposed-packages), no sound card detected (CPU: Intel i7-1065G).

  Relevant dmesg output:

  ```
  [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-icl.ri failed with error -2
  [4.544997] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-icl.ri failed err: -2
  [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Mon Mar  2 20:47:33 2020
  InstallationDate: Installed on 2020-02-28 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-02-28 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4934ba68-d847-4a31-8844-10f79fcaab92 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865571/+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 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Mario Vukelic]

Still occurs on this Asus in 20.04 with kernel 5.4.0-15 and the
-proposed -17.

Super annoying, I have to fix this for the Asus' owner by adding the
[Element Master] workaround on every Ubuntu upgrade or in case the
responsible package updates.

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

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721345/+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 1865571] Re: Sound card not detected on HP Spectre x360 13-aw0xxx

[Séverin Lemaignan]

Tested from a Ubuntu 18.04 live USB stick: the sound works. Adding the
tag `regression`.

** Tags added: regression

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

Title:
  Sound card not detected on HP Spectre x360 13-aw0xxx

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0
  (via proposed-packages), no sound card detected (CPU: Intel i7-1065G).

  Relevant dmesg output:

  ```
  [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-icl.ri failed with error -2
  [4.544997] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-icl.ri failed err: -2
  [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Mon Mar  2 20:47:33 2020
  InstallationDate: Installed on 2020-02-28 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-02-28 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4934ba68-d847-4a31-8844-10f79fcaab92 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865571/+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 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic

[Mario Vukelic]

As per prev. comment, the test kernel re-enables the keyboard brightness
setting. However, the slider in the Gnome panel menu is not being moved
when using the keyboard keys. Dragging the slider with the mouse does
change the brightness, though.

(May be related: The volume slider in the panel menu & the volume keys
show the same behaviour: the volume keys work but do not affect the
slider)

And by the way, the brightness problem also occurs on Asus Zenbook Flip
UX561UD, and the test kernel behaves in the same way, keys work but
slider unaffected.

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

Title:
  [Dell XPS 15 9575] Screen brightness stopped working with linux-
  image-5.4.0-9-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Focal Fossa 3 days ago and nothing broke. At the time,
  it was still using linux 5.3 (linux-image-5.3.0-24-generic).

  Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after
  rebooting, the screen brightness does not work anymore - neither from
  keyboard keys nor from the slider in the gnome-shell panel.

  It works again when rebooting into the previous linux-
  image-5.3.0-24-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mario  1892 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 20:23:31 2020
  InstallationDate: Installed on 2018-09-13 (481 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+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 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3

[Kai-Heng Feng]

The better way to handle this is to ask Realtek to implement correct
depop function in the codec driver.

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Seth Forshee]

@kaihengfeng: This looks like it must be a regression from the updated
firmware you sent for bug 1858751. It looks like this has been reverted
upstream, so I'm going to go ahead and revert it in our linux-firmware
package too.

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Seth Forshee]

I've applied the revert. There's a linux-firmware in bionic-proposed
right now which should release on Monday, after that happens I will
upload a new package with the revert.

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Peter Ries]

I can confirm that reverting to linux-firmware:amd64=1.173.12 with
kernel 5.3.0-40-generic on Xubuntu 18.04.4 solved my problem.

Workaround with kernel parameter "radeon.modeset=0
rd.driver.blacklist=radeon" removed error messages but caused fan to
work constantly when watching e. g. youtube in chrome.

Using Samsung ativbook 730U3E with display controller: Advanced Micro
Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M]

Regards
Peter

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Peter Ries]

edit to post #10: my problem was the same as in original posting - just
to avoid confusion

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
  SourcePackage: xorg
  

[Kernel-packages] [Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1865480, bug 1863339
+   bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1865106] Re: xenial/linux: 4.4.0-176.206 -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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
-   xenial/linux-fips: bug 1863331, bug 1865199
+   xenial/linux-fips: bug 1865199, bug 1863331
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  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/1865106

Title:
  xenial/linux: 4.4.0-176.206 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1865199, bug 1863331
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  variant: debs

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

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Здравко]

Just some clarifications, @harry17

The reported issue isn't related only to a single ("current" - probably
latest) kernel. The issue isn't stick to any particular kernel; initial
report is related to a particular context, of course. When there is some
issue related to initial firmware loading (at boot time), this isn't
firmware issue, but a driver issue, the driver performing firmware load!
Am I wrong?! Here the case is very different. The issue is firmware
related, definitely, and the 'symptoms' come up all the time, not only
at boot time (at boot is more noticeable, but not restricted to)! There
could be (and I believe it is) a driver's 'guilty' too. Before the last
firmware update and next rollback, one part (error) from initial report
present yet. Especially:

...
[ +0.100566] radeon :01:00.0: failed VCE resume (-110).
...

And repeats again and again all the time when 1.173.12 runs (same like
all errors from initial report get repeat while 1.173.15 runs) with
kernel 4.15.0-88-generic. The error in "/build/linux-
WUVVsw/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c" (in my case)
brings up once, initially.

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: 

[Kernel-packages] [Bug 1865041] Re: Bump crash version on Bionic and Eoan to match Focal

[Łukasz Zemczak]

Hello Guilherme, or anyone else affected,

Accepted crash into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  Bump crash version on Bionic and Eoan to match Focal

Status in crash package in Ubuntu:
  Confirmed
Status in crash source package in Bionic:
  Fix Committed
Status in crash source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  * The crash tool aims to allow investigating kernel core dumps collected 
through the kexec mechanism; as such, this tool is tightly coupled with kernel 
version, needing awareness for example about kernel structs layout and other 
kernel "API" details.

  * Currently the crash tool is outdated in Bionic, not allowing users
  to debug kernel core dumps collected with the latest HWE kernel
  (version 5.3). Also, many bugs and improvements are added to crash as
  newer kernels are released.

  * This LP's goal is to bump the version of crash tool in both Bionic
  and Eoan in order to match Focal version (7.2.8). With that we can
  address the Bionic issue when opening kernel 5.3 dumps and gather more
  fixes with the updated package.

  [Test Case]
  * The test performed is basically collect dumps with kdump-tools and open in 
crash. In this particular case, the tests were with kernels 4.15.0-88 and 
5.3.0-26 (in Bionic) and kernel 5.3.0-23 (in Eoan) using the crash tool built 
with the hereby attached source.

  [Regression Potential]
  * Crash tool aims to have full retro-compatibility with kernel, so the 
likelihood for regressions are low. If regressions are found, it's likely the 
same regression applies to all crash/kernel pair versions, so by having the 
package synced between releases we increase the exposure to gather more bug 
reports and fix things in a more straightforward fashion.

  NOTICE: This bump was agreed with Ubuntu kdump-tools/crash maintainer,
  Thadeu Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1865041/+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 1858958] Re: fails on arm64 w/ 5.4 kernel: crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore

[Łukasz Zemczak]

Hello dann, or anyone else affected,

Accepted crash into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  fails on arm64 w/ 5.4 kernel: crash: cannot determine VA_BITS_ACTUAL:
  please use /proc/kcore

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Bionic:
  Fix Committed
Status in crash source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  autopkgtest failures

  [test case]

  crash autopkgtests have began to fail on arm64, as seen here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/arm64/c/crash/20191223_190616_50c73@/log.gz

  The significant difference between this test and the last successful
  one is that the host kernel has moved from 5.3 to 5.4. As crash needs
  to understand some internals of the kernel memory, it often needs
  updates to deal with new kernels.

  I've verified that the existing crash still works fine w/ a 5.3
  kernel[1], but does not w/ 5.4:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r)

  crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore

  However, note hte "please use /proc/kcore" - if I point crash at that
  instead of whatever it normally uses (/dev/mem?) it is able to start
  [2]. The same is also true w/ current upstream as of commit 7c2d41e
  btw - it fails w/o /proc/kcore and works with it.

  [1]
  ubuntu@d05-3:~$ sudo crash /usr/lib/debug/boot/vmlinux-5.3.0-26-generic

  crash 7.2.6
  Copyright (C) 2002-2019  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-5.3.0-26-generic
  DUMPFILE: /proc/kcore
  CPUS: 64
  DATE: Wed Jan  8 22:32:40 2020
    UPTIME: 4 days, 20:46:37
  LOAD AVERAGE: 1.09, 0.76, 0.46
     TASKS: 836
  NODENAME: d05-3
   RELEASE: 5.3.0-26-generic
   VERSION: #28-Ubuntu SMP Wed Dec 18 05:39:18 UTC 2019
   MACHINE: aarch64  (unknown Mhz)
    MEMORY: 127.7 GB
   PID: 19415
   COMMAND: "crash"
  TASK: 801464623b00  [THREAD_INFO: 801464623b00]
   CPU: 13
     STATE: TASK_RUNNING (ACTIVE)

  crash> quit

  [2]
  ubuntu@d05-3:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) 
/proc/kcore
  Thu Jan  9 00:20:20 2020

  ubuntu@d05-3:~$ sudo crash /usr/lib/debug/boot/vmlinux-$(uname -r)
  /proc/kcore

  crash 7.2.6
  Copyright (C) 2002-2019  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 

[Kernel-packages] [Bug 1865277] Re: kernel issue crash on netstat

[Po-Hsu Lin]

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

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

Title:
  kernel issue crash on netstat

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  netstat cli on kernel crash and stop network responding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/1865277/+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 1866357] [NEW] Pop sound from build-in speaker during cold boot and resume from S3

[David Chen]

Public bug reported:

[Description]
On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

[More detail]
There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

[Experiment]
With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

[HW info]
Codec: Realtek ALC3253
00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


Device is not with me at this moment, I will provide more info if
required.

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

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  New

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+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 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan

[David Krauser]

With kernel version 5.4.0, the touchscreen does not work. Attaching a
dmesg with this kernel.

** Attachment added: "dmesg.5.4.0-14-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334326/+files/dmesg.5.4.0-14-generic.log

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

Title:
  Touchscreen Unresponsive in Focal, but Works in Eoan

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  After upgrading my Surface Go to Focal from Eoan, the touchscreen has
  stopped working.

  A snippet from journalctl:

  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event4 13:68 fd 28 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" 
"none"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) selected scheme none/0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration factor: 2.000
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration threshold: 4
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/mouse0)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, 
ignoring this device.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been 
added with another device file.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/event5)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
Applying InputClass "libinput tablet catchall"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 
'libinput' for 'ELAN9038:00 04F3:261A'
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event5 13:69 fd 29 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/mouse1)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, 
ignoring this device.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been 
added with another device file.

  ProblemType: Bug
  DistroRelease: Ubuntu 

[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan

[David Krauser]

With kernel version 5.3.0, the touchscreen works. Attaching a dmesg with
this kernel.

** Attachment added: "dmesg.5.3.0-29-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334325/+files/dmesg.5.3.0-29-generic.log

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

Title:
  Touchscreen Unresponsive in Focal, but Works in Eoan

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  After upgrading my Surface Go to Focal from Eoan, the touchscreen has
  stopped working.

  A snippet from journalctl:

  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event4 13:68 fd 28 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" 
"none"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) selected scheme none/0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration factor: 2.000
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
(accel) acceleration threshold: 4
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: is tagged by udev as: Touchscreen
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4  - ELAN9038:00 
04F3:261A: device is a touch device
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/mouse0)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, 
ignoring this device.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been 
added with another device file.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/event5)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
Applying InputClass "libinput tablet catchall"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 
'libinput' for 'ELAN9038:00 04F3:261A'
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for 
/dev/input/event5 13:69 fd 29 paused 0
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: 
always reports core events
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" 
"/dev/input/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" 
"server/udev"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device removed
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5"
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended 
input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: is tagged by udev as: Tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5  - ELAN9038:00 
04F3:261A: device is a tablet
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input 
device ELAN9038:00 04F3:261A (/dev/input/mouse1)
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, 
ignoring this device.
  12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been 
added with another device file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  

[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend

[MARTIN]

After an out of suspend, I tape again in a terminal window:
apport-collect 1865471

You can see the result.
I change the status of the bug to 'Confirmed'.

If I can do anything else or in terminal window, please inform me.

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

  There many months than I use "suspend" (settings -> energy -> When the
  shutdown button...) on Ubuntu 18.04 or 19.10.

  But at each wake up from my computer, the USB 3.1 Gen 1 ports (only
  motherboard back panel) no work after (loose use of webcam,
  keyboard...).

  No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from internal USB 
header).
  No problems with USB 2.0/1.1 ports (motherboard back panel).

  I think my motherboard is not at fault because I did not reproduce this bug 
on Windows 10.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-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/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  christophe   1565 F pulseaudio
   /dev/snd/controlC0:  christophe   1565 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (15 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-40-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/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  

[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)

[norman shen]

Hi, sorry to ask non related questions. But could youe please teach how
did you identity there is a negative refcnts from the dmesg? thanks...

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

Title:
  Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading from 14.04 to 18.04, we see very frequent warnings
  about negative refcnts in dst_release:

  [ 3117.882227] WARNING: CPU: 6 PID: 0 at 
/build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 
nf_xfrm_me_harder+0x127/0x140 [nf_nat]
  [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel 
authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 
ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb 
xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding 
algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 
dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle 
xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel 
xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial 
ipmi_si
  [ 3117.882265]  irqbypass intel_cstate mei_me mei ioatdma acpi_pad 
intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich 
mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel 
nf_conntrack iptable_filter ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 ttm 
crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic 
ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc 
sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp 
hid mxm_wmi cryptd
  [ 3117.882309]  drm libahci megaraid_sas pps_core mdio wmi
  [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW
4.15.0-30-generic #32-Ubuntu
  [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS 
SE5C610.86B.01.01.0022.062820171903 06/28/2017
  [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat]
  [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246
  [ 3117.882322] RAX:  RBX: 90de4000 RCX: 
1924
  [ 3117.882323] RDX:  RSI: 88d749ae6400 RDI: 
88d655e96600
  [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 
0018
  [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 
88d655e96600
  [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 
88d7493dc000
  [ 3117.882327] FS:  () GS:88d77f38() 
knlGS:
  [ 3117.882327] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 
003606e0
  [ 3117.882329] DR0:  DR1:  DR2: 

  [ 3117.882330] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 3117.882331] Call Trace:
  [ 3117.882332]  
  [ 3117.882337]  ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4]
  [ 3117.882339]  nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4]
  [ 3117.882342]  iptable_nat_ipv4_out+0x15/0x20 [iptable_nat]
  [ 3117.882347]  nf_hook_slow+0x48/0xc0
  [ 3117.882353]  ip_output+0xd2/0xe0
  [ 3117.882355]  ? ip_fragment.constprop.44+0x80/0x80
  [ 3117.882357]  ip_forward_finish+0x49/0x70
  [ 3117.882359]  ip_forward+0x366/0x440
  [ 3117.882361]  ? ip_frag_mem+0x20/0x20
  [ 3117.882362]  ip_rcv_finish+0x129/0x430
  [ 3117.882364]  ip_rcv+0x28f/0x3a0
  [ 3117.882366]  ? inet_del_offload+0x40/0x40
  [ 3117.882372]  __netif_receive_skb_core+0x432/0xb40
  [ 3117.882379]  ? handle_edge_irq+0x7c/0x190
  [ 3117.882384]  ? irq_exit+0x67/0xc0
  [ 3117.882391]  ? do_IRQ+0x82/0xd0
  [ 3117.882393]  __netif_receive_skb+0x18/0x60
  [ 3117.882395]  ? __netif_receive_skb+0x18/0x60
  [ 3117.882397]  netif_receive_skb_internal+0x37/0xd0
  [ 3117.882398]  napi_gro_receive+0xc5/0xf0
  [ 3117.882407]  ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe]
  [ 3117.882411]  ixgbe_poll+0x256/0x710 [ixgbe]
  [ 3117.882413]  ? do_IRQ+0x82/0xd0
  [ 3117.882415]  net_rx_action+0x140/0x3a0
  [ 3117.882418]  __do_softirq+0xdf/0x2b2
  [ 3117.882419]  irq_exit+0xb6/0xc0
  [ 3117.882421]  do_IRQ+0x82/0xd0
  [ 3117.882423]  common_interrupt+0x84/0x84
  [ 3117.882424]  
  [ 3117.882427] RIP: 

[Kernel-packages] [Bug 1866326] Re: Login freezes when using Nvidia drivers 435 and 440

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435
(Ubuntu)

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

Title:
  Login freezes when using Nvidia drivers 435 and 440

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I
  have chosen to use "discrete graphics" which means that I am using the
  Nvidia card.

  Until a recent update everything was working fine. After the automatic
  update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly
  an upgrade of the Nvidia drivers) the opearing system hands after I
  enter the login credentials. I have tried to get some output from the
  startup screen by removing the "quite splash" from the grub file but
  it does not give any error information. It just hangs.

  I am using Nouveau to login to the computer, but with Nouveau I the
  HDMI port is not working

  I can try to add more debugging information if one helps me to collect
  it

  I am using Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  6 11:39:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: I don't know
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2297]
   NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2297]
  InstallationDate: Installed on 2020-02-29 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20QQS1JE00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET34W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QQS1JE00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P53
  dmi.product.name: 20QQS1JE00
  dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
  dmi.product.version: ThinkPad P53
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1866326/+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 1866326] [NEW] Login freezes when using Nvidia drivers 435 and 440

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I have
chosen to use "discrete graphics" which means that I am using the Nvidia
card.

Until a recent update everything was working fine. After the automatic
update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly an
upgrade of the Nvidia drivers) the opearing system hands after I enter
the login credentials. I have tried to get some output from the startup
screen by removing the "quite splash" from the grub file but it does not
give any error information. It just hangs.

I am using Nouveau to login to the computer, but with Nouveau I the HDMI
port is not working

I can try to add more debugging information if one helps me to collect
it

I am using Ubuntu 18.04.4

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  6 11:39:29 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: I don't know
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2297]
 NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2297]
InstallationDate: Installed on 2020-02-29 (5 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: LENOVO 20QQS1JE00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET34W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QQS1JE00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QQS1JE00
dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: nvidia-graphics-drivers-435 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic freeze ubuntu
-- 
Login freezes when using Nvidia drivers 435 and 440
https://bugs.launchpad.net/bugs/1866326
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-435 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 1866224] 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 1866224

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

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

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

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

** Tags added: 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/1866224

Title:
  mercurial autopkgtest is failing on s390x

Status in git package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mercurial package in Ubuntu:
  New

Bug description:
  Mercurial autopkgtest started failing with git/1:2.25.1-1ubuntu1:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  focal/focal/s390x/m/mercurial/20200305_163916_8dbb2@/log.gz

  ...
  # Test test-bundle2-exchange.t#sshv1 
  ok
  test-bundle2-exchange.t#sshv1
  test-bundle2-exchange.t#sshv1 ... # Running sh 
"/tmp/hgtests.30cCY5/child94/test-bundle2-exchange.t-sshv1.sh" 

  --- /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t
  +++ 
/tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t#sshv1.err
  @@ -880,42 +880,47 @@
 adding changesets
 adding manifests
 adding file changes
  -  transaction abort!
  -  Cleaning up the mess...
  -  rollback completed
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  added 1 changesets with 1 changes to 1 files
 pushkey: lock state after "phases"
 lock:  free
 wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_NEW_OBSMARKERS=0 HG_NODE=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a 
HG_NODE_LAST=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_SOURCE=push 
HG_TXNID=TXN:$ID$ HG_TXNNAME=push HG_URL=file:$TESTTMP/other
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  file:/*/$TESTTMP/other HG_URL=file:$TESTTMP/other (glob)
 $ hg -R main push ssh://user@dummy/other -r e7ec4e813ba6
 pushing to ssh://user@dummy/other
 searching for changes
  -  remote: adding changesets
  -  remote: adding manifests
  -  remote: adding file changes
  -  remote: transaction abort!
  -  remote: Cleaning up the mess...
  -  remote: rollback completed
  +  no changes found
  +  remote: pre-close-tip:e7ec4e813ba6 draft 
 remote: pushkey: lock state after "phases"
 remote: lock:  free
 remote: wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  remote: postclose-tip:e7ec4e813ba6 draft 
  +  remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env 
HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ 
HG_TXNNAME=serve HG_URL=remote:ssh:$LOCALIP
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  ssh://user@dummy/other HG_URL=ssh://user@dummy/other
  +  [1]
 $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6
 pushing to http://localhost:$HGPORT2/
 searching for changes
  -  remote: adding changesets
  -  remote: adding manifests
  -  remote: adding file changes
  -  remote: transaction abort!
  -  remote: Cleaning up the mess...
  -  remote: rollback completed
  +  no changes found
  +  remote: pre-close-tip:e7ec4e813ba6 draft 
 remote: pushkey: lock state after "phases"
  # Killing daemon process 21822 
 remote: lock:  free
 remote: wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  remote: postclose-tip:e7ec4e813ba6 draft 
  +  remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env 
HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ 
HG_TXNNAME=serve HG_URL=remote:http:$LOCALIP:
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  http://localhost:$HGPORT2/ HG_URL=http://localhost:$HGPORT2/
  +  [1]
   
   Test lazily acquiring the lock during unbundle
 $ cp $TESTTMP/hgrc.orig $HGRCPATH

  ERROR: test-bundle2-exchange.t#sshv1 output changed
  !# Ret was: 0 (test-bundle2-exchange.t#sshv1) 
  test-bundle2-exchange.t#sshv2
  test-bundle2-exchange.t#sshv2 ... # Test 

[Kernel-packages] [Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -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: 1865109
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 05:56 UTC
  reason:
-   build-packages-ppa: Pending -- building in ppa lrm:failed
+   promote-to-proposed: Pending -- source package tags missing
  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/1865200

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1865109
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 05:56 UTC
  reason:
promote-to-proposed: Pending -- source package tags missing
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+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 1865109] Re: bionic/linux: 4.15.0-91.92 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1863339, bug 1865480
+   bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+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 1866333] [NEW] Focal update: v5.4.24 upstream stable release

[Paolo Pisati]

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:

   v5.4.24 upstream stable release
   from git://git.kernel.org/


Linux 5.4.24
blktrace: Protect q->blk_trace with RCU
kvm: nVMX: VMWRITE checks unsupported field before read-only field
kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field
mm, thp: fix defrag setting if newline is not used
mm/huge_memory.c: use head to check huge zero page
mm/gup: allow FOLL_FORCE for get_user_pages_fast()
mm/debug.c: always print flags in dump_page()
locking/lockdep: Fix lockdep_stats indentation problem
xfs: clear kernel only flags in XFS_IOC_ATTRMULTI_BY_HANDLE
bus: tegra-aconnect: Remove PM_CLK dependency
netfilter: nf_flowtable: fix documentation
netfilter: nft_tunnel: no need to call htons() when dumping ports
thermal: brcmstb_thermal: Do not use DT coefficients
thermal: db8500: Depromote debug print
ubifs: Fix ino_t format warnings in orphan_delete()
rcu: Allow only one expedited GP to run concurrently with wakeups
KVM: x86: Remove spurious clearing of async #PF MSR
KVM: x86: Remove spurious kvm_mmu_unload() from vcpu destruction path
x86/resctrl: Check monitoring static key in the MBM overflow handler
perf ui gtk: Add missing zalloc object
perf hists browser: Restore ESC as "Zoom out" of DSO/thread/etc
pwm: omap-dmtimer: put_device() after of_find_device_by_node()
lib/vdso: Update coarse timekeeper unconditionally
lib/vdso: Make __arch_update_vdso_data() logic understandable
kprobes: Set unoptimized flag after unoptimizing code
ima: ima/lsm policy rule loading logic bug fixes
drivers: net: xgene: Fix the order of the arguments of 'alloc_etherdev_mqs()'
RDMA/hns: Bugfix for posting a wqe with sge
RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs
f2fs: fix to add swap extent correctly
sched/fair: Optimize select_idle_cpu
KVM: Check for a bad hva before dropping into the ghc slow path
KVM: SVM: Override default MMIO mask if memory encryption is enabled
mwifiex: delete unused mwifiex_get_intf_num()
mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame()
namei: only return -ECHILD from follow_dotdot_rcu()
kbuild: make single target builds even faster
kbuild: remove unneeded variable, single-all
kbuild: move headers_check rule to usr/include/Makefile
kbuild: remove header compile test
selftests: Install settings files to fix TIMEOUT failures
net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
net/smc: no peer ID in CLC decline for SMCD
net: atlantic: fix out of range usage of active_vlans array
net: atlantic: fix potential error handling
net: atlantic: fix use after free kasan warn
net: netlink: cap max groups which will be considered in netlink_bind()
s390/qeth: vnicc Fix EOPNOTSUPP precedence
nvme-pci: Hold cq_poll_lock while completing CQEs
usb: charger: assign specific number for enum value
hv_netvsc: Fix unwanted wakeup in netvsc_attach()
kbuild: fix DT binding schema rule to detect command line changes
mac80211: Remove a redundant mutex unlock
nl80211: fix potential leak in AP start
drm/i915/gvt: Separate display reset from ALL_ENGINES reset
drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime
i2c: jz4780: silence log flood on txabrt
i2c: altera: Fix potential integer overflow
MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
HID: hiddev: Fix race in in hiddev_disconnect()
HID: alps: Fix an error handling path in 'alps_input_configured()'
netfilter: xt_hashlimit: reduce hashlimit_mutex scope for htable_put()
netfilter: ipset: Fix forceadd evaluation path
vhost: Check docket sk_family instead of call getname
net/smc: transfer fasync_list in case of fallback
netfilter: ipset: Fix "INFO: rcu detected stall in hash_xxx" reports
io_uring: fix 32-bit compatability with sendmsg/recvmsg
cpufreq: Fix policy initialization for internal governor drivers
amdgpu/gmc_v9: save/restore sdpif regs during S3
Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
tracing: Disable trace_printk() on post poned tests
macintosh: therm_windtunnel: fix regression when instantiating devices
drm/radeon: Inline drm_get_pci_dev
drm/amdgpu: Drop DRIVER_USE_AGP
HID: core: increase HID report buffer size to 8KiB
HID: core: fix off-by-one memset in hid_report_raw_event()
HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
KVM: VMX: check descriptor table exits on instruction emulation
ACPI: watchdog: Fix gas->access_width usage
ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
audit: always check the netlink payload length in audit_receive_msg()
audit: fix 

[Kernel-packages] [Bug 1866224] Re: mercurial autopkgtest is failing on s390x

[Balint Reczey]

OK, so I've been able to reproduce the issue locally with 5.4 kernel,
running Focal as the lxc host.

Linux autopkgtest-lxd-eyhbbj 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6
22:46:43 UTC 2020 s390x s390x s390x GNU/Linux

I did not observe the failure with Eoan host, kernel 5.3.x

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

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

Title:
  mercurial autopkgtest is failing on s390x

Status in git package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in mercurial package in Ubuntu:
  New

Bug description:
  Mercurial autopkgtest started failing with git/1:2.25.1-1ubuntu1:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  focal/focal/s390x/m/mercurial/20200305_163916_8dbb2@/log.gz

  ...
  # Test test-bundle2-exchange.t#sshv1 
  ok
  test-bundle2-exchange.t#sshv1
  test-bundle2-exchange.t#sshv1 ... # Running sh 
"/tmp/hgtests.30cCY5/child94/test-bundle2-exchange.t-sshv1.sh" 

  --- /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t
  +++ 
/tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t#sshv1.err
  @@ -880,42 +880,47 @@
 adding changesets
 adding manifests
 adding file changes
  -  transaction abort!
  -  Cleaning up the mess...
  -  rollback completed
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  added 1 changesets with 1 changes to 1 files
 pushkey: lock state after "phases"
 lock:  free
 wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_NEW_OBSMARKERS=0 HG_NODE=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a 
HG_NODE_LAST=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_SOURCE=push 
HG_TXNID=TXN:$ID$ HG_TXNNAME=push HG_URL=file:$TESTTMP/other
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  file:/*/$TESTTMP/other HG_URL=file:$TESTTMP/other (glob)
 $ hg -R main push ssh://user@dummy/other -r e7ec4e813ba6
 pushing to ssh://user@dummy/other
 searching for changes
  -  remote: adding changesets
  -  remote: adding manifests
  -  remote: adding file changes
  -  remote: transaction abort!
  -  remote: Cleaning up the mess...
  -  remote: rollback completed
  +  no changes found
  +  remote: pre-close-tip:e7ec4e813ba6 draft 
 remote: pushkey: lock state after "phases"
 remote: lock:  free
 remote: wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  remote: postclose-tip:e7ec4e813ba6 draft 
  +  remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env 
HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ 
HG_TXNNAME=serve HG_URL=remote:ssh:$LOCALIP
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  ssh://user@dummy/other HG_URL=ssh://user@dummy/other
  +  [1]
 $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6
 pushing to http://localhost:$HGPORT2/
 searching for changes
  -  remote: adding changesets
  -  remote: adding manifests
  -  remote: adding file changes
  -  remote: transaction abort!
  -  remote: Cleaning up the mess...
  -  remote: rollback completed
  +  no changes found
  +  remote: pre-close-tip:e7ec4e813ba6 draft 
 remote: pushkey: lock state after "phases"
  # Killing daemon process 21822 
 remote: lock:  free
 remote: wlock: free
  -  abort: Clown phase push failed
  -  [255]
  +  remote: postclose-tip:e7ec4e813ba6 draft 
  +  remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env 
HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ 
HG_TXNNAME=serve HG_URL=remote:http:$LOCALIP:
  +  pre-close-tip:e7ec4e813ba6 draft 
  +  postclose-tip:e7ec4e813ba6 draft 
  +  txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose 
HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response
  +  http://localhost:$HGPORT2/ HG_URL=http://localhost:$HGPORT2/
  +  [1]
   
   Test lazily acquiring the lock during unbundle
 $ cp $TESTTMP/hgrc.orig $HGRCPATH

  ERROR: test-bundle2-exchange.t#sshv1 output changed
  !# Ret was: 0 (test-bundle2-exchange.t#sshv1) 
  test-bundle2-exchange.t#sshv2
  test-bundle2-exchange.t#sshv2 ... # Test test-bundle2-exchange.t#sshv2 
  # Running sh "/tmp/hgtests.30cCY5/child95/test-bundle2-exchange.t-sshv2.sh" 
  # Killing daemon process 22519 
  # Ret was: 0 (test-bundle2-exchange.t#sshv2) 
  ok
  ...

  The tests are passing locally in lxc on bionic s390x host:

  Linux 

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Harry W. Haines, III]

There are two separate issues presented here now and it has become
confusing to the person it was assigned to.  The original issue was the
latest firmware update: linux-firmware 1.173.15 with the current HWE
5.3.0-40-generic kernel causing issues with the AMD Oland graphics.

It was apparent on boot time there was an issue because usually this
system boots in under 10 seconds.  Looked in dmesg and saw all the time
outs for the Oland card.  Rolled back to the previous firmware version,
1.173.12 and the problem went away.

Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340] vendor: ASUSTeK driver: radeon

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 

[Kernel-packages] [Bug 1865106] Re: xenial/linux: 4.4.0-176.206 -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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
+   xenial/linux-raspi2: bug 1863324
+   xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  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/1865106

Title:
  xenial/linux: 4.4.0-176.206 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  variant: debs

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

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

Title:
  btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test failure in fallocate06 was composed by two issues, one is xfs
  fill_fs test issue addressed in bug 1865967.

  Another is this one, this is the case 2 of btrfs (fill_fs):

  tst_test.c:1290: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2

  This issue can be found from X to F
  X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/
  B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
  D - https://pastebin.ubuntu.com/p/cryTnnn5wF/
  E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
  F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/

  Note that the hint printed in the test:
HINT: You _MAY_ be missing kernel fixes, see:
   
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e

  It something that will get printed after the test, as it's for XFS so
  it has nothing to do with this issue here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+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 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

** Description changed:

- This test failures can be found on different releases:
+ Test failure in fallocate06 was composed by two issues, one is btrfs
+ fill_fs test issue addressed in bug 1866323.
  
+ Another is this one, this is the case 2 of xfs (fill_fs):
+ tst_test.c:1290: INFO: Testing on xfs
+ tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts=''
+ tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
+ fallocate06.c:117: INFO: Copy-on-write is not supported
+ fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
+ fallocate06.c:157: PASS: write() successful
+ fallocate06.c:201: PASS: Misaligned allocation works as expected
+ fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
+ fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
+ fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
+ tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827
+ tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
+ fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
+ fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
+ fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
+ 
+ 
+ This test failures can be found from X to E
  X - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)
  
  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!
  
  https://pastebin.ubuntu.com/p/9FfVrZkQN8/
  
  B - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)
  
  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!
  
  https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
  
  D - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)
  
  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!
  
  https://pastebin.ubuntu.com/p/cryTnnn5wF/
  
  E - 2 failures reported:
  fallocate06.c:151: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)
  
  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!
  
  https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
- 
- F - 1 failure reported:
- fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)
- 
- Test didn't terminates with BROK.
- 
- https://pastebin.ubuntu.com/p/FKPJKCS2zr/

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

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

Title:
  xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

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

Bug description:
  Test failure in fallocate06 was composed by two issues, one is btrfs
  fill_fs test issue addressed in bug 1866323.

  Another is this one, this is the case 2 of xfs (fill_fs):
  tst_test.c:1290: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is not supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: 

[Kernel-packages] [Bug 1866323] [NEW] btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

Public bug reported:

Test failure in fallocate06 was composed by two issues, one is xfs
fill_fs test issue addressed in bug 1865967.

Another is this one, this is the case 2 of btrfs (fill_fs):

tst_test.c:1290: INFO: Testing on btrfs
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
fallocate06.c:117: INFO: Copy-on-write is supported
fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
fallocate06.c:157: PASS: write() successful
fallocate06.c:201: PASS: Misaligned allocation works as expected
fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) 
successful
fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) 
cleared the correct file range
fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
fallocate06.c:157: PASS: write() successful
fallocate06.c:201: PASS: Misaligned allocation works as expected
fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) 
failed unexpectedly: ENOSPC (2

This issue can be found from X to F
X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/
B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
D - https://pastebin.ubuntu.com/p/cryTnnn5wF/
E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/

Note that the hint printed in the test:
  HINT: You _MAY_ be missing kernel fixes, see:
 
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e

It something that will get printed after the test, as it's for XFS so it
has nothing to do with this issue here.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: bionic disco eoan focal kqa-blocker sru-20200217 xenial

** Description changed:

  Test failure in fallocate06 was composed by two issues, one is xfs
  fill_fs test issue addressed in bug 1865967.
  
  Another is this one, this is the case 2 of btrfs (fill_fs):
  
  tst_test.c:1290: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2
  
  This issue can be found from X to F
  X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/
  B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
  D - https://pastebin.ubuntu.com/p/cryTnnn5wF/
  E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
  F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/
+ 
+ Note that the hint printed in the test:
+   HINT: You _MAY_ be missing kernel fixes, see:
+  
+  

[Kernel-packages] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

** Summary changed:

- fallocate06 from ubuntu_ltp_syscalls failed
+ xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

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

Title:
  xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  This test failures can be found on different releases:

  X - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)

  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!

  https://pastebin.ubuntu.com/p/9FfVrZkQN8/

  B - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)

  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!

  https://pastebin.ubuntu.com/p/Zc9TW4sQKF/

  D - 2 failures reported:
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)

  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!

  https://pastebin.ubuntu.com/p/cryTnnn5wF/

  E - 2 failures reported:
  fallocate06.c:151: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)

  Test terminates with:
  tst_test.c:1274: BROK: Test killed by SIGIOT/SIGABRT!

  https://pastebin.ubuntu.com/p/FXTZpsX7Qb/

  F - 1 failure reported:
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28)

  Test didn't terminates with BROK.

  https://pastebin.ubuntu.com/p/FKPJKCS2zr/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865967/+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 1864897] Re: booting 5.3.0-40 with encrypted disk fails

[a]

Kernel installed as described in
https://wiki.ubuntu.com/Kernel/MainlineBuilds . First dpkg -i linux-
image-
unsigned-5.6.0-050600rc4-generic_5.6.0-050600rc4.202003012332_amd64.deb
was terminated unsuccessfully with error messages; trying it again as
last instead of third file yielded several messages but worked. The test
kernel boots OK, i. e., the password for disk decryption is asked for
and afterwards the user password.

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

Title:
  booting 5.3.0-40 with encrypted disk fails

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up
  in a blank screen. Selecting 5.3.0-29 in the grub menu instead works,
  i. e., "please unlock disk" is displayed and after doing so xubuntu
  19.10 is started. The installation is encrypted as provided by the
  installer. Is some different but might be related to bug #1863759.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Feb 26 18:11:45 2020
  InstallationDate: Installed on 2019-10-17 (131 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-02-24 17:34:11.828555
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   None
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1309 F pulseaudio
   /dev/snd/controlC0:  al 1309 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-17 (137 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864897/+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 1865245] Re: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 02. March 2020 10:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1865244
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1104.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 02. March 2020 10:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1865244
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865245/+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 1865190] Re: eoan/linux-azure: 5.3.0-1015.17 -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: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   build-packages-ppa: Ongoing -- building in ppa lrm:depwait
- signed:depwait
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1865189
  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/1865190

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  In Progress
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:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
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: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1865189
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865190/+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 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -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: 1863338
+ kernel-stable-master-bug: 1865106
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1134.142 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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: 1865106
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863329/+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 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -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: 1863338
+ kernel-stable-master-bug: 1865106
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 20. February 2020 16:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1863322
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1130.139 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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: 1865106
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 20. February 2020 16:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1863322
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+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 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker

[Gavin Lin]

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

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

Title:
  xenial/linux-snapdragon: 4.4.0-1134.142 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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: 1863338
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
  variant: debs

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

[Gavin Lin]

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

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

Title:
  bionic/linux-raspi2: 4.15.0-1057.61 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1865109
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 27. February 2020 09:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1864725
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864726/+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 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker

[Gavin Lin]

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

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

Title:
  xenial/linux-raspi2: 4.4.0-1130.139 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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: 1865106
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 20. February 2020 16:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1863322
  variant: debs

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

[Gavin Lin]

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

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

Title:
  bionic/linux-snapdragon: 4.15.0-1074.81 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1865109
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 27. February 2020 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1864727
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864729/+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 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

[Gavin Lin]

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

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1865111
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Monday, 17. February 2020 23:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863269/+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 1866056] Re: [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config

[Frank Heimes]

Request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-March/thread.html#108047
changing status to 'In Progress'.

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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(fheimes)

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

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

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

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

Title:
  [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in
  kernel config

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  The current CONFIG_PCI_NR_FUNCTIONS setting (64) is not sufficient
  anymore for network adapters that support SRIOV and up to 130 PCI
  functions.

  Therefore we need to increase the CONFIG_PCI_NR_FUNCTIONS value to 512,
  within the kernel config for Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866056/+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 1865251] Re: xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865109
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 02. March 2020 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1865249
xenial/linux-gcp/gke-kernel: bug 1865250
  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/1865251

Title:
  xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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: 1865109
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 02. March 2020 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1865249
xenial/linux-gcp/gke-kernel: bug 1865250
  variant: debs

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

[MARTIN]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1865471/+attachment/5333832/+files/Lspci.txt

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

  There many months than I use "suspend" (settings -> energy -> When the
  shutdown button...) on Ubuntu 18.04 or 19.10.

  But at each wake up from my computer, the USB 3.1 Gen 1 ports (only
  motherboard back panel) no work after (loose use of webcam,
  keyboard...).

  No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from internal USB 
header).
  No problems with USB 2.0/1.1 ports (motherboard back panel).

  I think my motherboard is not at fault because I did not reproduce this bug 
on Windows 10.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-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/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  christophe   1565 F pulseaudio
   /dev/snd/controlC0:  christophe   1565 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (15 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-40-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/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1865190] Re: eoan/linux-azure: 5.3.0-1015.17 -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: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   build-packages-ppa: Ongoing -- building in ppa main:building
+   build-packages-ppa: Ongoing -- building in ppa lrm:depwait
+ signed:depwait
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1865189
  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/1865190

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  In Progress
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:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
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: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
build-packages-ppa: Ongoing -- building in ppa lrm:depwait
  signed:depwait
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1865189
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865190/+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 1865431] Re: bionic/linux-gcp: 5.0.0-1033.34 -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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:51 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Stalled -- package copies requested to Proposed
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

** 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:51 UTC
  reason:
-   promote-to-proposed: Stalled -- package copies requested to Proposed
+   build-packages-proposed: Ongoing -- building in Proposed
+ signed:depwait
+   promote-to-proposed: Stalled -- packages copying to Proposed
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

** 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:51 UTC
  reason:
-   build-packages-proposed: Ongoing -- building in Proposed
- signed:depwait
+   build-packages-proposed: Pending -- building in Proposed
+ signed:queued
promote-to-proposed: Stalled -- packages copying to Proposed
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  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/1865431

Title:
  bionic/linux-gcp: 5.0.0-1033.34 -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 verification-testing series:
  New
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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:51 UTC
  reason:
build-packages-proposed: Pending -- building in Proposed
  signed:queued
promote-to-proposed: Stalled -- packages copying to Proposed
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865431/+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 1865111] Re: eoan/linux: 5.3.0-42.34 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  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/1865111

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865111/+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 1865111] Re: eoan/linux: 5.3.0-42.34 -proposed tracker

[Canonical Certification Team]

Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/Hl9UGd57/312-eoan-linux-
image-530-42-generic-530-4234

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1865139
eoan/linux-aws: bug 1865482
eoan/linux-azure: bug 1865190
eoan/linux-gcp: bug 1865491
eoan/linux-kvm: bug 1865438
eoan/linux-oracle: bug 1865493
eoan/linux-raspi2: bug 1863269
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865111/+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 1866196] Re: hugeshmctl01 from hugetlb in ubuntu_ltp failed on B / E

[Po-Hsu Lin]

Found on Eoan as well.

** Summary changed:

- hugeshmctl01 from hugetlb in ubuntu_ltp failed on B
+ hugeshmctl01 from hugetlb in ubuntu_ltp failed on B / E

** Tags added: 5.3 eoan

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

Title:
  hugeshmctl01 from hugetlb in ubuntu_ltp failed on B / E

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue found on Bionic, across amd64 / arm64 / i386 / P8 / s390x

  <<>>
  tag=hugeshmctl01 stime=1583419276
  cmdline="hugeshmctl01 -i 5"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  mem.c:817: INFO: set nr_hugepages to 128
  hugeshmctl01.c:198: PASS: pid, size, # of attaches and mode are correct - 
pass #0
  hugeshmctl01.c:198: PASS: pid, size, # of attaches and mode are correct - 
pass #1
  hugeshmctl01.c:263: PASS: new mode and change time are correct
  hugeshmctl01.c:280: PASS: shmctl in func_rmid() failed as expected, shared 
memory appears to be removed
  tst_checkpoint.c:149: BROK: hugeshmctl01.c:152: tst_checkpoint_wait(0, 
1): ETIMEDOUT (110)
  mem.c:817: INFO: set nr_hugepages to 0

  Summary:
  passed   4
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  dmesg on s2lp3:
  [84600.210919] BUG: non-zero pgtables_bytes on freeing mm: 16384
  [84600.211628] BUG: non-zero pgtables_bytes on freeing mm: 16384
  [84601.361848] LTP: starting hugeshmctl01 (hugeshmctl01 -i 5)
  [84602.435421] User process fault: interruption code 003b ilc:2 in 
hugeshmctl01[2aa33f0+25000]
  [84602.435435] Failing address: 0200 TEID: 02000400
  [84602.435437] Fault in primary space mode while using user ASCE.
  [84602.435439] AS:00079ec141c7 R3:0024
  [84602.435444] CPU: 3 PID: 74199 Comm: hugeshmctl01 Tainted: P   O
 4.15.0-91-generic #92-Ubuntu
  [84602.435445] Hardware name: IBM 2964 N63 400 (LPAR)
  [84602.435447] User PSW : a994e531 a60b6ea2
  [84602.435449]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [84602.435450] User GPRS:  02aa0002  
0004
  [84602.435451]02aa33f06602 03ffb679ecf8  

  [84602.435452]03ff0002 02aa 02aa 
0200
  [84602.435453]03ffb69a6000 02aa33f1b300 02aa33f06602 
03ffd6d7dfa8
  [84602.435462] User Code: 02aa33f06640: e3101012  lt  
%r1,0(%r1)
    02aa33f06646: a7840038  brc 
8,02aa33f066b6
   #02aa33f0664a: c4b80001061b  lgrl
%r11,02aa33f27280
   >02aa33f06650: 50a0b000  st  
%r10,0(%r11)
    02aa33f06654: a7690001  lghi%r6,1
    02aa33f06658: a759  lghi%r5,0
    02aa33f0665c: a749  lghi%r4,0
    02aa33f06660: a739008d  lghi%r3,141
  [84602.435472] Last Breaking-Event-Address:
  [84602.435476]  [<02aa33f06602>] 0x2aa33f06602

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-91-generic 4.15.0-91.92
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Mar  5 14:41:35 2020
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M audit=0 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-91-generic N/A
   linux-backports-modules-4.15.0-91-generic  N/A
   linux-firmware 1.173.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this