[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Kai-Heng Feng]

https://lore.kernel.org/lkml/20200311165806.12365-1-kai.heng.f...@canonical.com/

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA Corporation Device 1aec
 |\-00.3  NVIDIA Corporation Device 1aed
  ...

  Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
  Controller" in Windows.

  I'm not sure if it's serving any useful purpose on this laptop, and it
  certainly doesn't seem to function properly:

  If I enable UCSI logging on startup (root's crontab):

  @reboot bash -c 'echo 1 >
  /sys/kernel/debug/tracing/events/ucsi/enable'

  ..the steps to reproduce above result in the following 
/sys/kernel/debug/tracing/trace:
  # tracer: nop
  #
  # 

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Nickolay Ponomarev]

As the original reporter, I feel the obligation to reply: I'm not using
the problematic laptop anymore, so if anyone else can test the proposed
version - that would be most awesome!


kaihengfeng, thanks for taking a look! I'm curious - are you in contact with / 
part of the kernel USB team? Could you link to the commit the version you 
posted was built from? Testing new kernels is rather time-consuming for me due 
to lack of experience. Understanding the proposed patch and how it can fix the 
problem would make it much more fun (especially as the last time I checked - 
December i think? - the mainline kernel had regressed further on this hardware.)

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA 

[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio

[Hui Wang]

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

** Description changed:

+ Drop the B, so far only need to merge this patchset to OEM-B first,
+ After the patchset is widely verified with oem-b kernel, I send the
+ patchset to B and F then.
+ 
+ 
  This patchset will add support of mst audio for nvidia hdmi/dp, this
  patchset changes lots of common code on hda_jack and hdmi codec, so it
  is not easy to say it is 100% safe for other machines, but our oem
  project needs this patchset to be backported to ubuntu kernel, because
  the tight sechdule of oem project, we backport this patchset to B and
  OEM-B first, if the hdmi audio works well for a period of time after
  this patchset is merged, I will backport this patchset to focal, maybe
  eoan as well.
  
  [Impact]
  On some LENOVO I+N machines, when setting the graphic mode to discrete,
  The dp/hdmi audio on the Docking Gen2 can't work with this machine +
- LENOVO Docking Gen2 
+ LENOVO Docking Gen2
  
  [Fix]
  Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1,
  those patches could fix this issue.
  
  [Test Case]
  set the machien to discrete, plug the dock gen2 to it, then boot, after
  booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works.
  
  test other machines without Nvidia graphic or without gen2, their hdmi/dp
  audio still work.
  
- 
  [Regression Risk]
  Low, those patches come from mainline kernel, I have tested those patches
  on the machiens with or without nvidia hdmi, and on the machines with or 
without
  docks, all worked well as before.

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

Title:
  alsa/hdmi: support nvidia mst hdmi/dp audio

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

Bug description:
  Drop the B, so far only need to merge this patchset to OEM-B first,
  After the patchset is widely verified with oem-b kernel, I send the
  patchset to B and F then.

  
  This patchset will add support of mst audio for nvidia hdmi/dp, this
  patchset changes lots of common code on hda_jack and hdmi codec, so it
  is not easy to say it is 100% safe for other machines, but our oem
  project needs this patchset to be backported to ubuntu kernel, because
  the tight sechdule of oem project, we backport this patchset to B and
  OEM-B first, if the hdmi audio works well for a period of time after
  this patchset is merged, I will backport this patchset to focal, maybe
  eoan as well.

  [Impact]
  On some LENOVO I+N machines, when setting the graphic mode to discrete,
  The dp/hdmi audio on the Docking Gen2 can't work with this machine +
  LENOVO Docking Gen2

  [Fix]
  Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1,
  those patches could fix this issue.

  [Test Case]
  set the machien to discrete, plug the dock gen2 to it, then boot, after
  booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works.

  test other machines without Nvidia graphic or without gen2, their hdmi/dp
  audio still work.

  [Regression Risk]
  Low, those patches come from mainline kernel, I have tested those patches
  on the machiens with or without nvidia hdmi, and on the machines with or 
without
  docks, all worked well as before.

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

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

[Kernel-packages] [Bug 1868091] Re: AMD graphics terrible pixelation on XFCE

[opnsrctechtrn]

apport-collect updated and posted below. Again I know this is Linux-
Mint, but syncing to ensure there is visibility. I posted in the XFCE
and LM forums, and essentially my understanding this is a driver
incompatibility or library issue between the amdgpu open source drives
in kernel 5.3 and XFCE's Windows Compositor. Disabling windows
compositor (vsync) fixes the pixelation, but introduces wicked tearing,
while all this was and is fine using 5.0.

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

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

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] WifiSyslog.txt

[opnsrctechtrn]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339159/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] UdevDb.txt

[opnsrctechtrn]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1868091/+attachment/5339158/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] ProcInterrupts.txt

[opnsrctechtrn]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339154/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] ProcEnviron.txt

[opnsrctechtrn]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339153/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] ProcCpuinfo.txt

[opnsrctechtrn]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339151/+files/ProcCpuinfo.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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] ProcCpuinfoMinimal.txt

[opnsrctechtrn]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339152/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] PulseList.txt

[opnsrctechtrn]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339156/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] RfKill.txt

[opnsrctechtrn]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1868091/+attachment/5339157/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] CRDA.txt

[opnsrctechtrn]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1868091/+attachment/5339146/+files/CRDA.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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] ProcModules.txt

[opnsrctechtrn]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339155/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] Lsusb.txt

[opnsrctechtrn]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1868091/+attachment/5339150/+files/Lsusb.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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] CurrentDmesg.txt

[opnsrctechtrn]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339147/+files/CurrentDmesg.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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] Lspci.txt

[opnsrctechtrn]

apport information

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

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

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] IwConfig.txt

[opnsrctechtrn]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339148/+files/IwConfig.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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AMCN26WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14API
  dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
  dmi.product.family: IdeaPad S340-14API
  dmi.product.name: 81NB
  dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
  dmi.product.version: Lenovo IdeaPad S340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868091] Re: AMD graphics terrible pixelation on XFCE

[opnsrctechtrn]

apport information

** Tags added: apport-collected tricia

** Description changed:

  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems like
  the major difference is AMD base driver changes from 5.0.0-37 to 5.3 <-
  thus far any version causes severe pixelation for every new window
  rendering Linux Mint XFCE unusable unless the Windows Display Compositor
  is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB RAM.
  5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which also
  seems to work (though not as snappy as the original XFCE). I wanted to
  highlight and also understand if Xubuntu might face a similar issue with
  that APU come the 20.04 update or if there is a fix that hasn't made it
  to the Linux Mint distribution.
  
  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403
  
  Thank you
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  joe2641 F pulseaudio
+  /dev/snd/controlC0:  joe2641 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Linux Mint 19.3
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2020-01-03 (76 days ago)
+ InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
+ MachineType: LENOVO 81NB
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
+ Tags:  tricia
+ Uname: Linux 5.3.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/15/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: AMCN26WW(V1.09)
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40700 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo IdeaPad S340-14API
+ dmi.modalias: 
dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API:
+ dmi.product.family: IdeaPad S340-14API
+ dmi.product.name: 81NB
+ dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API
+ dmi.product.version: Lenovo IdeaPad S340-14API
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1868091/+attachment/5339145/+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/1868091

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joe2641 F pulseaudio
   /dev/snd/controlC0:  joe2641 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-03 (76 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: LENOVO 81NB
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-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.173.16
  Tags:  tricia
  

[Kernel-packages] [Bug 1868196] 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/1868196

Title:
  HID ELAN9038 probe fails with "report is too long"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of upgrade to kernel 5.3.0-42 I see errors in journal reported for
  ELAN9038 HID.

  $ uname -a
Linux 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo journalctl -b | grep multitouch
hid-multitouch 0018:04F3:261A.0001: report is too long
hid-multitouch 0018:04F3:261A.0001: item 0 1 0 8 parsing failed
hid-multitouch: probe of 0018:04F3:261A.0001 failed with error -22

  The same device on 5.3.0-40 works without issues.

  $ uname -a
Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo journalctl -b | grep multitouch
hid-multitouch 0018:04F3:261A.0001: input,hidraw0: I2C HID v1.00 Device 
[ELAN9038:00 04F3:261A] on i2c-ELAN9038:00

  I did find the same issue has been also reported on version 5.6 under
  bug #206259 (https://bugzilla.kernel.org/show_bug.cgi?id=206259).

  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.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josip  3946 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 19:36:40 2020
  InstallationDate: Installed on 2020-03-08 (11 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:096f Microsoft Corp. Surface Type Cover
   Bus 001 Device 002: ID 0cf3:e302 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Go
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 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: 06/24/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 1.0.19
  dmi.board.name: Surface Go
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr1.0.19:bd06/24/2019:svnMicrosoftCorporation:pnSurfaceGo:pvr1:rvnMicrosoftCorporation:rnSurfaceGo:rvr:cvnMicrosoftCorporation:ct9:cvrChassisVersion:
  dmi.product.family: Surface
  dmi.product.name: Surface Go
  dmi.product.sku: Surface_Go_1824_Consumer
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1868197] 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/1868197

Title:
  iwlwifi fails to communicate with Intel Wireless-AC 9650 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This isn't a bug just in the Ubuntu kernel, as it happened on Debian
  too, and I wouldn't rule out any hardware issue either, but I wanted
  to share this here to see if I could get any help. I dual boot Windows
  and Linux and I think my WiFi card might be failing, but it could also
  be a case of bad firmware. It used to work well, but now both Windows
  and Linux fail to start my card most of the time. However, sometimes
  Windows will successfully be able to use it.

  This is the latest bit of error lines that have appeared in dmesg:

  [8.109230] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [8.521736] [ cut here ]
  [8.521737] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c)
  [8.521772] WARNING: CPU: 4 PID: 487 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2015 
iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
  [8.521772] Modules linked in: cmac bnep snd_hda_codec_hdmi nls_iso8859_1 
sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_hda_codec_realtek 
snd_soc_hdac_hda snd_hda_codec_generic ledtrig_audio snd_hda_ext_core 
snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match 
snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp joydev coretemp kvm_intel kvm irqbypass 
snd_hda_intel snd_intel_nhlt snd_hda_codec mei_hdcp snd_hda_core intel_rapl_msr 
snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel nouveau snd_seq 
snd_seq_device iwlmvm aes_x86_64 crypto_simd ttm cryptd asus_nb_wmi snd_timer 
i915 glue_helper intel_cstate mac80211 uvcvideo videobuf2_vmalloc input_leds 
drm_kms_helper intel_rapl_perf serio_raw wmi_bmof libarc4 btusb 
videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel
  [8.521786]  hid_sensor_accel_3d asus_wmi videobuf2_common snd mxm_wmi 
bluetooth hid_sensor_trigger industrialio_triggered_buffer kfifo_buf drm 
hid_sensor_iio_common videodev industrialio iwlwifi i2c_algo_bit fb_sys_fops 
soundcore mc mei_me syscopyarea ecdh_generic processor_thermal_device ecc 
cros_ec_ishtp idma64 hid_multitouch intel_rapl_common cros_ec_core virt_dma 
sysfillrect intel_pch_thermal intel_soc_dts_iosf sysimgblt mei cfg80211 
int3403_thermal int340x_thermal_zone intel_hid int3400_thermal acpi_thermal_rel 
mac_hid sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp 
parport ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_loader intel_ishtp_hid hid_generic nvme nvme_core i2c_i801 ahci 
intel_lpss_pci intel_ish_ipc i2c_hid libahci intel_lpss intel_ishtp hid 
pinctrl_cannonlake wmi video pinctrl_intel
  [8.521801] CPU: 4 PID: 487 Comm: irq/146-iwlwifi Tainted: GW  
   5.3.0-42-generic #34-Ubuntu
  [8.521801] Hardware name: ASUSTeK COMPUTER INC. ZenBook 
Q536FD_Q536FD/Q536FD, BIOS Q536FD.306 05/31/2019
  [8.521806] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
  [8.521807] Code: fa da 49 8d 57 08 bf 00 20 00 00 e8 c1 4f 81 d9 e9 30 ff 
ff ff 89 c6 48 c7 c7 58 f5 6c c0 c6 05 81 11 03 00 01 e8 e2 51 7f d9 <0f> 0b e9 
eb fe ff ff 49 8b 7c 24 30 48 c7 c1 c0 f5 6c c0 31 d2 31
  [8.521807] RSP: 0018:aee380b8bc98 EFLAGS: 00010082
  [8.521808] RAX:  RBX: aee380b8bcd0 RCX: 
0006
  [8.521808] RDX: 0007 RSI: 0082 RDI: 
9422dbb17440
  [8.521809] RBP: aee380b8bcc0 R08: 0469 R09: 
0004
  [8.521809] R10:  R11: 0001 R12: 
9422d3670018
  [8.521809] R13:  R14: 9422d36790b4 R15: 
0c04000c
  [8.521810] FS:  () GS:9422dbb0() 
knlGS:
  [8.521810] CS:  0010 DS:  ES:  CR0: 80050033
  [8.521811] CR2: 557d76a01338 CR3: 0002f2e0a003 CR4: 
003606e0
  [8.521811] Call Trace:
  [8.521817]  iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi]
  [8.521822]  iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm]
  [8.521825]  ? __dev_printk+0x5c/0x6f
  [8.521826]  ? _dev_err+0x6c/0x83
  [8.521827]  ? lock_timer_base+0x72/0xa0
  [8.521831]  iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm]
  [8.521834]  iwl_mvm_nic_error+0x35/0x40 [iwlmvm]
  [8.521838]  iwl_pcie_irq_handle_error+0xb1/0x110 [iwlwifi]
  [8.521841]  iwl_pcie_irq_msix_handler+0x197/0x4b0 

[Kernel-packages] [Bug 1868196] [NEW] HID ELAN9038 probe fails with "report is too long"

[Josip Medved]

Public bug reported:

As of upgrade to kernel 5.3.0-42 I see errors in journal reported for
ELAN9038 HID.

$ uname -a
  Linux 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

$ sudo journalctl -b | grep multitouch
  hid-multitouch 0018:04F3:261A.0001: report is too long
  hid-multitouch 0018:04F3:261A.0001: item 0 1 0 8 parsing failed
  hid-multitouch: probe of 0018:04F3:261A.0001 failed with error -22

The same device on 5.3.0-40 works without issues.

$ uname -a
  Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

$ sudo journalctl -b | grep multitouch
  hid-multitouch 0018:04F3:261A.0001: input,hidraw0: I2C HID v1.00 Device 
[ELAN9038:00 04F3:261A] on i2c-ELAN9038:00

