[Kernel-packages] [Bug 1863874] Re: Backport GetFB2 ioctl

[Timo Aaltonen]

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

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

Title:
  Backport GetFB2 ioctl

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  We need this in order to re-enable intel CCS compression, which was
  originally disabled in mesa to fix this bug:

  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776

  GetFB2 was recently added to drm-misc, and should get upstream in 5.7,
  but would be best to have it in focal and unstable kernel so that the
  userland parts can be added.

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

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

[Kernel-packages] [Bug 1851956] Re: [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After is normal.

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

Title:
  [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After
  is normal.

Status in linux package in Ubuntu:
  Expired

Bug description:
  When init the grub boot, stop and wait for 2 minutes, circa...
  After this time, normal speed and OS load normally, no problem !!! Ubuntu 
Studio 18.04 LTS. Sony Vaio VPCEE45B. 
  Ubuntu Studio 20.04 (Daily) work fine, without wait 
  Thanks
  

  (My english is bad,,,sorry)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18
  Uname: Linux 4.15.0-66-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov  9 16:26:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] 
[104d:9077]
  InstallationDate: Installed on 2019-11-08 (1 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Sony Corporation VPCEE45FB
  ProcEnviron:
   LANGUAGE=pt_BR
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0200Z5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEE45FB
  dmi.product.version: C8002NHR
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Nov  9 15:54:20 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Atsushi Enomoto]

Thanks, with 5.3.0-43 it's working again.

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  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.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867663] Re: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

[Daniel van Vugt]

"upgrade your system" just means to run:

  sudo apt update
  sudo apt full-upgrade

And yeah it sounds like the retracing service is confused between
nvidia-340 and nvidia-390. If that happens again then please report a
bug about that to the relevant package you have installed with something
like:

  ubuntu-bug nvidia-driver-390

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

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

[Anthony Wong]

As we got two reports that this issue has been fixed, I'm closing this
bug. Feel free to report back if you see the issue unresolved. Thanks!

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

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

Status in linux package in Ubuntu:
  Fix Released

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 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Hui Wang]

5.3.0-43 is in the proposed, please try -43 kernel.

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  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.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Schuyler Duveen]

The same kernel update broke suspend: after resuming, the mouse and
keyboard don't work -- just reporting here in case this helps locate the
core issue.

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  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.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1853993] Re: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

[Ike Panhc]

Thanks. kernel 5.3.0-43.36 works for me.

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

Title:
  [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init
  device

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Disks will be lost on SAS interface reset

  [Fix]
  scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

  [Test]
  Resetting SAS interfaces shall not lose any disks

  [Regression Potential]
  Patch only for hisi_sas. Lowest risk for other platform/driver.

  "[Steps to Reproduce]
  1. Close all the PHYS;
  2. Inject error;
  3. Open one PHY;

  [Actual Results]
  Some disk will be lost

  [Expected Results]
  No disk will be lost

  [Reproducibility]
  occasionally

  [Additional information]
  Hardware: D06 CS
  Firmware: NA
  Kernel: NA

  [Resolution]
  When init device for SAS disks, it will send TMF IO to clear disks. At that
  time TMF IO is broken by some operations such as injecting controller reset
  from HW RAs event, the TMF IO will be timeout, and at last device will be
  gone. Print is as followed:

  hisi_sas_v3_hw :74:02.0: dev[240:1] found
  ...
  hisi_sas_v3_hw :74:02.0: controller resetting...
  hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11
  hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11
  hisi_sas_v3_hw :74:02.0: controller reset complete
  hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done
  hisi_sas_v3_hw :74:02.0: dev[240:1] is gone
  sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d,
  error:5

  To improve the reliability, retry TMF IO max of 3 times for SAS disks which
  is the same as softreset does."

  scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1853993/+subscriptions

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

[Kernel-packages] [Bug 1853964] Re: [hns-1126]net: hns3: make hclge_service use delayed workqueue

[Ike Panhc]

Thanks. kernel 5.3.0-43.36 works for me.

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

Title:
  [hns-1126]net: hns3: make hclge_service use delayed workqueue

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  System crashes when setting irq affinity and turning on/off on the interfaces

  [Fix]
  net: hns3: make hclge_service use delayed workqueue

  [Test]
  Writing smp_affinity_list and turning on/off in loop

  [Regression Potential]
  This patch only for hns3. Lowest risk for other platform/driver

  "[Bug Description]
  Currently, up/down port process may concurrently operate 
timer(del_timer_sync/add_timer_on) with setting IRQ affinity, and cause system 
breaking down.

  [Steps to Reproduce]
  set misc irp affinity of PF during up/down port by follow script:
  while((1))
  do
  for i in {0..31}; do echo $i > /proc/irq/678/smp_affinity_list; done
  done
  while((1))
  do
  ifconfig eth4 down
  ifconfig eth4 up
  done

  [Actual Results]
  System break down.
  kernel call trace

  [Expected Results]
  System run normally.

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  This patch uses delayed work instead of using timers to trigger the
  hclge_serive."

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1853964/+subscriptions

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

[Kernel-packages] [Bug 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error

[Ike Panhc]

Thanks. kernel 5.3.0-43.36 works for me.

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

Title:
  [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Sometimes, TPM fails because SPI data error

  [Fix]
  bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error

  [Test]
  Reboot system few times and no TPM error message

  [Regression Potential]
  Only on SPI function. Already tested on focal kernel

  [Bug Description]

  Because of out-of-order execution about some CPU architecture,
  In this debug stage we find Completing spi interrupt enable ->
  prodrucing TXEI interrupt -> running "interrupt_transfer" function
  will prior to set "dw->rx and dws->rx_end" data, so this patch add
  memory barrier to enable dw->rx and dw->rx_end to be visible and
  solve to send SPI data error.
  eg:
  it will fix to this following low possibility error in testing environment
  which using SPI control to connect TPM Modules

  kernel: tpm tpm0: Operation Timed out
  kernel: tpm tpm0: tpm_relinquish_locality: : error -1

  [Steps to Reproduce]
  1) enable ima and tpm
  2)reboot this system
  3)

  [Actual Results]
  kernel: tpm tpm0: Operation Timed out
  kernel: tpm tpm0: tpm_relinquish_locality: : error -1

  [Expected Results]
  ok

  [Reproducibility]
  low probabilities

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1859744/+subscriptions

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

[Kernel-packages] [Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

[Ike Panhc]

Thanks. kernel 5.3.0-43.36 works for me.

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

Title:
  [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64
  platform

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  No TPM eventlog information in sysfs

  [Fix]
  d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

  [Test]
  ls -l /sys/kernel/security/tpm0/binary_bios_measurements

  [Regression Potential]
  Only affect arm64 system with TPM. Lowest risk for other platform.

  [Bug Description]

  this patch gets tpm eventlog information such as device boot status,event guid
  and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog"
  functions to get it for ARM64 platorm.

  [Steps to Reproduce]
  1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements
  2)
  3)

  [Actual Results]
  '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory

  [Expected Results]
  ok

  [Reproducibility]
  100%

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1859743/+subscriptions

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

