[Kernel-packages] [Bug 1880519] Re: System stops responding while entering S3 with SD card installed

[Hsuan-Yu Lin]

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

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

Title:
  System stops responding while entering S3 with SD card installed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Won't Fix
Status in linux-oem source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Triaged
Status in linux-oem source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  The system stops responding while entering S3, screen will be lit up if 
touchpad is triggered by finger. Cursor could be seen with black background, 
but system is not responding to any input.

  [Fix]
  b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM
  f0c472a6da51 xhci: Return if xHCI doesn't support LPM

  [test]
  With the above patch applied:

  4.15.0-1081-oem PASSED (30/30)
  bionic PASSED (30/30)
  bionic-oem PASSED (30/30)
  bionic-oem-osp1 PASSED (30/30)
  eoan PASSED (30/30)
  focal PASSED (30/30)
  focal-oem PASSED (30/30)
  ubuntu-unstable PASSED (30/30)

  [Regression Potential]

  [Reproduce Steps]
  1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso
  2. Upgrade kernel to 4.15.0-1080-oem
  3. Boot the system with 4.15.0-1080-oem kernel
  4. Insert SD card
  5. Suspend the system to S3

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

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

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

[Kai-Heng Feng]

Please also test the kernel, which includes latest patch from Realtek:
https://people.canonical.com/~khfeng/lp1850439/

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

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

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[Hui Wang]

@Corbin and @gogolink,

On the 20.04, we could install the ubuntu 5.6.0-oem kernel, you could
install that kernel on the 20.04. Let us see if that kernel has this
issue or not.

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  