I did find the same issue has been also reported on version 5.6 under
bug #206259 (https://bugzilla.kernel.org/show_bug.cgi?id=206259).

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.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  josip  3946 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 19:36:40 2020
InstallationDate: Installed on 2020-03-08 (11 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 045e:096f Microsoft Corp. Surface Type Cover
 Bus 001 Device 002: ID 0cf3:e302 Qualcomm Atheros Communications 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Microsoft Corporation Surface Go
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 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: 06/24/2019
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: 1.0.19
dmi.board.name: Surface Go
dmi.board.vendor: Microsoft Corporation
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr1.0.19:bd06/24/2019:svnMicrosoftCorporation:pnSurfaceGo:pvr1:rvnMicrosoftCorporation:rnSurfaceGo:rvr:cvnMicrosoftCorporation:ct9:cvrChassisVersion:
dmi.product.family: Surface
dmi.product.name: Surface Go
dmi.product.sku: Surface_Go_1824_Consumer
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation

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


** Tags: amd64 apport-bug 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/1868196

Title:
  HID ELAN9038 probe fails with "report is too long"

Status in linux package in Ubuntu:
  New

Bug description:
  As of upgrade to kernel 5.3.0-42 I see errors in journal reported for
  ELAN9038 HID.

  $ uname -a
Linux 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo journalctl -b | grep multitouch
hid-multitouch 0018:04F3:261A.0001: report is too long
hid-multitouch 0018:04F3:261A.0001: item 0 1 0 8 parsing failed
hid-multitouch: probe of 0018:04F3:261A.0001 failed with error -22

  The same device on 5.3.0-40 works without issues.

  $ uname -a
Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo journalctl -b | grep multitouch
hid-multitouch 0018:04F3:261A.0001: input,hidraw0: I2C HID v1.00 Device 
[ELAN9038:00 04F3:261A] on i2c-ELAN9038:00

  I did find the same issue has been also reported on version 5.6 under
  bug #206259 (https://bugzilla.kernel.org/show_bug.cgi?id=206259).

  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.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josip  3946 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 19:36:40 2020
  InstallationDate: Installed on 2020-03-08 (11 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:096f Microsoft Corp. Surface Type 

[Kernel-packages] [Bug 1868197] [NEW] iwlwifi fails to communicate with Intel Wireless-AC 9650 card

[Noah Gregory]

Public bug reported:

This isn't a bug just in the Ubuntu kernel, as it happened on Debian
too, and I wouldn't rule out any hardware issue either, but I wanted to
share this here to see if I could get any help. I dual boot Windows and
Linux and I think my WiFi card might be failing, but it could also be a
case of bad firmware. It used to work well, but now both Windows and
Linux fail to start my card most of the time. However, sometimes Windows
will successfully be able to use it.

This is the latest bit of error lines that have appeared in dmesg:

[8.109230] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[8.521736] [ cut here ]
[8.521737] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c)
[8.521772] WARNING: CPU: 4 PID: 487 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2015 
iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
[8.521772] Modules linked in: cmac bnep snd_hda_codec_hdmi nls_iso8859_1 
sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_hda_codec_realtek 
snd_soc_hdac_hda snd_hda_codec_generic ledtrig_audio snd_hda_ext_core 
snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match 
snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp joydev coretemp kvm_intel kvm irqbypass 
snd_hda_intel snd_intel_nhlt snd_hda_codec mei_hdcp snd_hda_core intel_rapl_msr 
snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel nouveau snd_seq 
snd_seq_device iwlmvm aes_x86_64 crypto_simd ttm cryptd asus_nb_wmi snd_timer 
i915 glue_helper intel_cstate mac80211 uvcvideo videobuf2_vmalloc input_leds 
drm_kms_helper intel_rapl_perf serio_raw wmi_bmof libarc4 btusb 
videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel
[8.521786]  hid_sensor_accel_3d asus_wmi videobuf2_common snd mxm_wmi 
bluetooth hid_sensor_trigger industrialio_triggered_buffer kfifo_buf drm 
hid_sensor_iio_common videodev industrialio iwlwifi i2c_algo_bit fb_sys_fops 
soundcore mc mei_me syscopyarea ecdh_generic processor_thermal_device ecc 
cros_ec_ishtp idma64 hid_multitouch intel_rapl_common cros_ec_core virt_dma 
sysfillrect intel_pch_thermal intel_soc_dts_iosf sysimgblt mei cfg80211 
int3403_thermal int340x_thermal_zone intel_hid int3400_thermal acpi_thermal_rel 
mac_hid sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp 
parport ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_loader intel_ishtp_hid hid_generic nvme nvme_core i2c_i801 ahci 
intel_lpss_pci intel_ish_ipc i2c_hid libahci intel_lpss intel_ishtp hid 
pinctrl_cannonlake wmi video pinctrl_intel
[8.521801] CPU: 4 PID: 487 Comm: irq/146-iwlwifi Tainted: GW
 5.3.0-42-generic #34-Ubuntu
[8.521801] Hardware name: ASUSTeK COMPUTER INC. ZenBook 
Q536FD_Q536FD/Q536FD, BIOS Q536FD.306 05/31/2019
[8.521806] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
[8.521807] Code: fa da 49 8d 57 08 bf 00 20 00 00 e8 c1 4f 81 d9 e9 30 ff 
ff ff 89 c6 48 c7 c7 58 f5 6c c0 c6 05 81 11 03 00 01 e8 e2 51 7f d9 <0f> 0b e9 
eb fe ff ff 49 8b 7c 24 30 48 c7 c1 c0 f5 6c c0 31 d2 31
[8.521807] RSP: 0018:aee380b8bc98 EFLAGS: 00010082
[8.521808] RAX:  RBX: aee380b8bcd0 RCX: 0006
[8.521808] RDX: 0007 RSI: 0082 RDI: 9422dbb17440
[8.521809] RBP: aee380b8bcc0 R08: 0469 R09: 0004
[8.521809] R10:  R11: 0001 R12: 9422d3670018
[8.521809] R13:  R14: 9422d36790b4 R15: 0c04000c
[8.521810] FS:  () GS:9422dbb0() 
knlGS:
[8.521810] CS:  0010 DS:  ES:  CR0: 80050033
[8.521811] CR2: 557d76a01338 CR3: 0002f2e0a003 CR4: 003606e0
[8.521811] Call Trace:
[8.521817]  iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi]
[8.521822]  iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm]
[8.521825]  ? __dev_printk+0x5c/0x6f
[8.521826]  ? _dev_err+0x6c/0x83
[8.521827]  ? lock_timer_base+0x72/0xa0
[8.521831]  iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm]
[8.521834]  iwl_mvm_nic_error+0x35/0x40 [iwlmvm]
[8.521838]  iwl_pcie_irq_handle_error+0xb1/0x110 [iwlwifi]
[8.521841]  iwl_pcie_irq_msix_handler+0x197/0x4b0 [iwlwifi]
[8.521843]  ? irq_finalize_oneshot.part.0+0xf0/0xf0
[8.521844]  irq_thread_fn+0x28/0x60
[8.521845]  irq_thread+0xda/0x170
[8.521845]  ? irq_forced_thread_fn+0x80/0x80
[8.521847]  kthread+0x104/0x140
[8.521848]  ? irq_thread_check_affinity+0xf0/0xf0
[8.521849]  ? kthread_park+0x80/0x80
[8.521851]  ret_from_fork+0x35/0x40
[8.521852] ---[ end trace 8398d136a219cba4 ]---
[8.521853] iwlwifi :00:14.3: iwlwifi 

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

[Hui Wang]

Akkana,

Could you upload your dmesg, or could you install 5.3.0-43 kernel, and
with -43 kernel, you could remove dmic_detect=0 or keep it.

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

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

@eddie,

If your usb audio doesn't work, please file a new bug against the linux
kernel. Let's track your issue in that bug.

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 1860013] Re: [thunderx] Synchronous External Abort: synchronous parity or ECC error

[dann frazier]

sorry s/Juery/Juerg/!

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

Title:
  [thunderx] Synchronous External Abort: synchronous parity or ECC error

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Impact]
  Under load, ThunderX systems eventually fail with:

  [  282.360376] Synchronous External Abort: synchronous parity or ECC error 
(0x9618) at 0xa6eb7000
  [  282.372351] Internal error: : 9618 [#1] SMP
  [  282.379152] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
shpchp cavium_rng_vf 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 uas usb_storage ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt aes_ce_blk fb_sys_fops aes_ce_cipher drm crc32_ce 
crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci libahci thunder_bgx 
thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd aes_arm64
  [  282.467284] Process cc1 (pid: 39700, stack limit = 0xe0c44146)
  [  282.477172] CPU: 25 PID: 39700 Comm: cc1 Not tainted 4.15.0-75-generic 
#85+lp1857074.1
  [  282.488379] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [  282.500121] pstate: 8005 (Nzcv daif -PAN -UAO)
  [  282.508297] pc : __arch_copy_to_user+0x13c/0x248
  [  282.516430] lr : cp_new_stat+0x140/0x178
  [  282.523768] sp : 2e4d3d40
  [  282.530369] x29: 2e4d3d40 x28: 801f51fa2d00 
  [  282.538988] x27: 08b52000 x26: 0050 
  [  282.548031] x25: 0124 x24: 0015 
  [  282.556872] x23:  x22: 2e4d3d88 
  [  282.565449] x21: 801f51fa2d00 x20: 09588000 
  [  282.574109] x19: 2e4d3e30 x18: a87e7a70 
  [  282.582790] x17: a8756110 x16: 082f4448 
  [  282.591433] x15:  x14: 0012 
  [  282.599986] x13: 00682e6c746e6366 x12: 2f78756e696c2f69 
  [  282.608730] x11:  x10: 0cf0 
  [  282.617283] x9 : 1000 x8 : 000181a4 
  [  282.625839] x7 : 01001a2b x6 : 2e4d3da0 
  [  282.634238] x5 : 2e4d3e08 x4 : 0008 
  [  282.642754] x3 : 0802 x2 : fff8 
  [  282.651250] x1 : 2e4d3d90 x0 : 2e4d3d88 
  [  282.660013] Call trace:
  [  282.665421]  __arch_copy_to_user+0x13c/0x248
  [  282.672979]  SyS_newfstat+0x58/0x88
  [  282.679272]  el0_svc_naked+0x30/0x34
  [  282.685605] Code: a8c12027 a88120c7 d503201f d503201f (a8c12829) 
  [  282.694411] ---[ end trace 863693cf0c3fd297 ]---

  [Test Case]
  We found this by doing a reboot/kernel build loop. (The reboot maybe 
unnecessary). Code to automate this setup is at:
https://code.launchpad.net/~dannf/+git/kernel-build-reboot-loop

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1860013] Re: [thunderx] Synchronous External Abort: synchronous parity or ECC error

[dann frazier]

@Juery: I have no reason to believe this is related to the boot
regression we fixed (bug 1857074). I haven't re-tested lately, but as of
4.15.0-76 it was still reproducible.

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

Title:
  [thunderx] Synchronous External Abort: synchronous parity or ECC error

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Impact]
  Under load, ThunderX systems eventually fail with:

  [  282.360376] Synchronous External Abort: synchronous parity or ECC error 
(0x9618) at 0xa6eb7000
  [  282.372351] Internal error: : 9618 [#1] SMP
  [  282.379152] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
shpchp cavium_rng_vf 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 uas usb_storage ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt aes_ce_blk fb_sys_fops aes_ce_cipher drm crc32_ce 
crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci libahci thunder_bgx 
thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd aes_arm64
  [  282.467284] Process cc1 (pid: 39700, stack limit = 0xe0c44146)
  [  282.477172] CPU: 25 PID: 39700 Comm: cc1 Not tainted 4.15.0-75-generic 
#85+lp1857074.1
  [  282.488379] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [  282.500121] pstate: 8005 (Nzcv daif -PAN -UAO)
  [  282.508297] pc : __arch_copy_to_user+0x13c/0x248
  [  282.516430] lr : cp_new_stat+0x140/0x178
  [  282.523768] sp : 2e4d3d40
  [  282.530369] x29: 2e4d3d40 x28: 801f51fa2d00 
  [  282.538988] x27: 08b52000 x26: 0050 
  [  282.548031] x25: 0124 x24: 0015 
  [  282.556872] x23:  x22: 2e4d3d88 
  [  282.565449] x21: 801f51fa2d00 x20: 09588000 
  [  282.574109] x19: 2e4d3e30 x18: a87e7a70 
  [  282.582790] x17: a8756110 x16: 082f4448 
  [  282.591433] x15:  x14: 0012 
  [  282.599986] x13: 00682e6c746e6366 x12: 2f78756e696c2f69 
  [  282.608730] x11:  x10: 0cf0 
  [  282.617283] x9 : 1000 x8 : 000181a4 
  [  282.625839] x7 : 01001a2b x6 : 2e4d3da0 
  [  282.634238] x5 : 2e4d3e08 x4 : 0008 
  [  282.642754] x3 : 0802 x2 : fff8 
  [  282.651250] x1 : 2e4d3d90 x0 : 2e4d3d88 
  [  282.660013] Call trace:
  [  282.665421]  __arch_copy_to_user+0x13c/0x248
  [  282.672979]  SyS_newfstat+0x58/0x88
  [  282.679272]  el0_svc_naked+0x30/0x34
  [  282.685605] Code: a8c12027 a88120c7 d503201f d503201f (a8c12829) 
  [  282.694411] ---[ end trace 863693cf0c3fd297 ]---

  [Test Case]
  We found this by doing a reboot/kernel build loop. (The reboot maybe 
unnecessary). Code to automate this setup is at:
https://code.launchpad.net/~dannf/+git/kernel-build-reboot-loop

  [Fix]
  [Regression Risk]

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

[Eddie Dunn]

@hui.wang

My USB headset no longer works. I installed kernel 5.3.0-43 from
proposed and libasound2 from your ppa.

$ uname -a
Linux eddie-minut 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
$ cat /sys/devices/virtual/dmi/id/bios_version
N2HET46W (1.29 )
$ dpkg -l libasound2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   Architecture Description
+++--=--
ii  libasound2:amd64 1.1.9-0ubuntu1.2++testucm amd64shared library for 
ALSA applications

$ dmesg
...
[  464.139786] usb 1-3: Manufacturer: Kingston
[  464.378226] input: Kingston HyperX Cloud Flight Wireless Headset Consumer 
Control as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input33
[  464.437214] input: Kingston HyperX Cloud Flight Wireless Headset as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input34
[  464.437594] input: Kingston HyperX Cloud Flight Wireless Headset as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input35
[  464.437943] input: Kingston HyperX Cloud Flight Wireless Headset as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input36
[  464.438711] hid-generic 0003:0951:16C4.0005: input,hiddev0,hidraw1: USB HID 
v1.11 Device [Kingston HyperX Cloud Flight Wireless Headset] on 
usb-:00:14.0-3/input3
[  465.169150] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
[  465.264582] sof-audio-pci :00:1f.3: firmware boot complete
[  465.578000] debugfs: File 'Analog Playback and Capture' in directory 'HDA 
Analog' already present!
[  465.703404] debugfs: File 'Analog Playback and Capture' in directory 'HDA 
Analog' already present!
[  532.954965] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
[  533.052406] sof-audio-pci :00:1f.3: firmware boot complete
[  543.902184] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0

When I plug in a headset with a mic in the 3.5mm port, it still seems to
use the internal mic instead of that of the headset.

I also get a lot of popping sounds in the 3.5mm headset when playing
audio, but that might not be related to this issue as I had that on
kernel 5.3.0-41 as well.

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-master-bug: 1865198
+ kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Friday, 13. March 2020 17:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Signoff
- phase-changed: Friday, 13. March 2020 17:28 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Thursday, 19. March 2020 22:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Holding -- stakeholder signoff not verified
-   stakeholder-signoff: Stalled -- waiting for signoff
+   promote-to-updates: Holding -- master bug not ready for release
  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/1865197

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Updates
  phase-changed: Thursday, 19. March 2020 22:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Jack Hammons]

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

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Friday, 13. March 2020 17:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

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