[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support

[quanxian]

** Attachment added: "tgl_commit_20200313.list"
   
https://bugs.launchpad.net/intel/+bug/1855399/+attachment/5338577/+files/tgl_commit_20200313.list

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

Title:
  [TGL] graphics kernel support

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

Bug description:
  Description:

  This feature tracks the updates TGL graphics updates.

  We will submit the commit id lists since 5.4.

  20.04 will use v5.4 as a base, (2109/11/25)

  first commit lists will be provided in 2020/01, if you need more
  before that, please let us know.

  Target Release: 20.10
  Target Kernel: v5.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions

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

[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

[Hui Wang]

@Vamshee,

We are doing that, and almost done. please refer to:
https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1859754/comments/66

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

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  There are 2 physical speakers on the X1 7th, and one is Bass speaker
  and connect to a DAC which doesn't have volume control on it.

  [Fix]
  adjust that speaker to connect to a DAC which has volume control
  capability.

  
  [Test Case]
  adjust the output volume from UI and play sound from speaker.

  
  [Regression Risk]
  Low, these change is specific to 2 lenovo machines.


  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

[Hui Wang]

Please wait for the 5.3.0-43 kernel, and it is already in the -propose.
please refer to:

https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1859754/comments/66

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and is merged to focal
  kernel, now we backport this patch to Eoan kernel if -42 doesn't
  introduce this fix patch from stable.

  The patch introduced the crash:
  commit 063821115e02229d5fd3de31bad270d5e30aeb41
  Author: Dragos Tarcatu 
  Date: Mon Dec 9 18:39:38 2019 -0600

  ASoC: topology: Check return value for snd_soc_add_dai_link()

  BugLink: https://bugs.launchpad.net/bugs/1861929

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

  snd_soc_add_dai_link() might fail. This situation occurs for
  instance in a very specific use case where a PCM device and a
  Back End DAI link are given identical names in the topology.
  When this happens, soc_new_pcm_runtime() fails and then
  snd_soc_add_dai_link() returns -ENOMEM when called from
  soc_tplg_fe_link_create(). Because of that, the link will not
  get added into the card list, so any attempt to remove it later
  ends up in a panic.

  Fix that by checking the return status and free the memory in case
  of an error.

  Reviewed-by: Ranjani Sridharan 
  Signed-off-by: Dragos Tarcatu 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  
  [Impact]
  During the boot, the sof driver crash because the hdmi_pcm_list
  is not initialized before it is used.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backport
  this patch to ubuntu kernel

  [Test Case]
  Boot the -41 kernel with this patch added.
  blacklist the snd_soc_skl
  the kernel can boot successfully, and sof driver worked well

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. Focal kernel already
  has this patch and works well.



  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu 

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-base - 4.5ubuntu3

---
linux-base (4.5ubuntu3) focal; urgency=medium

  * Add linux-base-sgx package with SGX udev rules (LP: #1867820).

 -- Timo Aaltonen   Wed, 18 Mar 2020 13:05:24 +0200

** Changed in: linux-base (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  New
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867663] Re: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

[Diego]

Hi, Thank you for your feedback 
Upgrade my system? I'm using the developer version of Ubuntu (20.04)
Can I offer any other information to help?
Sorry I'm not a advanced user, but certainly my system isn't outdated.

Ps.: I'm not using nvidia-340. I'm using nvidia-390.132

Thank you again =D

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

[Vamshee Paduru]

@Shengyao how about 18.04 and kernel 5.0.0.1044-oem-osp1 ?...Can we
apply the fix in #5 ?...If I do that then the volume reduces but the mic
starts to work.And a HDMI1/2/3 Output -sof-skl_hda_card show up...Our
goal is to have the Mic functional on CMT Lake X1 Carbon 7th. Please let
us know.

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

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  There are 2 physical speakers on the X1 7th, and one is Bass speaker
  and connect to a DAC which doesn't have volume control on it.

  [Fix]
  adjust that speaker to connect to a DAC which has volume control
  capability.

  
  [Test Case]
  adjust the output volume from UI and play sound from speaker.

  
  [Regression Risk]
  Low, these change is specific to 2 lenovo machines.


  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867820] Please test proposed package

[Andy Whitcroft]

Hello Marcelo, or anyone else affected,

Accepted linux-base into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/linux-
base/4.5ubuntu1.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 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.

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  New
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  New

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Andy Whitcroft]

Hello Marcelo, or anyone else affected,

Accepted linux-base into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/linux-
base/4.5ubuntu2.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 and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: linux-base (Ubuntu Eoan)
   Status: New => Fix Committed

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

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  New
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  New

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867983] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Computer is freezed after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  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.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  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=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1867983] [NEW] Computer is freezed after suspend

[Glandos]

Public bug reported:

I am using an old HP EliteBook 6930p with current Ubuntu.

When the computer is suspended, even after a fresh boot, it does not
wake up: the power comes back, but the laptop is frozen, and does not
respond to ping.

It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

I am holding kernel purge for now, but this is annoying.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-29-generic 5.3.0-29.31
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.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  isabelle   1010 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 20:46:35 2020
HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
InstallationDate: Installed on 2015-03-15 (1830 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP EliteBook 6930p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
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=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCU Ver. F.12
dmi.board.name: 30DB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.27
dmi.chassis.asset.tag: CZC939161W
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 6930p
dmi.product.sku: J1610781
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug eoan wayland-session

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

Title:
  Computer is freezed after suspend

Status in linux package in Ubuntu:
  New

Bug description:
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  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.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  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=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

[Taha Soomro]

Anything we can do to help get this patched?

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug

[Taihsiang Ho]

Verified via

1. ping and is accessible externally via eth

2. checked the loaded kernel modules and enablement log of dmesg

3. checkbox-cli

$ checkbox-cli run com.canonical.certification::ethernet/detect
com.canonical.certification::ethernet/info_automated
com.canonical.certification::ethernet/info_automated_server

Finalizing session that hasn't been submitted anywhere: 
checkbox-run-2020-03-18T18.30.47
==[ Results ]===
 ☑ : Hardware Manifest
 ☑ : Detect if at least one ethernet device is detected
 ☑ : Enumerate available system executables
 ☑ : Collect information about hardware devices (udev)
 ☑ : Gather info on current state of network devices
 ☑ : Provide information about detected ethernet devices
ubuntu@scobee:~$ uname -a
Linux scobee 4.15.0-92-generic #93-Ubuntu SMP Mon Mar 16 15:40:04 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

Title:
  [hns3-0114]net: hns3: fix ETS bandwidth validation bug

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  When a TC's PFC is disabled or enabled, the RX private buffer for
  this TC need to be changed too, otherwise this may cause packet
  dropped problem.

  [Impact]
  The corresponding ethernet interface could not be up again.

  [Fix]
  cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653
  net: hns3: fix ETS bandwidth validation bug

  [Test Case]
  1.lldpad -d
  2.lldptool -L -i eth0 adminStatus=rxtx
  3.lldptool -T -i eth0 -V ETS-CFG
  tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets
  up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0
  4.down device
  5.up

  [Regression Risk]
  Low, the patch is only specific to the hns3 driver.


  == Original Bug Description ==

  
  [Bug Description]
  When a TC's PFC is disabled or enabled, the RX private buffer for
  this TC need to be changed too, otherwise this may cause packet
  dropped problem.

  [Steps to Reproduce]
  1.lldpad -d
  2.lldptool -L -i eth0 adminStatus=rxtx
  3.lldptool -T -i eth0 -V ETS-CFG 
tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets 
up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0
  4.down device
  5.up

  [Actual Results]
  up fail

  [Expected Results]
  up ok

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  This patch fixes it by calling hclge_buffer_alloc to reallocate
  buffer when pfc_en changes.

  c2d568978193 net: hns3: fix ETS bandwidth validation bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions

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

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Eugene Crosser]

I can confirm that suspend works normally with the kernel from comment #16
Thank you!

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

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [ 911.413625] Restarting tasks ... done.
  [ 911.462021] PM: suspend exit

  It looks like Ethernet driver prevents suspend. Ethernet is not
  connected (I do not have the adaptor).

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

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

