[Kernel-packages] [Bug 1909898] Re: No response from TouchPad in 'Acer Aspire 5 A517-52G-79Z5' after installing Ubuntu 20.04.1 LTS

[Launchpad Bug Tracker]

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

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

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

Title:
  No response from TouchPad in 'Acer Aspire 5 A517-52G-79Z5' after
  installing Ubuntu 20.04.1 LTS

Status in linux package in Ubuntu:
  Expired

Bug description:
  If I remember correctly the touchpad was already not responding when
  booting into Ubuntu from USB stick.

  I followed the guidline
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo.
  Unfortunately, I have not found the manufacturer of the touchpad. In
  the

  cat /proc/bus/input/devices > ~/devices

  output I could not find any 'touchpad' entry. Output file 'devices' is
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 12:35:18 2021
  InstallationDate: Installed on 2021-01-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Aspire A517-52G
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Chassis Location
  dmi.board.name: Jasmine_TL
  dmi.board.vendor: TGL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd11/02/2020:svnAcer:pnAspireA517-52G:pvrV1.04:rvnTGL:rnJasmine_TL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A517-52G
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1921594] Re: zfsutils-linux misspells zfs-zed recommendation

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 2.0.2-1ubuntu5

---
zfs-linux (2.0.2-1ubuntu5) hirsute; urgency=medium

  * Fix typo in debian/control, fs-zed should be zfs-zed (LP: #1921594)
fix zfsutils-linux Recommends.

 -- Colin Ian King   Sat, 27 Mar 2021 22:08:23
+

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

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

Title:
  zfsutils-linux misspells zfs-zed recommendation

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux
  package contains a misspelling in its recommended dependency on zfs-
  zed, which is spelled instead as "fs-zed".

  Debian has since imported Ubuntu changes into the control.ubuntu file
  upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still
  has this error.

  I don't know how essential zed is, but the ubiquity installer does not
  mark zfs-zed as manually installed, so it won't be installed for new
  users when I think it otherwise would be.

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

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

[Kernel-packages] [Bug 1921603] Re: The last update detroyed my Ubuntu boot in use since 18.04

[BertN45]

** Description changed:

  The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, 
fortunately I dual boot between zfs and ext4.
- My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The 
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last 
system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so 
I thought about HW issues. Without my SSHD and also with another HDD, the 
system got passed the BIOS. So now I started thinking about boot issues. I 
downloaded boot-repair and that one repaired the ext4 install, so I was happy 
for a short moment. 
+ My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The 
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last 
system update of 20.04 went wrong, the system did hang in the BIOS screen, so I 
thought about HW issues. Without my SSHD and also with another HDD, the system 
got passed the BIOS. So now I started thinking about boot issues. I downloaded 
boot-repair and that one repaired the ext4 install, so I was happy for a short 
moment. 
  
  Did run update-grub, but caused the zfs ubuntu to show up in the boot
  menu, but the system failed to boot, because it needed bootpool/BOOT,
  which never existed on this laptop, running update-grub in the ext
  install had the next result, see:
  
  bertadmin@Ubuntu-ext:~$ sudo update-grub
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.4.0-70-generic
  Found initrd image: /boot/initrd.img-5.4.0-70-generic
  cannot open 'bpool/BOOT/mate-1804': dataset does not exist
 <--
  Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
  Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
  cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist 
 <--
  Found linux image: vmlinuz-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
  Found initrd image: initrd.img-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
  /usr/sbin/grub-probe: error: unknown filesystem.
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  device-mapper: reload ioctl on osprober-linux-sda3  failed: Device or 
resource busy
  Command failed.
  device-mapper: reload ioctl on osprober-linux-sda4  failed: Device or 
resource busy
  Command failed.
  done
  
  
  This does not make me happy, not at all. Fortunately I have access to all my 
data through the ext4 installation.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfs-initramfs (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 27 20:07:56 2021
  InstallationDate: Installed on 2019-09-09 (565 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago)

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

Title:
  The last update detroyed my Ubuntu boot in use since 18.04

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, 
fortunately I dual boot between zfs and ext4.
  My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The 
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last 
system update of 20.04 went wrong, the system did hang in the BIOS screen, so I 
thought about HW issues. Without my SSHD and also with another HDD, the system 
got passed the BIOS. So now I started thinking about boot issues. I downloaded 
boot-repair and that one repaired the ext4 install, so I was happy for a short 
moment. 

  Did run update-grub, but caused the zfs ubuntu to show up in the boot
  menu, but the system failed to boot, because it needed bootpool/BOOT,
  which never existed on this laptop, running update-grub in the ext
  install had the next result, see:

  bertadmin@Ubuntu-ext:~$ sudo update-grub
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.4.0-70-generic
  Found initrd image: /boot/initrd.img-5.4.0-70-generic
  cannot open 'bpool/BOOT/mate-1804': dataset does not exist
 <--
  Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
  Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
  cannot open 'bpool/BOOT/mate-1804@210

[Kernel-packages] [Bug 1921603] [NEW] The last update detroyed my Ubuntu boot in use since 18.04

[BertN45]

Public bug reported:

The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, fortunately 
I dual boot between zfs and ext4.
My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The 
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last 
system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so 
I thought about HW issues. Without my SSHD and also with another HDD, the 
system got passed the BIOS. So now I started thinking about boot issues. I 
downloaded boot-repair and that one repaired the ext4 install, so I was happy 
for a short moment. 

Did run update-grub, but caused the zfs ubuntu to show up in the boot
menu, but the system failed to boot, because it needed bootpool/BOOT,
which never existed on this laptop, running update-grub in the ext
install had the next result, see:

bertadmin@Ubuntu-ext:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-70-generic
Found initrd image: /boot/initrd.img-5.4.0-70-generic
cannot open 'bpool/BOOT/mate-1804': dataset does not exist  
   <--
Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist   
   <--
Found linux image: vmlinuz-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
Found initrd image: initrd.img-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
/usr/sbin/grub-probe: error: unknown filesystem.
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
device-mapper: reload ioctl on osprober-linux-sda3  failed: Device or resource 
busy
Command failed.
device-mapper: reload ioctl on osprober-linux-sda4  failed: Device or resource 
busy
Command failed.
done


This does not make me happy, not at all. Fortunately I have access to all my 
data through the ext4 installation.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zfs-initramfs (not installed)
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 27 20:07:56 2021
InstallationDate: Installed on 2019-09-09 (565 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  The last update detroyed my Ubuntu boot in use since 18.04

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, 
fortunately I dual boot between zfs and ext4.
  My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The 
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last 
system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so 
I thought about HW issues. Without my SSHD and also with another HDD, the 
system got passed the BIOS. So now I started thinking about boot issues. I 
downloaded boot-repair and that one repaired the ext4 install, so I was happy 
for a short moment. 

  Did run update-grub, but caused the zfs ubuntu to show up in the boot
  menu, but the system failed to boot, because it needed bootpool/BOOT,
  which never existed on this laptop, running update-grub in the ext
  install had the next result, see:

  bertadmin@Ubuntu-ext:~$ sudo update-grub
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.4.0-70-generic
  Found initrd image: /boot/initrd.img-5.4.0-70-generic
  cannot open 'bpool/BOOT/mate-1804': dataset does not exist
 <--
  Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
  Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
  cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist 
 <--
  Found linux image: vmlinuz-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
  Found initrd image: initrd.img-5.8.0-43-generic in 
vms/roots/mate-1804@210213-linux43
  /usr/sbin/grub-probe: error: unknown filesystem.
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  device-mapper: reload ioctl on osprober-linux-sda3  failed: Device or 
resource busy
  Com

[Kernel-packages] [Bug 1921594] Re: zfsutils-linux misspells zfs-zed recommendation

[Colin Ian King]

Thanks for reporting this issue, I've uploaded a fix to the
debian/control to address this issue.

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

Title:
  zfsutils-linux misspells zfs-zed recommendation

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux
  package contains a misspelling in its recommended dependency on zfs-
  zed, which is spelled instead as "fs-zed".

  Debian has since imported Ubuntu changes into the control.ubuntu file
  upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still
  has this error.

  I don't know how essential zed is, but the ubiquity installer does not
  mark zfs-zed as manually installed, so it won't be installed for new
  users when I think it otherwise would be.

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

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

[Kernel-packages] [Bug 1921594] Re: zfsutils-linux misspells zfs-zed recommendation

[Colin Ian King]

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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfsutils-linux misspells zfs-zed recommendation

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux
  package contains a misspelling in its recommended dependency on zfs-
  zed, which is spelled instead as "fs-zed".

  Debian has since imported Ubuntu changes into the control.ubuntu file
  upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still
  has this error.

  I don't know how essential zed is, but the ubiquity installer does not
  mark zfs-zed as manually installed, so it won't be installed for new
  users when I think it otherwise would be.

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

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

[Kernel-packages] [Bug 1921411] Re: linux-azure: Install PMEM modules by default

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-groovy

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

Title:
  linux-azure: Install PMEM modules by default

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux-azure source package in Groovy:
  Fix Committed
Status in linux-azure-4.15 source package in Groovy:
  Invalid

Bug description:
  [Impact]

  Some workloads, for example SQL Server, require PMEM support from
  different modules for performance reasons. Most of this modules are
  included in the linux-modules-extra package but linux-azure doesn't
  install it by default.

  Move these modules to the linux-modules package so they are installed
  by default: nd_blk.ko, nd_pmem.ko, device_dax.ko, dax_hmem.ko,
  kmem.ko, dax_pmem.ko, dax_pmem_compat.ko, virtio_pmem.ko ,
  nd_virtio.ko.

  (Some modules are not available depending on the kernel version)

  [Test Plan]

  The modules listed below should be included in the linux-modules
  package instead of in the linux-modules-extra package.

  [Where problems could occur]

  The additional modules shouldn't cause any troubles and in case of
  problem they can be blacklisted or removed from linux-modules.

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

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

[Kernel-packages] [Bug 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45

[Julian Petri]

I believe this is going to be fixed in 5.8.0-49 which is in 'proposed'
status for Groovy.

https://bugs.launchpad.net/ubuntu/+source/linux/5.8.0-49.55
"HID: wacom: Correct NULL dereference on AES pen proximity"

This corresponds to the following upstream bug reports:
https://github.com/linuxwacom/input-wacom/issues/230
https://bugzilla.kernel.org/show_bug.cgi?id=211261

** Bug watch added: github.com/linuxwacom/input-wacom/issues #230
   https://github.com/linuxwacom/input-wacom/issues/230

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

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

Title:
  Stylus and touchscreen not working in kernel 5.8.0-45

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an update from 16th March 2021, the stylus for Acer Spin 5
  stopped working and wasn't charging.

  Returning to version 5.8.0-43 fixed the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.30
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 16 16:12:45 2021
  InstallationDate: Installed on 2020-12-23 (82 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1863939] Re: Linux 5.4 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4 from mainline PPA does boot

[RussianNeuroMancer]

Issue is still reproducible with Linux 5.11 on Ubuntu 21.04.

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

Title:
  Linux 5.4 from focal repo does not boot on Lenovo Yoga C630 WOS, while
  Linux 5.4 from mainline PPA does boot

Status in linux package in Ubuntu:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Hello!

  I found that both of generic and snapdragon kernels from focal
  repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does
  not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device
  tree blob..." (which means I can not provide apport report, because I
  can not boot kernel from focal repository, and apport refuse to
  collect information with other kernels).

  At the same time snapdragon kernel from https://kernel.ubuntu.com
  /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with
  https://bugzilla.kernel.org/show_bug.cgi?id=204685 and
  https://bugs.launchpad.net/bugs/1863761 ).

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

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

[Kernel-packages] [Bug 1921594] Re: zfsutils-linux misspells zfs-zed recommendation

[Randall Leeds]

My apologies, but I tried for several hours to figure out how to submit
a fix and I cannot figure it out, so I'm just reporting it as a bug.

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

Title:
  zfsutils-linux misspells zfs-zed recommendation

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux
  package contains a misspelling in its recommended dependency on zfs-
  zed, which is spelled instead as "fs-zed".

  Debian has since imported Ubuntu changes into the control.ubuntu file
  upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still
  has this error.

  I don't know how essential zed is, but the ubiquity installer does not
  mark zfs-zed as manually installed, so it won't be installed for new
  users when I think it otherwise would be.

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

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

[Kernel-packages] [Bug 1921594] [NEW] zfsutils-linux misspells zfs-zed recommendation

[Randall Leeds]

Public bug reported:

Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux package
contains a misspelling in its recommended dependency on zfs-zed, which
is spelled instead as "fs-zed".

Debian has since imported Ubuntu changes into the control.ubuntu file
upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still has
this error.

I don't know how essential zed is, but the ubiquity installer does not
mark zfs-zed as manually installed, so it won't be installed for new
users when I think it otherwise would be.

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

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

Title:
  zfsutils-linux misspells zfs-zed recommendation

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Since the version 2.0.2 imports of zfs-linux, the zfsutils-linux
  package contains a misspelling in its recommended dependency on zfs-
  zed, which is spelled instead as "fs-zed".

  Debian has since imported Ubuntu changes into the control.ubuntu file
  upstream, without the typo, but the most recent 2.0.2-1ubuntu4 still
  has this error.

  I don't know how essential zed is, but the ubiquity installer does not
  mark zfs-zed as manually installed, so it won't be installed for new
  users when I think it otherwise would be.

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

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

[Kernel-packages] [Bug 1918793] Re: HP m400 cartridges fail to find NIC when deploying hirsute

[dann frazier]

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

Title:
  HP m400 cartridges fail to find NIC when deploying hirsute

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  They do not appear to find the Mellanox NIC:

  [0.00] Linux version 5.10.0-14-generic (buildd@bos02-arm64-008) (gcc 
(Ubuntu 10.2.1-6ubuntu2) 10.2.1 20210121, GNU ld (GNU Binutils for Ubuntu) 
2.36) #15-Ubuntu SMP Fri Jan 29 15:08:45 UTC 2021 (Ubuntu 5.10.0-14.15-generic 
5.10.11)
  [0.00] Machine model: HP ProLiant m400 Server Cartridge
  [0.00] efi: UEFI not found.
  [...]
  ipconfig: BOOTIF: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  [...]
  (initramfs) cat /proc/cmdline
  nomodeset ro 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/xgene-uboot/hirsute/stable/squashfs
 ip=ms10-35-mcdivittB0-kernel:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.229.32.21:5248/MAAS/metadata/latest/by-id/chbcrm/?op=get_preseed
 apparmor=0 log_host=10.229.32.21 log_port=5247 --- console=ttyS0,9600n8r 
BOOTIF=01-14-58-d0-58-c3-c2
  (initramfs) ls /sys/class/net
  lo
  (initramfs)

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

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

[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

[Azis naufal]

Hello!

I'm happy that I found a workaround of dsdt patch for this bug.
But I'm very sorry. I do this workaround at my fedora 34 beta with linux 5.11.9.
I hope it's possible to apply it in ubuntu.
So, I run cat /proc/acpi/wakeup command. Here is the output: 
Device  S-state   Status   Sysfs node
XHC   S4*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
RP01  S4*enabled   pci::00:1c.0
PXSX  S4*disabled
RP02  S4*disabled
PXSX  S4*disabled
RP03  S4*disabled
PXSX  S4*disabled
RP04  S4*disabled
PXSX  S4*disabled
RP05  S4*enabled   pci::00:1c.4
PXSX  S4*disabled  pci::02:00.0
RP06  S4*disabled
PXSX  S4*disabled
RP07  S4*disabled
PXSX  S4*disabled
RP08  S4*disabled
PXSX  S4*disabled
RP09  S5*enabled   pci::00:1d.0
PXSX  S4*disabled  pci::03:00.0
RP10  S4*disabled
PXSX  S4*disabled
RP11  S4*enabled   pci::00:1d.2
PXSX  S4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
RP12  S4*disabled
PXSX  S4*disabled
RP13  S4*enabled   pci::00:1d.4
PXSX  S4*disabled  pci::05:00.0
RP14  S4*disabled
PXSX  S4*disabled
RP15  S4*disabled
PXSX  S4*disabled
RP16  S4*disabled
PXSX  S4*disabled
RP17  S4*disabled
PXSX  S4*disabled
RP18  S4*disabled
PXSX  S4*disabled
RP19  S4*disabled
PXSX  S4*disabled
RP20  S4*disabled
PXSX  S4*disabled
RP21  S4*disabled
PXSX  S4*disabled
RP22  S4*disabled
PXSX  S4*disabled
RP23  S4*disabled
PXSX  S4*disabled
RP24  S4*disabled
PXSX  S4*disabled
CNVW  S4*disabled  pci::00:14.3
TXHC  S4*enabled   pci::00:0d.0
TDM0  S4*disabled
TDM1  S4*disabled
TRP0  S4*disabled
PXSX  S4*disabled
TRP1  S4*disabled
PXSX  S4*disabled
TRP2  S4*disabled
PXSX  S4*disabled
TRP3  S4*disabled
PXSX  S4*disabled
AWAC  S4*enabled   platform:ACPI000E:00

As you can see there is no LID0 listed.
So, I dump the DSDT using this command:
cat /sys/firmware/acpi/tables/DSDT > dsdt.aml 

Decompile it using this command:
iasl -d dsdt.aml

Open the decompiled file using your favorite text editor.
Find AWAC device and then find _PRW method in AWAC device bracket.
Here is _PRW method that I found:
Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
{
Return (GPRW (0x72, 0x04))
}

Copy the method. 
Find LID0 device and paste the _PRW method in LID0 device bracket.

Compile it using this command:
iasl -ve -tc dsdt.dsl

And pack it using this command:
mkdir -p kernel/firmware/acpi
cp dsdt.aml kernel/firmware/acpi
find kernel | cpio -H newc --create > acpi_override
cp acpi_override /boot

use the acpi_override to boot as initrd.
And here is the new output of cat /proc/acpi/wakeup command.
Device  S-state   Status   Sysfs node
XHC   S4*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
RP01  S4*enabled   pci::00:1c.0
PXSX  S4*disabled
RP02  S4*disabled
PXSX  S4*disabled
RP03  S4*disabled
PXSX  S4*disabled
RP04  S4*disabled
PXSX  S4*disabled
RP05  S4*enabled   pci::00:1c.4
PXSX  S4*disabled  pci::02:00.0
RP06  S4*disabled
PXSX  S4*disabled
RP07  S4*disabled
PXSX  S4*disabled
RP08  S4*disabled
PXSX  S4*disabled
RP09  S5*enabled   pci::00:1d.0
PXSX  S4*disabled  pci::03:00.0
RP10  S4*disabled
PXSX  S4*disabled
RP11  S4*enabled   pci::00:1d.2
PXSX  S4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
RP12  S4*disabled
PXSX  S4*disabled
RP13  S4*enabled   pci::00:1d.4
PXSX  S4*disabled  pci::05:00.0
RP14  S4*disabled
PXSX  S4*disabled
RP15  S4*disabled
PXSX  S4*disabled
RP16  S4*disabled
PXSX  S4*disabled
RP17  S4*disabled
PXSX  S4*disabled
RP18  S4*disabled
PXSX  S4*disabled
RP19  S4*disabled
PXSX  S4*disabled
RP20  S4*disabled
PXSX  S4*disabled
RP21  S4*disabled
PXSX  S4*disabled
RP22  S4*disabled
PXSX  S4*disabled
RP23  S4*disabled
PXSX  S4*disabled
RP24  S4*disabled
PXSX  S4*disabled
CNVW  S4*disabled  pci::00:14.3
TXHC  S4*enabled   pci::00:0d.0
TDM0  S4*disabled
TDM1  S4*disabled
TRP0  S4*disabled
PXSX  S4*disabled
TRP1  S4*disabled
PXSX  S4*disabled
TRP2  S4   

[Kernel-packages] [Bug 1856372] Re: Wifi drops, particularly under load

[Bernhard]

I am affected by this bug as well. It happens in Fedora 33 and in
Kubuntu 20.10. Is there any fix for this problem (I don't care in which
distribution)?

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

Title:
  Wifi drops, particularly under load

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card,
  internet drops out, particularly when downloading at speeds ~1MB/s say
  via P2P torrent or ooka speedtest. The wifi connection (at least
  reported by wicd) remains active, but I cannot ping the router or
  access the internet. No error message is logged in journalctl after
  the internet drops. Details on my card, firmware and dmesg given below
  I'm not the only one with this issue:
  https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-
  disconnects-on-ubuntu-18-04-with-qualcomm-atheros

  The issue DOES NOT occur with wired connection (ethernet).
  
-
    *-network
     description: Wireless interface
     product: QCA6174 802.11ac Wireless Network Adapter
     vendor: Qualcomm Atheros
     physical id: 0
     bus info: pci@:3a:00.0
     logical name: wlp58s0
     version: 32
     serial: 9c:b6:d0:d4:9b:33
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00140-QCARMSWPZ-1 
latency=0 link=no multicast=yes wireless=IEEE 802.11

     resources: irq:135 memory:dc00-dc1f
  
-
  $ dmesg | grep ath10k

  [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [2.951390] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
4ed3569e
  [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536

  
-
  $ dmesg | grep pcieport

  [0.959817] pcieport :00:1c.0: AER: enabled with IRQ 122
  [0.960121] pcieport :00:1c.4: AER: enabled with IRQ 123
  [0.960397] pcieport :00:1c.5: AER: enabled with IRQ 124
  [0.960657] pcieport :00:1d.0: AER: enabled with IRQ 125
  [6.644709] pcieport :02:01.0: bridge window [io  0x1000-0x0fff] to 
[bus 04-38] add_size 1000
  [6.644711] pcieport :02:02.0: bridge window [io  0x1000-0x0fff] to 
[bus 39] add_size 1000
  [6.644713] pcieport :02:02.0: bridge window [mem 
0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10
  [6.644716] pcieport :01:00.0: bridge window [io  0x1000-0x0fff] to 
[bus 02-39] add_size 3000
  [6.644719] pcieport :01:00.0: BAR 13: no space for [io  size 0x3000]
  [6.644721] pcieport :01:00.0: BAR 13: failed to assign [io  size 
0x3000]
  [6.644723] pcieport :01:00.0: BAR 13: no space for [io  size 0x3000]
  [6.644724] pcieport :01:00.0: BAR 13: failed to assign [io  size 
0x3000]
  [6.644728] pcieport :02:02.0: BAR 15: no space for [mem size 
0x0020 64bit pref]
  [6.644729] pcieport :02:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [6.644731] pcieport :02:01.0: BAR 13: no space for [io  size 0x1000]
  [6.644732] pcieport :02:01.0: BAR 13: failed to assign [io  size 
0x1000]
  [6.644734] pcieport :02:02.0: BAR 13: no space for [io  size 0x1000]
  [6.644735] pcieport :02:02.0: BAR 13: failed to assign [io  size 
0x1000]
  [6.644738] pcieport :02:02.0: BAR 15: no space for [mem size 
0x0020 64bit pref]

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

[Noa Sakurajin]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1921576/+attachment/5481462/+files/ProcEnviron.txt

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-07-17 (253 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.11.10 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to hirsute on 2021-03-26 (1 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin lxd nordvpn plugdev 
sambashare sudo tty
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1921576] Re: bluetooth not working on linux 5.11.0-13-generic

[Noa Sakurajin]

apport information

** Tags added: apport-collected

** Description changed:

  1) System version:
  
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04
  
  2) apt-cache policy linux-image-5.11.0-13-generic:
  
  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu61
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2020-07-17 (253 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: linux (not installed)
+ Tags:  hirsute
+ Uname: Linux 5.11.10 x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to hirsute on 2021-03-26 (1 days ago)
+ UserGroups: adm cdrom dialout dip docker lpadmin lxd nordvpn plugdev 
sambashare sudo tty
+ _MarkForUpload: True

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-07-17 (253 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.11.10 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to hirsute on 2021-03-26 (1 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin lxd nordvpn plugdev 
sambashare sudo tty
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1921576] Re: bluetooth not working on linux 5.11.0-13-generic

[Jeremy]

The apport-collect 1921576 should work even if apport doesn't recognize
package linux

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment

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

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

[Kernel-packages] [Bug 1918880] Re: pulseaudio threaded-ml suspend issue

[kailoran]

I haven't encountered the problem in over a week after switching to a
5.10 kernel (from linux-image-oem-20.04-edge).

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

Title:
  pulseaudio threaded-ml suspend issue

Status in linux-oem-5.6 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My laptop failed to suspend overnight and was unresponsive when I
  opened it back up. This is on Ubuntu 20.04.2 LTS with kernel
  5.6.0-1048-oem and pulseaudio:amd64/focal-updates
  1:13.99.1-1ubuntu3.10 uptodate. In syslog, I found a stream of suspend
  attempts with pulseaudio-related issues repeating in a 40s cycle, so
  reporting this as a PA issue.

  Mar 12 00:08:31 churn systemd[1]: Reached target Sleep.
  Mar 12 00:08:31 churn upowerd[1698]: Could not acquire inhibitor lock: 
GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation 
inhibition has been requested for is already running
  Mar 12 00:08:31 churn systemd[1]: Starting Suspend...
  Mar 12 00:08:31 churn ModemManager[1427]:   [sleep-monitor] inhibit 
failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation 
inhibition has been requested for is already running
  Mar 12 00:08:31 churn kernel: [883904.845262] iwlwifi :00:14.3: Applying 
debug destination EXTERNAL_DRAM
  Mar 12 00:08:31 churn ModemManager[1427]:   Couldn't check support for 
device '/sys/devices/pci:00/:00:14.3': Device support check task 
already available for device '/sys/devices/pci:00/:00:14.3'
  Mar 12 00:08:31 churn systemd-sleep[516395]: Suspending system...
  Mar 12 00:08:31 churn kernel: [883904.853576] PM: suspend entry (s2idle)
  Mar 12 00:08:51 churn kernel: [883904.856917] Filesystems sync: 0.003 seconds
  Mar 12 00:08:51 churn kernel: [883904.857284] Freezing user space processes 
... 
  Mar 12 00:08:51 churn kernel: [883904.991749] iwlwifi :00:14.3: FW 
already configured (0) - re-configuring
  Mar 12 00:08:51 churn kernel: [883924.868069] Freezing of tasks failed after 
20.010 seconds (1 tasks refusing to freeze, wq_busy=0):
  Mar 12 00:08:51 churn kernel: [883924.868160] threaded-ml D0  3306   
2128 0x80004326
  Mar 12 00:08:51 churn kernel: [883924.868166] Call Trace:
  Mar 12 00:08:51 churn kernel: [883924.868183]  __schedule+0x2d8/0x760
  Mar 12 00:08:51 churn kernel: [883924.868188]  schedule+0x55/0xc0
  Mar 12 00:08:51 churn kernel: [883924.868195]  do_exit.cold+0x9f/0xb5
  Mar 12 00:08:51 churn kernel: [883924.868200]  rewind_stack_do_exit+0x17/0x20
  Mar 12 00:08:51 churn kernel: [883924.868205] RIP: 0033:0x7fc8a96ebcb9
  Mar 12 00:08:51 churn kernel: [883924.868216] Code: Bad RIP value.
  Mar 12 00:08:51 churn kernel: [883924.868219] RSP: 002b:7fc899504850 
EFLAGS: 0293 ORIG_RAX: 0007
  Mar 12 00:08:51 churn kernel: [883924.868223] RAX: fdfc RBX: 
208bbe357f60 RCX: 7fc8a96ebcb9
  Mar 12 00:08:51 churn kernel: [883924.868225] RDX: 7530 RSI: 
0003 RDI: 208bbe357f60
  Mar 12 00:08:51 churn kernel: [883924.868227] RBP: 0003 R08: 
 R09: 1587756a
  Mar 12 00:08:51 churn kernel: [883924.868229] R10: 0f90 R11: 
0293 R12: 7530
  Mar 12 00:08:51 churn kernel: [883924.868231] R13: 7530 R14: 
208bbe3285d0 R15: 7fff6f13d440
  Mar 12 00:08:51 churn kernel: [883924.868427] OOM killer enabled.
  Mar 12 00:08:51 churn rtkit-daemon[1608]: The canary thread is apparently 
starving. Taking action.
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1026] device 
(p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
  Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoting known real-time threads.
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1036] 
manager: NetworkManager state is now DISCONNECTED
  Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoted 0 threads.
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1039] 
manager: sleep: sleep requested (sleeping: no  enabled: yes)
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1039] device 
(wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Mar 12 00:08:51 churn pulseaudio[2134]: q overrun, queuing locally
  Mar 12 00:08:51 churn kernel: [883924.868429] Restarting tasks ... done.
  Mar 12 00:08:51 churn pulseaudio[2134]: message repeated 4 times: [ q 
overrun, queuing locally]
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1245] device 
(p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Mar 12 00:08:51 churn NetworkManager[1297]:   [1615504131.1247] 
manager: NetworkManager state is now ASLEEP
  Mar 12 00:08:51 churn kernel: [883924

[Kernel-packages] [Bug 1919425] Re: System freeze

[kailoran]

As an update, it's now been roughly a week with no freezes or crashes
for me. I have not changed my usage pattern: same dock, same external
display, devices, etc., and same applications used. I did change one
thing however. When I was switching again to the linux-image-
oem-20.04-edge I decided to reinstall it just to be sure. I spotted a
post-install warning I didn't notice previously:

  update-initramfs: Generating /boot/initrd.img-5.10.0-1016-oem
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

I indeed did not have tgl_huc_7.5.0.bin on my machine, despite having
linux-firmware installed. It did not seem available in any installable
package, so I decided to grab this one file from a newer debian package
(it was added upstream a few months back) and reinstalled again with it
in place. There was no update-initramfs warning this time, and I haven't
had a freeze since.

It could be a coincidence of course, but maybe the kernel/firmware
relationship is related.

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

Title:
  System freeze

Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  I've been getting freezes on Ubuntu 20.04 on my Dell Latitude 7420
  laptop with a secondary display connected through a WD19 Dell dock.
  I'm on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8
  and 5.10 without much success (other types of freezes). Some freezes
  lock up the machine hard with no way to ssh in or check anything and
  no logs. The one below I was able to ssh in and dump dmesg, rebooting
  via ssh froze and I had to do a hard reboot.

  [ 7557.306199] BUG: unable to handle page fault for address: 8ceca8900758
  [ 7557.306206] #PF: supervisor write access in kernel mode
  [ 7557.306209] #PF: error_code(0x0002) - not-present page
  [ 7557.306211] PGD 39601067 P4D 39601067 PUD 0
  [ 7557.306217] Oops: 0002 [#1] SMP NOPTI
  [ 7557.306221] CPU: 4 PID: 6181 Comm: chrome Tainted: GW  O  
5.6.0-1048-oem #52-Ubuntu
  [ 7557.306223] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 
01/18/2021
  [ 7557.306231] RIP: 0010:remove_wait_queue+0x25/0x50
  [ 7557.306235] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc 
53 48 89 f3 e8 f9 e2 a1 00 48 8b 53 18 4c 89 e7 48 89 c6 48 8b 43 20 <48> 89 42 
08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 43 18 48
  [ 7557.306237] RSP: 0018:b14e015cba78 EFLAGS: 00010046
  [ 7557.306240] RAX: 8caca8900750 RBX: b14e015cbc80 RCX: 
0001
  [ 7557.306242] RDX: 8ceca8900750 RSI: 0282 RDI: 
8caca8900748
  [ 7557.306244] RBP: b14e015cba88 R08: 8cac52a2c000 R09: 
0003
  [ 7557.306245] R10: 0084 R11: fffb159a R12: 
8caca8900748
  [ 7557.306247] R13:  R14: b14e015cbc70 R15: 
0001
  [ 7557.306250] FS:  7f137ff04d80() GS:8cacaf70() 
knlGS:
  [ 7557.306252] CS:  0010 DS:  ES:  CR0: 80050033
  [ 7557.306254] CR2: 8ceca8900758 CR3: 0007ee554005 CR4: 
00760ee0
  [ 7557.306255] PKRU: 5554
  [ 7557.306257] Call Trace:
  [ 7557.306265]  poll_freewait+0x42/0xa0
  [ 7557.306268]  do_sys_poll+0x480/0x520
  [ 7557.306275]  ? poll_select_finish+0x210/0x210
  [ 7557.306278]  ? poll_select_finish+0x210/0x210
  [ 7557.306282]  ? poll_select_finish+0x210/0x210
  [ 7557.306284]  ? poll_select_finish+0x210/0x210
  [ 7557.306287]  ? poll_select_finish+0x210/0x210
  [ 7557.306292]  ? fput+0x13/0x15
  [ 7557.306296]  ? __sys_sendto+0x153/0x190
  [ 7557.306300]  ? __fget_light+0x62/0x80
  [ 7557.306303]  ? fput+0x13/0x15
  [ 7557.306306]  ? __sys_recvmsg+0x88/0xa0
  [ 7557.306310]  ? ktime_get_ts64+0x4c/0xe0
  [ 7557.306313]  __x64_sys_poll+0xa5/0x140
  [ 7557.306319]  do_syscall_64+0x57/0x1b0
  [ 7557.306324]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 7557.306328] RIP: 0033:0x7f1381360aff
  [ 7557.306330] Code: 54 24 1c 48 89 74 24 10 48 89 7c 24 08 e8 79 1c f8 ff 8b 
54 24 1c 48 8b 74 24 10 41 89 c0 48 8b 7c 24 08 b8 07 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2b 44 89 c7 89 44 24 08 e8 ad 1c f8 ff 8b 44
  [ 7557.306332] RSP: 002b:7fff0cd693d0 EFLAGS: 0293 ORIG_RAX: 
0007
  [ 7557.306335] RAX: ffda RBX: 7f13828e60d0 RCX: 
7f1381360aff
  [ 7557.306336] RDX: 0ea1 RSI: 0005 RDI: 
377ea82ca210
  [ 7557.306338] RBP: 377ea82ca210 R08:  R09: 
0001
  [ 7557.306339] R10: 377ea8b40460 R11: 0293 R12: 
0005
  [ 7557.306341] R13: 7fff0cd69414 R14: 0ea1 R15: 
377ea6d9bd10
  [ 7557.306346] Modules linked in: rfcomm vboxnetadp(O) vboxnetflt(O) 
vboxdrv(O) ccm typec_displayport cmac al

[Kernel-packages] [Bug 1921576] Re: bluetooth not working on linux 5.11.0-13-generic

[Noa Sakurajin]

Since apport can not even find the package named linux, its not possible
to collect the logs properly.

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment

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

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

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

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

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

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

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

** Tags added: hirsute

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment

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

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

[Kernel-packages] [Bug 1921576] [NEW] bluetooth not working on linux 5.11.0-13-generic

[Noa Sakurajin]

Public bug reported:

1) System version:

Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

2) apt-cache policy linux-image-5.11.0-13-generic:

linux-image-5.11.0-13-generic:
  Installed: 5.11.0-13.14
  Candidate: 5.11.0-13.14
  Version table:
 *** 5.11.0-13.14 500
500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
100 /var/lib/dpkg/status

3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
4) It seems like the bluetooth adapter was not able to initialize properly, so 
that bluetooth connections are not working at all.
5) wifi/bluetooth adapter: intel 8265
6) working kernel configuration as attachment

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

** Attachment added: "working kernel config"
   
https://bugs.launchpad.net/bugs/1921576/+attachment/5481426/+files/config-5.11.5

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

Title:
  bluetooth not working on linux 5.11.0-13-generic

Status in linux package in Ubuntu:
  New

Bug description:
  1) System version:

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) apt-cache policy linux-image-5.11.0-13-generic:

  linux-image-5.11.0-13-generic:
Installed: 5.11.0-13.14
Candidate: 5.11.0-13.14
Version table:
   *** 5.11.0-13.14 500
  500 http://de.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) Bluetooth should activate correctly and I should be able to connect to 
bluetooth devices
  4) It seems like the bluetooth adapter was not able to initialize properly, 
so that bluetooth connections are not working at all.
  5) wifi/bluetooth adapter: intel 8265
  6) working kernel configuration as attachment

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

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

Re: [Kernel-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

[Gilbertf]

sound fine on 5.8.0-48-generic #54~20.04.1-Ubuntu

On 3/27/21 10:00 AM, Steph Gosling wrote:
> On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every
> other login I have no sound and the repeated message:
>
> [  257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI 
> class/subclass/prog-if info 0x040380
> [  257.494305] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
> [  257.494512] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> i915_audio_component_bind_ops [i915])
> [  257.521021] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: 
> line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
> [  257.521023] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
> (0x0/0x0/0x0/0x0/0x0)
> [  257.521025] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
> (0x21/0x0/0x0/0x0/0x0)
> [  257.521026] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
> [  257.521026] snd_hda_codec_realtek hdaudioC0D0:inputs:
> [  257.521028] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
> [  257.521029] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1b
> [  257.521030] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
> [  279.240059] snd_hda_intel :00:1f.3: azx_get_response timeout, 
> switching to polling mode: last cmd=0x202f8100
> [  280.243100] snd_hda_intel :00:1f.3: No response from codec, disabling 
> MSI: last cmd=0x202f8100
> [  281.255097] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x202f8100
> [  282.259095] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x202f8100
> [  283.267252] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20170500
>
>
> however on a log out and back in (i.e. not a reboot, but end and start an X 
> session) and the audio initialises fine the second time.
>

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

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

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[Henrik Juul Hansen]

Hi again,

I have reopened this issue. It is not fixed in mainline 5.11.0, 5.11.7
or 5.11.10.

I think I was using your kernel and mixed up the version numbers when I sent 
the message in #34. Since last I have updated BIOS version from V304->V306. For 
the last month I have been using the laptop with a USB-hub so I have not payed 
much attention to the power consumption - this is why I did not see this before 
now.
Let me know if you need me to send more information.

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  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/1912057/+subscriptions

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

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[Henrik Juul Hansen]

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  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/1912057/+subscriptions

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

[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0

[Jan Kellermann]

Kernel 5.4.0-71 is on proposed-channel and solves this problem!

Big thanks to you all!

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

Title:
  Missing Commit for 5.4-Kernel breaks  xen Dom0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  You commited "xen: Fix event channel callback via INTX/GSI" for kernel 
5.4.0-67 for HWE 18.04 and 20.04.
  This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also 
Commit "xen: Fix XenStore initialisation for XS_LOCAL"

  See https://lkml.org/lkml/2021/1/28/1235
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

  Upstream:
  Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2
  Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1

  5.10:
  Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11)
  Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13)

  5.4:
  Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93)
  Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95)

  Without this patch you cannot start guests (DomU) on this machine!

  Error message while creating DomU:
  libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to 