[Kernel-packages] [Bug 1694367] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1694367

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

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

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

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

** Tags added: yakkety

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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

[Kernel-packages] [Bug 1755968] Re: Failed to install ubuntu 18.04 desktop 64bit latest daily build image in ESXi. It seems like installer crash at the starting point to install

[Juhani Numminen]

Changed the bug status to Fix Released due to reporter's previous
message.

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Failed to install ubuntu 18.04 desktop 64bit latest daily build image
  in ESXi. It seems like installer crash at the starting point to
  install

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Failed to install ubuntu 18.04 desktop 64bit latest daily build image
  in ESXi. It seems like installer crash at the starting point.

  Error message is below:

  [ ***] S start job is running for Ubuntu live CD installer (2min 9s / no 
limit) 
  dbus-daemon[754]: [session uid=999 pid=754] Activating service 
name='org.gtk.vfs.Daemon' requested 
  by '1:0' (uid=999 pid=755 comm="" label="unconfined")
  dbus-daemon[754]: [session uid=999 pid=754] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[754]: [session uid=999 pid=754] Activating service 
name='org.gtk.vfs.Daemon' requested 
  by '1:0' (uid=999 pid=755 comm="" label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[754]: [session uid=999 pid=754] Successfully activate service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:766): GUdev-CRITICAL **:07:43:22.201:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE(device)'
  failed

  (gvfsd-metadata:766): GUdev-CRITICAL **:07:43:22.201:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE(device)'
  failed

  A connection to the bus can't be made
  Using CD-ROM mount point /cdroom/
  Identifying...[784a7e1250cc02e5c8ccdd23115a-2]
  Scaaning disc for index files...
  Found 2 package indexes , 0 source indexes, 0 translation indexes and 1 
signatures
  Found label 'Ubuntu 18.04 LTS _Binnic Beaver_ -Alpha amd64 (20180311)'
  This disc is called:
  Found label 'Ubuntu 18.04 LTS _Binnic Beaver_ -Alpha amd64 (20180311)'
  Copying package lists..gpgv:Signature made Sun Mar 11 07:55:27 2018 UTC
  gpgv: using RSA key D94AA3f0EEFE21092
  gpgv: Good signature from "Ubuntu CD Image Automatic Signing key (2012) 
"
  Reading Package Index... Done
  Wring new source list
  Source list entries for this disc are:
  deb cdrom:[Uubntu 18.04 LTS _Bolic Beaver_ -Alpha amd64 (20180311)]/bionic 
main restricted
  Repeat this process for the rest of CDs in your set.
  [ OK ] Starting LSB: Speech Dispatcher.
  [ OK ] Starting LSB: Automatic crash report generation.
  [ OK ] Starting LSB: Record successful boot for GRUB
  [ OK ] Thermal Daemon Service
  [ OK ] Start Tools to automatically collect and submit kernel crash 
signatures...

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

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

[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device

[pheidrias]

Same here: Toshiba Portege z20t C

Interestingly, the touchpad works but the keyboard doesnt. I have to
detach and reattach it to make it work.

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

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

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

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:02:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1868091] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1868091

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

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

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

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

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

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you

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

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

[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4

[Juhani Numminen]

Unrelated to kernel-package that contains tools for building a custom
kernel.

** Changed in: kernel-package (Ubuntu)
   Status: New => Invalid

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

Title:
  IR pilot is not working after kernel change from 3.13 to 4.4

Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  linux-image-4.4.0-72-generic

  I'm using custom IR receiver with CIR header in my ASRock MoBo.
  This one IR receiver serves 3 devices - HTPC, TV and amplifier.

  Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped 
to work with HTPC.
  mode2 app shows, that IR header is receiving something, but there is 
something wrong.

  Example pulse-pause timings for 3.13 kernel are:
  space 2949
  pulse 39
  space 1157
  pulse 39
  space 1159
  pulse 39
  Example pulse-pause timings for 4.4 kernel are:
  space 16777176
  pulse 1
  space 16777176
  pulse 1
  space 16777176
  pulse 1

  for this same button.

  Maybe I'm not only one which wants still to use lirc_sir
  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 11:55:14 2017
  SourcePackage: lirc
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dugi  10933 F pulseaudio
   /dev/snd/controlC0:  dugi  10933 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro 
video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf 
nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: lirc_sir
  Tags:  trusty staging trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 07/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: FM2A75 Pro4-M
  dmi.board.vendor: ASRock
  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.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 4.11.0-041100rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1681838/+subscriptions

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

[Kernel-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

[Juhani Numminen]

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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

[Kernel-packages] [Bug 1868091] Re: AMD graphics terrible pixelation on XFCE

[Juhani Numminen]

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

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

Title:
  AMD graphics terrible pixelation on XFCE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  So posted this on several forums in Linux Mint 19.3 and XFCE. Seems
  like the major difference is AMD base driver changes from 5.0.0-37 to
  5.3 <- thus far any version causes severe pixelation for every new
  window rendering Linux Mint XFCE unusable unless the Windows Display
  Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB
  RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which
  also seems to work (though not as snappy as the original XFCE). I
  wanted to highlight and also understand if Xubuntu might face a
  similar issue with that APU come the 20.04 update or if there is a fix
  that hasn't made it to the Linux Mint distribution.

  Other posts for reference: 
  https://forums.linuxmint.com/viewtopic.php?t=310609
  https://bugzilla.xfce.org/show_bug.cgi?id=16403

  Thank you

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

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

[Kernel-packages] [Bug 1755968] [NEW] Failed to install ubuntu 18.04 desktop 64bit latest daily build image in ESXi. It seems like installer crash at the starting point to install

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Failed to install ubuntu 18.04 desktop 64bit latest daily build image in
ESXi. It seems like installer crash at the starting point.

Error message is below:

[ ***] S start job is running for Ubuntu live CD installer (2min 9s / no limit) 
dbus-daemon[754]: [session uid=999 pid=754] Activating service 
name='org.gtk.vfs.Daemon' requested 
by '1:0' (uid=999 pid=755 comm="" label="unconfined")
dbus-daemon[754]: [session uid=999 pid=754] Successfully activated service 
'org.gtk.vfs.Daemon'
dbus-daemon[754]: [session uid=999 pid=754] Activating service 
name='org.gtk.vfs.Daemon' requested 
by '1:0' (uid=999 pid=755 comm="" label="unconfined")
fuse: device not found, try 'modprobe fuse' first
dbus-daemon[754]: [session uid=999 pid=754] Successfully activate service 
'org.gtk.vfs.Metadata'

(gvfsd-metadata:766): GUdev-CRITICAL **:07:43:22.201:
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE(device)' failed

(gvfsd-metadata:766): GUdev-CRITICAL **:07:43:22.201:
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE(device)' failed

A connection to the bus can't be made
Using CD-ROM mount point /cdroom/
Identifying...[784a7e1250cc02e5c8ccdd23115a-2]
Scaaning disc for index files...
Found 2 package indexes , 0 source indexes, 0 translation indexes and 1 
signatures
Found label 'Ubuntu 18.04 LTS _Binnic Beaver_ -Alpha amd64 (20180311)'
This disc is called:
Found label 'Ubuntu 18.04 LTS _Binnic Beaver_ -Alpha amd64 (20180311)'
Copying package lists..gpgv:Signature made Sun Mar 11 07:55:27 2018 UTC
gpgv: using RSA key D94AA3f0EEFE21092
gpgv: Good signature from "Ubuntu CD Image Automatic Signing key (2012) 
"
Reading Package Index... Done
Wring new source list
Source list entries for this disc are:
deb cdrom:[Uubntu 18.04 LTS _Bolic Beaver_ -Alpha amd64 (20180311)]/bionic main 
restricted
Repeat this process for the rest of CDs in your set.
[ OK ] Starting LSB: Speech Dispatcher.
[ OK ] Starting LSB: Automatic crash report generation.
[ OK ] Starting LSB: Record successful boot for GRUB
[ OK ] Thermal Daemon Service
[ OK ] Start Tools to automatically collect and submit kernel crash 
signatures...

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

-- 
Failed to install ubuntu 18.04 desktop 64bit latest daily build image in ESXi. 
It seems like installer crash at the starting point to install
https://bugs.launchpad.net/bugs/1755968
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1694367] [NEW] Screen tearing in 16.10 onwards

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In 16.10 onwards my laptop has always shown screen tearing globally,
additionally GL applications will not v-sync despite attempting to, they
appear to sync slightly off from the [integrated] display.

This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely
sure if it's a bug with either or a default miss-configuration in
ubuntu...

ubuntu-bug also appears to be broken...

** Affects: mesa
 Importance: High
 Status: Unknown

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

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

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

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

[Kernel-packages] [Bug 1868091] [NEW] AMD graphics terrible pixelation on XFCE

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

So posted this on several forums in Linux Mint 19.3 and XFCE. Seems like
the major difference is AMD base driver changes from 5.0.0-37 to 5.3 <-
thus far any version causes severe pixelation for every new window
rendering Linux Mint XFCE unusable unless the Windows Display Compositor
is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB RAM.
5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which also
seems to work (though not as snappy as the original XFCE). I wanted to
highlight and also understand if Xubuntu might face a similar issue with
that APU come the 20.04 update or if there is a fix that hasn't made it
to the Linux Mint distribution.

Other posts for reference: 
https://forums.linuxmint.com/viewtopic.php?t=310609
https://bugzilla.xfce.org/show_bug.cgi?id=16403

Thank you

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


** Tags: bot-comment
-- 
AMD graphics terrible pixelation on XFCE
https://bugs.launchpad.net/bugs/1868091
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

[Seth Forshee]

This should be fixed in focal now. I've uploaded packages for bionic and
eoan too, those are waiting to be approved and built.

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

Title:
  Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  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: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro 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
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN: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/1860697/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal

[Seth Forshee]

Let me just double check with you about disabling CONFIG_PM, as it also
supports runtime power management of devices. If CONFIG_PM is disabled
devices will not be put into low power states when idle.

-- 
You 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 1868165] 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/1868165

Title:
  [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from
  5.3.0-40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo ThinkPad X1 Carbon 7th edition laptop running Ubuntu
  19.10 desktop. I recently applied a software update that contained a
  new kernel, 5.3.0-42, and upon restarting, the internal audio
  interface was not found; internal speakers and the headphone output
  were unusable.

  Upon rebooting with the previous kernel, 5.3.0-40, the problem went
  away again. Subsequent testing confirms this is repeatable.

  Some relevant lines from `dmesg` follow.

  On kernel 5.3.0-40 (working):

  [4.386007] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.391825] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [4.392016] thermal thermal_zone5: failed to read out thermal zone (-61)
  [4.430083] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC285: 
line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
  [4.430085] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.430087] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.430087] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.430088] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.430089] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19

  
  On kernel 5.3.0-42 (broken):

  [3.076809] i915 :00:02.0: fb0: i915drmfb frame buffer device
  [3.088029] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.173463] snd_soc_skl :00:1f.3: Direct firmware load for 
9dc8-LENOVO-TP-N2H-4752-tplg.bin failed with error -2
  [3.173465] 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
  [3.173480] snd_soc_skl :00:1f.3: Direct firmware load for dfw_sst.bin 
failed with error -2
  [3.173481] snd_soc_skl :00:1f.3: Fallback tplg fw dfw_sst.bin load 
failed with -2
  [3.173484] snd_soc_skl :00:1f.3: Failed to init topology!
  [3.173486] snd_soc_skl :00:1f.3: ASoC: failed to probe component -2
  [3.173496] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -2
  [3.173508] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -2

  
  I've attached `lspci -vnvn` and `dmesg` output for both the -40 and -42 
kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  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.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gamache1768 F pulseaudio
   /dev/snd/controlC1:  gamache1768 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 15:08:14 2020
  InstallationDate: Installed on 2019-11-21 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QD0007US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=90290cff-6557-4384-b8a9-1b83f860ea01 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 20QD0007US
  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:pn20QD0007US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD0007US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD0007US
  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/1868165/+subscriptions

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

[Kernel-packages] [Bug 1868165] [NEW] [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from 5.3.0-40

[Pete Gamache]

Public bug reported:

I have a Lenovo ThinkPad X1 Carbon 7th edition laptop running Ubuntu
19.10 desktop. I recently applied a software update that contained a new
kernel, 5.3.0-42, and upon restarting, the internal audio interface was
not found; internal speakers and the headphone output were unusable.

Upon rebooting with the previous kernel, 5.3.0-40, the problem went away
again. Subsequent testing confirms this is repeatable.

Some relevant lines from `dmesg` follow.

On kernel 5.3.0-40 (working):

[4.386007] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.391825] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[4.392016] thermal thermal_zone5: failed to read out thermal zone (-61)
[4.430083] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC285: 
line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
[4.430085] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[4.430087] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[4.430087] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[4.430088] snd_hda_codec_realtek hdaudioC0D0:inputs:
[4.430089] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19


On kernel 5.3.0-42 (broken):