[Kernel-packages] [Bug 1522949] Re: Bluetooth doesn't work on 0930:0225 Toshiba Corporation

[mohamed mahrous mahrous mohamed amer]

I was able to fix it by downloading the BCM.hcd file for my driver then
running on the terminal the following:

make the directory mutable
 sudo chattr -i /lib/firmware/brcm

copy the .hcd file in directory 
 sudo cp /home/user/BCM.hcd /lib/firmware/brcm

then undo mutablity changes in directory 
 sudo chattr +i /lib/firmware/brcm

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

Title:
  Bluetooth doesn't work on 0930:0225 Toshiba Corporation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  I have not been able to get bluetooth running in Ubuntu 14.04, 14.10,
  or 15.10 on my Toshiba laptop. Bluetooth does work under Windows.
  There is no bluetooth icon. The bluetooth manager says "Bluetooth is
  disabled" whether I set it to On or Off.

  
  rfkill list:

  0: Toshiba Bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
  [...]

  The modified kernel is because I installed btusb-lp1506615-dkms from
  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth . No
  change in behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josiah 1874 F pulseaudio
   /dev/snd/controlC1:  josiah 1874 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec  4 14:45:28 2015
  HibernationDevice: RESUME=UUID=0bcbd4ab-9f94-44d7-857f-717f4e7c9481
  InstallationDate: Installed on 2015-12-03 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite L75-B
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \boot\vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=edea9167-ead7-4da4-81ac-fa65520b3e91 ro quiet splash vt.handoff=7 
initrd=boot\initrd.img-4.2.0-16-generic
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd11/03/2014:svnTOSHIBA:pnSatelliteL75-B:pvrPSKRLU-01400M:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L75-B
  dmi.product.version: PSKRLU-01400M
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1864392] Re: WiFi not working

[Jonas Gamao]

So I tried removing the line, which worked, but introduced another
problem: I can't access the APs, no matter which password I provide.

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

Title:
  WiFi not working