add device with path /
  libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add 
disk devices

  See:
  - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14
  - 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f
  - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95
  - 
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

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

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

[Kernel-packages] [Bug 1909369] Re: linux-headers-5.10.3-051003-generic is not supported

[Marvin Schin]

Thanks for coming back on the issue, Jeff.

I tried to install the bcmwl-kernel-source_6.30.223.271+bdcom-
0ubuntu8_amd64.deb but it still does not work (at least for me):

DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel
5.10.11-051011-generic (x86_64)

make: Entering directory '/usr/src/linux-headers-5.10.11-051011-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
  CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
In file included from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
 warning: this statement may fall through [-Wimplicit-fallthrough=]
   52 |  if (wl_dbg_level & WL_DBG_DBG) {   \
  | ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:794:3:
 note: in expansion of macro ‘WL_DBG’
  794 |   WL_DBG(("network eap\n"));
  |   ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:795:2:
 note: here
  795 |  default:
  |  ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function 
‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:784:2: 
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
  784 |  if ((val & 0xff00) != 0)
  |  ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:786:3: note: 
...this statement, but the latter is misleadingly indented as if it were 
guarded by the ‘if’
  786 |   bar1_size = pci_resource_len(pdev, 2);
  |   ^
  LD [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/wl.o
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  MODPOST /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/Module.symvers
make[2]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/wl.ko'.  Stop.
make[2]: *** Waiting for unfinished jobs
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/wl.mod.o
make[1]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make: *** [Makefile:1709: modules] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.11-051011-generic'

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

Title:
  linux-headers-5.10.3-051003-generic is not supported

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  > $  lsb_release -rd  
 
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  > $  sudo apt-cache policy bcmwl-kernel-source
 
  bcmwl-kernel-source:
Installé : (aucun)
Candidat : 6.30.223.271+bdcom-0ubuntu5
   Table de version :
   6.30.223.271+bdcom-0ubuntu5 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 
Packages

  Hello,

  I tried to install a wireless network adapter broadcom BCM4360, i nned to 
install the package bcmwl-kernel-source but when i try to install it i have the 
following error : "ERROR (dkms apport): kernel package 
linux-headers-5.10.3-051003-generic is not supported
  Error! Bad return status for module build on kernel: 5.10.3-051003-generic 
(x86_64)
  "

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source (not installed)
  Uname: Linux 5.10.3-051003-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 26 21:16:07 2020
  InstallationDate: Installed on 2020-01-05 (356 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

[Steph Gosling]

On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every
other login I have no sound and the repeated message:

[  257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
[  257.494305] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[  257.494512] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[  257.521021] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[  257.521023] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[  257.521025] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[  257.521026] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[  257.521026] snd_hda_codec_realtek hdaudioC0D0:inputs:
[  257.521028] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[  257.521029] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1b
[  257.521030] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[  279.240059] snd_hda_intel :00:1f.3: azx_get_response timeout, switching 
to polling mode: last cmd=0x202f8100
[  280.243100] snd_hda_intel :00:1f.3: No response from codec, disabling 
MSI: last cmd=0x202f8100
[  281.255097] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x202f8100
[  282.259095] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x202f8100
[  283.267252] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500


however on a log out and back in (i.e. not a reboot, but end and start an X 
session) and the audio initialises fine the second time.

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

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

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Sp