[3.076809] i915 :00:02.0: fb0: i915drmfb frame buffer device
[3.088029] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.173463] snd_soc_skl :00:1f.3: Direct firmware load for 
9dc8-LENOVO-TP-N2H-4752-tplg.bin failed with error -2
[3.173465] 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
[3.173480] snd_soc_skl :00:1f.3: Direct firmware load for dfw_sst.bin 
failed with error -2
[3.173481] snd_soc_skl :00:1f.3: Fallback tplg fw dfw_sst.bin load 
failed with -2
[3.173484] snd_soc_skl :00:1f.3: Failed to init topology!
[3.173486] snd_soc_skl :00:1f.3: ASoC: failed to probe component -2
[3.173496] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -2
[3.173508] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -2


I've attached `lspci -vnvn` and `dmesg` output for both the -40 and -42 kernels.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-40-generic 5.3.0-40.32
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.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gamache1768 F pulseaudio
 /dev/snd/controlC1:  gamache1768 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 15:08:14 2020
InstallationDate: Installed on 2019-11-21 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QD0007US
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=90290cff-6557-4384-b8a9-1b83f860ea01 ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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: 20QD0007US
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:pn20QD0007US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD0007US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QD0007US
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Contains `lspci -vnvn` and `dmesg` output for the 
5.3.0-40 and -42 kernels."
   
https://bugs.launchpad.net/bugs/1868165/+attachment/5339013/+files/gamache-bug-materials.tgz

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