Status in backport-iwlwifi-dkms package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No WiFi APs are detected.  It's like the driver doesn't recognize the
  hardware.

  I tried reinstalling it, but it didn't work.

  Please fix this ASAP.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.1
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-40-generic
  OS Type: 64-bit
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: backport-iwlwifi-dkms 7906-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 18:43:16 2020
  InstallationDate: Installed on 2020-01-19 (35 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: backport-iwlwifi-dkms
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (37 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (37 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamiyuki   2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (50 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
   
   enx00249b1ec202  no wireless extensions.
  MachineType: LENOVO 20SA0002US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-40.32-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.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-40-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: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamiyuki   2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (50 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
   
   

[Kernel-packages] [Bug 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware

[Taihsiang Ho]

I also verified 18.04-hwe 5.3.0-42-generic #34~18.04.1-Ubuntu fixes this
issue ( 5.3.0-40-generic #32~18.04.1-Ubuntu still has this issue).
Verified on d06-1.

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

Title:
  [hns3-0120]pad the short frame before sending to the hardware

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The hardware can not handle short frames below or equal to 32
  bytes.

  [Impact]
  The system may hang or endless event log in /var/log/syslog

  [Fix]
  Cherry-pick or backport the upstream fix 
36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before 
sending to the hardware

  [Test Case]
  Send a frame less than 33 bytes.

  [Regression Risk]
  Low, the patch is only specific to the hns3 driver.

  == Original Bug Description ==

  [Bug Description]
  The hardware can not handle short frames below or equal to 32
  bytes according to the hardware user manual, and it will trigger
  a RAS error when the frame's length is below 33 bytes.

  [Steps to Reproduce]
  1.send a frame less than 33 bytes.

  [Actual Results]
  a RAS occurs

  [Expected Results]
  no RAS

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  pads the SKB when skb->len is below 33 bytes before sending it to hardware.

  net: hns3: pad the short frame before sending to the hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1860320/+subscriptions

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

[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work

[Luki]

Here is a step by step guide I found: https://www.sysorchestra.com
/setup-soundcard-and-microphone-on-lenovo-thinkpad-x1-carbon-7th-gen-
with-linux-mint-19-3/

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

Title:
  Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't
  work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation
  doesn't work.

  A microphone on a headset plugged into the 3.5mm jack works fine.

  This is probably relevant:
  https://bugzilla.kernel.org/show_bug.cgi?id=201251

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:13:25 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

[Stefan Bader]

I am adding the block-proposed-bionic before this falls in between
cracks. Right now we ended up in a situation where the nvidia-440
modules were added to the kernel lrm package build but the version used
for the nvidia-390 modules was not updated to the proposed version. The
hope is that having the meta from the driver package held back in
proposed is less risk than releasing user-space for everything and not
having the right modules in lrm.

** Tags added: block-proposed-bionic

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  New
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC

[Kernel-packages] [Bug 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware

[Taihsiang Ho]

Verified and the bug is fixed.

- 4.15.0-92-generic, scobee
- 4.15.0-92-generic, d06-2

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

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

Title:
  [hns3-0120]pad the short frame before sending to the hardware

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The hardware can not handle short frames below or equal to 32
  bytes.

  [Impact]
  The system may hang or endless event log in /var/log/syslog

  [Fix]
  Cherry-pick or backport the upstream fix 
36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before 
sending to the hardware

  [Test Case]
  Send a frame less than 33 bytes.

  [Regression Risk]
  Low, the patch is only specific to the hns3 driver.

  == Original Bug Description ==

  [Bug Description]
  The hardware can not handle short frames below or equal to 32
  bytes according to the hardware user manual, and it will trigger
  a RAS error when the frame's length is below 33 bytes.

  [Steps to Reproduce]
  1.send a frame less than 33 bytes.

  [Actual Results]
  a RAS occurs

  [Expected Results]
  no RAS

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  pads the SKB when skb->len is below 33 bytes before sending it to hardware.

  net: hns3: pad the short frame before sending to the hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1860320/+subscriptions

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

[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]

[Andrew Cloke]

Additional data point: I successfully deployed bionic 4.15.0-91 to
dawes, a single-socket ThunderX Gigabyte system.

ubuntu@dawes:~$ uname -a
Linux dawes 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:10:16 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

Note, however, that this issue was reported on wright, which is a 2-socket 
ThunderX system.
Sean has the only the only other 2-socket ThunderX system (recht) reserved, so 
I'm not able to test with that.

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

Title:
  Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158
  [ipmi_msghandler]

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

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel 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 nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect 

[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -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
  kernel-stable-master-bug: 1866488
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 14. March 2020 10:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1866484

Title:
  focal/linux-azure: 5.4.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure 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: 1866488
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 14. March 2020 10:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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

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

[bugproxy]

--- Comment From h.carst...@de.ibm.com 2020-03-18 11:32 EDT---
CONFIG_HIBERNATION: Hibernation (aka Suspend-to-Disk) is known to broken on 
s390 since a long time - the architecure support for this will be removed from 
the kernel soon. Therefore this config option should be disabled.

CONFIG_PM is rather useless without CONFIG_HIBERNATION, therefore
disable this as well.

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

Title:
  [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for
  focal

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Addl change required for kernel config.

  
  from
  CONFIG_HIBERNATION=y
  CONFIG_PM=y

  to
  #CONFIG_HIBERNATION is not set
  #CONFIG_PM is not set

  
  hope that will be the last ticket for 20.04...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions

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

[Kernel-packages] [Bug 1867663] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1867663/+attachment/5338403/+files/Stacktrace.txt

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

[Kernel-packages] [Bug 1867663] Crash report cannot be processed

[Apport retracing service]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for nvidia-340


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1867663/+attachment/5337626/+files/CoreDump.gz

** Tags removed: need-amd64-retrace

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

[Kernel-packages] [Bug 1867663] nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

[Apport retracing service]

StacktraceSource:
 #0  0x7f68be68b18b in ?? ()
 #1  0x00394000 in ?? ()
 #2  0x in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

[Kernel-packages] [Bug 1867663] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1867663/+attachment/5338404/+files/ThreadStacktrace.txt

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Invalid

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

Title:
  nvidia-persistenced assert failure: malloc(): invalid size (unsorted)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  System freeze aleatory

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: malloc(): invalid size (unsorted)
  Date: Mon Mar 16 14:51:26 2020
  ExecutablePath: /usr/bin/nvidia-persistenced
  InstallationDate: Installed on 2020-03-13 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/nvidia-persistenced --user nvidia-persistenced 
--no-persistence-mode --verbose
  Signal: 6
  SourcePackage: nvidia-graphics-drivers-390
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f68be830b80 , bytes=bytes@entry=504) 
at malloc.c:3766
   __GI___libc_malloc (bytes=bytes@entry=504) at malloc.c:3058
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffdfaf87c30, 
sizeloc=sizeloc@entry=0x7ffdfaf87c38) at memstream.c:76
   __vsyslog_internal (pri=30, fmt=0x407480 "Verbose syslog connection opened", 
ap=0x7ffdfaf87d20, mode_flags=0) at ../misc/syslog.c:181
   __syslog (pri=, fmt=) at ../misc/syslog.c:117
  Title: nvidia-persistenced assert failure: malloc(): invalid size (unsorted)
  UpgradeStatus: Upgraded to focal on 2020-03-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663/+subscriptions

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

[Kernel-packages] [Bug 1845704] Re: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04

[Adnan Hodzic]

I also have same problem on Ubuntu 20.04 (kernel: 5.4.0-18-generic) on
both HDMI or USB-C, used to work fine on 19.10 with 5.3.

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

Title:
  HDMI monitor is not detected as sound output device starting from
  kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 18.10 from kernel 4.18.0-20-generic to
  4.18.0-21-generic, HDMI Audio stopped working, system does not detect
  it at all as a sound output device. Downgrading to 4.18.0-20 helped on
  Ubuntu 18.10, but currently I'm using Ubuntu 19.04 with kernel
  5.0.0-29-generic, and HDMI sound still does not work and system cannot
  detect it.

  Adding the following parameters to GRUB didn't helped ():
  - amdgpu.dc=1
  - radeon.audio=1

  Video card: Radeon HD 4850 with 2 DVI ports with ability to output
  sound thru DVI (DVI-HDMI cable or DVI-HDMI adapter).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oshmyrko   2595 F pulseaudio
   /dev/snd/controlC2:  oshmyrko   2595 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 22:14:27 2019
  InstallationDate: Installed on 2019-04-13 (166 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=a88b1763-5d14-4204-ba95-d6718c22158d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-07-09 (80 days ago)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  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.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0: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.sku: SKU
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845704/+subscriptions

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

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

[Jean-]

I just upgraded my ubuntu 19.10 and suddenly lost my sound card. Kernel
was updated from 5.3.0-40 to 5.3.0-42. This switched the sound driver
from snd_hda to snd_soc which sounds very promising but it seems a
firmware is missing and it is unclear where we are supposed to get the
firmware from.

```
dmesg | grep -C1 -E 'ALSA|HDA|HDMI|sof|snd[_-]|sound|hda.codec|hda.intel'   

   
[0.261825] ACPI: Added _OSI(Linux-Dell-Video)
[0.261827] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.261828] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
--
[1.801143] integrity: Loading X.509 certificate: UEFI:db
[1.801169] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 
2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[1.801169] integrity: Loading X.509 certificate: UEFI:db
[1.801179] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 
2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[1.801839] ima: Allocated hash algorithm: sha1
--
[   10.292817] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input11
[   10.292946] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ 
platform, aborting probe
[   10.295854] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
--
[   10.413077] iwlwifi :00:14.3: base HW address: dc:71:96:b9:0a:d2
[   10.416236] snd_soc_skl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
[   10.40] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   10.482071] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
--
[   10.566796] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
[   10.594049] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3
[   10.596829] snd_soc_skl :00:1f.3: Direct firmware load for 
9dc8-LENOVO-TP-N2H-4752-tplg.bin failed with error -2
[   10.596831] snd_soc_skl :00:1f.3: tplg fw 
9dc8-LENOVO-TP-N2H-4752-tplg.bin load failed with -2, falling back to 
dfw_sst.bin
[   10.596845] snd_soc_skl :00:1f.3: Direct firmware load for dfw_sst.bin 
failed with error -2
[   10.596846] snd_soc_skl :00:1f.3: Fallback tplg fw dfw_sst.bin load 
failed with -2
[   10.596849] snd_soc_skl :00:1f.3: Failed to init topology!
[   10.596850] snd_soc_skl :00:1f.3: ASoC: failed to probe component -2
[   10.596859] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -2

```

other people who encounter issues with 5.3.0-42 :
- https://askubuntu.com/questions/1218058/ubuntu-19-10-audio-driver-issue
- 
https://askubuntu.com/questions/1217949/ubuntu-no-sound-dummy-output-and-no-sound-card-detected

I apologize if this is the wrong place/issue, this is the closest I
could find in the tracker

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and 

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Michael Reiger]

Looks good so far; with kernel 5.3.0-43 from proposed and the libasound2
from your ppa.

Microphone selection seems to be a bit iffy when I have a headset
plugged into the headset jack (both are available to select, and the
default seems to be the built-in one) but otherwise good.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1866170] Re: Suspend triggers Hardware Error in e1000e driver

[Kai-Heng Feng]

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

A test kernel can be found here:
https://people.canonical.com/~khfeng/lp1865570/eoan/

** This bug has been marked a duplicate of bug 1865570
   suspend only works once on ThinkPad X1 Carbon gen 7

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

Title:
  Suspend triggers Hardware Error in e1000e driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing problems since a recent kernel update.

  The laptop, a Lenovo X1 gen 7, won't suspend.

  This is the relevant kernel log

  
  -->  # modprobe e1000e:

  [  129.848320] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  [  129.848321] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [  129.848592] e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [  130.041352] e1000e :00:1f.6 :00:1f.6 (uninitialized): registered 
PHC clock
  [  130.108943] e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 
98:fa:9b:7a:d9:f8
  [  130.108945] e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
  [  130.109109] e1000e :00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FF-0FF
  [  130.110252] e1000e :00:1f.6 enp0s31f6: renamed from eth0
  --> Close laptop cover
  [  135.766644] PM: suspend entry (s2idle)
  [  135.827181] Filesystems sync: 0.060 seconds
  [  135.827625] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [  135.829446] OOM killer disabled.
  [  135.829446] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  135.830557] printk: Suspending console(s) (use no_console_suspend to debug)
  [  135.847372] wlp0s20f3: deauthenticating from 6c:3b:6b:45:31:33 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  135.952129] e1000e: EEE TX LPI TIMER: 0011
  [  168.243513] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [  168.552833] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [  168.620018] iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  [  171.122887] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast 
Packet
  [  171.789683] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [  172.316635] OOM killer enabled.
  [  172.316635] Restarting tasks ... done.
  [  172.524828] PM: suspend exit
  [  173.520752] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [  173.823096] e1000e: enp0s31f6 NIC Link is Down
  [  173.832543] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [  173.947544] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [  174.012469] iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  [  174.950102] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [  179.453930] wlp0s20f3: authenticate with 6c:3b:6b:45:31:33
  [  179.456251] wlp0s20f3: send auth to 6c:3b:6b:45:31:33 (try 1/3)
  [  179.494829] wlp0s20f3: authenticated
  [  179.496193] wlp0s20f3: associate with 6c:3b:6b:45:31:33 (try 1/3)
  [  179.498191] wlp0s20f3: RX AssocResp from 6c:3b:6b:45:31:33 (capab=0x431 
status=0 aid=2)
  [  179.500628] wlp0s20f3: associated
  [  179.512786] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-modules-5.3.0-42-generic 5.3.0-42.34
  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:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 2099 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 11:10:06 2020
  Dependencies:
   
  InstallationDate: Installed on 2019-10-07 (149 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QDCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-19 (107 days ago)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  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:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Kai-Heng Feng]

A test kernel can be found here:
https://people.canonical.com/~khfeng/lp1865570/focal/

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

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [ 911.413625] Restarting tasks ... done.
  [ 911.462021] PM: suspend exit

  It looks like Ethernet driver prevents suspend. Ethernet is not
  connected (I do not have the adaptor).

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

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

[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle

[Dean Henrichsmeyer]

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

Title:
  5.3.0-23-generic causes fans to spin when idle

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: "drm/i915/gen8+: Add RC6 CTX corruption WA" makes it
  effectively impossible to enter RC6 for some Intel GPUs when a display
  server is running. This results in increased energy usage and
  temperature.

  Fix: Upstream has changed too much to make the fixes there applicable,
  but Chris Wilson has provided a patch for 5.3, here:
  https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  Test Case: See test results below. On an affected machine powertop
  will show increased RC6 usage on an idle desktop after the patch, and
  other symptoms of excessive power use should also subside.

  Regression Potential: The 5.3 patch is pretty straightforward, and
  only adds running of an existing delayed worker to retire GPU
  requests. No regressions have been reported in testing so far.

  ---

  After upgrading to 5.3.0-23-generic the fans in my machine don't stop
  running. They always sound like something is utilizing CPU - even with
  no applications running after boot.

  If I boot back to 5.3.0-19-generic it's fine.

  My microcode version is reported as 0xd4 and iucode-tool reports:

  iucode-tool: system has processor(s) with signature 0x000506e3

  Let me know if you need anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   2898 F pulseaudio
   /dev/snd/pcmC2D0p:   dean   2898 F...m pulseaudio
   /dev/snd/controlC0:  dean   2898 F pulseaudio
   /dev/snd/controlC1:  dean   2898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 13:03:34 2019
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (482 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1867916] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-88-generic N/A
   linux-backports-modules-4.15.0-88-generic  N/A
   linux-firmware 1.173.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.asset.tag: 0191525
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work

[Hui Wang]

@Alexander,

Please refer to https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1859754/comments/66

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

Title:
  Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't
  work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation
  doesn't work.

  A microphone on a headset plugged into the 3.5mm jack works fine.

  This is probably relevant:
  https://bugzilla.kernel.org/show_bug.cgi?id=201251

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:13:25 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867916] [NEW] Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Sebastian Marsching]

Public bug reported:

After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
does not boot any longer. It always crashes during boot with a kernel
panic.

I suspect that this crash might be related to Bcache because this is the
only one of our systems where we use Bcache and the kernel panic appears
right after Bcache initialization.

I already checked that this bug still exists in the 4.15.0-92.93 kernel
from proposed.

Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.

I attached a screenshot with the trace of the kernel panic.

The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:

bcache: register_bcache() error /dev/dm-0: device already registered

When booting with kernel 4.15.0-88 that does not have this problem, the
next message is

bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)

After that the next message is:

Begin: Loading essential drivers ... done

This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
 crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 18 12:55:18 2020
HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
InstallationDate: Installed on 2013-07-02 (2450 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
MachineType: HP ProLiant DL160 G6
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-88-generic N/A
 linux-backports-modules-4.15.0-88-generic  N/A
 linux-firmware 1.173.16
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
dmi.bios.date: 11/06/2009
dmi.bios.vendor: HP
dmi.bios.version: O33
dmi.chassis.asset.tag: 0191525
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL160 G6
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of the kernel panic"
   
https://bugs.launchpad.net/bugs/1867916/+attachment/5338345/+files/IMG_3762.JPG

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel 

[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work

[Alexander Fieroch]

Any updates on this as now in times with corona people could use the
micro for homeoffice video calls...

For the manual way - what has the user to do in addition to copy these
UCM file directories?

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

Title:
  Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't
  work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation
  doesn't work.

  A microphone on a headset plugged into the 3.5mm jack works fine.

  This is probably relevant:
  https://bugzilla.kernel.org/show_bug.cgi?id=201251

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:13:25 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

[Kirill]

bump

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Paolo Mainardi]

Ok thanks @jui.wang, it's in the pre-released updates, because i saw
that -42 had been promoted upstream between yesterday and today causing
several issues, i had to manually downgrade to -40.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Hui Wang]

@Paolo,

Enable Pre-released updates (eoan-proposed) in the Software & Updates
sudo apt-get update
sudo apt install linux-image-unsigned-5.3.0-4 {pressing tab}, it will list -43 
kernel.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Marcelo Cerri]

linux-base for xenial:
https://kernel.ubuntu.com/~mhcerri/azure/lp1867820/

** Patch added: "linux-base for xenial"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/linux-azure/+bug/1867820/+attachment/5338344/+files/linux-base_4.5ubuntu1.1~16.04.1.debdiff

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-base source package in Bionic:
  In Progress
Status in linux-azure source package in Eoan:
  New
Status in linux-base source package in Eoan:
  New
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  New

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Marcelo Cerri]

Linux

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-base source package in Bionic:
  In Progress
Status in linux-azure source package in Eoan:
  New
Status in linux-base source package in Eoan:
  New
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  New

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Paolo Mainardi]

thanks @hui.wang, where can i find the 5.3.0-43 ? is it in the upstream
repos ?

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1863592] Re: bionic/linux-oem: 4.15.0-1073.83 -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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Wednesday, 19. February 2020 22:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason: {}
  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/1863592

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Wednesday, 19. February 2020 22:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs

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

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