[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU

[Shu Shen]

I don't think the fix has been back-ported to 5.4 kernel.

The upstream kernel fix was included in kernel 5.8-rc1 and later:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound?h=v5.8-rc4=89d73ccab20a684d8446cea4d8ac6a2608c8d390

I tested with the 5.8-rc1 mainline kernel on Ubuntu 20.04:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc1. Sound output
works without any boot parameter but the microphone array did not work
for me on SF314-57-74V6.

With security boot enabled on the laptop, manual signing the mainline
kernel is very cumbersome and difficult when doing software updates. I
lost appetite and will probably wait for Ubuntu 20.10 which might pick
up a later release of the kernel that has the 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/1877757

Title:
  No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7
  CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New focal installation on a new Acer Swift 3 laptop with core i7-1065G7.
  No sound detected, KDE/pavucontrol shows Dummy output.
  External headset also not detected.

  I've googled around and tried to reinstall alsa and pulseaudio, tried
  alsa force-reload as well. Nothing helps.

  With snd_hda_intel.dmic_detect=0 speakers start working but microphone
  is not detected. External headset detected with both headphones and
  mic. I use this as a workaround for a time being.

  I've checked
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It
  is closed  and use  recent kernel and firmware  but it does not fix my
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May  9 18:56:15 2020
  InstallationDate: Installed on 2020-04-24 (15 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Swift SF314-57G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57G
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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

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

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

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wo

[Kai-Heng Feng]

** Package changed: alsa-driver (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/1852067

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1885693] Re: Unwanted reboot after screen is locked

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1885693

Title:
  Unwanted reboot after screen is locked

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After locking the screen to leave the computer for a few minutes, I
  come back to a computer that is freshly rebooted. It usually happens 1
  out of 4 or 5 times when locking the screen.

  This only happens when my laptop (Lenovo T470s, also seen with T490)
  is connected to my USB-C dock. The problem has been observed with
  18.04, 19.10 and 20.04.

  /var/log/syslog contains:

  Jun 30 10:47:05 jbn3 kernel: [33470.649606] [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.
  Jun 30 10:47:23 jbn3 kernel: [33488.187142] [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.
  Jun 30 10:47:23 jbn3 kernel: [33488.419723] [drm:pipe_config_mismatch [i915]] 
*ERROR* mismatch in pixel_rate (expected 241500, found 482999)
  Jun 30 10:47:23 jbn3 kernel: [33488.419818] [drm:pipe_config_mismatch [i915]] 
*ERROR* mismatch in shared_dpll (expected a870403d, found 
5108ff4b)
  Jun 30 10:47:23 jbn3 kernel: [33488.419902] [drm:pipe_config_mismatch [i915]] 
*ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001)
  Jun 30 10:47:23 jbn3 kernel: [33488.419986] [drm:pipe_config_mismatch [i915]] 
*ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 241500, found 
482999)
  Jun 30 10:47:23 jbn3 kernel: [33488.420067] [drm:pipe_config_mismatch [i915]] 
*ERROR* mismatch in port_clock (expected 27, found 54)
  Jun 30 10:47:23 jbn3 kernel: [33488.420071] [ cut here 
]
  Jun 30 10:47:23 jbn3 kernel: [33488.420072] pipe state doesn't match!
  Jun 30 10:47:23 jbn3 kernel: [33488.420249] WARNING: CPU: 0 PID: 2300 at 
drivers/gpu/drm/i915/display/intel_display.c:13158 
verify_crtc_state+0x2ad/0x300 [i915]
  Jun 30 10:47:23 jbn3 kernel: [33488.420251] Modules linked in: xt_nat 
xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc hid_generic 
snd_usb_audio usbhid snd_usbmidi_lib hid cdc_ether r8152 vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) ccm aufs overlay bnep nls_iso8859_1 joydev 
intel_rapl_msr mei_hdcp cdc_mbim qcserial usb_wwan cdc_wdm usbserial cdc_ncm 
usbnet mii uvcvideo btusb btrtl snd_hda_codec_hdmi btbcm btintel 
intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp bluetooth 
kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel 
snd_intel_dspcfg snd_hda_codec intel_cstate rmi_smbus ecdh_generic rmi_core 
intel_rapl_perf ecc videobuf2_vmalloc snd_hda_core videobuf2_memops 
videobuf2_v4l2 snd_hwdep iwlmvm snd_seq_midi videobuf2_common 
snd_seq_midi_event mac80211 videodev intel_wmi_thunderbolt libarc4 snd_pcm 
input_leds iwlwifi
  Jun 30 10:47:23 jbn3 kernel: [33488.420310]  snd_rawmidi mc serio_raw snd_seq 
wmi_bmof thinkpad_acpi nvram cfg80211 ledtrig_audio mei_me 
intel_xhci_usb_role_switch mei snd_seq_device intel_pch_thermal snd_timer 
ucsi_acpi typec_ucsi roles typec snd soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c dm_crypt uas usb_storage i915 crct10dif_pclmul crc32_pclmul 
nvme ghash_clmulni_intel i2c_algo_bit aesni_intel crypto_simd cryptd 
glue_helper psmouse e1000e i2c_i801 nvme_core drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops thunderbolt drm wmi video
  Jun 30 10:47:23 jbn3 kernel: [33488.420358] CPU: 0 PID: 2300 Comm: Xorg 
Tainted: G   OE 5.4.0-39-generic #43-Ubuntu
  Jun 30 10:47:23 jbn3 kernel: [33488.420360] Hardware name: LENOVO 
20HF004MMX/20HF004MMX, BIOS N1WET59W (1.38 ) 04/22/2020
  Jun 30 10:47:23 jbn3 kernel: [33488.420437] RIP: 
0010:verify_crtc_state+0x2ad/0x300 [i915]
  Jun 30 10:47:23 jbn3 kernel: [33488.420441] Code: b6 45 bf e9 8d fe ff ff 80 
3d 45 77 10 00 00 0f b6 f0 48 c7 c7 40 aa 85 c0 75 32 e8 1d 48 d5 ff e9 1e fe 
ff ff e8 6e 9e b1 ef <0f> 0b e9 1b ff ff ff e8 62 9e b1 ef 0f 0b e9 85 fe ff ff 
e8 56 9e
  Jun 30 10:47:23 jbn3 kernel: [33488.420444] RSP: 0018:b1b74290fa80 
EFLAGS: 00010282
  Jun 30 10:47:23 jbn3 kernel: [33488.420448] RAX:  RBX: 
97a35f0002b0 RCX: 0006
  Jun 30 10:47:23 jbn3 kernel: [33488.420450] RDX: 0007 RSI: 
0092 RDI: 97a3724178c0
  Jun 30 10:47:23 jbn3 kernel: [33488.420452] RBP: b1b74290fac8 R08: 
0ae9 R09: 0004

[Kernel-packages] [Bug 1852067] [NEW] [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps to replicate the bug.

1. Start laptop with Ubuntu 18.04.3 LTS.
Sound from built-in speakers works fine.
Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
2. Connect headphones (wired, mini-jack connector).
Sound from headphones works fine. No sound from built-in speakers (which is OK, 
obviously).
Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
3. Disconnect headphones from computer.
No sound from built-in speakers.
Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
help. Only full laptop restart helps.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marcin 2115 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 12:26:58 2019
InstallationDate: Installed on 2019-04-02 (223 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1672 F pulseaudio
  marcin 2115 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.08.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.3A.00
dmi.chassis.asset.tag: 5CD91018X5
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2YN61AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic wayland-session
-- 
[HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from 
built-in speakers after disconnecting headphones. Prior to connecting 
headphones speakers works ok.
https://bugs.launchpad.net/bugs/1852067
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 1886912] Re: DELL M3800 Touchscreen not working after login

[Kai-Heng Feng]

Can you please add "dyndbg='file drivers/usb/* +p'" to kernel parameter,
and attach dmesg here? Thanks!

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Kai-Heng Feng]

Which graphics does the HDMI connect to? Intel or Nvidia?

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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

[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse

[Kai-Heng Feng]

No, uninstalling drivers are unnecessary.

Only thing needs to do is to install the kernel debs.

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

Title:
  Touchpad recognised as generic mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
  ideapadY700. My laptop recognises touchpad as mouse. I have no other
  mouse plugged.

  Touchpad firmware: 2ul001af
  Lenovo ideapad700-15ISK BIOS version: CDCN54WW

  I'm new in Ubuntu and I don't know much...

  ```$ uname -a```

  ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21
  12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux```

  ```$ dmesg | grep psmouse```

  ```[   30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 
failed.
  [   30.218879] psmouse serio1: elantech: failed to query firmware version.
  [  165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  ```

  ```$ xinput```

  ```⎡ Virtual core pointer id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Logitech Wheel Mouse   id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ```

  ```$ cat /proc/bus/input/devices```

  ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063
  N: Name="PS/2 Logitech Wheel Mouse"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input19
  U: Uniq=
  H: Handlers=mouse0 event16
  B: PROP=1
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3
  ```
  I have read a lot of solutions; I tried to use xorg, but it didn't work.
  When I removed it, it worked for a day (only) and I decided erase and 
re-install Ubuntu.

  Please help!
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nando  1137 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:24:24 2020
  InstallationDate: Installed on 2020-06-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80NV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 

[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd

[Kai-Heng Feng]

New HP AMD laptops only supports s2idle.

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

Title:
  limited hardware support AMD 4700u HP Envy x360 13-ay003nd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Hibernate:
  screen goes off, nothing else happens. After user interaction, screen turns 
on. Login screen is shown. Sometimes screen does not turn on: physical reboot 
required.
  kernel upgrade to 5.8rc3 or 5.8rc4 has no effect.

  Brightness:
  Adjusting brightness has no effect, nightmode has no effect.
  Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, 
brightness can be adjusted and nightmode works But after a reboot brightness is 
always at max. Also brightness cannot be lowered as much as normally expected.

  CPU & fan:
  CPU is always high, 5.8rc3 solves this partially, fan is still always on and 
quite high (after clean Ubuntu install, nothing configured or installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  asterix 881 F pulseaudio
   /dev/snd/controlC1:  asterix 881 F pulseaudio
   /dev/snd/controlC0:  asterix 881 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jul  9 12:21:02 2020
  InstallationDate: Installed on 2020-07-09 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.30
  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.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 1D5H9EA#ABH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Kailiang Yang]

Hi All,

Please test again for below commands.

hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7778

If possible please check all 4 of:

1. Speakers
2. Headphones output
3. Internal mic.
4. Headset mic. (using a phone headset with builtin mic with a single T-R-R-S 
connector)

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

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

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[gogolink]

On 5.5.10, sound is also not working; but just as on 5.4.0-40, at least
when I click on volume control (in panel), it does show me a volume
level and allow me to open audio mixer, which shows "Dummy output" and
"No cards available for configuration."  (So there seems to be some
change somewhere between 5.5.10 and 5.5.19, but the first workable
kernel is 5.6.0.)

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[gogolink]

Sound seems to be working fully on 5.6.0-050600rc3.
On 5.5.19-050519, sound was totally broken.  When I clicked on volume control, 
the message was "not connected to the pulse audio server."

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] 

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

[Kamyar Kaviani]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1886234/+attachment/5391186/+files/WifiSyslog.txt

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

[Kernel-packages] [Bug 1886234] Lsusb-t.txt

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 

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

[Kamyar Kaviani]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1886234/+attachment/5391174/+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/1886234

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] 

[Kernel-packages] [Bug 1886234] Lsusb-v.txt

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] 

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

[Kamyar Kaviani]

apport information

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

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

[Kernel-packages] [Bug 1886234] Lspci-vt.txt

[Kamyar Kaviani]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1886234/+attachment/5391175/+files/Lspci-vt.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/1886234

Title:
  libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1
  with -EEXIST, don't try to register things with the same name in the
  same directory.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:

  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 

[Kernel-packages] [Bug 1886234] Re: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory.

[Kamyar Kaviani]

apport information

** Tags added: apport-collected

** Description changed:

  After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and
  turning the VM off, I see this in dmesg:
  
  [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, 
widening DMA allocations
  [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config.
  [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f
  [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded
  [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6
  [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1
  [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1
  [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config.
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on
  [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on
  [ 4680.392669] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1'
  [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G   OE 
5.4.0-40-generic #44-Ubuntu
  [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG 
STRIX X570-E GAMING, BIOS 1409 05/12/2020
  [ 4680.392674] Call Trace:
  [ 4680.392681]  dump_stack+0x6d/0x9a
  [ 4680.392684]  sysfs_warn_dup.cold+0x17/0x35
  [ 4680.392685]  sysfs_create_dir_ns+0xb8/0xd0
  [ 4680.392687]  kobject_add_internal+0xbd/0x2b0
  [ 4680.392688]  kobject_add+0x7e/0xb0
  [ 4680.392692]  device_add+0x132/0x6b0
  [ 4680.392696]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392702]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392706]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392709]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392712]  ? snd_hwdep_new+0xfe/0x146 [snd_hwdep]
  [ 4680.392715]  snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth]
  [ 4680.392717]  snd_emux_register+0x11a/0x190 [snd_emux_synth]
  [ 4680.392719]  ? 0xc1065000
  [ 4680.392721]  ? sf_sample_new+0x20/0x20 [snd_emux_synth]
  [ 4680.392723]  snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth]
  [ 4680.392725]  really_probe+0x2b3/0x3e0
  [ 4680.392726]  driver_probe_device+0xbc/0x100
  [ 4680.392728]  __device_attach_driver+0x71/0xd0
  [ 4680.392729]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392731]  bus_for_each_drv+0x84/0xd0
  [ 4680.392732]  __device_attach+0xe1/0x160
  [ 4680.392734]  device_initial_probe+0x13/0x20
  [ 4680.392735]  bus_probe_device+0x8f/0xa0
  [ 4680.392737]  device_add+0x3c7/0x6b0
  [ 4680.392740]  ? __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392742]  snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device]
  [ 4680.392745]  __snd_device_register.part.0+0x1f/0x30 [snd]
  [ 4680.392748]  snd_device_register_all+0x33/0x50 [snd]
  [ 4680.392751]  snd_card_register+0x62/0x1b0 [snd]
  [ 4680.392753]  ? snd_seq_device_new+0xd0/0x126 [snd_seq_device]
  [ 4680.392758]  snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1]
  [ 4680.392761]  local_pci_probe+0x48/0x80
  [ 4680.392763]  pci_device_probe+0x10f/0x1b0
  [ 4680.392765]  really_probe+0x159/0x3e0
  [ 4680.392766]  driver_probe_device+0xbc/0x100
  [ 4680.392767]  __device_attach_driver+0x71/0xd0
  [ 4680.392769]  ? driver_allows_async_probing+0x50/0x50
  [ 4680.392770]  bus_for_each_drv+0x84/0xd0
  [ 4680.392771]  __device_attach+0xe1/0x160
  [ 4680.392773]  device_attach+0x10/0x20
  [ 4680.392775]  bus_rescan_devices_helper+0x39/0x80
  [ 4680.392777]  drivers_probe_store+0x36/0x60
  [ 4680.392778]  bus_attr_store+0x27/0x30
  [ 4680.392780]  sysfs_kf_write+0x3e/0x50
  [ 4680.392782]  kernfs_fop_write+0xda/0x1b0
  [ 4680.392784]  __vfs_write+0x1b/0x40
  [ 4680.392785]  vfs_write+0xb9/0x1a0
  [ 4680.392786]  ksys_write+0x67/0xe0
  [ 4680.392788]  __x64_sys_write+0x1a/0x20
  [ 4680.392790]  do_syscall_64+0x57/0x190
  [ 4680.392793]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 4680.392794] RIP: 0033:0x7f52456222cf
  [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48
  [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 
0001
  [ 4680.392798] RAX: ffda RBX: 000c RCX: 
7f52456222cf
  [ 4680.392799] RDX: 000c RSI: 7f5230062f50 RDI: 
0019
  [ 4680.392800] RBP: 7f5230062f50 R08:  R09: 

  [ 4680.392800] R10:  R11: 0293 R12: 
0019
  [ 4680.392801] R13: 0019 R14:  R15: 
7f5245b3ef70
  [ 4680.392803] kobject_add_internal failed for emu10k1-synth-0-1 with 
-EEXIST, don't try to register things with the same name in the same 

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[gogolink]

@Corbin
Thanks, that worked!

And with this I can report that sound in 5.6.3 DOES work for me.  Will
go back now and try to find the *1st* workable kernel.

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
 

[Kernel-packages] [Bug 1880519] Re: System stops responding while entering S3 with SD card installed

[Hsuan-Yu Lin]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => In Progress

** Description changed:

  [Impact]
  The system stops responding while entering S3, screen will be lit up if 
touchpad is triggered by finger. Cursor could be seen with black background, 
but system is not responding to any input.
  
  [Fix]
- https://lkml.org/lkml/2020/5/20/410
- https://lkml.org/lkml/2020/5/20/411
+ b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM
+ f0c472a6da51 xhci: Return if xHCI doesn't support LPM
  
  [test]
  With the above patch applied:
  
  4.15.0-1081-oem PASSED (30/30)
  bionic PASSED (30/30)
  bionic-oem PASSED (30/30)
  bionic-oem-osp1 PASSED (30/30)
  eoan PASSED (30/30)
  focal PASSED (30/30)
  focal-oem PASSED (30/30)
  ubuntu-unstable PASSED (30/30)
  
- 
  [Regression Potential]
  
  [Reproduce Steps]
  1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso
  2. Upgrade kernel to 4.15.0-1080-oem
  3. Boot the system with 4.15.0-1080-oem kernel
  4. Insert SD card
  5. Suspend the system to S3

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

Title:
  System stops responding while entering S3 with SD card installed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  Confirmed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in linux-oem source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Triaged
Status in linux-oem source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  The system stops responding while entering S3, screen will be lit up if 
touchpad is triggered by finger. Cursor could be seen with black background, 
but system is not responding to any input.

  [Fix]
  b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM
  f0c472a6da51 xhci: Return if xHCI doesn't support LPM

  [test]
  With the above patch applied:

  4.15.0-1081-oem PASSED (30/30)
  bionic PASSED (30/30)
  bionic-oem PASSED (30/30)
  bionic-oem-osp1 PASSED (30/30)
  eoan PASSED (30/30)
  focal PASSED (30/30)
  focal-oem PASSED (30/30)
  ubuntu-unstable PASSED (30/30)

  [Regression Potential]

  [Reproduce Steps]
  1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso
  2. Upgrade kernel to 4.15.0-1080-oem
  3. Boot the system with 4.15.0-1080-oem kernel
  4. Insert SD card
  5. Suspend the system to S3

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

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

[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd

[AaronMa]

For backlight issue.
Use 5.7.7 kernel should be OK, no patches needs.

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

Title:
  limited hardware support AMD 4700u HP Envy x360 13-ay003nd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Hibernate:
  screen goes off, nothing else happens. After user interaction, screen turns 
on. Login screen is shown. Sometimes screen does not turn on: physical reboot 
required.
  kernel upgrade to 5.8rc3 or 5.8rc4 has no effect.

  Brightness:
  Adjusting brightness has no effect, nightmode has no effect.
  Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, 
brightness can be adjusted and nightmode works But after a reboot brightness is 
always at max. Also brightness cannot be lowered as much as normally expected.

  CPU & fan:
  CPU is always high, 5.8rc3 solves this partially, fan is still always on and 
quite high (after clean Ubuntu install, nothing configured or installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  asterix 881 F pulseaudio
   /dev/snd/controlC1:  asterix 881 F pulseaudio
   /dev/snd/controlC0:  asterix 881 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jul  9 12:21:02 2020
  InstallationDate: Installed on 2020-07-09 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.30
  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.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 1D5H9EA#ABH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd

[AaronMa]

Please append "mem_sleep_default=deep" in kernel cmdline (/etc/default/grub; 
update-grub)
Try to  use s3.

AMD claims that s2idle is not supported.

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

Title:
  limited hardware support AMD 4700u HP Envy x360 13-ay003nd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Hibernate:
  screen goes off, nothing else happens. After user interaction, screen turns 
on. Login screen is shown. Sometimes screen does not turn on: physical reboot 
required.
  kernel upgrade to 5.8rc3 or 5.8rc4 has no effect.

  Brightness:
  Adjusting brightness has no effect, nightmode has no effect.
  Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, 
brightness can be adjusted and nightmode works But after a reboot brightness is 
always at max. Also brightness cannot be lowered as much as normally expected.

  CPU & fan:
  CPU is always high, 5.8rc3 solves this partially, fan is still always on and 
quite high (after clean Ubuntu install, nothing configured or installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  asterix 881 F pulseaudio
   /dev/snd/controlC1:  asterix 881 F pulseaudio
   /dev/snd/controlC0:  asterix 881 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jul  9 12:21:02 2020
  InstallationDate: Installed on 2020-07-09 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.30
  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.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 1D5H9EA#ABH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[Corbin]

@gogolink
try turning off secure boot

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 

[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

[Khaled El Mously]

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

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

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.

  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.

  [Test case]
  Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.

  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.

  --

  Reported from a user:

  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.

  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.

  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 80050033
  [  696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 
003606e0
  [  696.397135] DR0:  DR1:  DR2: 

  [  696.397152] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  696.397169] Call Trace:
  [  696.397175]  
  [  696.397183]  sk_filter_trim_cap+0xd0/0x1b0
  [  696.397191]  tcp_v4_rcv+0x8b7/0xa80
  [  696.397199]  ip_local_deliver_finish+0x66/0x210
  [  696.397208]  ip_local_deliver+0x7e/0xe0
  [  696.397215]  ? ip_rcv_finish+0x430/0x430
  [  696.397223]  ip_rcv_finish+0x129/0x430
  [  696.397230]  ip_rcv+0x296/0x360
  [  696.397238]  ? inet_del_offload+0x40/0x40
  [  696.397249]  __netif_receive_skb_core+0x432/0xb80
  [  696.397261]  ? skb_send_sock+0x50/0x50
  [  696.397271]  ? tcp4_gro_receive+0x137/0x1a0
  [  696.397280]  __netif_receive_skb+0x18/0x60
  [  696.397290]  ? __netif_receive_skb+0x18/0x60
  [  696.397300]  netif_receive_skb_internal+0x45/0xe0
  [  696.397309]  napi_gro_receive+0xc5/0xf0
  [  696.397317]  xennet_poll+0x9ca/0xbc0
  [  696.397325]  net_rx_action+0x140/0x3a0
  [  696.397334]  __do_softirq+0xe4/0x2d4
  [  696.397344]  irq_exit+0xc5/0xd0
  [  696.397352]  xen_evtchn_do_upcall+0x30/0x50
  [  696.397361]  xen_hvm_callback_vector+0x90/0xa0
  [  696.397371]  
  [  696.397378] RIP: 0010:native_safe_halt+0x12/0x20
  [  696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: 
ff0c
  [  696.397405] RAX: 8efc1800 RBX: 0006 RCX: 

[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD

[You-Sheng Yang]

https://bugzilla.kernel.org/show_bug.cgi?id=204873, and it suggests the
fix
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c?id=d829229e35f302fd49c052b5c5906c90ecf9911d
has been landed in v5.5.


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

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

Title:
  Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel
  switch, iwlwifi Microcode SW Error: FW error in SYNC CMD
  CHANNEL_SWITCH_TIME_EVENT_CMD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33

  I occasionally see a message on my screen that disk space is low. I
  try rebooting since my computer is unresponsive. Normal reboot does
  not work, sudo reboot does not work. I have to power off the machine
  using power button. Machine boots but hangs because its trying to
  repair journal info.

  I can't see what causes that since I was not using my computer at the time.
  edit: see comment #14

  So with a live session, I can see that syslog and kern.log files have
  grown to several GB until the drive is full.

  When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any 
problem so far.
  edit: not true actually, this happened again using this upstream kernel.

  Never had this issue with previous Ubuntu versions with the very same
  hardware configuration, since 16.04.

  Included: partial syslog and kern.log with the same message repeated over and 
over.
  edit: and when the event starts.

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

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

[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled

[Matthew Ruffell]

I asked the customer to test 4.4.0-186-generic from -proposed on their
HP DL360 Gen10 machines with the Intel Xeon Gold 5120 CPU. The machine
has Sub-NUMA Clustering enabled and it is active.

The machine boots successfully, and there are no call traces or kernel
oops present:

# uname -rv
4.4.0-186-generic #216-Ubuntu SMP Wed Jul 1 05:34:05 UTC 2020

[Thu Jul 9 18:33:32 2020] x86: Booting SMP configuration:
[Thu Jul 9 18:33:32 2020]  node #0, CPUs: #1
[Thu Jul 9 18:33:32 2020] NMI watchdog: enabled on all CPUs, permanently 
consumes one hw-PMU counter.
[Thu Jul 9 18:33:32 2020] #2 #3 #4 #5 #6
[Thu Jul 9 18:33:32 2020]  node #1, CPUs: #7 #8 #9 #10 #11 #12 #13
[Thu Jul 9 18:33:32 2020]  node #0, CPUs: #14
[Thu Jul 9 18:33:32 2020] MDS CPU bug present and SMT on, data leak possible. 
See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for 
more details.
[Thu Jul 9 18:33:32 2020] TAA CPU bug present and SMT on, data leak possible. 
See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html 
for more details.
[Thu Jul 9 18:33:32 2020] #15 #16 #17 #18 #19 #20
[Thu Jul 9 18:33:32 2020]  node #1, CPUs: #21 #22 #23 #24 #2

The issue is fixed, and I am happy to mark this as verified.

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

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

Title:
  smpboot: don't call topology_sane() when Sub-NUMA-Clustering is
  enabled

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

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

  [Impact]

  Intel Skylake server processors and onward have a different Last Level
  Cache (LLC) topology than earlier processors, and such processors have
  a new feature called Sub-NUMA-Clustering (SNC) which is similar to the
  existing Cluster-On-Die (CoD) feature earlier server processors has.

  Sub-NUMA-Clustering divides the system into two "slices", each of
  which are allocated half the CPU cores, half the Last Level Cache and
  one memory controller. Each slice is enumerated as a NUMA node.

  The difference between Sub-NUMA-Clustering and Cluster-On-Die is how
  the Last Level Cache is exposed to each NUMA node. CoD had the same
  cache line present in each half of the LLC. In SNC, each cache line is
  only present in its respective slice. Because of this, the semantics
  around accessing LLC changes, with a process accessing NUMA-local
  memory only seeing half the LLC capacity.

  On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and
  Bionic 4.15 kernels we see the following oops during NUMA node
  enumeration:

   node #0, CPUs: #1 #2 #3 #4 #5 #6
   node #1, CPUs: #7
  sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. 
Ignoring dependency.
  WARNING: CPU: 7 PID: 0 at 
/build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 
topology_sane.isra.4+0x6c/0x70
  Modules linked in:
  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu
  Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 
10/02/2018
  RIP: 0010:topology_sane.isra.4+0x6c/0x70
  Call Trace:
  set_cpu_sibling_map+0x153/0x540
  start_secondary+0xb2/0x200
  secondary_startup_64+0xa5/0xb0
  #8 #9 #10 #11 #12 #13
   node #0, CPUs: #14 #15 #16 #17 #18 #19 #20
   node #1, CPUs: #21 #22 #23 #24 #25 #26 #27
  smp: Brought up 2 nodes, 28 CPUs

  This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10.

  The oops happens because topology_sane() checks to see if the Last
  Level Cache line matches across different CPUs, which it no longer
  does.

  [Fix]

  The fix comes in the form of the following upstream commit, which
  landed in Linux 4.17:

  commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2
  Author: Alison Schofield 
  Date: Fri Apr 6 17:21:30 2018 -0700
  Subject: x86,sched: Allow topologies where NUMA nodes share an LLC
  Link: 
https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2

  The commit adds a check for this particular family of Intel
  processors, and if the CPU family matches, it simply skips the check
  to topology_sane().

  The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with
  the only remarks being re-arranging #includes and small context
  fixups.

  [Testcase]

  Unfortunately, this is hardware specific. To test this, you need a
  Intel Skylake server processor which supports Sub-NUMA-Clustering.

  We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10
  that has successfully tested the below test kernels, with good
  results.

  Xenial 4.4 ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga

  Xenial 4.15 HWE ppa:
  

[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

[Thadeu Lima de Souza Cascardo]

https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11419106
/+listing-archive-extra

So, this package on my ppa is built for bionic, but should work on other
series too.

It has a service that will call a wrapper that will start the reproducer
and reboot. The reason for the reboot is because once we add a task to
net_prio cgroup, it will disable cgroup bpf and we can't call the
reproducer again. And the reproducer, though it can cause the refcount
to go below 0 every time, it won't always cause the exact crash from
this bug.

Once you want to disable the reproducer, you should add to the kernel
cmdline the parameter "systemd.mask=cgroup-bpf-net-prio-crash.service".
Then, you need to remove the package and can get your system back.

You may be running some service that will add a task to net_prio or
net_cls cgroup, thus preventing the reproducer to run at all (but not
stop it from rebooting your system over and over again). lxd comes to
mind here.

You may check that it's the case (before installing the reproducer) by looking 
at dmesg and searching for:
cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls 
activation

The following WARN is the demonstration that the refcount underflow has 
happened (though not the crash):
[   12.581125] [ cut here ]
[   12.585021] percpu ref (cgroup_bpf_release_fn) <= 0 (-357) after switching 
to atomic
[   12.585092] WARNING: CPU: 2 PID: 665 at lib/percpu-refcount.c:160 
percpu_ref_switch_to_atomic_rcu+0x12e/0x140

The crash will cause a panic and likely prevent the system from
rebooting, showing you have reproduced the issue.

If you never see the WARN, the bug has been mitigated, though it can
still happen if we modify the reproducer slightly to also change
net_cls.classid.

Cascardo.

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

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.

  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.

  [Test case]
  Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.

  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.

  --

  Reported from a user:

  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.

  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.

  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Ian Hand]

@Califa, I am sorry to hear for you bad experience.

@Kai-Heng, OK so I don't think I have the proper know-how to
successfully set up the systemd oneshot service. However, the best
solution I currently have set up is a keyboard shortcut that runs a bash
script that resets the touchpad on demand whenever it may fail again in
the future.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default 

[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login

[altadeos]

dmesg on latest mainline kernel

** Attachment added: "dmesg-5.8.0-RC4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+attachment/5391132/+files/dmesg-5.8.0-RC4

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login

[altadeos]

lspci -vnvn on latest mainline kernel

** Attachment added: "lspci-5.8.0-RC4-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+attachment/5391133/+files/lspci-5.8.0-RC4-vnvn.log

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login

[altadeos]

Hello,

Tried with the latest mainline kernel and the problem is the same.

uname -a

5.8.0-050800-generic #202007052030 SMP Mon Jul 6 00:37:33 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

Best regards

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Thanks for that.

I have a nVidia GeForce GTX 960M graphic card.

I am using proprietary drivers; I didn't need to do anything, it was
automatically installed when I first installed Ubuntu 20.04.

I've read on the page you sent me before, that I need to remove the
nVidia drivers before installing the new kernel.

Is that really necessary? They really insist on that point.

If so, how do I remove them and installing them back? I am looking for
answers in 'Ask Ubuntu', but as I didn't download the drivers and it was
automatic, I don't know how to do it.

Sorry, I'm a noob and I'm really scared of messing up with the system
as, although I have dual boot with Windows, I already have migrated
plenty of stuff and I don't want to have to re-install everything
back...

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

Title:
  Touchpad recognised as generic mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
  ideapadY700. My laptop recognises touchpad as mouse. I have no other
  mouse plugged.

  Touchpad firmware: 2ul001af
  Lenovo ideapad700-15ISK BIOS version: CDCN54WW

  I'm new in Ubuntu and I don't know much...

  ```$ uname -a```

  ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21
  12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux```

  ```$ dmesg | grep psmouse```

  ```[   30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 
failed.
  [   30.218879] psmouse serio1: elantech: failed to query firmware version.
  [  165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  ```

  ```$ xinput```

  ```⎡ Virtual core pointer id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Logitech Wheel Mouse   id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ```

  ```$ cat /proc/bus/input/devices```

  ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063
  N: Name="PS/2 Logitech Wheel Mouse"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input19
  U: Uniq=
  H: Handlers=mouse0 event16
  B: PROP=1
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3
  ```
  I have read a lot of solutions; I tried to use xorg, but it didn't work.
  When I removed it, it worked for a day (only) and I decided erase and 
re-install Ubuntu.

  Please help!
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nando  1137 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:24:24 2020
  InstallationDate: Installed on 2020-06-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80NV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  

[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.

  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.

  [Test case]
  Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.

  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.

  --

  Reported from a user:

  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.

  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.

  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 80050033
  [  696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 
003606e0
  [  696.397135] DR0:  DR1:  DR2: 

  [  696.397152] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  696.397169] Call Trace:
  [  696.397175]  
  [  696.397183]  sk_filter_trim_cap+0xd0/0x1b0
  [  696.397191]  tcp_v4_rcv+0x8b7/0xa80
  [  696.397199]  ip_local_deliver_finish+0x66/0x210
  [  696.397208]  ip_local_deliver+0x7e/0xe0
  [  696.397215]  ? ip_rcv_finish+0x430/0x430
  [  696.397223]  ip_rcv_finish+0x129/0x430
  [  696.397230]  ip_rcv+0x296/0x360
  [  696.397238]  ? inet_del_offload+0x40/0x40
  [  696.397249]  __netif_receive_skb_core+0x432/0xb80
  [  696.397261]  ? skb_send_sock+0x50/0x50
  [  696.397271]  ? tcp4_gro_receive+0x137/0x1a0
  [  696.397280]  __netif_receive_skb+0x18/0x60
  [  696.397290]  ? __netif_receive_skb+0x18/0x60
  [  696.397300]  netif_receive_skb_internal+0x45/0xe0
  [  696.397309]  napi_gro_receive+0xc5/0xf0
  [  696.397317]  xennet_poll+0x9ca/0xbc0
  [  696.397325]  net_rx_action+0x140/0x3a0
  [  696.397334]  __do_softirq+0xe4/0x2d4
  [  696.397344]  irq_exit+0xc5/0xd0
  [  696.397352]  xen_evtchn_do_upcall+0x30/0x50
  [  696.397361]  xen_hvm_callback_vector+0x90/0xa0
  [  696.397371]  
  [  696.397378] RIP: 0010:native_safe_halt+0x12/0x20
  [  696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: 
ff0c
  [  696.397405] RAX: 8efc1800 RBX: 0006 RCX: 

  [  696.397419] RDX:  RSI:  RDI: 

  [  696.397435] RBP: 94c4862cbe80 R08: 

[Kernel-packages] [Bug 1887011] [NEW] Xenial update: v4.4.230 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   v4.4.230 upstream stable release
   from git://git.kernel.org/

btrfs: cow_file_range() num_bytes and disk_num_bytes are same
btrfs: fix data block group relocation failure due to concurrent scrub
mm: fix swap cache node allocation mask
EDAC/amd64: Read back the scrub rate PCI register on F15h
mm/slub: fix stack overruns with SLUB_STATS
usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
kgdb: Avoid suspicious RCU usage warning
crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in 
milliseconds
hwmon: (max6697) Make sure the OVERT mask is set correctly
hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
virtio-blk: free vblk-vqs in error path of virtblk_probe()
i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
Revert "ALSA: usb-audio: Improve frames size computation"
SMB3: Honor 'seal' flag for multiuser mounts
SMB3: Honor persistent/resilient handle flags for multiuser mounts
cifs: Fix the target file was deleted when rename failed.
MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
netfilter: nf_conntrack_h323: lost .data_len definition for Q.931/ipv6
Linux 4.4.230
UBUNTU: upstream stable to v4.4.230

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v4.4.230 upstream stable release
+    from git://git.kernel.org/
  
-v4.4.230 upstream stable release
-from git://git.kernel.org/
+ btrfs: cow_file_range() num_bytes and disk_num_bytes are same
+ btrfs: fix data block group relocation failure due to concurrent scrub
+ mm: fix swap cache node allocation mask
+ EDAC/amd64: Read back the scrub rate PCI register on F15h
+ mm/slub: fix stack overruns with SLUB_STATS
+ usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
+ kgdb: Avoid suspicious RCU usage warning
+ crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
+ sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in 
milliseconds
+ hwmon: (max6697) Make sure the OVERT mask is set correctly
+ hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
+ virtio-blk: free vblk-vqs in error path of virtblk_probe()
+ i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
+ Revert "ALSA: usb-audio: Improve frames size computation"
+ SMB3: Honor 'seal' flag for multiuser mounts
+ SMB3: Honor persistent/resilient handle flags for multiuser mounts
+ cifs: Fix the target file was deleted when rename failed.
+ MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
+ netfilter: nf_conntrack_h323: lost .data_len definition for Q.931/ipv6
+ Linux 4.4.230
+ UBUNTU: upstream stable to v4.4.230

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

Title:
  Xenial update: v4.4.230 upstream stable release

Status in linux package in Ubuntu:
  

[Kernel-packages] [Bug 1877461] Re: Bionic update: upstream stable patchset 2020-05-07

[Khaled El Mously]

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

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

Title:
  Bionic update: upstream stable patchset 2020-05-07

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-05-07

  Ported from the following upstream stable releases:
  v4.14.178, v4.19.119

     from git://git.kernel.org/

  ext4: fix extent_status fragmentation for plain files
  net: ipv4: avoid unused variable warning for sysctl
  drm/msm: Use the correct dma_sync calls harder
  crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static
  vti4: removed duplicate log message.
  watchdog: reset last_hw_keepalive time at start
  scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
  ceph: return ceph_mdsc_do_request() errors from __get_parent()
  ceph: don't skip updating wanted caps when cap is stale
  pwm: rcar: Fix late Runtime PM enablement
  scsi: iscsi: Report unbind session event when the target has been removed
  ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map()
  kernel/gcov/fs.c: gcov_seq_next() should increase position index
  selftests: kmod: fix handling test numbers above 9
  ipc/util.c: sysvipc_find_ipc() should increase position index
  s390/cio: avoid duplicated 'ADD' uevents
  pwm: renesas-tpu: Fix late Runtime PM enablement
  pwm: bcm2835: Dynamically allocate base
  perf/core: Disable page faults when getting phys address
  PCI/ASPM: Allow re-enabling Clock PM
  mm, slub: restore the original intention of prefetch_freepointer()
  cxgb4: fix large delays in PTP synchronization
  ipv6: fix restrict IPV6_ADDRFORM operation
  macsec: avoid to set wrong mtu
  macvlan: fix null dereference in macvlan_device_event()
  net: bcmgenet: correct per TX/RX ring statistics
  net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
  net/x25: Fix x25_neigh refcnt leak when receiving frame
  tcp: cache line align MAX_TCP_HEADER
  team: fix hang in team_mode_get()
  net: dsa: b53: Fix ARL register definitions
  xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
  vrf: Check skb for XFRM_TRANSFORMED flag
  KEYS: Avoid false positive ENOMEM error on key read
  ALSA: hda: Remove ASUS ROG Zenith from the blacklist
  iio: adc: stm32-adc: fix sleep in atomic context
  iio: xilinx-xadc: Fix ADC-B powerdown
  iio: xilinx-xadc: Fix clearing interrupt when enabling trigger
  iio: xilinx-xadc: Fix sequencer configuration for aux channels in 
simultaneous mode
  fs/namespace.c: fix mountpoint reference counter race
  USB: sisusbvga: Change port variable from signed to unsigned
  USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 
RGB RAPIDFIRE
  USB: early: Handle AMD's spec-compliant identifiers, too
  USB: core: Fix free-while-in-use bug in the USB S-Glibrary
  USB: hub: Fix handling of connect changes during sleep
  overflow.h: Add arithmetic shift helper
  vmalloc: fix remap_vmalloc_range() bounds checks
  mm/hugetlb: fix a addressing exception caused by huge_pte_offset
  mm/ksm: fix NULL pointer dereference when KSM zero page is enabled
  tools/vm: fix cross-compile build
  ALSA: usx2y: Fix potential NULL dereference
  ALSA: hda/realtek - Add new codec supported for ALC245
  ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
  ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices
  tpm/tpm_tis: Free IRQ if probing fails
  tpm: ibmvtpm: retry on H_CLOSED in tpm_ibmvtpm_send()
  KVM: Check validity of resolved slot when searching memslots
  KVM: VMX: Enable machine check support for 32bit targets
  tty: hvc: fix buffer overflow during hvc_alloc().
  tty: rocket, avoid OOB access
  usb-storage: Add unusual_devs entry for JMicron JMS566
  audit: check the length of userspace generated audit records
  ASoC: dapm: fixup dapm kcontrol widget
  iwlwifi: pcie: actually release queue memory in TVQM
  ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y
  powerpc/setup_64: Set cache-line-size based on cache-block-size
  staging: comedi: dt2815: fix writing hi byte of analog output
  staging: comedi: Fix comedi_device refcnt leak in comedi_open
  vt: don't hardcode the mem allocation upper bound
  staging: vt6656: Don't set 

[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic

[Colin Ian King]

Fix committed on the scrub failure: https://kernel.ubuntu.com/git/ubuntu
/autotest-client-
tests.git/commit/?id=f3234a34ecfd81a78fc58aebd6398c40aa097809

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

Title:
  zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in
  Bionic

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz

  The dkms tests are failing for two reasons:
  1. spl-linux can't be installed (see bug 1885285).
  2. test kernel-smoke-test fails with the following error:

  autopkgtest [16:08:43]: test kernel-smoke-test: [---
  kernel smoke test, create and destroy pool, 2x2 mirror: PASSED
  kernel smoke test, create and destroy pool, 4x1 mirror: PASSED
  kernel smoke test, create and destroy pool, nested raidz3: PASSED
  kernel smoke test, create and destroy pool, raidz1: PASSED
  kernel smoke test, create and destroy pool, raidz2: PASSED
  kernel smoke test, create and destroy pool, raidz3: PASSED
  kernel smoke test, create and destroy pool, striped: PASSED
  kernel smoke test, create and destroy ZFS Intent Log: PASSED
  kernel smoke test, create and destroy ZFS filesystems: PASSED
  kernel smoke test, ZFS snapshot: PASSED
  kernel smoke test, ZFS clone: PASSED
  kernel smoke test, ZFS send and receive: PASSED
  kernel smoke test, corrupt data and clean with a scrub: cannot scrub 
pool-smoke-6551: currently resilvering
  FAILED: zpool scrub failed, exit code=1
  autopkgtest [16:09:24]: test kernel-smoke-test: ---]

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

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

[Kernel-packages] [Bug 237318] Re: Scroll wheel not working on Logitech Trackman Wheel

[Philippe Coval]

I know it's invalid for long time ,
but my scroll wheel isnt working on my 20.04, and I dont remember it worked on 
earlier versions


Any clue ?

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

does not help

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

Title:
  Scroll wheel not working on Logitech Trackman Wheel

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu Hardy (and Gutsy), the scroll wheel of a Logitech Trackman
  wheel is not working.

  Only scroll events are affected. Middle click is working as expected.

  Also, xev doesn't show any event for the scroll actions.

  lsusb : Bus 004 Device 003: ID 046d:c404 Logitech, Inc. TrackMan Wheel

  Autogenerated xorg.conf :

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"

  EndSection

  Section "InputDevice"
Identifier  "Synaptics Touchpad"
Driver  "synaptics"
Option  "SendCoreEvents""true"
Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"
Option  "HorizEdgeScroll"   "0"
  EndSection

  Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"
InputDevice "Synaptics Touchpad"
  EndSection

  (the trackman is connected to a laptop with a touchpad)

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

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

[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

[Thadeu Lima de Souza Cascardo]

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Invalid

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

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

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

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

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

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

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.

  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.

  [Test case]
  Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.

  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.

  --

  Reported from a user:

  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.

  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.

  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 80050033
  [  696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 
003606e0
  [  696.397135] DR0:  DR1:  DR2: 

  [  696.397152] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  696.397169] Call Trace:
  [  696.397175]  
  [  696.397183]  sk_filter_trim_cap+0xd0/0x1b0
  [  696.397191]  tcp_v4_rcv+0x8b7/0xa80
  [  696.397199]  ip_local_deliver_finish+0x66/0x210
  [  696.397208]  ip_local_deliver+0x7e/0xe0
  [  696.397215]  ? ip_rcv_finish+0x430/0x430
  [  696.397223]  ip_rcv_finish+0x129/0x430
  [  696.397230]  ip_rcv+0x296/0x360
  [  696.397238]  ? inet_del_offload+0x40/0x40
  [  696.397249]  __netif_receive_skb_core+0x432/0xb80
  [  696.397261]  ? skb_send_sock+0x50/0x50
  [  696.397271]  ? tcp4_gro_receive+0x137/0x1a0
  [  696.397280]  __netif_receive_skb+0x18/0x60
  [  696.397290]  ? __netif_receive_skb+0x18/0x60
  [  696.397300]  netif_receive_skb_internal+0x45/0xe0
  [  696.397309]  napi_gro_receive+0xc5/0xf0
  [  696.397317]  xennet_poll+0x9ca/0xbc0
  [  696.397325]  net_rx_action+0x140/0x3a0
  [  696.397334]  __do_softirq+0xe4/0x2d4
  [  696.397344]  

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Noctis Bennington]

Same result Kai-Heng. :(

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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

[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown

[Tim Ryder]

The butter zone for me seems to be 60% which lets the CPU go as high as
2.40GHZ while maxing the temp at around 80C when gaming.

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed
Status in Gentoo Linux:
  New

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

[Robert Boerner]

@Hui,

Thank you for your efforts here, they are much appreciated.

You ask,"...if you plug sth into the 3.5mm audio jack, does the output
change to lineout/headphone?"

I am afraid I am not sure what 'sth' means when you say, '...plug sth
into the 3.5mm audio jack...'

Does 'sth' refer to stereo headphones? (as opposed to stereo speakers)

Apologies in advance if the question is in any way redundant, however I
just want to make sure I understand your wishes correctly and not make
any incorrect assumptions.

Just to reiterate and to be clear, at every point during my testing
standard analog speakers have been powered on and connected to the host
system's 3.5mm audio output jack.

To put that another way, I am testing with a 'real' hardware setup.

This is documented in the demonstration video I made about the problem
--> https://youtu.be/gJNpK3Mgw2U

Assuming for the moment that my understanding as described is correct, I
tested again in the following manner:

1. Simple stereo headphones connected to the 3.5mm analog audio output port of 
the host.
2. Ran 'pactl list' command.
3. Relevant snippet from the tool output is identical to what is seen in the 
previous log (and what you describe):

analog-output-lineout: Line Out (priority: 9000, latency offset: 0 usec, not 
available)
   Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo

4. Disconnected stereo headphones from host system.
5. Connected stereo analog speakers to the 3.5mm analog audio output port of 
the host.
6. Ran 'pactl list' command again.
7. Relevant snippet from the tool output is identical as before:

analog-output-lineout: Line Out (priority: 9000, latency offset: 0 usec, not 
available)
   Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo

8. In both cases despite having an audio output device connected to the
host, the entry in the log file output is still listed as 'not
available'


Please let me know if I can provide any additional information, and thank you 
as always for the help!

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

Title:
  [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1215 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Intel(R) Client Systems NUC8CCHK
  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
  

[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible

[Oliver Grawert]

in fact it seems like in 5.3 USB is not working at all !!! i verified
that today ...

my self-built kernel uses the focal 5.4 branch where USB works fine
then:

https://github.com/ogra1/linux-raspberrypi-
org/blob/master/snap/snapcraft.yaml

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

Title:
  USB support missing in initrd makes booting core with writable on USB
  impossible

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Xenial:
  New
Status in linux-raspi2 source package in Bionic:
  Invalid
Status in linux-raspi source package in Focal:
  New

Bug description:
  when using a gadget.yaml like:

  volumes:
    pi4-system-boot:
  schema: mbr
  bootloader: u-boot
  structure:
    - type: 0C
  filesystem: vfat
  filesystem-label: system-boot
  size: 512M
  content:
    - source: boot-assets/
  target: /
    pi4-usb-writable:
  schema: mbr
  structure:
    - name: writable
  type: 83
  filesystem: ext4
  filesystem-label: writable
  size: 650M
  role: system-data

  this creates two separate img files for a Pi image ... one for SD to
  hold the boot files, one for USB that carries the rootfs ...

  sadly our kernel will then not find the writable partition because it
  lacks support for usb disks (usb-storage seems to be there but not
  sufficient)

  adding the following to a re-built kernel snap makes everything work
  (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys)

    - CONFIG_ENCLOSURE_SERVICES=y
    - CONFIG_SCSI_SAS_ATTRS=y
    - CONFIG_USB_STORAGE=y
    - CONFIG_USB_UAS=y

  can we please have these either built into the kernel or added to the
  core initrd as modules ?

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

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

[Kernel-packages] [Bug 1886995] [NEW] Focal update: v5.4.51 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

io_uring: make sure async workqueue is canceled on exit
mm: fix swap cache node allocation mask
EDAC/amd64: Read back the scrub rate PCI register on F15h
usbnet: smsc95xx: Fix use-after-free after removal
sched/debug: Make sd->flags sysctl read-only
mm/slub.c: fix corrupted freechain in deactivate_slab()
mm/slub: fix stack overruns with SLUB_STATS
rxrpc: Fix race between incoming ACK parser and retransmitter
usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
tools lib traceevent: Add append() function helper for appending strings
tools lib traceevent: Handle __attribute__((user)) in field names
s390/debug: avoid kernel warning on too large number of pages
nvme-multipath: set bdi capabilities once
nvme-multipath: fix deadlock between ana_work and scan_work
nvme-multipath: fix deadlock due to head->lock
nvme-multipath: fix bogus request queue reference put
kgdb: Avoid suspicious RCU usage warning
selftests: tpm: Use /bin/sh instead of /bin/bash
crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
drm/msm/dpu: fix error return code in dpu_encoder_init
rxrpc: Fix afs large storage transmission performance drop
RDMA/counter: Query a counter before release
cxgb4: use unaligned conversion for fetching timestamp
cxgb4: parse TC-U32 key values and masks natively
cxgb4: fix endian conversions for L4 ports in filters
cxgb4: use correct type for all-mask IP address comparison
cxgb4: fix SGE queue dump destination buffer context
hwmon: (max6697) Make sure the OVERT mask is set correctly
hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
thermal/drivers/mediatek: Fix bank number settings on mt8183
thermal/drivers/rcar_gen3: Fix undefined temperature if negative
nfsd4: fix nfsdfs reference count loop
nfsd: fix nfsdfs inode reference count leak
drm: sun4i: hdmi: Remove extra HPD polling
virtio-blk: free vblk-vqs in error path of virtblk_probe()
SMB3: Honor 'posix' flag for multiuser mounts
nvme: fix identify error status silent ignore
nvme: fix a crash in nvme_mpath_add_disk
samples/vfs: avoid warning in statx override
i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
i2c: mlxcpld: check correct size of maximum RECV_LEN packet
spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
nfsd: apply umask on fs without ACL support
Revert "ALSA: usb-audio: Improve frames size computation"
SMB3: Honor 'seal' flag for multiuser mounts
SMB3: Honor persistent/resilient handle flags for multiuser mounts
SMB3: Honor lease disabling for multiuser mounts
SMB3: Honor 'handletimeout' flag for multiuser mounts
cifs: Fix the target file was deleted when rename failed.
MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names
MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
drm/amd/display: Only revalidate bandwidth on medium and fast updates
drm/amdgpu: use %u rather than %d for sclk/mclk
drm/amdgpu/atomfirmware: fix vram_info fetching for renoir
dma-buf: Move dma_buf_release() from fops to dentry_ops
irqchip/gic: Atomically update affinity
mm, compaction: fully assume capture is not NULL in compact_zone_order()
mm, compaction: make capture control handling safe wrt interrupts
x86/resctrl: Fix memory bandwidth counter width for AMD
dm zoned: assign max_io_len correctly
UBUNTU: [Config] updateconfigs for EFI_CUSTOM_SSDT_OVERLAYS
efi: Make it possible to disable efivar_ssdt entirely
Linux 5.4.51
UBUNTU: upstream stable to v5.4.51

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a 

[Kernel-packages] [Bug 1885671] Re: Touchpad is not detected - HP Probok 430 G2

[Alex Hung]

@azimcuetcse01,

I believed vicamo meant the procedures in comment #2, such as

  1. upload logs by running "apport-collect 1885671"
  2. change bug status to "confirm"

Please update to latest packages and kernel (sudo apt update && sudo apt
upgrade -y && sudo reboot) and reproduce the bug before you upload logs.

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

Title:
  Touchpad is not detected - HP Probok 430 G2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Touchpad is not detected in my newly installed Ububtu 5.4.0-39. I have
  checked "/proc/bus/input/devices" but havent seen any TouchPad info

  
  Device: HP ProBookk 430 G2

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

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

[Kernel-packages] [Bug 1864669] Re: overlayfs regression - internal getxattr operations without sepolicy checking

[Marcelo Cerri]

** Summary changed:

- [linux-azure] overlayfs regression - internal getxattr operations without 
sepolicy checking
+ overlayfs regression - internal getxattr operations without sepolicy checking

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

Title:
  overlayfs regression - internal getxattr operations without sepolicy
  checking

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

Bug description:
  Bug description and repro:

  Run the following commands on host instances:

  Prepare the overlayfs directories:
  $ cd /tmp
  $ mkdir -p base/dir1/dir2 upper olwork merged
  $ touch base/dir1/dir2/file
  $ chown -R 10:10 base upper olwork merged

  Verify that the directory is owned by user 10:
  $ ls -al merged/ 
  total 8
  drwxr-xr-x  2 10 10 4096 Nov  1 07:08 .
  drwxrwxrwt 16 root   root   4096 Nov  1 07:08 ..

  We use lxc-usernsexec to start a new shell as user 10.
  $ lxc-usernsexec -m b:0:10:1 -- /bin/bash
  $$ ls -al merged/
  total 8
  drwxr-xr-x  2 root   root4096 Nov  1 07:08 .
  drwxrwxrwt 16 nobody nogroup 4096 Nov  1 07:08 ..

  Notice that the ownership of . and .. has changed because the new shell is 
running as the remapped user.
  Now, mount the overlayfs as an unprivileged user in the new shell. This is 
the key to trigger the bug.
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2/file 
  -rw-r--r-- 1 root root 0 Nov  1 07:09 merged/dir1/dir2/file

  We can see the file in the base layer from the mount directory. Now trigger 
the bug:
  $$ rm -rf merged/dir1/dir2/
  $$ mkdir merged/dir1/dir2
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 2 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..

  File does not show up in the newly created dir2 as expected. But it will 
reappear after we remount the filesystem (or any other means that might evict 
the cached dentry, such as attempt to delete the parent directory):
  $$ umount merged
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..
  -rw-r--r-- 1 root root0 Nov  1 07:09 file
  $$ exit
  $

  This is a recent kernel regression. I tried the above step on an old
  kernel (4.4.0-1072-aws) but cannot reproduce.


  I looked up linux source code and figured out where the "regression" is 
coming from. The issue lies in how overlayfs checks the "opaque" flag from the 
underlying upper-level filesystem. It checks the "trusted.overlay.opaque" 
extended attribute to decide whether to hide the directory content from the 
lower level. The logic are different in 4.4 and 4.15 kernel.
  In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
int res;
char val;
struct inode *inode = dentry->d_inode;

if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;

res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  In 4.15: 
https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
  }

  bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
  {
int res;
char val;

if (!d_is_dir(dentry))
return false;

res = vfs_getxattr(dentry, name, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  The 4.4 version simply uses the internal i_node callback 
inode->i_op->getxattr from the host filesystem, which doesn't perform any 
permission check. While the 4.15 version calls the VFS interface vfs_getxattr 
that performs bunch of permission checks before the 

[Kernel-packages] [Bug 1864669] Re: [linux-azure] overlayfs regression - internal getxattr operations without sepolicy checking

[Marcelo Cerri]

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

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Invalid

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

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

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

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

Title:
  [linux-azure] overlayfs regression - internal getxattr operations
  without sepolicy checking

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

Bug description:
  Bug description and repro:

  Run the following commands on host instances:

  Prepare the overlayfs directories:
  $ cd /tmp
  $ mkdir -p base/dir1/dir2 upper olwork merged
  $ touch base/dir1/dir2/file
  $ chown -R 10:10 base upper olwork merged

  Verify that the directory is owned by user 10:
  $ ls -al merged/ 
  total 8
  drwxr-xr-x  2 10 10 4096 Nov  1 07:08 .
  drwxrwxrwt 16 root   root   4096 Nov  1 07:08 ..

  We use lxc-usernsexec to start a new shell as user 10.
  $ lxc-usernsexec -m b:0:10:1 -- /bin/bash
  $$ ls -al merged/
  total 8
  drwxr-xr-x  2 root   root4096 Nov  1 07:08 .
  drwxrwxrwt 16 nobody nogroup 4096 Nov  1 07:08 ..

  Notice that the ownership of . and .. has changed because the new shell is 
running as the remapped user.
  Now, mount the overlayfs as an unprivileged user in the new shell. This is 
the key to trigger the bug.
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2/file 
  -rw-r--r-- 1 root root 0 Nov  1 07:09 merged/dir1/dir2/file

  We can see the file in the base layer from the mount directory. Now trigger 
the bug:
  $$ rm -rf merged/dir1/dir2/
  $$ mkdir merged/dir1/dir2
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 2 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..

  File does not show up in the newly created dir2 as expected. But it will 
reappear after we remount the filesystem (or any other means that might evict 
the cached dentry, such as attempt to delete the parent directory):
  $$ umount merged
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..
  -rw-r--r-- 1 root root0 Nov  1 07:09 file
  $$ exit
  $

  This is a recent kernel regression. I tried the above step on an old
  kernel (4.4.0-1072-aws) but cannot reproduce.


  I looked up linux source code and figured out where the "regression" is 
coming from. The issue lies in how overlayfs checks the "opaque" flag from the 
underlying upper-level filesystem. It checks the "trusted.overlay.opaque" 
extended attribute to decide whether to hide the directory content from the 
lower level. The logic are different in 4.4 and 4.15 kernel.
  In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
int res;
char val;
struct inode *inode = dentry->d_inode;

if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;

res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  In 4.15: 
https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
  }

  bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
  {
int res;
char val;

if (!d_is_dir(dentry))
return false;

res = vfs_getxattr(dentry, name, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  The 4.4 version simply uses the internal i_node callback 

[Kernel-packages] [Bug 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554

[Abhishek Shingade]

@You-Sheng Yang (vicamo) , I have added the ppa:vicamo/ppa-1886257 .
When the update happens , I will inform you , via the comment section

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

Title:
  Touchpad detection issue in Fujitsu Lifebook UH554

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop model : Fujitsu Lifebook UH554

  Ram : 8 GB

  HDD : 500 GB

  Processor : i5

  Manufacturer of the Touchpad : Unknown

  
  When the symptom first appeared : After installing the OS 20.04 itself
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shingade   1340 F pulseaudio
   /dev/snd/controlC0:  shingade   1340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd 
   Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK UH554
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout 
i8042.nomux vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.25
  dmi.board.name: FJNBB34
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK UH554
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Califa101]

Okay. I have bad news to give you. I definitely think I'm going to return the 
laptop. Today I have been using the touchpad in Windows for a long time (I use 
the laptop almost always without a mouse) and it has several faults, although 
it does not always do them: the cursor does not stop where I want it to stop 
and also, in the Upon release, it makes a slight displacement in any direction.
It is a pity that, otherwise, this laptop is very good value for money.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 

[Kernel-packages] [Bug 1886588] Re: ath10k_pci often crashes in focal

[Alex Hung]

The log in description clearly points out "firmware crashed", and that
may be something we can forward to the hardware vendor.

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

Title:
  ath10k_pci often crashes in focal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WIreless connectivity has been very flaky in focal ever since release.
  Thought I'd start investigating a bit. This is all I found, but it
  clearly signisfies an error. Please let med know, if I can provide
  more information.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware crashed! (guid 
ba24fee9-d0cb-42e2-9aef-06f0d07a053e)
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: board_file api 2 bmi_id 
N/A crc32 4ac0889b
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: htt-ver 3.60 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to get memcpy hi 
address for firmware address 4: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read firmware 
dump area: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: Copy Engine register 
dump:
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [00]: 0x00034400  11  11 
  3   3
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [01]: 0x00034800   3   2 
175 176
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [02]: 0x00034c00  12  11 
 10  11
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [03]: 0x00035000  12  12 
 14  12
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [04]: 0x00035400 6557 
6549  11 203
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [05]: 0x00035800   0   0 
 64   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [06]: 0x00035c00   3   1 
 10   8
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [07]: 0x00036000   1   0 
  1   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read 
hi_board_data address: -28
  [ma. juli  6 23:16:51 2020] ieee80211 phy0: Hardware restart was requested
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: unsupported HTC service 
id: 1536
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: device successfully 
recovered
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature above threshold, cpu 
clock throttled (total events = 6714)
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature/speed normal
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] veth76e34af: renamed from eth0
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] device veth76af7ee left promiscuous mode
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:18 2020] wlp59s0: deauthenticating from 00:22:07:80:6c:2e 
by local choice (Reason: 3=DEAUTH_LEAVING)
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 

[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic

[Colin Ian King]

Urgh. Looks like a timing issue again on the scrub status. I'll see if I
can make the test more resilient.

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

Title:
  zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in
  Bionic

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz

  The dkms tests are failing for two reasons:
  1. spl-linux can't be installed (see bug 1885285).
  2. test kernel-smoke-test fails with the following error:

  autopkgtest [16:08:43]: test kernel-smoke-test: [---
  kernel smoke test, create and destroy pool, 2x2 mirror: PASSED
  kernel smoke test, create and destroy pool, 4x1 mirror: PASSED
  kernel smoke test, create and destroy pool, nested raidz3: PASSED
  kernel smoke test, create and destroy pool, raidz1: PASSED
  kernel smoke test, create and destroy pool, raidz2: PASSED
  kernel smoke test, create and destroy pool, raidz3: PASSED
  kernel smoke test, create and destroy pool, striped: PASSED
  kernel smoke test, create and destroy ZFS Intent Log: PASSED
  kernel smoke test, create and destroy ZFS filesystems: PASSED
  kernel smoke test, ZFS snapshot: PASSED
  kernel smoke test, ZFS clone: PASSED
  kernel smoke test, ZFS send and receive: PASSED
  kernel smoke test, corrupt data and clean with a scrub: cannot scrub 
pool-smoke-6551: currently resilvering
  FAILED: zpool scrub failed, exit code=1
  autopkgtest [16:09:24]: test kernel-smoke-test: ---]

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Califa101]

I understand you, @Ian, but you will have the problem when you have to
use the laptop without being able to support the mouse ...

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  

[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic

[Kleber Sacilotto de Souza]

Note that this is not a regression, as the same testcase already failed with 
linux-hwe 5.3 based:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200611_034311_16319@/log.gz

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

Title:
  zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in
  Bionic

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz

  The dkms tests are failing for two reasons:
  1. spl-linux can't be installed (see bug 1885285).
  2. test kernel-smoke-test fails with the following error:

  autopkgtest [16:08:43]: test kernel-smoke-test: [---
  kernel smoke test, create and destroy pool, 2x2 mirror: PASSED
  kernel smoke test, create and destroy pool, 4x1 mirror: PASSED
  kernel smoke test, create and destroy pool, nested raidz3: PASSED
  kernel smoke test, create and destroy pool, raidz1: PASSED
  kernel smoke test, create and destroy pool, raidz2: PASSED
  kernel smoke test, create and destroy pool, raidz3: PASSED
  kernel smoke test, create and destroy pool, striped: PASSED
  kernel smoke test, create and destroy ZFS Intent Log: PASSED
  kernel smoke test, create and destroy ZFS filesystems: PASSED
  kernel smoke test, ZFS snapshot: PASSED
  kernel smoke test, ZFS clone: PASSED
  kernel smoke test, ZFS send and receive: PASSED
  kernel smoke test, corrupt data and clean with a scrub: cannot scrub 
pool-smoke-6551: currently resilvering
  FAILED: zpool scrub failed, exit code=1
  autopkgtest [16:09:24]: test kernel-smoke-test: ---]

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

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

[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd

[rud]

Thanks for the quick reply.

it is s2idle and the BIOS has no option to modify anything related to
this. There are only boot options, TPM that can be configured
unfortunately.

Should I provide more extensive logs as described here? I just do not know how 
to execute the pmtrace command, which arguments to use. 
https://wiki.ubuntu.com/DebuggingKernelSuspend

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

Title:
  limited hardware support AMD 4700u HP Envy x360 13-ay003nd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Hibernate:
  screen goes off, nothing else happens. After user interaction, screen turns 
on. Login screen is shown. Sometimes screen does not turn on: physical reboot 
required.
  kernel upgrade to 5.8rc3 or 5.8rc4 has no effect.

  Brightness:
  Adjusting brightness has no effect, nightmode has no effect.
  Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, 
brightness can be adjusted and nightmode works But after a reboot brightness is 
always at max. Also brightness cannot be lowered as much as normally expected.

  CPU & fan:
  CPU is always high, 5.8rc3 solves this partially, fan is still always on and 
quite high (after clean Ubuntu install, nothing configured or installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  asterix 881 F pulseaudio
   /dev/snd/controlC1:  asterix 881 F pulseaudio
   /dev/snd/controlC0:  asterix 881 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jul  9 12:21:02 2020
  InstallationDate: Installed on 2020-07-09 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.30
  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.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 1D5H9EA#ABH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554

[You-Sheng Yang]

@Abhishek, I'm trying to upstream necessary change for this device so
that you don't have to carry additional boot parameters anymore. PPA for
testing is at https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1886257,
but it might take up to hours before finishes. After those kernel
packages are built and published into that PPA, I'll need your
verification before going on to submit patch to kernel mailing list.
Please attach dmesg of either prebuilt kernel and the device validness
once it's done. Thank you.

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1886257

Title:
  Touchpad detection issue in Fujitsu Lifebook UH554

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop model : Fujitsu Lifebook UH554

  Ram : 8 GB

  HDD : 500 GB

  Processor : i5

  Manufacturer of the Touchpad : Unknown

  
  When the symptom first appeared : After installing the OS 20.04 itself
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shingade   1340 F pulseaudio
   /dev/snd/controlC0:  shingade   1340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd 
   Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK UH554
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout 
i8042.nomux vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.25
  dmi.board.name: FJNBB34
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK UH554
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD

[Sébastien Wertz]

Same issue here (logs filling up the disk because of wifi-related
messages; wifi connection lost) but with an older kernel version:
5.3.0-62-generic.

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

Title:
  Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel
  switch, iwlwifi Microcode SW Error: FW error in SYNC CMD
  CHANNEL_SWITCH_TIME_EVENT_CMD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33

  I occasionally see a message on my screen that disk space is low. I
  try rebooting since my computer is unresponsive. Normal reboot does
  not work, sudo reboot does not work. I have to power off the machine
  using power button. Machine boots but hangs because its trying to
  repair journal info.

  I can't see what causes that since I was not using my computer at the time.
  edit: see comment #14

  So with a live session, I can see that syslog and kern.log files have
  grown to several GB until the drive is full.

  When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any 
problem so far.
  edit: not true actually, this happened again using this upstream kernel.

  Never had this issue with previous Ubuntu versions with the very same
  hardware configuration, since 16.04.

  Included: partial syslog and kern.log with the same message repeated over and 
over.
  edit: and when the event starts.

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

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

[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly

[Colin Ian King]

Can you inform me the exact test configuration you were using?

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

Title:
  ZFS performance drops suddenly

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Run Phoronix Flexible IO / Random write benchmark.  
  After running the benchmark repeatedly multiple times (occasionally it can be 
30 minutes or 8 hours), the performance drops suddenly. The only way (I know 
of) to get back to high performance is reboot.
  ---
  $ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" | 
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops; 
done
  $ less /tmp/iops
  ...
  2095
  2095
  2093
  783
  388
  389
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.7.5-1ubuntu16.9
  ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
  Uname: Linux 5.3.0-1023-aws x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Tue Jun 16 08:55:01 2020
  Ec2AMI: ami-06fd83ae47b05282f
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1f
  Ec2InstanceType: c4.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [deleted]

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

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

[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly

[Colin Ian King]

Oh, no problem, I can see that in the bug report. Apologies.

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

Title:
  ZFS performance drops suddenly

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Run Phoronix Flexible IO / Random write benchmark.  
  After running the benchmark repeatedly multiple times (occasionally it can be 
30 minutes or 8 hours), the performance drops suddenly. The only way (I know 
of) to get back to high performance is reboot.
  ---
  $ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" | 
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops; 
done
  $ less /tmp/iops
  ...
  2095
  2095
  2093
  783
  388
  389
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.7.5-1ubuntu16.9
  ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
  Uname: Linux 5.3.0-1023-aws x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Tue Jun 16 08:55:01 2020
  Ec2AMI: ami-06fd83ae47b05282f
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1f
  Ec2InstanceType: c4.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [deleted]

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

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

[Kernel-packages] [Bug 1878507] Re: No HDMI audio in ubuntu 20.04

[Kai-Heng Feng]

Can you please temporarily remove "~/.config/pulse/* " and attach `pactl
list cards` here? Thanks!

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

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

** Changed in: pulseaudio (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/1878507

Title:
  No HDMI audio in ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sound settings does not offer hdmi audio in 20.04, but was there in 16 and 18 
LTSs.
  New HDMI monitor is fine but no audio. Reboot to Ubuntu 16.04.1 LTS (16.04) 
{linux /boot/vmlinuz-4.4.0-24-generic} and all is well.

  ALSA Information Script v 0.4.65 ran giving result at:
  http://alsa-project.org/db/?f=84926788cff2eb5d8d305d6a896608514495ce2f

  Deleting ~/.config/pulse/* broke all the sound but ok again when
  restored

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1715 F pulseaudio
   /dev/snd/controlC1:  paul   1715 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 01:06:50 2020
  HibernationDevice: RESUME=UUID=6ee76bfb-393c-47bf-807f-6d0d8929c120
  InstallationDate: Installed on 2016-06-15 (1428 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a0ad560d-ee6e-4f49-b40f-d239ecfcf167 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-06 (7 days ago)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0915
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0915:bd12/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1885349] Re: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in

[Kai-Heng Feng]

should be -37...

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

Title:
  Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after
  logging in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my kids' computer to the 5.4.0-39-generic kernel today.
  Afterwards, the screen started freezing very shortly after logging in.

  When choosing the older 5.4.0-37-generic from the grub menu I see no
  crashes at all.

  I could login over SSH from my computer without difficulty. Running
  dmesg showed some variation of the following. For example, just now it
  crashed when my daughter tried to launch Firefox after logging in, and
  the following appeared while I was watching the output of 'dmesg -w':

  68.824967] NVRM: GPU at PCI::01:00: 
GPU-7f44f739-3c25-c282-d7a3-c4ec7c79e755
  [   68.824970] NVRM: GPU Board Serial Number:
  [   68.824974] NVRM: Xid (PCI::01:00): 79, pid=926, GPU has fallen off 
the bus.
  [   68.824976] NVRM: GPU :01:00.0: GPU has fallen off the bus.
  [   68.824977] NVRM: GPU :01:00.0: GPU is on Board .
  [   68.826134] NVRM: A GPU crash dump has been created. If possible, please 
run
     NVRM: nvidia-bug-report.sh as root to collect this data before
     NVRM: the NVIDIA kernel module is unloaded

  The system has been running beautifully up until today. Installing the
  other driver versions listed below didn't help any.

  $ sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1C82sv1458sd3746bc03sc00i00
  vendor   : NVIDIA Corporation
  model: GP107 [GeForce GTX 1050 Ti]
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sat Jun 27 16:27:12 2020
  HibernationDevice: RESUME=UUID=447e6756-8310-4bc0-9ccc-108f1df5019b
  InstallationDate: Installed on 2014-07-08 (2180 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=464ea2d6-bc69-4340-88ed-33902e231ef3 ro mds=off mitigations=off quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97N-WIFI
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.

[Frank Heimes]

Well, we do drive our storage sub-system from time to time to the limits - 
especially if we do parallel LPAR deployments for OpenStack environments.
But that's on a z13 and a DS8k - and so far we never saw such issues in this 
environment.

Further investigations in Launchpad did not resulted in further
references to similar reports like this, with SCSI / wbt (or wbt in
general) on focal.

However, I found that there were wbt, respectively blk-wbt, issues in the past 
with kernels > 4.10 and < v4.19 that partially led to CPU hard lockups on heavy 
writes (largely reported on NVMe drives).
But those bugs where only reported on bionic (and cosmic) - which fits to the 
kernel range above - and got fixed quite some time ago.
The bionic (and cosmic) kernels where patched via backports of:
2887e41b910b - "blk-wbt: Avoid lock contention and thundering herd issue in 
wbt_wait"
38cfb5a45ee0 - "blk-wbt: improve waking of tasks"
I just double checked that the fixes from those tickets are (still) in, and 
they are.

With only having heard about this problem in this bug here, I agree that 
recommending to turn WBT off in general would not be good - even preferring 
stability over performance.
(I still have the suspicion that it could be XIV related, rather than general 
block or SCSI layer...)

However, for now we may add a statement to the s390x section of the
release notes pointing to WBT and the udev rule for disabling it for the
block-devices, in case one hits such issues under high disk I/O stress.

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

Title:
  [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be
  triggered by scsi errors.

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

Bug description:
  We can reproduce a crash in the block layer with lots of stress on
  lots of SCSI disks (on an XIV storage server).

  We seem to have several scsi stalls in the logs/errors (needs to be
  analyzed further) but in the end we do crash with this this calltrace.

  [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403
  [20832.901159] Fault in home space mode while using kernel ASCE.
  [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 
S:03fc1cc78800 P:0400 
  [20832.901264] Oops: 0011 ilc:2 [#1] SMP 
  [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables 
iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw 
vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash 
dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 
libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup
  [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 
5.4.0-29-generic #33-Ubuntu
  [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR)
  [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be 
(try_to_wake_up+0x4e/0x700)
  [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 
0003
  [20832.901750] 004c 040003fd005a4600 
0003
  [20832.901753]0003 7fe00dea8454  
7fe00dea7b00
  [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 
7fe0021c7a60
  [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la  
%r9,2388(%r2)
01d3cbd559b6: 582003acl   
%r2,940
   #01d3cbd559ba: a718lhi %r1,0
   >01d3cbd559be: ba129000cs  
%r1,%r2,0(%r9)
01d3cbd559c2: a77401c9brc 
7,01d3cbd55d54
01d3cbd559c6: e310b0080004lg  
%r1,8(%r11)
01d3cbd559cc: b9800018ngr 
%r1,%r8
01d3cbd559d0: a774001fbrc 
7,01d3cbd55a0e
  [20832.901784] Call Trace:
  [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474)
  [20832.901823]  

[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1886912

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1885349] Re: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in

[Kai-Heng Feng]

Hmm, there aren't many change between -37 and -39. Can you please attach
dmesg under -39?

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

Title:
  Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after
  logging in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my kids' computer to the 5.4.0-39-generic kernel today.
  Afterwards, the screen started freezing very shortly after logging in.

  When choosing the older 5.4.0-37-generic from the grub menu I see no
  crashes at all.

  I could login over SSH from my computer without difficulty. Running
  dmesg showed some variation of the following. For example, just now it
  crashed when my daughter tried to launch Firefox after logging in, and
  the following appeared while I was watching the output of 'dmesg -w':

  68.824967] NVRM: GPU at PCI::01:00: 
GPU-7f44f739-3c25-c282-d7a3-c4ec7c79e755
  [   68.824970] NVRM: GPU Board Serial Number:
  [   68.824974] NVRM: Xid (PCI::01:00): 79, pid=926, GPU has fallen off 
the bus.
  [   68.824976] NVRM: GPU :01:00.0: GPU has fallen off the bus.
  [   68.824977] NVRM: GPU :01:00.0: GPU is on Board .
  [   68.826134] NVRM: A GPU crash dump has been created. If possible, please 
run
     NVRM: nvidia-bug-report.sh as root to collect this data before
     NVRM: the NVIDIA kernel module is unloaded

  The system has been running beautifully up until today. Installing the
  other driver versions listed below didn't help any.

  $ sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1C82sv1458sd3746bc03sc00i00
  vendor   : NVIDIA Corporation
  model: GP107 [GeForce GTX 1050 Ti]
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sat Jun 27 16:27:12 2020
  HibernationDevice: RESUME=UUID=447e6756-8310-4bc0-9ccc-108f1df5019b
  InstallationDate: Installed on 2014-07-08 (2180 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=464ea2d6-bc69-4340-88ed-33902e231ef3 ro mds=off mitigations=off quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97N-WIFI
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1885349] Re: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in

[Kai-Heng Feng]

Hmm, there aren't many change between -39 and -40. Can you please attach
dmesg under -39?

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

Title:
  Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after
  logging in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my kids' computer to the 5.4.0-39-generic kernel today.
  Afterwards, the screen started freezing very shortly after logging in.

  When choosing the older 5.4.0-37-generic from the grub menu I see no
  crashes at all.

  I could login over SSH from my computer without difficulty. Running
  dmesg showed some variation of the following. For example, just now it
  crashed when my daughter tried to launch Firefox after logging in, and
  the following appeared while I was watching the output of 'dmesg -w':

  68.824967] NVRM: GPU at PCI::01:00: 
GPU-7f44f739-3c25-c282-d7a3-c4ec7c79e755
  [   68.824970] NVRM: GPU Board Serial Number:
  [   68.824974] NVRM: Xid (PCI::01:00): 79, pid=926, GPU has fallen off 
the bus.
  [   68.824976] NVRM: GPU :01:00.0: GPU has fallen off the bus.
  [   68.824977] NVRM: GPU :01:00.0: GPU is on Board .
  [   68.826134] NVRM: A GPU crash dump has been created. If possible, please 
run
     NVRM: nvidia-bug-report.sh as root to collect this data before
     NVRM: the NVIDIA kernel module is unloaded

  The system has been running beautifully up until today. Installing the
  other driver versions listed below didn't help any.

  $ sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1C82sv1458sd3746bc03sc00i00
  vendor   : NVIDIA Corporation
  model: GP107 [GeForce GTX 1050 Ti]
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sat Jun 27 16:27:12 2020
  HibernationDevice: RESUME=UUID=447e6756-8310-4bc0-9ccc-108f1df5019b
  InstallationDate: Installed on 2014-07-08 (2180 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=464ea2d6-bc69-4340-88ed-33902e231ef3 ro mds=off mitigations=off quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97N-WIFI
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1861278] Re: RTL8821CE - 5GHZ networks not working

[You-Sheng Yang]

Public bug 1885862 instead.

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

Title:
  RTL8821CE - 5GHZ networks not working

Status in linux package in Ubuntu:
  Incomplete
Status in rtl8821ce package in Ubuntu:
  Incomplete
Status in rtl8821ce source package in Bionic:
  Confirmed
Status in rtl8821ce source package in Eoan:
  Confirmed
Status in rtl8821ce source package in Focal:
  Incomplete

Bug description:
  5 GHZ networks are not showing up

  dmesg | grep 8821
  [2.85] rtl8821ce: loading out-of-tree module taints kernel.
  [2.403456] rtl8821ce: module verification failed: signature and/or 
required key missing - tainting kernel
  [2.435475] RTW: rtl8821ce v5.2.5.2.1_.20181112_beta
  [2.435480] RTW: rtl8821ce BT-Coex version = COEX20170310-1212
  [4.599321] rtl8821ce :02:00.0 wlo1: renamed from wlan0

  dmesg |grep -i firm
  [0.147142] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [3.101456] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)

  iw list
  returns nothing...

  iwlist wlo1 freq
  wlo1  22 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
Current Frequency:2.437 GHz (Channel 6)

  Related:
  https://github.com/tomaspinho/rtl8821ce/issues/34
  https://github.com/tomaspinho/rtl8821ce/issues/103
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 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 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1861278] Re: RTL8821CE - 5GHZ networks not working

[You-Sheng Yang]

Probably you Android phone is equipped with some other WiFi chip.
Currently this RTL8821CE driver supports only 5G networks listed in `iw
list`.

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

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

Title:
  RTL8821CE - 5GHZ networks not working

Status in linux package in Ubuntu:
  Incomplete
Status in rtl8821ce package in Ubuntu:
  Incomplete
Status in rtl8821ce source package in Bionic:
  Confirmed
Status in rtl8821ce source package in Eoan:
  Confirmed
Status in rtl8821ce source package in Focal:
  Incomplete

Bug description:
  5 GHZ networks are not showing up

  dmesg | grep 8821
  [2.85] rtl8821ce: loading out-of-tree module taints kernel.
  [2.403456] rtl8821ce: module verification failed: signature and/or 
required key missing - tainting kernel
  [2.435475] RTW: rtl8821ce v5.2.5.2.1_.20181112_beta
  [2.435480] RTW: rtl8821ce BT-Coex version = COEX20170310-1212
  [4.599321] rtl8821ce :02:00.0 wlo1: renamed from wlan0

  dmesg |grep -i firm
  [0.147142] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [3.101456] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)

  iw list
  returns nothing...

  iwlist wlo1 freq
  wlo1  22 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
Current Frequency:2.437 GHz (Channel 6)

  Related:
  https://github.com/tomaspinho/rtl8821ce/issues/34
  https://github.com/tomaspinho/rtl8821ce/issues/103
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 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 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1861278] Re: RTL8821CE - 5GHZ networks not working

[You-Sheng Yang]

Add linux package to affected for bug 1884513 is to backport 8821ce
support in rtw88. Let's see if it will have better support for 5G
networks.

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

Title:
  RTL8821CE - 5GHZ networks not working

Status in linux package in Ubuntu:
  Incomplete
Status in rtl8821ce package in Ubuntu:
  Incomplete
Status in rtl8821ce source package in Bionic:
  Confirmed
Status in rtl8821ce source package in Eoan:
  Confirmed
Status in rtl8821ce source package in Focal:
  Incomplete

Bug description:
  5 GHZ networks are not showing up

  dmesg | grep 8821
  [2.85] rtl8821ce: loading out-of-tree module taints kernel.
  [2.403456] rtl8821ce: module verification failed: signature and/or 
required key missing - tainting kernel
  [2.435475] RTW: rtl8821ce v5.2.5.2.1_.20181112_beta
  [2.435480] RTW: rtl8821ce BT-Coex version = COEX20170310-1212
  [4.599321] rtl8821ce :02:00.0 wlo1: renamed from wlan0

  dmesg |grep -i firm
  [0.147142] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [3.101456] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)

  iw list
  returns nothing...

  iwlist wlo1 freq
  wlo1  22 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
Current Frequency:2.437 GHz (Channel 6)

  Related:
  https://github.com/tomaspinho/rtl8821ce/issues/34
  https://github.com/tomaspinho/rtl8821ce/issues/103
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 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 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Kai-Heng Feng]

There won't be any "definitive solution" until Chuwi can push Hantick to
take a look on 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/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default 

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Ian Hand]

@Califa, I left Windows behind a long time ago, I only use it at work
now due to it being on my work machine. It is a personal preference for
me to use Ubuntu. Yes, I could easily go back to Windows but I will not.
As I said before, I am not absolutely stuck as I have an external mouse.
I would rather contribute to the Open Source project that is Ubuntu by
means of trying to fix this bug than go back to Windows.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends 

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Califa101]

Why don't you use Windows until a definitive solution for Ubuntu comes
out and you get out of trouble?

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: 

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Ian Hand]

@Kai-Heng, thanks, much appreciated. I will configure this evening will
let you know how it goes.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default 

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

[gogolink]

@Hui Wang:
How do I actually load a mainline kernel?

I installed Ubuntu Mainline Kernel Installer, and used it too install kernel 
5.6.3;
but at boot attempt, I get this message:

error: /boot/vmlinuz-5.6.3-050603-generic has invalid signature.
error: you need to load the kernel first.

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: 

[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed

[Kai-Heng Feng]

No nothing. My suggestion is to install Windows, and if there's no
bluetooth, service the hardware to HP.

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

Title:
  Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not
  probed

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  Confirmed

Bug description:
  The driver installed just fine and wifi is working but bluetooth does
  not.

  I will gladly provide further debugging information.

  Ubuntu 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 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 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 1931 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-17 (231 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 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: ashmem_linux
  Tags:  focal staging staging
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  

[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend

[Kai-Heng Feng]

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ Some systems with ATA drives freeze during suspend
+ 
+ [Fix]
+ Avoid circular sync dependency by using async cookie.
+ 
+ [Test]
+ User reports positive feedback.
+ 
+ [Regression Potential]
+ Low. This patch makes synchronize more targeted, prevents many potential
+ freeze.
+ 
+ === Original Bug Report ===
  I am using an old HP EliteBook 6930p with current Ubuntu.
  
  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.
  
  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.
  
  I am holding kernel purge for now, but this is annoying.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  isabelle   1010 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
-  Socket 0:
-3.3V
-   16-bit
-   PC Card
-Subdevice 0 (function 0) bound to driver "pata_pcmcia"
+  Socket 0:
+    3.3V
+   16-bit
+   PC Card
+    Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-29-generic N/A
-  linux-backports-modules-5.3.0-29-generic  N/A
-  linux-firmware1.183.4
+  linux-restricted-modules-5.3.0-29-generic N/A
+  linux-backports-modules-5.3.0-29-generic  N/A
+  linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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

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

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

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

Title:
  Computer is frozen after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems with ATA drives freeze during suspend

  [Fix]
  Avoid circular sync dependency by using async cookie.

  [Test]
  User reports positive feedback.

  [Regression Potential]
  Low. This patch makes synchronize more targeted, prevents many potential
  freeze.

  === Original Bug Report ===
  I am using an old HP EliteBook 6930p with current Ubuntu.

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F 

[Kernel-packages] [Bug 1886890] Re: sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4

[Po-Hsu Lin]

** Description changed:

  == SRU Justification ==
  A new regression test case "sched_rr_get_interval01" for commit 975e155ed873 
("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in 
milliseconds"). Has been added to the LTP syscalls test suite.
  
  On Xenial 4.4.0-186.216, this test is failing with:
  
   startup='Wed Jul 8 10:36:58 2020'
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   sched_rr_get_interval01.c:43: INFO: Testing variant: vDSO or syscall with 
libc spec
   sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
   sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
   sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms 
!= 100 got 25
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   sched_rr_get_interval01.c:43: INFO: Testing variant: syscall with old kernel 
spec
   sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
   sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
   sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms 
!= 100 got 25
  
   HINT: You _MAY_ be missing kernel fixes, see:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=975e155ed873
  
   Summary:
   passed 4
   failed 2
   skipped 0
   warnings 0
   tag=sched_rr_get_interval01 stime=1594204618 dur=0 exit=exited stat=1 
core=no cu=0 cs=0
  
  == Fixes ==
  975e155ed873 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice 
tuning knob in milliseconds")
  
  This patch can be cherry-picked in to the affected Xenial kernel. It's
  already been applied in newer kernels.
  
  == Test ==
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1886890-sched_rr_get_interval01/
  
  With the patch applied, this test will pass without any issue.
+ 
+ And it can be simply tested with:
+ # echo 100 > /proc/sys/kernel/sched_rr_timeslice_ms
+ # cat /proc/sys/kernel/sched_rr_timeslice_ms
+ 100
+ (was 25 before the patch)

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

Title:
  sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4

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

Bug description:
  == SRU Justification ==
  A new regression test case "sched_rr_get_interval01" for commit 975e155ed873 
("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in 
milliseconds"). Has been added to the LTP syscalls test suite.

  On Xenial 4.4.0-186.216, this test is failing with:

   startup='Wed Jul 8 10:36:58 2020'
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   sched_rr_get_interval01.c:43: INFO: Testing variant: vDSO or syscall with 
libc spec
   sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
   sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
   sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms 
!= 100 got 25
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   sched_rr_get_interval01.c:43: INFO: Testing variant: syscall with old kernel 
spec
   sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
   sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
   sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms 
!= 100 got 25

   HINT: You _MAY_ be missing kernel fixes, see:

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

   Summary:
   passed 4
   failed 2
   skipped 0
   warnings 0
   tag=sched_rr_get_interval01 stime=1594204618 dur=0 exit=exited stat=1 
core=no cu=0 cs=0

  == Fixes ==
  975e155ed873 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice 
tuning knob in milliseconds")

  This patch can be cherry-picked in to the affected Xenial kernel. It's
  already been applied in newer kernels.

  == Test ==
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1886890-sched_rr_get_interval01/

  With the patch applied, this test will pass without any issue.

  And it can be simply tested with:
  # echo 100 > /proc/sys/kernel/sched_rr_timeslice_ms
  # cat /proc/sys/kernel/sched_rr_timeslice_ms
  100
  (was 25 before the patch)

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Kai-Heng Feng]

For me I always use the manpage:
https://www.freedesktop.org/software/systemd/man/systemd.service.html

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: 

[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown

[Tim Ryder]

Playing with the settings, if i set the extension to 50% cpu and turbo
boost ON then it will turbo up to 2.00GHZ from 1.30GHZ(when under load)
and still maintain 60-70C during gaming which gives a little extra
performance.  Not sure what the sweet spot is  yet.

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed
Status in Gentoo Linux:
  New

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed

[justcomplaining]

I followed the instructions but have no idea whether it worked or not (I
can't take the battery out so I had to take the 15-seconds-power-button
route).


[0.00] microcode: microcode updated early to revision 0xd6, date = 
2020-04-27
[0.00] Linux version 5.8.0-050800-generic (kernel@gloin) (gcc (Ubuntu 
9.3.0-13ubuntu1) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #202007052030 
SMP Mon Jul 6 00:37:33 UTC 2020
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-050800-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x000937ff] usable
[0.00] BIOS-e820: [mem 0x00093800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x7a6aefff] usable
[0.00] BIOS-e820: [mem 0x7a6af000-0x7b49efff] reserved
[0.00] BIOS-e820: [mem 0x7b49f000-0x7bb8efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7bb8f000-0x7bc0efff] ACPI data
[0.00] BIOS-e820: [mem 0x7bc0f000-0x7bc0] usable
[0.00] BIOS-e820: [mem 0x7bc1-0x7f7f] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff30-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00027e7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 3.0 present.
[0.00] DMI: HP HP 250 G7 Notebook PC/8532, BIOS F.16 12/05/2018
[0.00] tsc: Detected 1800.000 MHz processor
[0.001815] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.001817] e820: remove [mem 0x000a-0x000f] usable
[0.001824] last_pfn = 0x27e800 max_arch_pfn = 0x4
[0.001829] MTRR default type: uncachable
[0.001830] MTRR fixed ranges enabled:
[0.001832]   0-9 write-back
[0.001833]   A-B uncachable
[0.001834]   C-F write-protect
[0.001835] MTRR variable ranges enabled:
[0.001837]   0 base 00FF00 mask 7FFF00 write-protect
[0.001839]   1 base 007D00 mask 7FFF00 uncachable
[0.001840]   2 base 00 mask 7F8000 write-back
[0.001841]   3 base 01 mask 7F write-back
[0.001842]   4 base 02 mask 7E write-back
[0.001843]   5 base 007E00 mask 7FFE00 uncachable
[0.001844]   6 disabled
[0.001844]   7 disabled
[0.001845]   8 disabled
[0.001845]   9 disabled
[0.002486] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.002723] last_pfn = 0x7bc10 max_arch_pfn = 0x4
[0.013762] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf]
[0.013851] check: Scanning 1 areas for low memory corruption
[0.013856] Using GB pages for direct mapping
[0.014272] RAMDISK: [mem 0x31f2d000-0x34f8dfff]
[0.014283] ACPI: Early table checksum verification disabled
[0.014287] ACPI: RSDP 0x000FE020 24 (v02 HPQOEM)
[0.014291] ACPI: XSDT 0x7BBEA188 FC (v01 HPQOEM SLIC-MPC 
 HP   0113)
[0.014298] ACPI: FACP 0x7BBEC000 00010C (v05 HPQOEM SLIC-MPC 
 HP   0004)
[0.014304] ACPI: DSDT 0x7BBA7000 04013F (v02 HPQOEM SLIC-MPC 
 ACPI 0004)
[0.014308] ACPI: FACS 0x7BB2E000 40
[0.014311] ACPI: UEFI 0x7BC0D000 000236 (v01 HPQOEM INSYDE   
0001 HP   0004)
[0.014314] ACPI: SSDT 0x7BC09000 0031C6 (v02 HPQOEM INSYDE   
3000 ACPI 

[Kernel-packages] [Bug 1886337] Re: Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04

[Diogo Menezes]

Yes, After install:
* 
amd64/linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb
* amd64/linux-modules-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb

Works well

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

Title:
   Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  My notebook has the Qualcomm Atheros QCA6174 802.11ac wireless network 
adapter (rev 32). 
  I have no problem using this device on Ubuntu 19.10, works well. 

  So, After I Format and Install Ubuntu 20.04 stopped working
  I Used to use Ubuntu 19.04 and linux-firmware 1.183 - Wifi - OK

  Now, I tried Ubuntu 20.04 with linux-firmware is 1.187 and it stopped working.
  After I tried Ubuntu 20.04 with linux-firmware is 1.187.1 and it stopped 
working.

  Now I need Using Ubuntu 20.04 with linux-firmware is 1.183 and it working 
well,
  But I need hold linux-firmware.

  
  So after I download 19.10's linux-firmware package from the ubuntu 
repositories, which is at 1.183. After I installed and apt-marked hold the 
package, so that it would not be upgrade, and rebooted, my wifi worked well.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.183
  Uname: Linux 5.4.0-40-generic x86_64
  Architecture: amd64
  NonfreeKernelModules: nvidia_modeset nvidia
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dmenezes   2470 F pulseaudio
   /dev/snd/controlC0:  dmenezes   2470 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0c45:6a08 Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. G7 7588
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia
  Package: linux-firmware 1.187.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=330509ee-8a3f-4851-b437-1a9b3a72c353 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0PK2PP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd07/15/2019:svnDellInc.:pnG77588:pvr:rvnDellInc.:rn0PK2PP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G7 7588
  dmi.product.sku: 0825
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1805693] Re: User reports a hang on 18.04 LTS(4.15.18) under a heavy I/O load

[Frank Heimes]

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

This issue seems to occur with kernels > 4.10 and < v4.19
and got already fixed with applying two patches to bionic (and cosmic) in LP 
1810998 - thx to Mauricio Faria de Oliveira.
Hence this bug here can be considered as done and I mark this bug as a 
duplicate of LP 1810998. 

** This bug has been marked a duplicate of bug 1810998
   CPU hard lockup with rigorous writes to NVMe drive

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

Title:
  User reports a hang on 18.04 LTS(4.15.18) under a heavy I/O load

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

Bug description:
  User reports a hang under heavy I/O:

  The IO hang problem on our cloud is caused by IO hang in block-wbt wbt_wait.
  The fix commit id is 2887e41b910bb14fd847cf01ab7a5993db989d88. It is a block 
write buffer throttle queue lock contention and thundering herd issue in 
wbt_wait()

  We can recreate the problem easily by running concurrent IO from
  multiple VMs with sequential write. We can provide fio workload as
  needed for recreate.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: focal

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Ian Hand]

@Kai-Heng, thanks. Just so I don't go and make a mistake along the way,
could you please forward me on a tutorial/blog page that gives a step by
step on how to set up Systemd oneshot. Thank you.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default 

[Kernel-packages] [Bug 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554

[You-Sheng Yang]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Touchpad detection issue in Fujitsu Lifebook UH554

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop model : Fujitsu Lifebook UH554

  Ram : 8 GB

  HDD : 500 GB

  Processor : i5

  Manufacturer of the Touchpad : Unknown

  
  When the symptom first appeared : After installing the OS 20.04 itself
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shingade   1340 F pulseaudio
   /dev/snd/controlC0:  shingade   1340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd 
   Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK UH554
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout 
i8042.nomux vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.25
  dmi.board.name: FJNBB34
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK UH554
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working

[You-Sheng Yang]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  ps/2 mouse not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ps/2 mouse not working , gave some command in terminal , this bug came
  out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 19:25:07 2020
  DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics 
Controller [8086:d613]
  InstallationDate: Installed on 2020-06-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago)
  dmi.bios.date: 01/08/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41RQ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE54511-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jul  3 08:17:23 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login

[altadeos]

I Think this problem is related to kernel or Gnome.
Tried with Nvidia proprietary driver and Intel driver and the problem is the 
same.

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

Title:
  DELL M3800 Touchscreen not working after login

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
  The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

  I'm on a dual boot computer and all is working well on Windows 10.

  How can I help you to track this bug and solve it ?

  Best regards

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

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

[Kai-Heng Feng]

Since it's a regression, would it be possible for you to do a kernel
bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

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

Title:
  high speed data to usb disk makes the kernel think that is has been
  unmounted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  When the speed of data with a usb disk device is too high, the probes
  that check if the disk still exists is missed. This makes the disk to
  be unmounted and is remounted with an other drive letter (/dev/sdX).
  If this disk is the root ("/"), the computer hangs.

  A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
  easily. This has never happened with a mechanical USB-drive.

  Symptoms and how to reproduce:

  1) (Disk mounted as root) Computer hangs. Only way to get started
  again is a hard reset.

  2) (Erasing disk, not mounted as root) If you erase a disk with dd
  ("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
  list and reappears as an other drive letter. In my case the data is
  redirected to /dev/null and the fans speed up. The apparent data
  transfer speed is also increased. Usually this happens after about 45
  to 60 minutes.

  3) Fill RAM with programs and make sure the swap to this disk is used.

  Bug found in:

  $ uname -a
  Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  $ cat /proc/version_signature
  Ubuntu 5.4.0-40.44-generic 5.4.44

  Bug not found in:

  Linux v4.15 (Ubuntu Bionic)

  Hardware:

  Tested with slower and faster computers. Tested directly connected to
  a computer and via a hub. They all reproduce this bug.

  Workaround:

  None found.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   6813 F pulseaudio
   /dev/snd/controlC0:  user   6813 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  MachineType: ASUSTeK COMPUTER INC. GL503VM
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VM.314
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1886912] [NEW] DELL M3800 Touchscreen not working after login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
The touchscreen is working good on login screen bug after I enter my 
credentials and the gnome session open I can't use it.

I'm on a dual boot computer and all is working well on Windows 10.

How can I help you to track this bug and solve it ?

Best regards

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


** Tags: bot-comment
-- 
DELL M3800 Touchscreen not working after login
https://bugs.launchpad.net/bugs/1886912
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