Title:
  [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from
  5.3.0-40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo ThinkPad X1 Carbon 7th edition laptop running Ubuntu
  19.10 desktop. I recently applied a software update that contained a
  new kernel, 5.3.0-42, and upon restarting, the internal 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.187

---
linux-firmware (1.187) focal; urgency=medium

  * Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 (LP: #1860697)
- SAUCE: update sof firmwares to v1.4.2

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
8eb0b281511d6455ca9151e52f694dc982193251 (LP: #1865130)
- check_whence: python3/utf-8 support
- Makefile: improve `make check` usefulness
- mediatek: Remove in-tree symlinks
- qca: Fix blueooth firmware name for QCA6174
- mediatek: move MT8173 VPU FW to subfolder
- linux-firmware: Update firmware file for Intel Bluetooth AX201
- qca: Add firmware files for BT chip wcn3991.
- nvidia: add TU116/117 signed firmware
- drm/amdgpu: update to latest 19.50 firmware for raven
- mediatek: update MT8173 VPU firmware to v1.1.4
- rtl_nic: update firmware for RTL8153A
- rtl_bt: Update RTL8822C BT FW to V0x0998_C2B4
- linux-firmware: add firmware for MT7622
- linux-firmware: add version 2 for MT7615E
- amdgpu: update to latest navi10 firmware from 19.50
- Revert "radeon: update oland rlc microcode from amdgpu"
- amlogic: update video decoder firmwares
- amdgpu: add renoir firmware for 19.50
- amdgpu: update raven2 firmware for 19.50
- nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.12.A.13
- qca: update bluetooth firmware for QCA6174
- i915: add HuC firmware v7.0.12 for TGL
- i915: Add DMC firmware v2.06 for TGL
- rtl_bt: Add firmware and configuration files for RTL8822C BT UART chip
- amdgpu: update vega10 firmware from 19.50
- amdgpu: update vega12 firmware from 19.50
- amdgpu: update vega20 firmware from 19.50
- linux-firmware: Update firmware file for Intel Bluetooth 9260
- linux-firmware: Update firmware file for Intel Bluetooth 9560
- linux-firmware: Update firmware file for Intel Bluetooth AX201
- linux-firmware: Update firmware file for Intel Bluetooth AX200

 -- Seth Forshee   Thu, 19 Mar 2020 11:37:49
-0500

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

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

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

Status in linux-firmware package in Ubuntu:
  Fix Released

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

  [Fix]
  Revert the new firmware.

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

  === Original Bug Report ===

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

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

[Kernel-packages] [Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.187

---
linux-firmware (1.187) focal; urgency=medium

  * Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 (LP: #1860697)
- SAUCE: update sof firmwares to v1.4.2

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
8eb0b281511d6455ca9151e52f694dc982193251 (LP: #1865130)
- check_whence: python3/utf-8 support
- Makefile: improve `make check` usefulness
- mediatek: Remove in-tree symlinks
- qca: Fix blueooth firmware name for QCA6174
- mediatek: move MT8173 VPU FW to subfolder
- linux-firmware: Update firmware file for Intel Bluetooth AX201
- qca: Add firmware files for BT chip wcn3991.
- nvidia: add TU116/117 signed firmware
- drm/amdgpu: update to latest 19.50 firmware for raven
- mediatek: update MT8173 VPU firmware to v1.1.4
- rtl_nic: update firmware for RTL8153A
- rtl_bt: Update RTL8822C BT FW to V0x0998_C2B4
- linux-firmware: add firmware for MT7622
- linux-firmware: add version 2 for MT7615E
- amdgpu: update to latest navi10 firmware from 19.50
- Revert "radeon: update oland rlc microcode from amdgpu"
- amlogic: update video decoder firmwares
- amdgpu: add renoir firmware for 19.50
- amdgpu: update raven2 firmware for 19.50
- nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.12.A.13
- qca: update bluetooth firmware for QCA6174
- i915: add HuC firmware v7.0.12 for TGL
- i915: Add DMC firmware v2.06 for TGL
- rtl_bt: Add firmware and configuration files for RTL8822C BT UART chip
- amdgpu: update vega10 firmware from 19.50
- amdgpu: update vega12 firmware from 19.50
- amdgpu: update vega20 firmware from 19.50
- linux-firmware: Update firmware file for Intel Bluetooth 9260
- linux-firmware: Update firmware file for Intel Bluetooth 9560
- linux-firmware: Update firmware file for Intel Bluetooth AX201
- linux-firmware: Update firmware file for Intel Bluetooth AX200

 -- Seth Forshee   Thu, 19 Mar 2020 11:37:49
-0500

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

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

Title:
  Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  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: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro 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
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN: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/1860697/+subscriptions

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

[Kernel-packages] [Bug 1868149] 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/1868149

Title:
  When booting with intel graphics (enabled through prime-select), the
  computer freezes rigth after selecting 'Kubuntu' in GRUB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After booting with Intel graphics enabled, the Kubuntu initial screen 
appears, then the Lenovo screen.
  After about 5-7 minutes in the Lenovo screen, it shows the following message 
(https://imgur.com/a/NO8O1qL), which adds a new one after increments of 2 
minutes, .

  When changing to the patch '18', the computer functions normally,
  allowing me to change to the NVIDIA graphics and that's where I'm able
  to boot to my normal setup, in patch '42'. The same happens in patch
  '40' by the way.

  The strange part is, a few days ago everything worked out fine. This first 
happened when I changed from NVIDIA to Intel (through prime-select, as usual), 
and instead of restarting the PC through the button in the UI, I used the 
'reboot' command in the terminal. 
  I have also previously noticed that restarting my computer by the command is 
slower when comparing to clicking the button.

  Thanks in advance for any help!

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simao  1614 F pulseaudio
   /dev/snd/controlC0:  simao  1614 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Mar 19 18:02:27 2020
  InstallationDate: Installed on 2020-02-19 (29 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81LK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=8163e18b-5db4-497d-9ade-b94fa1f4269e 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: 12/27/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BGCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad L340-15IRH Gaming
  dmi.modalias: 
dmi:bvnLENOVO:bvrBGCN28WW:bd12/27/2019:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:
  dmi.product.family: IdeaPad L340-15IRH Gaming
  dmi.product.name: 81LK
  dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming
  dmi.product.version: IdeaPad L340-15IRH Gaming
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868149] [NEW] When booting with intel graphics (enabled through prime-select), the computer freezes rigth after selecting 'Kubuntu' in GRUB

[Simão Santos]

Public bug reported:

After booting with Intel graphics enabled, the Kubuntu initial screen appears, 
then the Lenovo screen.
After about 5-7 minutes in the Lenovo screen, it shows the following message 
(https://imgur.com/a/NO8O1qL), which adds a new one after increments of 2 
minutes, .

When changing to the patch '18', the computer functions normally,
allowing me to change to the NVIDIA graphics and that's where I'm able
to boot to my normal setup, in patch '42'. The same happens in patch
'40' by the way.

The strange part is, a few days ago everything worked out fine. This first 
happened when I changed from NVIDIA to Intel (through prime-select, as usual), 
and instead of restarting the PC through the button in the UI, I used the 
'reboot' command in the terminal. 
I have also previously noticed that restarting my computer by the command is 
slower when comparing to clicking the button.

Thanks in advance for any help!

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  simao  1614 F pulseaudio
 /dev/snd/controlC0:  simao  1614 F pulseaudio
CurrentDesktop: KDE
Date: Thu Mar 19 18:02:27 2020
InstallationDate: Installed on 2020-02-19 (29 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera
 Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81LK
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=8163e18b-5db4-497d-9ade-b94fa1f4269e 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: 12/27/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: BGCN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad L340-15IRH Gaming
dmi.modalias: 
dmi:bvnLENOVO:bvrBGCN28WW:bd12/27/2019:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:
dmi.product.family: IdeaPad L340-15IRH Gaming
dmi.product.name: 81LK
dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming
dmi.product.version: IdeaPad L340-15IRH Gaming
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug 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/1868149

Title:
  When booting with intel graphics (enabled through prime-select), the
  computer freezes rigth after selecting 'Kubuntu' in GRUB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After booting with Intel graphics enabled, the Kubuntu initial screen 
appears, then the Lenovo screen.
  After about 5-7 minutes in the Lenovo screen, it shows the following message 
(https://imgur.com/a/NO8O1qL), which adds a new one after increments of 2 
minutes, .

  When changing to the patch '18', the computer functions normally,
  allowing me to change to the NVIDIA graphics and that's where I'm able
  to boot to my normal setup, in patch '42'. The same happens in patch
  '40' by the way.

  The strange part is, a few days ago everything worked out fine. This first 
happened when I changed from NVIDIA to Intel (through prime-select, as usual), 
and instead of restarting the PC through the button in the UI, I used the 
'reboot' command in the terminal. 
  I have also previously noticed that restarting my computer by the command is 
slower when comparing to clicking the button.

  Thanks in advance for any help!

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simao  1614 F pulseaudio
   /dev/snd/controlC0:  simao  1614 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Mar 19 18:02:27 2020
  

[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Tags removed: block-proposed-focal

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 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
+ phase: Ready for Promote to Release
+ phase-changed: Thursday, 19. March 2020 17:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy
  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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
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: Ready for Promote to Release
  phase-changed: Thursday, 19. March 2020 17:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
  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 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker

[Seth Forshee]

** Tags added: regression-testing-passed

-- 
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:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
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: Ready for Promote to Release
  phase-changed: Thursday, 19. March 2020 17:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
  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 1868134] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1868134

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

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

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

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

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

Title:
  Headphones Audio Out Not Delivering Sound

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  DELL M5510

  ~ $ cat /proc/asound/cards
   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xddc28000 irq 128

  4.15.0-91
  Exhibits no sound via headphones

  4.15.0-88
  No issue with sound via headphones

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  

  *** Problem in linux-image-4.15.0-88-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue... ^C

  ~ $ cat /proc/version_signature > version.log
  ~ $ sudo lspci -vnvn > lspci-vnvn.log
  [sudo] password:   
  ~ $ 

  Not sure why the above commands are not creating the required info.

  Thanks

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

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

[Kernel-packages] [Bug 1868134] Re: Headphones Audio Out Not Delivering Sound

[timoto]

~ $ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family 
HD Audio Controller (rev 31)

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

Title:
  Headphones Audio Out Not Delivering Sound

Status in linux package in Ubuntu:
  New

Bug description:
  DELL M5510

  ~ $ cat /proc/asound/cards
   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xddc28000 irq 128

  4.15.0-91
  Exhibits no sound via headphones

  4.15.0-88
  No issue with sound via headphones

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  

  *** Problem in linux-image-4.15.0-88-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue... ^C

  ~ $ cat /proc/version_signature > version.log
  ~ $ sudo lspci -vnvn > lspci-vnvn.log
  [sudo] password:   
  ~ $ 

  Not sure why the above commands are not creating the required info.

  Thanks

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

-- 
Mailing list: https://launchpad.net/~kernel-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]

Now running on 5.3.0-42 and the brightness controls are working!

(Mute and Indicator Lights still don't)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1868134] [NEW] Headphones Audio Out Not Delivering Sound

[timoto]

Public bug reported:

DELL M5510

~ $ cat /proc/asound/cards
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xddc28000 irq 128

4.15.0-91
Exhibits no sound via headphones

4.15.0-88
No issue with sound via headphones

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.


*** Problem in linux-image-4.15.0-88-generic

The problem cannot be reported:

This is not an official Linux package. Please remove any third party
package and try again.

Press any key to continue... ^C

~ $ cat /proc/version_signature > version.log
~ $ sudo lspci -vnvn > lspci-vnvn.log
[sudo] password:   
~ $ 

Not sure why the above commands are not creating the required info.

Thanks

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


** Tags: audio

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

Title:
  Headphones Audio Out Not Delivering Sound

Status in linux package in Ubuntu:
  New

Bug description:
  DELL M5510

  ~ $ cat /proc/asound/cards
   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xddc28000 irq 128

  4.15.0-91
  Exhibits no sound via headphones

  4.15.0-88
  No issue with sound via headphones

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  

  *** Problem in linux-image-4.15.0-88-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue... ^C

  ~ $ cat /proc/version_signature > version.log
  ~ $ sudo lspci -vnvn > lspci-vnvn.log
  [sudo] password:   
  ~ $ 

  Not sure why the above commands are not creating the required info.

  Thanks

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

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

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Colin Ian King]

Can you update the bug with the output from the command:

cat /proc/cmdline

I wonder if an overly pessimistic rootdelay setting is being used.

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

Title:
  multiple long delays during kernel and userspace boot

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

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
  Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
  Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
  Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s.
  Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s.
  Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1027-azure 5.0.0-1027.29~18.04.1
  ProcVersionSignature: User Name 5.0.0-1027.29~18.04.1-azure 5.0.21
  Uname: Linux 5.0.0-1027-azure x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
 

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

[Akkana Peck]

> Please add "options snd-hda-intel dmic_detect=0" in the
/etc/modprobe.d/alsa-base.conf, then the legacy hda driver will work as
before.

That workaround doesn't work on my Lenovo Carbon X1 gen7. It does let
pavucontrol see the audio card again, but no adjustment in pavucontrol,
alsamixergui or amixer actually results in audible sounds. Sound worked
before my last dist-upgrade.

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

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

[Jeremy Soller]

By the way, this issue still exists on 5.3.0 kernels -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863769

-- 
You 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 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x

[Frank Heimes]

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

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

Title:
  Remove linux-firmware dependency from kernel meta packages for s390x

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  As far as we understand all firmware upgrades (and the firmware itself) is 
coming from the HMC on case of IBM Z and LinuxONE.
  This not only incl. the CEC code, but also all the firmware for the different 
cards and adapters.
  If this is the case (and will be in future), it would make sense for us to 
get rid of the linux-firmware package for s390x - this would make things 
leaner, reduce size and eventually increase (installation) performance ...

  So please IBM can you confirm that all firmware updates (MCLs) are
  always done via the HMC and that is therefore the linux-firmware
  package is obsolete on s390x? Thx

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

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

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  apic test in kvm-unit-test failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions

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

[Kernel-packages] [Bug 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  openat03 in ubuntu_ltp_syscall failed with Trusty

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  <<>>
  tag=openat03 stime=1533289807
  cmdline="openat03"
  contacts=""
  analysis=exit
  <<>>
  openat030  TINFO  :  creating a file with O_TMPFILE flag
  incrementing stop
  openat030  TINFO  :  writing data to the file
  openat030  TINFO  :  file size is '4096'
  openat030  TINFO  :  looking for the file in '.'
  openat030  TINFO  :  file not found, OK
  openat030  TINFO  :  renaming '/tmp/ltp-5saSOZV2Gx/opea7u155/#286254 
(deleted)' -> 'tmpfile'
  openat030  TINFO  :  found a file: tmpfile
  openat031  TPASS  :  single file tests passed
  openat030  TINFO  :  create files in multiple directories
  openat030  TINFO  :  removing test directories
  openat030  TINFO  :  writing/reading temporary files
  openat030  TINFO  :  closing temporary files
  openat032  TPASS  :  multiple files tests passed
  openat030  TINFO  :  create multiple directories, link files into them
  openat030  TINFO  :  and check file permissions
  openat033  TFAIL  :  openat03.c:223: file mode read 0, but expected 
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-153-generic 3.13.0-153.203
  ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  3 07:50 seq
   crw-rw 1 root audio 116, 33 Aug  3 07:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Aug  3 09:49:41 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-153-generic N/A
   linux-backports-modules-3.13.0-153-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1785207/+subscriptions

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

[Kernel-packages] [Bug 1821905] Re: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

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

Bug description:
  This umip test failed on T-3.13 and T-4.4
  On X-4.4 this was skipped:
  SKIP umip (qemu-system-x86_64: CPU feature umip not found)

  So it looks like a qemu issue to me.

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu 
qemu64,+umip
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 
1 -cpu qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg
  CPU feature umip not found
  enabling apic
  UMIP=0, CPL=0
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  UMIP=0, CPL=3
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  PASS: exception from mov %cr0, %eax
  UMIP not available
  SUMMARY: 11 tests

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:10:13 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821905/+subscriptions

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

[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  Commit 92183a42898d ("fsnotify: fix ignore mask logic in
  send_to_group()") acknowledges the use case of ignoring an event on
  an inode mark, because of an ignore mask on a mount mark of the same
  group (i.e. I want to get all events on this file, except for the events
  that came from that mount).

  This change depends on correctly merging the inode marks and mount marks
  group lists, so that the mount mark ignore mask would be tested in
  send_to_group(). Alas, the merging of the lists did not take into
  account the case where event in question is not in the mask of any of
  the mount marks.

  To fix this, completely remove the tests for inode and mount event masks
  from the lists merging code.

  == Fix ==
  9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())

  Test kernels for Bionic can be found here:
  http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/

  It seems that T/X poses with the same issue and we might be able to backport
  it with the same logic, but I think we should target Bionic as it's a fix for
  for 92183a42898d which was only applied to Bionic.

  == Regression Potential ==
  Low.

  The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
  which generalizes the iteration of marks for inode_mark and vfsmount_mark, 
from:
  iter_info.inode_mark
  to:
  iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]

  But the patch can still be backported with the same logic without this
  commit.

  The test with the syscalls test in LTP test suite shows no sign of
  regression.

  == Test Case ==
  Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
  with the patched kernel.

  Full LTP syscalls test with 4.15.0-42 in -proposed:
  http://paste.ubuntu.com/p/Wm8nQ932g6/

  Full LTP syscalls test with patched 4.15.0-42:
  http://paste.ubuntu.com/p/nv4jW6shpJ/

  -

  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
  mke2fs 1.44.1 (24-Mar-2018)
  tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
  fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore 

[Kernel-packages] [Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This test has failed on:
   * T-3.13:
  - FAIL debug (11 tests, 6 unexpected failures)
   * T-4.4 / X-4.4:
  - FAIL debug (11 tests, 1 unexpected failures)

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=debug TIMEOUT=90s ACCEL= ./x86/run x86/debug.flat -smp 1
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/debug.flat 
-smp 1 # -initrd /tmp/tmp.WOQmQkB7bo
  enabling apic
  PASS: #BP
  PASS: hw breakpoint (test that dr6.BS is not set)
  PASS: hw breakpoint (test that dr6.BS is not cleared)
  PASS: single step
  FAIL: single step emulated instructions
  PASS: hw watchpoint (test that dr6.BS is not cleared)
  PASS: hw watchpoint (test that dr6.BS is not set)
  PASS: icebp
  PASS: MOV SS + watchpoint + ICEBP
  PASS: MOV SS + watchpoint + int $1
  PASS: MOV SS + watchpoint + INT3
  SUMMARY: 11 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:15:05 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821906/+subscriptions

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

[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  fanotify06 from ubuntu_ltp_syscalls failed

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

Bug description:
  == SRU Justification ==
  fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for
  overlayfs has received more than one expected event:
<<>>
tag=fanotify06 stime=1560747299
cmdline="fanotify06"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
mke2fs 1.44.6 (5-Mar-2019)
tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15

fanotify06.c:230: PASS: group 8 got no event
fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
fanotify06.c:220: FAIL: group 3 got event
fanotify06.c:220: FAIL: group 4 got event
fanotify06.c:220: FAIL: group 5 got event
fanotify06.c:220: FAIL: group 6 got event
fanotify06.c:220: FAIL: group 7 got event
fanotify06.c:220: FAIL: group 8 got event

Summary:
passed 9
failed 9
skipped 0
warnings 0

  This duplicated event was generated with operations on files with
  "fake" path.

  == Fix ==
  * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path)

  This patch can be cherry-picked into Disco.

  Older kernels are not affected by this issue (without commit d1d04ef8)

  == Test ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/

  Verified on a KVM node, the fanotify06 test will pass with this patched
  disco kernel:
   fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
   fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30
   fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30
   fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30
   fanotify06.c:230: PASS: group 3 got no event
   fanotify06.c:230: PASS: group 4 got no event
   fanotify06.c:230: PASS: group 5 got no event
   fanotify06.c:230: PASS: group 6 got no event
   fanotify06.c:230: PASS: group 7 got no event
   fanotify06.c:230: PASS: group 8 got no event

  == Regression Potential ==
  Low, fix limited to the overlayfs and just corrects the flag behaviour
  with "fake" path.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
   crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:

  Date: Mon Jun 17 04:40:18 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1866041] Re: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim
  resulted in ALLOW on 4.4 / 4.15 non-amd64

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

Bug description:
  The following failures:
  Test 53-sim-binary_tree%%034-1 result: FAILURE bpf_sim resulted in ALLOW
  Test 53-sim-binary_tree%%035-1 result: FAILURE bpf_sim resulted in ALLOW
  Test 53-sim-binary_tree%%036-1 result: FAILURE bpf_sim resulted in ALLOW

  Can be found on:
  4.15.0-92.93 - PoewrPC / s390x / i386
  4.4.0-177 - PoewrPC / s390x / i386

  Please find the complete test log with 4.4.0-177 in the attachment of
  comment 5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1
  ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Wed Mar  4 10:32:46 2020
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions

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

[Kernel-packages] [Bug 1854298] Re: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in
  upstream testsuite

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  A bisect shows this test is failing since commit 2104e51db38 (Simplify
  initialization of __upper)

  The test will fail with:
***
*** ./run --ov --ts=0 rmtree
***
TEST rmtree.py:4: Recursive remove populated lower dir with lower files
- rmtree /mnt/a/dir100
***
*** ./run --ov --ts=0 rmtree-new
***
TEST rmtree-new.py:4: Recursive remove populated lower dir with new subdir
 ./run --mkdir /mnt/a/dir100/b 0755
- rmtree /mnt/a/dir100
***
*** ./run --ov --ts=0 hard-link
***
TEST hard-link.py:10: Hard link file
 ./run --link /mnt/a/foo100 /mnt/a/no_foo100
stderr:
/mnt/a/foo100: File unexpectedly on upper layer

  
  For the complete test log, please refer the attachment.

  HEAD now is 1724ef2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-169-generic 4.4.0-169.198
  ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197
  Uname: Linux 4.4.0-169-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Thu Nov 28 04:21:52 2019
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

[Po-Hsu Lin]

Time out on T-4.4, with a slightly different error:
 BUILD_HEAD=4671e4ba
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.1jzuZsx4Jy -smp 1 
-cpu host,+vmx -append -exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test -vmx_controls_test -vmx_host_state_area_test -vmx_nm_test 
-vmx_nmi_window_test -vmx_intr_window_test -vmx_pending_event_test # -initrd 
/tmp/tmp.1FbpAwN033
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20
 PASS: test vmxon with FEATURE_CONTROL cleared
 PASS: test vmxon without FEATURE_CONTROL lock
 PASS: test enable VMX in FEATURE_CONTROL
 PASS: test FEATURE_CONTROL lock bit
 PASS: test vmxon with unaligned vmxon region
 PASS: test vmxon with bits set beyond physical address width
 PASS: test vmxon with invalid revision identifier
 PASS: test vmxon with valid vmxon region
 PASS: test vmptrld with unaligned vmcs
 PASS: test vmptrld with vmcs address bits set beyond physical address width
 PASS: test vmptrld with vmxon region
 FAIL: test vmptrld with vmxon region vm-instruction error
 PASS: test vmptrld with valid vmcs region
 PASS: test vmclear with unaligned vmcs
 PASS: test vmclear with vmcs address bits set beyond physical address width
 PASS: test vmclear with vmxon region
 PASS: test vmclear with valid vmcs region
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (current VMCS)
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (!current VMCS)
 PASS: test vmptrst
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: VMWRITE/VMREAD
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET_HI
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET_HI
 VMCLEAR VMCS0
 VMPTRLD VMCS0
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: current:VMCS0 active:[VMCS0]
 VMCLEAR VMCS0
 VMPTRLD VMCS0
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: current:VMCS0 active:[VMCS0]
 VMCLEAR VMCS1
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: current:VMCS0 active:[VMCS0]
 VMPTRLD VMCS1
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a

[Kernel-packages] [Bug 1867656] Re: The need for the linux-firmware package on s390x

[Seth Forshee]

** Package changed: linux-firmware (Ubuntu) => linux-meta (Ubuntu)

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

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

** Summary changed:

- The need for the linux-firmware package on s390x
+ Remove linux-firmware dependency from kernel meta packages for s390x

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

Title:
  Remove linux-firmware dependency from kernel meta packages for s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  As far as we understand all firmware upgrades (and the firmware itself) is 
coming from the HMC on case of IBM Z and LinuxONE.
  This not only incl. the CEC code, but also all the firmware for the different 
cards and adapters.
  If this is the case (and will be in future), it would make sense for us to 
get rid of the linux-firmware package for s390x - this would make things 
leaner, reduce size and eventually increase (installation) performance ...

  So please IBM can you confirm that all firmware updates (MCLs) are
  always done via the HMC and that is therefore the linux-firmware
  package is obsolete on s390x? Thx

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

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

[Kernel-packages] [Bug 1749427] Re: Unable to create KVM with uvtool on arm64 system

[Po-Hsu Lin]

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  Unable to create KVM with uvtool on arm64 system

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

Bug description:
  Not sure if this is related to bug 1452016, or just a HW issue:

  With the uvt-kvm create command on this Artful system, it returns:
  uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  
  With the same command running on a Xenail system + Artful kernel, it returns:
  qemu-system-aarch64: Cirrus VGA not available

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 14 11:01 seq
   crw-rw 1 root audio 116, 33 Feb 14 11:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: arm64
  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:
  CurrentDmesg:

  Date: Wed Feb 14 11:09:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1749427/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

[Gabriel Miranda]

I installed kernel 5.3.0-050300 and sound and microphone works fine:

Linux G3-3590 5.3.0-050300-generic #201909152230 SMP Sun Sep 15 22:32:54
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I'm using Ubuntu 18.04.04 on Dell G3 3590-A20P.

-- 
You 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 1827428] Re: Mouse cursor left frozen copy of itself

[Dane Elwell]

I am also having this issue on Fedora 31, Gnome 3.34.4 with a Radeon RX
590 using amdgpu on Wayland.

Video attached. Unsure how to replicate other than after locking.

(I appreciate this is an Ubuntu bug tracker, but it's the same issue.)

** Attachment added: "stuckcursor.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+attachment/5338885/+files/stuckcursor.mp4

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

Title:
  Mouse cursor left frozen copy of itself

Status in mutter package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[MARTIN]

** Description changed:

  Good morning.
  
  Many months I use "suspend"
  (settings->energy->When the shutdown button...) on Ubuntu 18.04 or 19.10.
  
  At each wake up, the USB ports 3.1 Gen 1 of motherboard back panel don't
  work (USB flash drive, webcam, keyboard).
  
  No problems with USB ports 2.0/1.1 of motherboard back panel.
  No problems with USB ports 3.1 Gen 1 / 2.0/1.1 of front panel (from internal 
USB header).
  
  I think my motherboard is not at fault because I did not reproduce this
  bug on Windows 10.
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.
  
   enp6s0no wireless extensions.
- MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
+ MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)
+ 
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:
  
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

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

  At each wake up, the USB ports 3.1 Gen 1 of motherboard back panel
  don't work (USB flash drive, webcam, keyboard).

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

  I think my motherboard is not at fault because I did not reproduce
  this bug on Windows 10.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)

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

  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

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

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4

[Heinz-Werner Seeck]

** Summary changed:

- [Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros
+ [Ubuntu 20.04]  Striding RQ as Default for ConnectX-4

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

Title:
  [Ubuntu 20.04]  Striding RQ as Default for ConnectX-4

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

Bug description:
  ello,
  Within our Network Performance runs in the RoCE Express 2(.1) area, we 
noticed a performance regression with streaming workloads which could be 
mitigated by using an ethtool setting.
   
  The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
  commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
  Author: Tariq Toukan 
  Date:   Tue Feb 20 15:17:54 2018 +0200
  net/mlx5e: RX, Always prefer Linear SKB configuration
  Prefer the linear SKB configuration of Legacy RQ over the
  non-linear one of Striding RQ.
  This implies that ConnectX-4 LX now uses legacy RQ by default,
  as it does not support the linear configuration of Striding RQ.
  Signed-off-by: Tariq Toukan 
  Signed-off-by: Saeed Mahameed 
   
  diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  index 2c634e50d051..333d4ed52b94 100644
  --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
  MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
  /* RQ */
  -   if (mlx5e_striding_rq_possible(mdev, params))
  -   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
  -   !slow_pci_heuristic(mdev));
  +   /* Prefer Striding RQ, unless any of the following holds:
  +* - Striding RQ configuration is not possible/supported.
  +* - Slow PCI heuristic.
  +* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
  +*/
  +   if (!slow_pci_heuristic(mdev) &&
  +   mlx5e_striding_rq_possible(mdev, params) &&
  +   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
  +!mlx5e_rx_is_linear_skb(mdev, params)))
  +   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
  mlx5e_set_rq_type(mdev, params);
  mlx5e_init_rq_type_params(mdev, params);
   
  We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
   
  Kernel used: 5.4.0-rc7
  The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
   
  Example throughput drop:
  (traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
  --
  Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
  --
  |  rr1c-200x30k--10   |15.10Gb/s|   20.77Gb/s|
  --

  As concluded in the communication with Mellanox, there is a possibility to 
use a simple ethtool command to switch between the queuing methods, allowing us 
to avoid kernel code changes:
  ethtool --set-priv-flags DEVNAME rx_striding_rq on
  (To list the available settings you may use: ethtool --show-priv-flags 
DEVNAME)

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

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

[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4

[Frank Heimes]

Not sure if I understand that ticket correctly - which 5.4-rc7 was used?
Was is directly from upstream?
And why is still a RC kernel in use - 5.4 is released since quite some time?

Well, if only commit "net/mlx5e: RX, Always prefer Linear SKB
configuration" is needed, then we are done, since it's already in the
Ubuntu focal kernel since quite some time:

focal-clean$ git log --oneline --grep "net/mlx5e: RX, Always prefer Linear SKB 
configuration"
5ffd81943d7a net/mlx5e: RX, Always prefer Linear SKB configuration
focal-clean$ git tag --contains 5ffd81943d7a
Ubuntu-5.4-5.4.0-10.13
Ubuntu-5.4-5.4.0-11.14
Ubuntu-5.4-5.4.0-12.15
Ubuntu-5.4-5.4.0-13.16
Ubuntu-5.4-5.4.0-14.17
Ubuntu-5.4.0-15.18
Ubuntu-5.4.0-16.19
Ubuntu-5.4.0-17.20
Ubuntu-5.4.0-17.21
Ubuntu-5.4.0-18.22
Ubuntu-5.4.0-8.11
Ubuntu-5.4.0-9.12

Looks to me that you can simply move to the current Ubuntu focal kernel
(ideally the one from proposed) and proceed with testing from there ...

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

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

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

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

Title:
  [Ubuntu 20.04]  Striding RQ as Default for ConnectX-4

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

Bug description:
  ello,
  Within our Network Performance runs in the RoCE Express 2(.1) area, we 
noticed a performance regression with streaming workloads which could be 
mitigated by using an ethtool setting.
   
  The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
  commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
  Author: Tariq Toukan 
  Date:   Tue Feb 20 15:17:54 2018 +0200
  net/mlx5e: RX, Always prefer Linear SKB configuration
  Prefer the linear SKB configuration of Legacy RQ over the
  non-linear one of Striding RQ.
  This implies that ConnectX-4 LX now uses legacy RQ by default,
  as it does not support the linear configuration of Striding RQ.
  Signed-off-by: Tariq Toukan 
  Signed-off-by: Saeed Mahameed 
   
  diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  index 2c634e50d051..333d4ed52b94 100644
  --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
  MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
  /* RQ */
  -   if (mlx5e_striding_rq_possible(mdev, params))
  -   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
  -   !slow_pci_heuristic(mdev));
  +   /* Prefer Striding RQ, unless any of the following holds:
  +* - Striding RQ configuration is not possible/supported.
  +* - Slow PCI heuristic.
  +* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
  +*/
  +   if (!slow_pci_heuristic(mdev) &&
  +   mlx5e_striding_rq_possible(mdev, params) &&
  +   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
  +!mlx5e_rx_is_linear_skb(mdev, params)))
  +   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
  mlx5e_set_rq_type(mdev, params);
  mlx5e_init_rq_type_params(mdev, params);
   
  We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
   
  Kernel used: 5.4.0-rc7
  The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
   
  Example throughput drop:
  (traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
  --
  Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
  --
  | |Legacy RQ|  Striding RQ   |
  --
  |  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
  --
  |  rr1c-200x30k--10   |

[Kernel-packages] [Bug 1513500] Re: In Ubuntu 15.10, the vmlinuz-4.2.0-17-generic will not take password on splash screen

[Po-Hsu Lin]

15.10 EOL, please feel free to open a new bug if you're still affected
by this.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  In Ubuntu 15.10, the vmlinuz-4.2.0-17-generic will not take password
  on splash screen

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I version-upgraded Ubuntu 15.04  in place to Ubuntu 15.10 on an HP 
workstation with a Intel Core i7 and 16GB RAM.  The HDD was previously in a 
different computer, and I have seen issues with the settings from the old 
machine fighting with the settings for current OS version.  The behaviour is as 
follows:
  When I log in with the 4.2.x kernel, the machine changes to a blank screen 
pauses for a moment and returns me to the login splash screen.
  I can log in normally if I use the 3.19.0-32-generic kernel.
  I can also change to TTY1 and log in at the command line with the 4.2.x 
kernel.

  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 15GiB
   *-cpu
product: Intel(R) Core(TM) i7 CPU 950  @ 3.07GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
size: 2133MHz
capacity: 3068MHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 
ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi 
flexpriority ept vpid cpufreq
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  professor   2070 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=6b0f4376-1add-4720-a293-e4eddd70e708
  InstallationDate: Installed on 2015-08-16 (81 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HPE-580t
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=ad00935f-4286-4e34-9e09-54594751abed ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-32.37-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-28 (8 days ago)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev pulse pulse-access 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: N/A
  dmi.board.name: 2A86
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.04E01
  dmi.chassis.asset.tag: 2MD1070H7V
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.10:bd09/16/2010:svnHewlett-Packard:pnHPE-580t:pvr:rvnPEGATRONCORPORATION:rn2A86:rvr1.04E01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: HPE-580t
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Gabriel Miranda]

I have the same issue using notebook Dell G3-3590-A20P, my sound and
microphone was gone when updated to Kernel 5.3.0-42.

Hos to upgrade to Linux Kernel 5.3.0-43?

-- 
You 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 1868113] [NEW] [Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros

[bugproxy]

Public bug reported:

ello,
Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed 
a performance regression with streaming workloads which could be mitigated by 
using an ethtool setting.
 
The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
Author: Tariq Toukan 
Date:   Tue Feb 20 15:17:54 2018 +0200
net/mlx5e: RX, Always prefer Linear SKB configuration
Prefer the linear SKB configuration of Legacy RQ over the
non-linear one of Striding RQ.
This implies that ConnectX-4 LX now uses legacy RQ by default,
as it does not support the linear configuration of Striding RQ.
Signed-off-by: Tariq Toukan 
Signed-off-by: Saeed Mahameed 
 
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
index 2c634e50d051..333d4ed52b94 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
@@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
/* RQ */
-   if (mlx5e_striding_rq_possible(mdev, params))
-   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
-   !slow_pci_heuristic(mdev));
+   /* Prefer Striding RQ, unless any of the following holds:
+* - Striding RQ configuration is not possible/supported.
+* - Slow PCI heuristic.
+* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
+*/
+   if (!slow_pci_heuristic(mdev) &&
+   mlx5e_striding_rq_possible(mdev, params) &&
+   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
+!mlx5e_rx_is_linear_skb(mdev, params)))
+   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
mlx5e_set_rq_type(mdev, params);
mlx5e_init_rq_type_params(mdev, params);
 
We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
 
Kernel used: 5.4.0-rc7
The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
 
Example throughput drop:
(traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
--
| |Legacy RQ|  Striding RQ   |
--
|str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
--
Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
--
| |Legacy RQ|  Striding RQ   |
--
|  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
--
|  rr1c-200x30k--10   |15.10Gb/s|   20.77Gb/s|
--

As concluded in the communication with Mellanox, there is a possibility to use 
a simple ethtool command to switch between the queuing methods, allowing us to 
avoid kernel code changes:
ethtool --set-priv-flags DEVNAME rx_striding_rq on
(To list the available settings you may use: ethtool --show-priv-flags DEVNAME)

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


** Tags: architecture-s39064 bugnameltc-184497 severity-medium 
targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-184497 severity-medium
targetmilestone-inin2004

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

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

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

Title:
  [Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros

Status in linux package in Ubuntu:
  New

Bug description:
  ello,
  Within our Network Performance runs in the RoCE Express 2(.1) area, we 
noticed a performance regression with streaming workloads which could be 
mitigated by using an ethtool setting.
   
  The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
  commit 5ffd81943d7a57423f204cd5844bf430b5634472 

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Vincenzo Conti]

Still present in Ubuntu 20.04

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1868113] [NEW] [Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

ello,
Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed 
a performance regression with streaming workloads which could be mitigated by 
using an ethtool setting.
 
The Commit which switched the default value from "Striding RQ" to "Legacy RQ" 
for ConnectX-4 devices (RoCE Express 2(.1)) is attached here:
commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad)
Author: Tariq Toukan 
Date:   Tue Feb 20 15:17:54 2018 +0200
net/mlx5e: RX, Always prefer Linear SKB configuration
Prefer the linear SKB configuration of Legacy RQ over the
non-linear one of Striding RQ.
This implies that ConnectX-4 LX now uses legacy RQ by default,
as it does not support the linear configuration of Striding RQ.
Signed-off-by: Tariq Toukan 
Signed-off-by: Saeed Mahameed 
 
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
index 2c634e50d051..333d4ed52b94 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
@@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, 
params->rx_cqe_compress_def);
/* RQ */
-   if (mlx5e_striding_rq_possible(mdev, params))
-   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ,
-   !slow_pci_heuristic(mdev));
+   /* Prefer Striding RQ, unless any of the following holds:
+* - Striding RQ configuration is not possible/supported.
+* - Slow PCI heuristic.
+* - Legacy RQ would use linear SKB while Striding RQ would use 
non-linear.
+*/
+   if (!slow_pci_heuristic(mdev) &&
+   mlx5e_striding_rq_possible(mdev, params) &&
+   (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) ||
+!mlx5e_rx_is_linear_skb(mdev, params)))
+   MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true);
mlx5e_set_rq_type(mdev, params);
mlx5e_init_rq_type_params(mdev, params);
 
We have modified the upstream-kernel to allow us running of measurements and 
compare differences between Legacy RQ vs Striding RQ. Here is an example below: 
 
Kernel used: 5.4.0-rc7
The measurements run on a dedicated machine (z14) using uperf with streaming 
profiles (MTU size 1500).
 
Example throughput drop:
(traffic via a shared card, i.e. client and server using VFs from the same 
ConnectX-4)
--
| |Legacy RQ|  Striding RQ   |
--
|str-writex30k (1 connection) |24.62Gb/s|   33.47Gb/s|
--
Additionaly, two tests with transactional workload using the ethtool proposed 
switch: 
--
| |Legacy RQ|  Striding RQ   |
--
|  rr1c-200x30k---1   | 4.12Gb/s|5.66Gb/s|
--
|  rr1c-200x30k--10   |15.10Gb/s|   20.77Gb/s|
--

As concluded in the communication with Mellanox, there is a possibility to use 
a simple ethtool command to switch between the queuing methods, allowing us to 
avoid kernel code changes:
ethtool --set-priv-flags DEVNAME rx_striding_rq on
(To list the available settings you may use: ethtool --show-priv-flags DEVNAME)

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


** Tags: architecture-s39064 bugnameltc-184497 severity-medium 
targetmilestone-inin2004
-- 
[Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros
https://bugs.launchpad.net/bugs/1868113
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1798061] Re: open14 in ubuntu_ltp_syscalls failed with T (Power8)

[Po-Hsu Lin]

As we're not supporting P8 on Trusty ESM anymore, I will close this bug.

** Changed in: ubuntu-kernel-tests
   Status: New => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  open14 in ubuntu_ltp_syscalls failed with T (Power8)

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  This issue can only be reproduced on Power8 node:

  <<>>
  tag=open14 stime=1539683773
  cmdline="open14"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  open14  1  TBROK  :  open14.c:58: open() failed: errno=EINVAL(22): 
Invalid argument
  open14  2  TBROK  :  open14.c:58: Remaining cases broken
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic ppc64le
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CurrentDmesg:
   [   75.881756] tg3 0003:05:00.0 enP3p5s0f0: Link is up at 1000 Mbps, full 
duplex
   [   75.881762] tg3 0003:05:00.0 enP3p5s0f0: Flow control is off for TX and 
off for RX
   [   75.881765] tg3 0003:05:00.0 enP3p5s0f0: EEE is disabled
   [   75.881788] IPv6: ADDRCONF(NETDEV_CHANGE): enP3p5s0f0: link becomes ready
   [  656.832585] LTP: starting open14
  Date: Tue Oct 16 09:56:22 2018
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.08 0.07 0.08 1/1034 3981
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3027 00:11:28789 0 EOF
   2: POSIX  ADVISORY  WRITE 3146 00:11:90135 0 EOF
   3: POSIX  ADVISORY  WRITE 3176 00:11:95241 0 EOF
   4: FLOCK  ADVISORY  WRITE 3093 00:11:89096 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.13.0-160-generic (buildd@bos02-ppc64el-007) (gcc 
version 4.8.4 (User Name 4.8.4-2ubuntu1~14.04.4) ) #210-User Name SMP Mon Sep 
24 18:06:36 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798061/+subscriptions

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

[Kernel-packages] [Bug 1867656] Re: The need for the linux-firmware package on s390x

[Dimitri John Ledkov]

I think we will continue to build/ship linux-firmware package in the
archive for s390x.

However, I think we want to drop the dependencies from src:linux-meta on
s390x such that linux-firmware is not pulled-in or installed by default.

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

Title:
  The need for the linux-firmware package on s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  As far as we understand all firmware upgrades (and the firmware itself) is 
coming from the HMC on case of IBM Z and LinuxONE.
  This not only incl. the CEC code, but also all the firmware for the different 
cards and adapters.
  If this is the case (and will be in future), it would make sense for us to 
get rid of the linux-firmware package for s390x - this would make things 
leaner, reduce size and eventually increase (installation) performance ...

  So please IBM can you confirm that all firmware updates (MCLs) are
  always done via the HMC and that is therefore the linux-firmware
  package is obsolete on s390x? Thx

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

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

[Kernel-packages] [Bug 1684776] Re: ubuntu_qrt_kernel_security test_050_personality failed on arm64 Trusty / X-hwe kernel

[Po-Hsu Lin]

As we're not testing ARM64 on Trusty ESM anymore, I will close this.

Please feel free to re-open this if think this is not correct.

** Changed in: qa-regression-testing
 Assignee: Connor Kuehl (connork) => (unassigned)

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: qa-regression-testing
   Status: In Progress => Invalid

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

Title:
  ubuntu_qrt_kernel_security test_050_personality failed on arm64 Trusty
  / X-hwe kernel

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  With 4.4.0-74.95~14.04.1 kernel, this test case failed on arm64 node.

  
  (This issue was reported in bug 163 as well, in this cycle, only 050, 060 
failed on this kernel)

  ==
  FAIL: test_050_personality (__main__.KernelSecurityTest)
  init missing READ_IMPLIES_EXEC
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 398, in test_050_personality
  self.assertEqual(output, expected, "/proc/1/personality contains %s (expected 
%s)" % (output, expected))
  AssertionError: /proc/1/personality contains 0040 (expected )

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1684776/+subscriptions

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

[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04

[Gabriel Miranda]

So here is an update. I did some tests with Linux Kernel 4.19 and 5.0 on
Ubuntu 18.04.04 and sound works fine but the microphone was not.

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

Title:
  Failed to init Intel sound card in 20.04

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  After installing current 20.04 release on ThinkBook 13s IML with Intel
  audio card there is no sound available because sound card not detected
  (only dummy output available in sound settings):

  $ alsamixer 
  cannot open mixer: No such file or directory

  $ lspci -nnk |grep -A2 audio
  lspci: Unable to load libkmod resources: error -12
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]
Subsystem: Lenovo Device [17aa:3816]
Kernel driver in use: sof-audio-pci
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
Subsystem: Lenovo Device [17aa:3819]

  $ pacmd list-cards 
  0 card(s) available.

  $ dmesg |grep sof
  [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB)
  [2.142149] systemd[1]: Mounting Mount unit for software-boutique, 
revision 54...
  [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 
54.
  [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine 
driver found
  [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode
  [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5
  [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cnl.ri failed with error -2
  [2.817054] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cnl.ri failed err: -2
  [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2

  I've found similar bug reported here:
  https://bugs.archlinux.org/task/64720

  As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot
  options and after that sound card successfully detected and started
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb 26 19:22:05 2020
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200221)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CQCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 13s-IML
  dmi.modalias: 
dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML:
  dmi.product.family: ThinkBook 13s-IML
  dmi.product.name: 20RR
  dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML
  dmi.product.version: Lenovo ThinkBook 13s-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04

[Gabriel Miranda]

I have the same problem here. My laptop is Dell G3-3590-A20P which have
2 audio cards:

00:1f.3 Multimedia audio controller: Intel Corporation Cannon Lake PCH Cavs 
(rev 10)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)

When I start the system with the HDMI cable plugged, the system only
recognizes only the NVIDIA driver (screenshot attached). More
information about my distro:

Linux G3-3590 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28
13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic

I have dual-boot with Windows 10 and the sound works perfectly. Only
have issues in Ubuntu.

I have already tried many things to solve this but unsuccessfully. I
will try to downgrade the kernel version.

** Attachment added: "screenshot_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864871/+attachment/5338771/+files/screenshot_2.png

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

Title:
  Failed to init Intel sound card in 20.04

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  After installing current 20.04 release on ThinkBook 13s IML with Intel
  audio card there is no sound available because sound card not detected
  (only dummy output available in sound settings):

  $ alsamixer 
  cannot open mixer: No such file or directory

  $ lspci -nnk |grep -A2 audio
  lspci: Unable to load libkmod resources: error -12
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]
Subsystem: Lenovo Device [17aa:3816]
Kernel driver in use: sof-audio-pci
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
Subsystem: Lenovo Device [17aa:3819]

  $ pacmd list-cards 
  0 card(s) available.

  $ dmesg |grep sof
  [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB)
  [2.142149] systemd[1]: Mounting Mount unit for software-boutique, 
revision 54...
  [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 
54.
  [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine 
driver found
  [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode
  [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5
  [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cnl.ri failed with error -2
  [2.817054] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cnl.ri failed err: -2
  [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2

  I've found similar bug reported here:
  https://bugs.archlinux.org/task/64720

  As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot
  options and after that sound card successfully detected and started
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb 26 19:22:05 2020
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200221)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CQCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  

[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature

[Dimitri John Ledkov]

= Refactor =

 The refactor commits, correct minor runtime/compiler warnings or have
 no effect on the resulting build. I want to take them in, as
 bugfixes, to keep the Ubuntu source matching the upstream as closely
 as possible for future cherrypicks to not conflict.

  11bdab2 include/boot/s390.h: add guard for `struct __vector128`
  b06af60 README.md: remove useless empty line
  2c10642 cpumf_helper: Avoid perl warning from pod2usage function
  6fcf64e lib/util_file.h: fix typo in the macro guard
  87b54fc CHANGELOG: Fix formatting

= HW Enablement =

 This commits fall under HWE SRU exception, these expand cpumf tool to
 display z15 specific counters & correctly report/trace fiber channel
 endpoint security status.

 They do not change behaviour on any existing hardware z13/z14
 platforms. And improve behaviour on z15 hardware.

  1086548 cpumf: Add IBM z15 extended counter defintion file
  5d2871d cpumf/data: Add new deflate counters for IBM z15

  fbf8513 zfcpdbf: print HBA FC Endpoint Security trace records
  67496af zdev: Report FC Endpoint Security of zfcp devices
  16b2799 zdev: Handle special case in if-case
  c063273 zdev: Introduce read-only attributes

Bugfix

 These are pure bugfixes to improve the `dbginfo` debug information
 collection tool. Fix documentation for correct ways to enable/disable
 secureboot (also requested in a separate ticket). And a bugfix to
 correct potential buffer overflow in zipl-libc (i.e. common libc-like
 functions which are used by the bootloader standalone code).

  f742ed7 dbginfo: gather ethtool output for per-queue coalescing
  4fa9656 dbginfo: collect softnet_stat
  d415b8e dbginfo: Removed collection of /var/log/opencryptoki/
  
  299fd2b zipl: fix zipl.conf man page example for secure boot

  36fed0e zipl/libc: Indicate truncated lines in printf with '...'
  f743002 zipl/libc: Replace sprintf with snprintf
  8874b90 zipl/libc: Fix potential buffer overflow in printf
  6fe9e6c zipl/libc: Introduce vsnprintf

PVM feature

 These are the commits related to the new PVM feature. They consist of
 creating a new userspace tool (genprotimg) as well as creating new
 bootloader stages. To support building the new bootloader stages,
 existing zipl bootloader stages have been refactored a little bit to
 use common headers with defined constants (rather than just
 hardcoding them). At the same time, the zipl-libc code has been
 improve to be more strict with parsing / validating certain things.

 The new zipl bootloader stages are only used for th PVM
 feature. Despite the refactors, there does not appear to be any
 behaviour changes of the existing zipl boot stages as used on
 existing hardware configurations for regular zipl IPL. And regular
 boot testing will be performed as part of the Focal to validate LPAR,
 z/VM, KVM platforms with/without secureboot where applicable.

  65b9fc4 genprotimg: introduce new tool for the creation of PV images
  d2f8f97 genprotimg: add relocator for stage3b
  2d60057 genprotimg: boot: use C pre-processor for linker script generation
  3356d6f genprotimg: boot: initial bootloader support
  67aef9b Consolidate `ALIGN, __ALIGN_MASK, ARRAY_SIZE` macros
  e51663b zipl/libc: printf: print on linemode and ASCII console
  f99560f zipl/sclp: add `sclp_print_ascii`
  303a370 zipl/sclp: add macros for the control-program masks
  a37170b zipl: refactor all EBCDIC code into separate files
  305235a include/boot/s390.h: fixes for -Werror=sign-conversion
  2568863 include/boot/s390.h: move panic and panic_notify to libc.h
  b0f82d2 zipl/libc: include 's390.h'
  b83c894 zipl: move s390.h to include/boot/s390.h
  f454c68 zipl: remove libc.h include in s390.h
  c55ceab Consolidate MIN and MAX macros
  2e28291 zipl: make BLK_PWRT unsigned int
  24fe8c1 zipl: move __always_inline/barrier/__pa32/pa to zt_common.h
  67e76b8 zipl/s390.h: rename `inline` macro into `__always_inline`
  97ab8fb zipl: move loaders layout definitions into separate header
  c07104d zipl: use STAGE3_ENTRY for STAGE3_LOAD_ADDRESS
  c871050 zipl: tape0: use constants defined in linux_layout.h
  7e37a1d zipl: move Linux layout definitions into separate header
  d884fb8 zipl/stage3: make IPL_DEVICE definition consistent with tape0.S
  0e385a8 zipl: add SIGP_SET_ARCHITECTURE to sigp.h and use it
  675c854 zipl: move SIGP related functions and definitions into separate header
  9d39a4b zipl: move IPL related definitions into separate header
  400167f Support `lib/zt_common.h` to be used in assembler and add `_AC` macro
  cc16e41 zipl: use STATIC_ASSERT macro for no padding verification
  bac3f93 lib/zt_common: add STATIC_ASSERT macro
  9719709 zipl/boot: fix comment in stage3.lds


** Changed in: s390-tools (Ubuntu)
   Status: Incomplete => New

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

Title:
  [FFe] Please accept patches for secure guest feature

Status in 

[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel

[Seth Forshee]

@laney: Shouldn't udisks2 prefer in-kernel filesystem support if
available, then fallback to a fuse driver? We also have a fuseext2
package, but if I have that installed I would still expect an ext2
formatted thumb drive to be mounted using the kernel's driver when I
insert it rather than the fuse driver.

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

Title:
  Focal uses the exfat fuse filesystem even though there is support in
  the kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  When a storage device formatted with exfat is automatically mounted on
  a system it is mounted with a fuse filesystem instead of a native,
  kernel filesystem. The kernel now has support for exfat.

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

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

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

[Seth Forshee]

Yes, sorry, I was blocked from uploading new linux-firmware packages for
various reasons. All of the blocking issues are cleared up now, so I
will upload new packages today.

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

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

Status in linux-firmware package in Ubuntu:
  Confirmed

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

  [Fix]
  Revert the new firmware.

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

  === Original Bug Report ===

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

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

  Also it affects the boot time.

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Andy Whitcroft]

** This bug is no longer a duplicate of bug 1867859
   trusty/linux-azure: 4.15.0-1075.80~14.04.1 -proposed tracker

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Friday, 13. March 2020 17:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

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

[Kernel-packages] [Bug 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly

[cosine]

Confirmed on a T480.

I lose my trackpoint mouse after a failed hibernation attempt, and can
suspend to ram anymore.

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

Title:
  linux-5.4 regression: hibernate-disk resumes instantly

Status in hibernate package in Ubuntu:
  Confirmed
Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk
  fails to properly hibernate and shutdown the system; instead, Ubuntu
  resumes instantly.

  $ sudo hibernate-disk
  [sudo] password for xyz: 
  hibernate-disk:Warning: Tuxonice binary signature file not found.
  $

  (Note that this warning has been there earlier and is presumably not
  associated with this bug.)

  Expected: Switch to console, memory-page writeout progress indication,
  poweroff

  Observed: Switch to console, very quickly switch back to X11

  Excerpt from dmesg:

  [  418.377514] usbcore: deregistering interface driver uvcvideo
  [  419.227465] Filesystems sync: 0.006 seconds
  [  419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  419.229889] OOM killer disabled.
  [  419.230429] PM: Marking nosave pages: [mem 0x-0x0fff]
  [  419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f]
  [  419.230440] PM: Marking nosave pages: [mem 0x99438000-0x]
  [  419.233760] PM: Basic memory bitmaps created
  [  419.234176] PM: Preallocating image memory... done (allocated 1188843 
pages)
  [  420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s)
  [  420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  420.041324] printk: Suspending console(s) (use no_console_suspend to debug)
  [  420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  421.278599] ACPI: EC: interrupt blocked
  [  421.297107] ACPI: Preparing to enter system sleep state S4
  [  421.301832] ACPI: EC: event blocked
  [  421.301833] ACPI: EC: EC stopped
  [  421.301834] PM: Saving platform NVS memory
  [  421.302557] Disabling non-boot CPUs ...
  [  421.303996] smpboot: CPU 1 is now offline
  [  421.307624] smpboot: CPU 2 is now offline
  [  421.309904] IRQ 129: no longer affine to CPU3
  [  421.310921] smpboot: CPU 3 is now offline
  [  421.314818] smpboot: CPU 4 is now offline
  [  421.317033] IRQ 16: no longer affine to CPU5
  [  421.317040] IRQ 132: no longer affine to CPU5
  [  421.318049] smpboot: CPU 5 is now offline
  [  421.320365] IRQ 126: no longer affine to CPU6
  [  421.320373] IRQ 130: no longer affine to CPU6
  [  421.321405] smpboot: CPU 6 is now offline
  [  421.325743] smpboot: CPU 7 is now offline
  [  421.330059] PM: Creating hibernation image:
  [  422.045974] PM: Need to copy 1182218 pages
  [  422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 
7053219
  [  423.427947] PM: Hibernation image created (1182218 pages copied)
  [  421.330504] PM: Restoring platform NVS memory
  [  421.330638] ACPI: EC: EC started
  [  421.331412] Enabling non-boot CPUs ...
  [  421.331453] x86: Booting SMP configuration:
  [  421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  421.332297] CPU1 is up
  [  421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [  421.333137] CPU2 is up
  [  421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [  421.333987] CPU3 is up
  [  421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1
  [  421.334926] CPU4 is up
  [  421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3
  [  421.335640] CPU5 is up
  [  421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5
  [  421.336447] CPU6 is up
  [  421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7
  [  421.337232] CPU7 is up
  [  421.340095] ACPI: Waking up from system sleep state S4
  [  421.347884] ACPI: EC: interrupt unblocked
  [  421.390488] ACPI: EC: event unblocked
  [  421.391425] tpm tpm0: tpm_try_transmit: send(): error -5
  [  421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.603306] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [  421.634367] iwlwifi :03:00.0: FW already configured (0) - 
re-configuring
  [  421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715396] ata1.00: supports DRM functions and may not be fully accessible
  [  421.716087] ata1.00: disabling queued TRIM support
  

[Kernel-packages] [Bug 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  linux-5.4 regression: hibernate-disk resumes instantly

Status in hibernate package in Ubuntu:
  Confirmed
Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk
  fails to properly hibernate and shutdown the system; instead, Ubuntu
  resumes instantly.

  $ sudo hibernate-disk
  [sudo] password for xyz: 
  hibernate-disk:Warning: Tuxonice binary signature file not found.
  $

  (Note that this warning has been there earlier and is presumably not
  associated with this bug.)

  Expected: Switch to console, memory-page writeout progress indication,
  poweroff

  Observed: Switch to console, very quickly switch back to X11

  Excerpt from dmesg:

  [  418.377514] usbcore: deregistering interface driver uvcvideo
  [  419.227465] Filesystems sync: 0.006 seconds
  [  419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  419.229889] OOM killer disabled.
  [  419.230429] PM: Marking nosave pages: [mem 0x-0x0fff]
  [  419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f]
  [  419.230440] PM: Marking nosave pages: [mem 0x99438000-0x]
  [  419.233760] PM: Basic memory bitmaps created
  [  419.234176] PM: Preallocating image memory... done (allocated 1188843 
pages)
  [  420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s)
  [  420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  420.041324] printk: Suspending console(s) (use no_console_suspend to debug)
  [  420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  421.278599] ACPI: EC: interrupt blocked
  [  421.297107] ACPI: Preparing to enter system sleep state S4
  [  421.301832] ACPI: EC: event blocked
  [  421.301833] ACPI: EC: EC stopped
  [  421.301834] PM: Saving platform NVS memory
  [  421.302557] Disabling non-boot CPUs ...
  [  421.303996] smpboot: CPU 1 is now offline
  [  421.307624] smpboot: CPU 2 is now offline
  [  421.309904] IRQ 129: no longer affine to CPU3
  [  421.310921] smpboot: CPU 3 is now offline
  [  421.314818] smpboot: CPU 4 is now offline
  [  421.317033] IRQ 16: no longer affine to CPU5
  [  421.317040] IRQ 132: no longer affine to CPU5
  [  421.318049] smpboot: CPU 5 is now offline
  [  421.320365] IRQ 126: no longer affine to CPU6
  [  421.320373] IRQ 130: no longer affine to CPU6
  [  421.321405] smpboot: CPU 6 is now offline
  [  421.325743] smpboot: CPU 7 is now offline
  [  421.330059] PM: Creating hibernation image:
  [  422.045974] PM: Need to copy 1182218 pages
  [  422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 
7053219
  [  423.427947] PM: Hibernation image created (1182218 pages copied)
  [  421.330504] PM: Restoring platform NVS memory
  [  421.330638] ACPI: EC: EC started
  [  421.331412] Enabling non-boot CPUs ...
  [  421.331453] x86: Booting SMP configuration:
  [  421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  421.332297] CPU1 is up
  [  421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [  421.333137] CPU2 is up
  [  421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [  421.333987] CPU3 is up
  [  421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1
  [  421.334926] CPU4 is up
  [  421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3
  [  421.335640] CPU5 is up
  [  421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5
  [  421.336447] CPU6 is up
  [  421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7
  [  421.337232] CPU7 is up
  [  421.340095] ACPI: Waking up from system sleep state S4
  [  421.347884] ACPI: EC: interrupt unblocked
  [  421.390488] ACPI: EC: event unblocked
  [  421.391425] tpm tpm0: tpm_try_transmit: send(): error -5
  [  421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.603306] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [  421.634367] iwlwifi :03:00.0: FW already configured (0) - 
re-configuring
  [  421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715396] ata1.00: supports DRM functions and may not be fully accessible
  [  421.716087] ata1.00: disabling 

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

[roland]

Thank you for going the extra mile in resolving this 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/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 1834651] Re: cannot completely disable sched autogroup

[ne1]

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

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

Title:
  cannot completely disable sched autogroup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  man 7 sched says:
  If autogrouping is disabled, then the root task group consists of all 
processes in the root CPU cgroup.

  In the meantime, no matter the autogrouping disablements
  cat /proc/*/autogroup
  Still shows processes being classified.
  Can anyone sched some light on this discrepancy:
  a) the autogrouping cannot be disabled
  b) even disabled there is unnecessary process classification taking place

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

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

[Kernel-packages] [Bug 1863864] Re: Lenovo e590 laptop hangs when connect to dock station with kernel 5.3.0+

[Adrian]

I've got a problem that I believe might be linked. I'm using a Lenvovo
ThinkPad E590 with ubuntu 18.04 kernel 5.3.0-42

Problem arise when using a USB-C dock station with minimal equipment on
it (power, mouse, keyboard).

If I start with the USB-C dock station connected, the system freezes
shortly after boot (only mouse left moving, with everything else frozen,
including keyboard CAPS and NUM lock)

If I allow the system to boot, and THEN connect the dock, then things
seem to work fine.

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

Title:
  Lenovo e590 laptop hangs when connect to dock station with kernel
  5.3.0+

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Lenovo ThinkPad e590, which connected via USB Type-C to Lenovo Dock 
station.
  To doc station connected network cable, USB mouse, keyboard, power, and two 
monitors.

  On previous kernel versions (include 5.0.0-37) it works ok.
  But after update to any version on 5.3.0 I can't use it with doc station:
  1) If I boot with connected Dock station then 2 external monitors are black 
and laptop monitor the same black
  2) If I boot without connected Dock station then Laptop works ok. At the 
moment when I connect USB Type-C cable to laptop screen become black, and 2 
external monitors show the image, but it hangs:
   I can move the mouse cursor but all other UI hangs, even the clock does not 
work, only REISUB helps.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andrii 1548 F pulseaudio
   /dev/snd/controlC1:  andrii 1548 F pulseaudio
   /dev/snd/controlC0:  andrii 1548 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2019-07-26 (207 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  MachineType: LENOVO 20NB000YRT
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic 
root=/dev/mapper/vg0-root ro 
cryptops=target=vg0-root,source=/dev/disk/by-uuid/737a3cbd-a798-45e6-88e3-602d767eae77,lvm=vg0
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-37-generic N/A
   linux-backports-modules-5.0.0-37-generic  N/A
   linux-firmware1.173.14
  Tags:  tessa
  Uname: Linux 5.0.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET27W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB000YRT
  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:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20NB000YRT:pvrThinkPadE590:rvnLENOVO:rn20NB000YRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB000YRT
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrii 1520 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2019-07-26 (209 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 06cb:00a2 Synaptics, Inc. 
   Bus 001 Device 003: ID 5986:2113 Acer, Inc 
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20NB000YRT
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=/dev/mapper/vg0-root ro 
cryptops=target=vg0-root,source=/dev/disk/by-uuid/737a3cbd-a798-45e6-88e3-602d767eae77,lvm=vg0
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  tessa
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET27W (1.10 )
  dmi.board.asset.tag: Not Available
  

[Kernel-packages] [Bug 1765998] Re: FS access deadlock with btrfs quotas enabled

[Dmitrii Shcherbakov]

Recently hit that on Focal due to the fact that quotas were enabled by
LXD.

This renders the system completely unresponsive if you use btrfs as a
rootfs with btrfs-transaction or btrfs-cleaner kernel threads hogging a
100% of 1 CPU core.

Booting using a live USB, disabling quotas and temporarily moving
/etc/systemd/system/snap-lxd-* files out helps (followed by `snap
disable lxd` until it gets updated with
https://github.com/lxc/lxd/pull/7032).

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

Title:
  FS access deadlock with btrfs quotas enabled

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

Bug description:
  I'm running into an issue on Ubuntu Bionic (but not Xenial) where
  shortly after boot, under heavy load from many LXD containers starting
  at once, access to the btrfs filesystem that the containers are on
  deadlocks.

  The issue is quite hard to reproduce on other systems, quite likely
  related to the size of the filesystem involved (4 devices with a total
  of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
  and the access pattern from many LXD containers at once. It definitely
  goes away when disabling btrfs quotas though. Another prerequisite to
  trigger this bug may be the container subvolumes sharing extents (from
  their parent image or due to deduplication).

  I can only reliably reproduce it on a production system that I can only do 
very limited testing on, however I have been able to gather the following 
information:
  - Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
  - There always seem to be (at least) two threads executing rmdir syscalls 
which are creating the circular dependency: One of them is in btrfs_cow_block 
=> ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants 
to acquire a lock that was already aquired by btrfs_search_slot of the other 
rmdir.
  - Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

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

[Kernel-packages] [Bug 1866041] Re: 53-sim-binary_tree and 55-basic-pfc_binary_tree from ubuntu_seccomp failed on 4.4 i386 / PowerPC / s390x

[Po-Hsu Lin]

Bug updated as the original issue has gone with upstream fixes, now this
(FAILURE bpf_sim resulted in ALLOW) is the latest issue

** Summary changed:

- 53-sim-binary_tree and 55-basic-pfc_binary_tree from ubuntu_seccomp failed on 
4.4 i386 / PowerPC / s390x
+ 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted 
in ALLOW on 4.4 / 4.15

** No longer affects: ubuntu-kernel-tests

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Description changed:

- Issue found with 4.4.0-148.174~14.04.1 and 4.4.0-176.206~14.04.1 on
- T-4.4 i386 node "fozzie" (passed on T-4.4 AMD64 nodes)
+ The following failures:
+ Test 53-sim-binary_tree%%034-1 result: FAILURE bpf_sim resulted in ALLOW
+ Test 53-sim-binary_tree%%035-1 result: FAILURE bpf_sim resulted in ALLOW
+ Test 53-sim-binary_tree%%036-1 result: FAILURE bpf_sim resulted in ALLOW
  
- This does not look like a regression, but a new test case added to the
- test suite instead.
+ Can be found on:
+ 4.15.0-92.93 - PoewrPC / s390x / i386
+ 4.4.0-177 - PoewrPC / s390x / i386
  
- 38f04da847 (tests: add tests for the binary tree)
- https://github.com/seccomp/libseccomp 
- 
- Failed cases:
-   Test 53-sim-binary_tree%%331-1 result:   FAILURE 53-sim-binary_tree 
rc=14
-   Test 55-basic-pfc_binary_tree%%001-1 result:   FAILURE 
55-basic-pfc_binary_tree.sh rc=1
- 
- 
- Please find the complete test log with 4.4.0-148.174~14.04.1 in the 
attachment.
+ Please find the complete test log with 4.4.0-177 in the attachment of
+ comment 5.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1
  ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Wed Mar  4 10:32:46 2020
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

** Attachment added: "ubuntu_seccomp.log"
   
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+attachment/5338728/+files/ubuntu_seccomp.log

** Summary changed:

- 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted 
in ALLOW on 4.4 / 4.15
+ 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted 
in ALLOW on 4.4 / 4.15 non-amd64

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

Title:
  53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim
  resulted in ALLOW on 4.4 / 4.15 non-amd64

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

Bug description:
  The following failures:
  Test 53-sim-binary_tree%%034-1 result: FAILURE bpf_sim resulted in ALLOW
  Test 53-sim-binary_tree%%035-1 result: FAILURE bpf_sim resulted in ALLOW
  Test 53-sim-binary_tree%%036-1 result: FAILURE bpf_sim resulted in ALLOW

  Can be found on:
  4.15.0-92.93 - PoewrPC / s390x / i386
  4.4.0-177 - PoewrPC / s390x / i386

  Please find the complete test log with 4.4.0-177 in the attachment of
  comment 5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1
  ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Wed Mar  4 10:32:46 2020
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions

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

[Kernel-packages] [Bug 1868061] Re: linux-image-5.3.0-42-generic regression: no audio output on HP EliteBook 840 G6

[Nico R.]

I am currently running another kernel and will not be able to quickly
provide the information produced by apport-collect. I am quite confident
that the information provided by me so far will help with triaging this
bug report or requesting further _specific_ details, and therefore I am
setting the bug status to 'Confirmed'.

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

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

Title:
  linux-image-5.3.0-42-generic regression: no audio output on HP
  EliteBook 840 G6

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Symptoms:

  no hardware audio output device found by PulseAudio on eoan after I
  have updated the system yesterday.

  
  Works: linux-image-5.3.0-40-generic
  Does not work: linux-image-5.3.0-42-generic

  
  * I suspect this is somewhat related to the recent changes for SkyLake+ 
platforms between tags Ubuntu-5.3.0-40.32 and Ubuntu-5.3.0-42.34 (I am 
referring to the repo at 
).

  * I am using the binary package from the Ubuntu repos, not a self-
  built kernel.

  * I can help with bisecting and testing if you like. If you like me
  to, I need a piece of advice: is
   the proper up-to-
  date documentation for building my Ubuntu kernel from the sources in
  the git repo?


  What I have tried so far:

  I wanted to reload the sound module(s), so I ran the following
  command:

  $ pulseaudio -k ; sudo rmmod snd_hda_intel snd_soc_skl_hda_dsp
  snd_soc_skl_ssp_clk snd_soc_skl snd_soc_skl_ipc

  Then I ran:

  # modprobe snd-hda-intel

  
  I found the following in my syslog (not totally sure about when exactly this 
happened – before or after the rmmod/modprobe):

  (see attached file)

  
  Output of ‘sudo lspci -vvnn’ (warning: on 5.3.0-40-generic! Because I am 
working in parallel and need a functioning audio setup right now; I can try 
this on another kernel in the evening if absolutely necessary, but this should 
suffice):

  (see attached file)

  
  If more information is necessary for proper debugging, please give me some 
instructions what to do. Thanks! ☺

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

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

[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3

[You-Sheng Yang]

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

-- 
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:
  Fix Committed
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:
  Fix Committed

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 1867587] Re: [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE kernel branch

[Andrew Cloke]

** Changed in: kunpeng920
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  SAS patchset have merged into mainline 5.6rc1 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  scsi: hisi_sas: Rename hisi_sas_cq.pci_irq_mask
  scsi: hisi_sas: Add prints for v3 hw interrupt converge and automatic affinity
  scsi: hisi_sas: Modify the file permissions of trigger_dump to write only
  scsi: hisi_sas: Replace magic number when handle channel interrupt
  scsi: hisi_sas: replace spin_lock_irqsave/spin_unlock_restore with 
spin_lock/spin_unlock
  scsi: hisi_sas: use threaded irq to process CQ interrupts

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

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

[Kernel-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)

[Daniel van Vugt]

** Tags removed: fixed-upstream

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  Triaged
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in Focal:
  Triaged
Status in gnome-bluetooth source package in Focal:
  Fix Released
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

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

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