[Kernel-packages] [Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker

[Ubuntu Kernel Bot]

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865109
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Tuesday, 17. March 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  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 1862012] Re: bionic/linux-oem: 4.15.0-1069.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: 1860123
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Monday, 10. February 2020 12:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason: {}
  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/1862012

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1860123
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Monday, 10. February 2020 12:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs

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

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

[Kernel-packages] [Bug 1855999] Re: alsa/hda/realtek: the line-out jack doens't work on a dell AIO

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: Invalid => 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/1859407

Title:
  peripheral devices on Dell WD19TB cannot be detected after suspend
  resume

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

Bug description:
  [SRU Justification]

  [Impact]
  If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell
  WD19TB into the laptop during suspend state, peripheral devices on the
  docking station cannot be re-probed after the system resumes.

  [Fix]
  Upstream commit 56b991849009f ("PM: sleep: Simplify suspend-to-idle control
  flow") along with its dependencies are required to fix this issue:

* 56b991849009f PM: sleep: Simplify suspend-to-idle control flow
* 41275eb5c7181 ACPI: PM: Set s2idle_wakeup earlier and clear it later
* 9089f16e053af ACPI: EC: Return bool from acpi_ec_dispatch_gpe()
* 6921de898ba8f ACPICA: Return u32 from acpi_dispatch_gpe()
* 3a79bc63d9075 PCI: irq: Introduce rearm_wake_irq()

  And 56b991849009f takes an additional fix as we've done for bug
  1858424:

* 016b87ca5c8c6 ACPI: EC: Rework flushing of pending work

  [Test Case]
  1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
  2. Suspend the system
  3. Un-plug the TBT 3 cable of WD19 docking station from laptop
  4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
  5. Press the Enter key or power button to wake up the system
  6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
  7. Check if the Ethernet interface is available and networking connection is 
up.

  [Regression Potential]
  Medium. The first four patches should not affect original functionalities. The
  last two mostly simplify the process and resolve a regression.

  == original bug description ==

  [Summary]
  If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB 
into the laptop during suspend state, peripheral devices on the docking station 
cannot be re-probed after the system resumes.

  [Steps to reproduce]
  1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
  2. Suspend the system
  3. Un-plug the TBT 3 cable of WD19 docking station from laptop
  4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
  5. Press the Enter key or power button to wake up the system
  6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
  7. Check if the Ethernet interface is available and networking connection is 
up.

  [Expected result]
  The Ethernet interface can be detected

  [Actual result]
  The Ethernet cannot be detected

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

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

[Kernel-packages] [Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1861837] Re: machine doesn't come up after suspend and re-opening the lid

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: Invalid => 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/1861837

Title:
  machine doesn't come up after suspend and re-opening the lid

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  If the sof driver fails to load the firmware, it doesn't release the
  resource, then it make the system hang when suspending and resuming.

  After this patchset is applied, please also apply the patchset we
  just reverted 2 weeks ago, since this patchset is the fixing patches
  for the patches we reverted (#1857409). If need me to resend the
  reverted patches, I will resend them.

  
  [Impact]
  The machine hangs during suspend/resume if the sof driver fails to
  load firmware.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backported
  those patches to ubuntu kernel

  [Test Case]
  sudo mv /lib/firmware/intel/sof /lib/firmware/intel/sof-bak, reboot
  then suspend and resume, the system will not hang anymore

  And if the sof driver load the firmware successfully, the audio
  functions all worked well as before.

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  these patches on Lenovo and Dell dmic machines.


  A Carbon X1 running current focal (fresh focal installation), and the
  linux-oem kernel doesn't come up after suspend and re-opening the lid.
  I have to force a power-off (holding the power button for a few
  seconds), and restart the machine.

  What information can I provide?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-17 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  MachineType: LENOVO 20QDCTO1WW
  Package: linux-oem (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-13-generic N/A
   linux-backports-modules-5.4.0-13-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-13-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: 11/26/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET42W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  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:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862012] Re: bionic/linux-oem: 4.15.0-1069.79 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1860248] Re: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

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

Title:
  No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered'
  after modprobe sof

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

Bug description:
  [Impact]
  When we boot the kernel on a Dell machchine which has a discrete
  nvidia graphic card, the sof driver will fail to initialize sometimes,
  and after investigation, we found if let nvidia hdmi audio load the
  codec driver first, the sof driver will fail to initialize 100%.

  [Fix]
  Intel release a patch to fix this issue, after applying this patch,
  the sof driver could work even the nividia hdmi audio initializes
  first.

  
  [Test Case]
  We test this patch, the issue could be reproduced anymore in
  100 times reboot.

  [Regression Risk]
  Low, Intel released the patch to us, and we already did large
  numbers of audio test in the oem project.

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

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

[Kernel-packages] [Bug 1861238] Re: Root can lift kernel lockdown via USB/IP

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1855999] Re: alsa/hda/realtek: the line-out jack doens't work on a dell AIO

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled

Status in linux-5.4 package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux-5.4 source package in Focal:
  In Progress

Bug description:
  [Impact]   
  After Ubuntu-5.4.0-9.12 which introduce DPCD backlight patches, the
  backlight control on some platforms fail to work.
  It seems using OUI string to map the panels which support DPCD
  backlight doesn't work well, it mis-mapped those panel that doesn't
  support DPCD backlight, and breaks the backlight control.
 
  [Fix]
  The author of the origin DPCD backlight patches recently provides a
  DP quirks based on EDID identification.

  [Fix]
  Verified on the machine with DPCD backlight and also on the machine
  which has regression with the OUI quirks, both of them work now.

  [Regression Potential]
  Low, it introduce a new quirks to list the panels which support DPCD
  backlight.

  ===

  After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no
  longer have the ability to control the backlight brightness on my HP
  EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen
  indicator pops up and shows that the brightness setting is being
  changed but the actual screen brightness is stuck on the lowest
  setting.

  This laptop has a built-in privacy screen. If I activate the privacy
  screen (fn-f2), then the actual screen brightness goes to the maximum
  setting and then I am able to dim and brighten the backlight as long
  as the privacy screen functionality is turned on.

  This is a regression from Eoan's 5.3.0-29.31 kernel where I was able
  to control the brightness with and without the privacy screen
  functionality being turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 31 11:42:16 2020
  InstallationDate: Installed on 2019-06-24 (221 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago)

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

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

[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1858156] Re: alsa/hda/realtek: chain a fixup to an existing quirk to fix the heaset-mic problem on 2 Dell machines

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native
  backlight on Lenovo E41-25/45

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

Bug description:
  SRU justification:

  [Impact]
  ACPI backlight control doesn't work on 2 Lenovo E41 laptops.

  [Fix]
  Use native backlight control instead.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new DMI strings with positive verification.

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

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

[Kernel-packages] [Bug 1853219] Re: [CML-H] Add intel_thermal_pch driver support Comet Lake -H

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

Title:
  [CML-H] Add intel_thermal_pch driver support Comet Lake -H

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Missing thermal_zone info for Intel PCH on Comet Lake (CML) platform.

  [Fix]
  Commit 35709c4ee772 ("thermal: intel: intel_pch_thermal: Add Comet Lake
  (CML) platform support") from v5.6-rc1 to be backported.

  [Test Case]
  Check if sysfs thermal zone entry of type "pch_cometlake" exists:

$ cat /sys/class/thermal/thermal_zone*/type | grep pch_cometlake

  [Regression Potential]
  Low. This affects only CML platforms.

  == original description ==

  Description
  Add intel_thermal_pch driver support Comet Lake -H

  Target Release: 20.04
  Target Kernel: 5.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1853219/+subscriptions

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

[Kernel-packages] [Bug 1853219] Re: [CML-H] Add intel_thermal_pch driver support Comet Lake -H

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

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

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

Title:
  [CML-H] Add intel_thermal_pch driver support Comet Lake -H

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Missing thermal_zone info for Intel PCH on Comet Lake (CML) platform.

  [Fix]
  Commit 35709c4ee772 ("thermal: intel: intel_pch_thermal: Add Comet Lake
  (CML) platform support") from v5.6-rc1 to be backported.

  [Test Case]
  Check if sysfs thermal zone entry of type "pch_cometlake" exists:

$ cat /sys/class/thermal/thermal_zone*/type | grep pch_cometlake

  [Regression Potential]
  Low. This affects only CML platforms.

  == original description ==

  Description
  Add intel_thermal_pch driver support Comet Lake -H

  Target Release: 20.04
  Target Kernel: 5.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1853219/+subscriptions

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

[Kernel-packages] [Bug 1862013] Re: bionic/linux-oem: 4.15.0-1071.81 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call 

[Kernel-packages] [Bug 1864576] Re: alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: Invalid => 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/1864061

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and is merged to focal
  kernel, now we backport this patch to Eoan kernel if -42 doesn't
  introduce this fix patch from stable.

  The patch introduced the crash:
  commit 063821115e02229d5fd3de31bad270d5e30aeb41
  Author: Dragos Tarcatu 
  Date: Mon Dec 9 18:39:38 2019 -0600

  ASoC: topology: Check return value for snd_soc_add_dai_link()

  BugLink: https://bugs.launchpad.net/bugs/1861929

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

  snd_soc_add_dai_link() might fail. This situation occurs for
  instance in a very specific use case where a PCM device and a
  Back End DAI link are given identical names in the topology.
  When this happens, soc_new_pcm_runtime() fails and then
  snd_soc_add_dai_link() returns -ENOMEM when called from
  soc_tplg_fe_link_create(). Because of that, the link will not
  get added into the card list, so any attempt to remove it later
  ends up in a panic.

  Fix that by checking the return status and free the memory in case
  of an error.

  Reviewed-by: Ranjani Sridharan 
  Signed-off-by: Dragos Tarcatu 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  
  [Impact]
  During the boot, the sof driver crash because the hdmi_pcm_list
  is not initialized before it is used.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backport
  this patch to ubuntu kernel

  [Test Case]
  Boot the -41 kernel with this patch added.
  blacklist the snd_soc_skl
  the kernel can boot successfully, and sof driver worked well

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. Focal kernel already
  has this patch and works well.



  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [

[Kernel-packages] [Bug 1862885] Re: Sometimes can't adjust brightness on Dell AIO

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sometimes can't adjust brightness on Dell AIO

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  We already added retry on the backlight driver, but the scalar have to take 
some time to activate panel during booting up, and 2 seconds seem doesn't 
enough. So, it sometimes fails to get the response from scalar.

  [Fix]
  Enlarge the retry time from 2 seconds to 5 seconds.
  We didn't observe the response time longer than 3 seconds, but to be more 
confident, enlarge the value to 5 seconds.

  [Test]
  Verified on new Dell AIO platform.

  [Regression Potential]
  Low, increase the retry times doesn't hurt anything.

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

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

[Kernel-packages] [Bug 1863880] Re: Another Dell AIO backlight issue

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: Invalid => 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/1863880

Title:
  Another Dell AIO backlight issue

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  The scalar which control the backlight sometimes doesn't respond the first 
command, so driver can't determinate whether this scalar is in charge of the 
backlight.

  [Fix]
  Move the retry block not only to read the response, but also includes write 
command, so that it re-send the command, too.

  [Test]
  Verified on the buggy Dell AIO, it passes 30 times and should be more 
reliable.

  [Regression Potential]
  Low, there is no code flow change, just move the retry block to include both 
write and read command.

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

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

[Kernel-packages] [Bug 1862313] Re: Support Headset Mic on HP cPC

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

Title:
  r8152 init may take up to 40 seconds at initialization with Dell
  WD19/WD19DC during hotplug

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  USB devices attached to Dell WD19/WD19DC USB Type-C dock take up to nearly one
  minutes to be ready for use.

  [Fix]
  r8152 driver init process involves several for-loops that each may take up to 
14
  seconds to exit when USB port reset occurs during hotplug. This is still
  reproducible with latest v5.6-rc mainline kernel although the fail rate is 
much
  lower since v5.5-rc7.

  [Test Case]
  Verified on Dell WD19DC.

  [Regression Potential]
  Low. Just to exit the loop early when it should have been.

  == original bug description ==

  Dell USB Type C docking WD19/WD19DC attaches additional peripherals
  as:

    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M

  where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the
  dock.

  When hotplugging such dock with additional usb devices already
  attached on it, the probing process may reset usb 2.1 port, therefore
  r8152 ethernet device is also reset. However, in r8152 driver there
  are several  for-loops that may take up to 14 seconds during the
  initialization for each in practice, and that has to be completed
  before USB may re-enumerate devices on the bus. As a result, devices
  attached to the dock will only be available after nearly 1 minute
  after the dock is plugged in.

    [  216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface
    [  216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id
    [  258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY 
not ready
    [  258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): 
Invalid header when reading pass-thru MAC addr
    [  258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get 
ether addr fail

  This can be reproduced on all kernel versions up to latest v5.6-rc2,
  but after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or
  so while it was around 1/2.

  The time consuming for-loops are at:
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2014 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 04:07:20 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-hodor+X95
  InstallationDate: Installed on 2020-01-16 (37 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IwConfig:
   enp1s0no wireless extensions.

   enxd8d090035306  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. Latitude 3310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Kernel-packages] [Bug 1863592] Re: bionic/linux-oem: 4.15.0-1073.83 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1864576] Re: alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

Title:
  alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  The mute led couldn't work after applying the FIXUP_SPEAKER2_TO_DAC1.

  [Fix]
  Chain a fixup to let mute led work.

  [Test Case]
  boot the system, press mute button, the led will work.

  
  [Regression Risk]
  Low, this patch is specific to LENOVO X1 Carbon machines. And
  I tested this patch on Lenovo and Dell machines.

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

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

[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call 

[Kernel-packages] [Bug 1862313] Re: Support Headset Mic on HP cPC

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

Title:
  Support Headset Mic on HP cPC

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

Bug description:
  [Impact]
  Two HP workstations can't detect headset microphone.

  [Fix]
  Apply vendor-specific coefficient to enable headset mic detection.

  [Test]
  Plug headset and see if the mic gets detected.
  Headset mic gets detected correctly after applying the patch.

  [Regression Potential]
  Low. The fix matches to very specific machines, so all other systems are 
unaffected.

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

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

[Kernel-packages] [Bug 1862567] Re: [SRU][B/OEM-B] Fix multitouch support on some devices

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1864730] Re: bionic/linux-oem: 4.15.0-1075.85 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call 

[Kernel-packages] [Bug 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: Invalid => 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/1865402

Title:
  Stop using get_scalar_status command in Dell AIO uart backlight driver

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  The get_scalar_status command was provided by ODM engineer and was newly 
introduced to determinate whether scalar is responsible for the backlight 
adjustment. That guy asked the scalar vendor to add this command and the 
command works as expected. But there is already a command in the Dell AIO 
scalar UART command spec. which can do the same thing since 2015, and the newly 
introduced get_scalar_status command is undocumented. To prevent from 
introducing regression in the future and to align with what Windows uses, 
replace this command with get_display_mode command.

  [Fix]
  Replace get_scalar_status command with get_display_mode command.

  [Test]
  Verified on new Dell AIO platforms.

  [Regression Potential]
  Low, the command is already in the spec. since 2015.

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

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

[Kernel-packages] [Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1076.86

---
linux-oem (4.15.0-1076.86) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1076.86 -proposed tracker (LP: #1865200)

  [ Ubuntu: 4.15.0-91.92 ]

  * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109)
  * CVE-2020-2732
- KVM: x86: emulate RDPID
- KVM: nVMX: Don't emulate instructions in guest mode
- KVM: nVMX: Refactor IO bitmap checks into helper function
- KVM: nVMX: Check IO instruction VM-exit conditions

linux-oem (4.15.0-1075.85) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1075.85 -proposed tracker (LP: #1864730)

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  [ Ubuntu: 4.15.0-90.91 ]

  * bionic/linux: 4.15.0-90.91 -proposed tracker (LP: #1864753)
  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
- [packaging] handle downloads from the librarian better

  [ Ubuntu: 4.15.0-90.90 ]

  * bionic/linux: 4.15.0-90.90 -proposed tracker (LP: #1864753)
  * vm-segv from ubuntu_stress_smoke_test failed on B (LP: #1864063)
- Revert "apparmor: don't try to replace stale label in ptrace access check"

linux-oem (4.15.0-1074.84) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1074.84 -proposed tracker (LP: #1863312)

  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- SAUCE: r8151: check disconnect status after long sleep

  * alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
(LP: #1864576)
- SAUCE: ALSA: hda/realtek - Fix a regression for mute led on Lenovo Carbon 
X1

  [ Ubuntu: 4.15.0-89.89 ]

  * bionic/linux: 4.15.0-89.89 -proposed tracker (LP: #1863350)
  * [SRU][B/OEM-B] Fix multitouch support on some devices (LP: #1862567)
- HID: core: move the dynamic quirks handling in core
- HID: quirks: move the list of special devices into a quirk
- HID: core: move the list of ignored devices in hid-quirks.c
- HID: core: remove the absolute need of hid_have_special_driver[]
  * [linux] Patch to prevent possible data corruption (LP: #1848739)
- blk-mq: silence false positive warnings in hctx_unlock()
  * Add bpftool to linux-tools-common (LP: #1774815)
- tools/bpftool: fix bpftool build with bintutils >= 2.9
- bpftool: make libbfd optional
- [Debian] Remove binutils-dev build dependency
- [Debian] package bpftool in linux-tools-common
  * Root can lift kernel lockdown via USB/IP (LP: #1861238)
- Revert "UBUNTU: SAUCE: (efi-lockdown) Add a SysRq option to lift kernel
  lockdown"
  * [Bionic] i915 incomplete fix for CVE-2019-14615 (LP: #1862840) //
CVE-2020-8832
- drm/i915: Use same test for eviction and submitting kernel context
- drm/i915: Define an engine class enum for the uABI
- drm/i915: Force the switch to the i915->kernel_context
- drm/i915: Move GT powersaving init to i915_gem_init()
- drm/i915: Move intel_init_clock_gating() to i915_gem_init()
- drm/i915: Inline intel_modeset_gem_init()
- drm/i915: Mark the context state as dirty/written
- drm/i915: Record the default hw state after reset upon load
  * Bionic update: upstream stable patchset 2020-02-12 (LP: #1863019)
- xfs: Sanity check flags of Q_XQUOTARM call
- mfd: intel-lpss: Add default I2C device properties for Gemini Lake
- powerpc/archrandom: fix arch_get_random_seed_int()
- tipc: fix wrong timeout input for tipc_wait_for_cond()
- mt7601u: fix bbp version check in mt7601u_wait_bbp_ready
- crypto: sun4i-ss - fix big endian issues
- drm/sti: do not remove the drm_bridge that was never added
- drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
- ALSA: hda: fix unused variable warning
- apparmor: don't try to replace stale label in ptrace access check
- PCI: iproc: Remove PAXC slot check to allow VF support
- drm/hisilicon: hibmc: Don't overwrite fb helper surface depth
- IB/rxe: replace kvfree with vfree
- IB/hfi1: Add mtu check for operational data VLs
- ALSA: usb-audio: update quirk for B PX to remove microphone
- staging: comedi: ni_mio_common: protect register write overflow
- pwm: lpss: Release runtime-pm reference from the driver's remove callback
- drm/sun4i: hdmi: Fix double flag assignation
- mlxsw: reg: QEEC: Add minimum shaper fields
- NTB: ntb_hw_idt: replace IS_ERR_OR_NULL with regular NULL checks
- pcrypt: use format specifier in kobject_add
- exportfs: fix 'passing zero to ERR_PTR()' warning
- drm/dp_mst: Skip validating ports during destruction, just ref
- net: phy: Fix not to call phy_resume() if PHY is not attached
- IB/rxe: Fix incorrect cache cleanup in error flow

[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1043.48

---
linux-oem-osp1 (5.0.0-1043.48) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1043.48 -proposed tracker (LP:
#1867111)

  * All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- SAUCE: Input: i8042 - Fix the selftest retry logic

  * r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC
during hotplug (LP: #1864284)
- UBUNTU SAUCE: r8151: check disconnect status after long sleep

  * Miscellaneous Ubuntu changes
- [Config] Bump the GCC version

 -- Timo Aaltonen   Thu, 12 Mar 2020
11:14:40 +0200

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

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

Title:
  All PS/2 ports on PS/2 Serial add-in bracket are not working after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  New
Status in linux-oem source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  PS/2 ports on PS/2 Serial add-in card do not work after S3.

  [Fix]
  The i8042 controller selftest fails while resuming, adding retry fix this 
issue.

  [Test]
  Verified on the target machine, the ps/2 keyboard keeps working after S3 test 
30 times.

  [Regression Potential]
  Low, there is a retry logic in controller selftest, but it returns directly 
if it fails to communicate with the controller. This commit make it retry 5 
times before return fails.

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

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

[Kernel-packages] [Bug 1862749] Re: [UBUNTU 20.04] Fix a potential data corruption issue for thin provisioned devices

[Frank Heimes]

The upstream stable patch set v5.4.26 was now applied that implicitly includes 
this patch.
Hence changing the status to Fix Committed.

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

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

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

Title:
  [UBUNTU 20.04] Fix a potential data corruption issue for thin
  provisioned devices

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

Bug description:
  This pro-active fix is requested to provide the code for disablement
  of Thin Provisioning within Ubuntu 20.04, like within Ubuntu 19.10 or
  providing the final solution from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1862749/+subscriptions

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

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Hui Wang]

The kernel 5.3.0-43 and 5.0.0-1043-oem-osp1 are ready, I just booted
with these kernels, no errors so far. And with these kernels, no need to
blacklist snd_soc_skl and snd_hda_intel.


For looking for ucm based on bios version, please test this alsa-lib 
1.1.9-0ubuntu1.2+testucm  in 
https://launchpad.net/~hui.wang/+archive/ubuntu/audio-master.


sudo add-apt-repository ppa:hui.wang/audio-master
sudo apt-get update
sudo apt install libasound2
reboot

thx.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

[Marcel Munce]

I'm so sorry. I did not have the time to reinstall Ubuntu on my machine
for testing the kernel.

It's now running on your provided 5.3.0-24 but that does not work either
:-(

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867885] ProcCpuinfoMinimal.txt

[Jesko]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338331/+files/ProcCpuinfoMinimal.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] RfKill.txt

[Jesko]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1867885/+attachment/5338336/+files/RfKill.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] WifiSyslog.txt

[Jesko]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338338/+files/WifiSyslog.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] ProcEnviron.txt

[Jesko]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338332/+files/ProcEnviron.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] UdevDb.txt

[Jesko]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1867885/+attachment/5338337/+files/UdevDb.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] PulseList.txt

[Jesko]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338335/+files/PulseList.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] ProcModules.txt

[Jesko]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338334/+files/ProcModules.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] ProcInterrupts.txt

[Jesko]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338333/+files/ProcInterrupts.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1867885] Re: Suspend does not work on Thinkpad X1 Yoga

[Jesko]

apport information

** Tags added: apport-collected

** Description changed:

  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
+ --- 
+ ProblemType: Bug
+ 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: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2020-01-15 (62 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ MachineType: LENOVO 20QFS10B00
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-42-generic N/A
+  linux-backports-modules-5.3.0-42-generic  N/A
+  linux-firmware1.183.4
+ Tags:  eoan
+ Uname: Linux 5.3.0-42-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: 02/21/2020
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET46W (1.29 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QFS10B00
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
+ dmi.product.family: ThinkPad X1 Yoga 4th
+ dmi.product.name: 20QFS10B00
+ dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
+ dmi.product.version: ThinkPad X1 Yoga 4th
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1867885/+attachment/5338324/+files/AlsaInfo.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/1867885

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  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: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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