date:20211008

All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1020.21) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-bluefield/unknown (arm64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (arm64)
zfs-linux/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-bluefield

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1061.59)

All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1061.59) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-08 Thread Pietro

@Benjamin Your trick does not seem to work for me

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-08 Thread Benjamin Stanger

After installation same situation for me, i've attached a photo of the
output. It's really weird: On some boots i am stuck also just at the
Lenovo Logo without any more possibillities, on other try of boot, i've
got the kernel panic. Even if i disable trackpad and touchpad, but if
disabled sometimes the notebooks is booting normal.

What seems to work is turn on Notebook, go to BIOS, don't change anything but 
save with F10 and then reboot.
Notebook boots normal without error. But if i turn it off and on again -> 
kernel panic.


** Attachment added: "PXL_20211008_212338338.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5531687/+files/PXL_20211008_212338338.jpg

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-08 Thread Pietro

I have downloaded all the files and tried to install them but I have these 
errors:
There were errors in processing:
 linux-cloud-tools-5.13.0-19-generic
 linux-headers-5.13.0-19-generic
 linux-tools-5.13.0-19-generic

dpkg: error in processing the package linux-tools-5.13.0-19-generic (--install):
problems with dependencies - left unconfigured

I don't know if this can cause problems, I tried the kernel but I am
stuck with the Lenovo logo without errors

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946437] Re: snap install lxd fails

This is a brand new install, so taking image from Ubuntu 21.10,
ugprading it, then installing lxd.

But I agree, it's not an lxd thing, happens to other snap packages as
well.

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

Title:
  snap install lxd fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1061.41)

All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1061.41) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
v4l2loopback/0.10.0-1ubuntu1.2 (amd64)
asic0x/1.0.1-1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
systemd/237-3ubuntu10.52 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-azure-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-08 Thread 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/1945590

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

Test kernel is available here, if you want to give it a try:

https://kernel.ubuntu.com/~arighi/lp1945590/

Thanks!

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.

** Patch added: 
"0001-Input-elantech-reduce-stack-usage-in-elantech_create.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5531669/+files/0001-Input-elantech-reduce-stack-usage-in-elantech_create.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/1945590

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.

** Patch added: 
"0001-Input-elantech-reduce-stack-usage-in-elantech_create.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5531663/+files/0001-Input-elantech-reduce-stack-usage-in-elantech_create.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/1945590

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946515] Re: impish provides no linux-modules-nvidia-*-server packages

2021-10-08 Thread dann frazier

patch https://lists.ubuntu.com/archives/kernel-
team/2021-October/124751.html

** Changed in: linux-restricted-modules (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

Title:
  impish provides no linux-modules-nvidia-*-server packages

Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  $ apt showsrc linux-restricted-modules | grep -e ^Version: -e server

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Version: 5.13.0-16.16
  Version: 5.13.0-19.19

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

Looking at the oops it seems that the stack gets corrupted inside
elantech_change_report_id(), that is defined in
drivers/input/mouse/elantech.c.

According to Stephan it seems that 5.11 is the last kernel that seems to
work.

If we look at the changes between 5.11 and 5.13 that are touching
drivers/input/mouse/elantech.c there's only one commit:

  9d383e96448dbfdd97a37e618f6af5a17a60ce0d ("Input: elantech - Prepare a
complete software node for the device")

It'd be interesting to revert this commit in the latest 5.13 and see if
the problem goes away.

I'll prepare a test kernel later (if you haven't done it already).

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946515] [NEW] impish provides no linux-modules-nvidia-*-server packages

2021-10-08 Thread dann frazier

Public bug reported:

$ apt showsrc linux-restricted-modules | grep -e ^Version: -e server

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

Version: 5.13.0-16.16
Version: 5.13.0-19.19

** Affects: linux-restricted-modules (Ubuntu)
 Importance: High
 Status: New

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

Title:
  impish provides no linux-modules-nvidia-*-server packages

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  $ apt showsrc linux-restricted-modules | grep -e ^Version: -e server

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Version: 5.13.0-16.16
  Version: 5.13.0-19.19

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


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

[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

2021-10-08 Thread Jesse Sung

** Changed in: linux-intel-5.13 (Ubuntu Focal)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

Status in intel:
  In Progress
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  The daily build containing the new kernel does not boot.  It gets
  stuck about 2 seconds into the cycle with the message "Run /init as
  init process" (see attached image file for boot message sequence.)

  System: TGL-Aaeon (CID: 202110-29509)

  Steps to reproduce:
  Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from 
https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/

  Uncompressed file with unxz -k

  Copied the .img file to my secondary USB drive.

  Boot 20.04 LTS from primary USB drive.

  Select Try Ubuntu

  Wipe out /dev/sda (primary storage)

  Use dd to copy the image from secondary USB drive to /dev/sda

  Reboot, removing USB drives when prompted.

  Expected Result:
  System should boot Ubuntu Desktop with kernel 5.13-1006

  Actual Result:
  System hangs 2 seconds into the boot cycle with
  "Run /init as init process"

  Reproducibility: 100%

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


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

[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

2021-10-08 Thread Jesse Sung

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

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

** Changed in: linux-intel-5.13 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

Status in intel:
  In Progress
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  The daily build containing the new kernel does not boot.  It gets
  stuck about 2 seconds into the cycle with the message "Run /init as
  init process" (see attached image file for boot message sequence.)

  System: TGL-Aaeon (CID: 202110-29509)

  Steps to reproduce:
  Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from 
https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/

  Uncompressed file with unxz -k

  Copied the .img file to my secondary USB drive.

  Boot 20.04 LTS from primary USB drive.

  Select Try Ubuntu

  Wipe out /dev/sda (primary storage)

  Use dd to copy the image from secondary USB drive to /dev/sda

  Reboot, removing USB drives when prompted.

  Expected Result:
  System should boot Ubuntu Desktop with kernel 5.13-1006

  Actual Result:
  System hangs 2 seconds into the boot cycle with
  "Run /init as init process"

  Reproducibility: 100%

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


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

[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

2021-10-08 Thread Kuroš Taheri-Golværzi

Today's first crash, which happened WHILE I was taking the Linux
Foundation Certified SysAdmin (LFCS) online exam. Is there anything
helpful in these error report logs? Anything? Anything at all? Am I
wasting my time?

** Attachment added: "prevboot-2021-10-08-a.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531651/+files/prevboot-2021-10-08-a.txt

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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

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

Hello Bijay, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.12 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system

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

Hello Bijay, or anyone else affected,

Accepted pulseaudio into hirsute-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:14.2-1ubuntu1.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: pulseaudio (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal

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

Hello Bijay, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.11 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

Hello Bijay, or anyone else affected,

Accepted alsa-ucm-conf into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.4-2ubuntu1.4 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels

[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware

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

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

Title:
  [SRU] Revert amdgpu/renoir firmware

Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA 
Dongle after the system resumed from S3.

  [Fix]
  Revert below change, this issue is gone.

  commit a543b9c1bfd12e60d962acd48108234481a8581f
  Author: Alex Deucher 
  Date:   Thu Jul 1 12:23:11 2021 +0800

  amdgpu: update renoir firmware from 21.20

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

  From internal git commit:
  8b05e03570818d047d7ea0a7388c89c4192fd20b

  Signed-off-by: Alex Deucher 
  Signed-off-by: Josh Boyer 
  (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0)
  [khfeng: Squashed multiple updates into one commit]
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Timo Aaltonen 

  [Test]
  Verify S3 on renoir's platforms.

  [Where problems could occur]
  Renoir based systems can't resume from s2idle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions


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

[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types

2021-10-08 Thread Tim Gardner

** Changed in: linux-azure-5.11 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

** Changed in: linux-azure (Ubuntu Hirsute)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-5.11 package in Ubuntu:
  Invalid
Status in linux-azure-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-5.11 source package in Bionic:
  Invalid
Status in linux-azure-5.4 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-5.11 source package in Focal:
  Fix Committed
Status in linux-azure-5.4 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure-5.11 source package in Hirsute:
  Invalid
Status in linux-azure-5.4 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure-5.11 source package in Impish:
  Invalid
Status in linux-azure-5.4 source package in Impish:
  Invalid

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)

2021-10-08 Thread Juno Computers

Hi, I no longer have the laptop in which I used to report the issue. On
the other hand the issue shows up on 2 other laptops that I have, the
main difference is the thermal number.

I have test cat /sys/class/thermal/thermal_zone(number error)/type and
it does say iwlwifi_1.

Using linux-firmware 1.187.17 on Ubuntu 20.04

[2.044581] thermal thermal_zone0: failed to read out thermal zone
(-61)

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

Title:
  thermal thermal_zone4: failed to read out thermal zone (-61)

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

Bug description:
  Thermald can't read zone4. It's making my fan go crazy, this issue
  seems to be a bit more controlled in 18.10.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  sudo apt-cache policy thermald 
  thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
   *** 1.7.0-5ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  cat /sys/class/thermal/thermal_zone4/type
  iwlwifi

  find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
  /sys/class/thermal/thermal_zone4/uevent
  /sys/class/thermal/thermal_zone4/trip_point_5_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_3_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_4_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_2_type
  passive
  /sys/class/thermal/thermal_zone4/power/runtime_active_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_active_kids
  0
  /sys/class/thermal/thermal_zone4/power/runtime_usage
  0
  /sys/class/thermal/thermal_zone4/power/runtime_status
  unsupported
  /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
  cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/thermal/thermal_zone4/power/async
  disabled
  /sys/class/thermal/thermal_zone4/power/runtime_suspended_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_enabled
  disabled
  /sys/class/thermal/thermal_zone4/power/control
  auto
  /sys/class/thermal/thermal_zone4/available_policies
  power_allocator user_space bang_bang fair_share step_wise 
  /sys/class/thermal/thermal_zone4/policy
  step_wise
  /sys/class/thermal/thermal_zone4/trip_point_3_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_1_type
  passive
  /sys/class/thermal/thermal_zone4/k_d
  cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
  /sys/class/thermal/thermal_zone4/sustainable_power
  cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
  /sys/class/thermal/thermal_zone4/type
  iwlwifi
  /sys/class/thermal/thermal_zone4/trip_point_7_type
  passive
  /sys/class/thermal/thermal_zone4/offset
  cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
  /sys/class/thermal/thermal_zone4/slope
  cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_2_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_0_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_6_type
  passive
  /sys/class/thermal/thermal_zone4/emul_temp
  cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
  /sys/class/thermal/thermal_zone4/k_po
  cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
  /sys/class/thermal/thermal_zone4/integral_cutoff
  cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
  /sys/class/thermal/thermal_zone4/k_i
  cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_1_temp
  -32768000
  /sys/class/thermal/thermal_zone4/k_pu
  cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
  /sys/class/thermal/thermal_zone4/temp
  46000
  /sys/class/thermal/thermal_zone4/trip_point_7_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_5_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_0_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_6_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_4_type
  passive

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


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

[Kernel-packages] [Bug 1946487] Re: laptop trackpad not working with Ubuntu 18.04.06

2021-10-08 Thread Romi

** Description changed:

+ 0.5) System:HP Envy Laptop
+  Processor: 11th Gen Intel® Core™ i7-1165G7 @2.80GHz × 8 
+  GNOME: 3.28.2
+  OS:64-bit 
+ 
  1.) Description:  Ubuntu 18.04.6 LTS
- Release:  18.04
+ Release:  18.04
  
- 2.) N/A --> laptop trackpad not working, no specific package (or
- version)
+ 2.) N/A --> laptop trackpad not working, not sure which package to
+ include here
  
  3.) Full use of the trackpad upon installing LTS Ubuntu 18
  
  4.) No functionality for it at all
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-87-generic 5.4.0-87.98~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
  Uname: Linux 5.4.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 09:33:09 2021
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- laptop trackpad not working with Ubuntu 18.04.06
+ HP laptop trackpad not working with Ubuntu 18.04.06

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

Title:
  HP laptop trackpad not working with Ubuntu 18.04.06

Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  0.5) System:HP Envy Laptop
   Processor: 11th Gen Intel® Core™ i7-1165G7 @2.80GHz × 8 
   GNOME: 3.28.2
   OS:64-bit 

  1.) Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  2.) N/A --> laptop trackpad not working, not sure which package to
  include here

  3.) Full use of the trackpad upon installing LTS Ubuntu 18

  4.) No functionality for it at all

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-87-generic 5.4.0-87.98~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
  Uname: Linux 5.4.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 09:33:09 2021
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1938048] Re: 5.13 RT kernel hangs on SMP shutdown

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Krzysztof Kozlowski (krzk)

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

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

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

Title:
  5.13 RT kernel hangs on SMP shutdown

Status in linux package in Ubuntu:
  Triaged

Bug description:
  shutting down RT SMP 5.13 impish kernels in kvm-qemu is hanging in 1
  in 20 or so reboots. gdb shows the hang is as follows:

  #0  0x81044f72 in native_halt () at 
/home/cking/rt-impish/impish/arch/x86/include/asm/irqflags.h:57
  #1  stop_this_cpu (dummy=dummy@entry=0x0 ) at 
/home/cking/rt-impish/impish/arch/x86/kernel/process.c:744
  #2  0x8106f70c in __sysvec_reboot (regs=) at 
/home/cking/rt-impish/impish/arch/x86/kernel/smp.c:138
  #3  0x81c5f4f7 in sysvec_reboot (regs=0x82e03d78) at 
/home/cking/rt-impish/impish/arch/x86/kernel/smp.c:134
  #4  0x81e00e02 in asm_sysvec_reboot () at 
/home/cking/rt-impish/impish/arch/x86/include/asm/idtentry.h:654

  this gets stuck in:

  asm volatile("hlt": : :"memory");

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


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

[Kernel-packages] [Bug 1938918] Re: 5.13 RT kernel hits scheduling while atomic with stress-ng enosys stressor

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Krzysztof Kozlowski (krzk)

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

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

Title:
  5.13 RT kernel hits scheduling while atomic with stress-ng enosys
  stressor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  stress-ng --enosys 0 -t 60 causes:

  [  513.783315] BUG: scheduling while atomic: stress-ng/42082/0x0002
  [  513.783319] Modules linked in: cuse snd_seq snd_seq_device dccp_ipv4 dccp 
atm chacha_generic chacha_x86_64 libchacha xxhash_generic wp512 
streebog_generic sm3_generic sha3_generic rmd160 poly1305_generic 
poly1305_x86_64 nhpoly1305_avx2 nhpoly1305_sse2 nhpoly1305 libpoly1305 
michael_mic md4 cmac ccm algif_rng twofish_generic twofish_avx_x86_64 
twofish_x86_64_3way twofish_x86_64 twofish_common sm4_generic serpent_avx2 
serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic fcrypt des3_ede_x86_64 
des_generic libdes cast6_avx_x86_64 cast6_generic cast5_avx_x86_64 
cast5_generic cast_common camellia_generic camellia_aesni_avx2 
camellia_aesni_avx_x86_64 camellia_x86_64 blowfish_generic blowfish_x86_64 
blowfish_common algif_skcipher algif_hash aegis128 aegis128_aesni algif_aead 
af_alg nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
intel_rapl_msr intel_rapl_common kvm_intel joydev kvm input_leds rapl serio_raw 
snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg
  [  513.783355]  snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep 
mac_hid snd_pcm snd_timer snd soundcore qemu_fw_cfg sch_fq_codel msr virtio_rng 
ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic qxl usbhid drm_ttm_helper 
ttm crct10dif_pclmul hid drm_kms_helper crc32_pclmul syscopyarea sysfillrect 
ghash_clmulni_intel sysimgblt fb_sys_fops aesni_intel cec crypto_simd cryptd 
psmouse virtio_net ahci rc_core virtio_blk i2c_i801 net_failover libahci drm 
lpc_ich i2c_smbus failover
  [  513.783387] CPU: 7 PID: 42082 Comm: stress-ng Tainted: GW 
5.13.0-1003-realtime #3-Ubuntu
  [  513.783389] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [  513.783390] Call Trace:
  [  513.783393]  show_stack+0x52/0x58
  [  513.783397]  dump_stack+0x7d/0x9c
  [  513.783400]  __schedule_bug.cold+0x4a/0x5b
  [  513.783403]  __schedule+0x53a/0x6b0
  [  513.783405]  ? rt_spin_unlock+0x18/0x50
  [  513.783407]  ? task_blocks_on_rt_mutex.constprop.0.isra.0+0x168/0x430
  [  513.783409]  schedule_rtlock+0x1f/0x40
  [  513.783411]  rtlock_slowlock_locked+0xf7/0x240
  [  513.783412]  ? memcg_slab_post_alloc_hook+0x53/0x280
  [  513.783416]  rt_spin_lock+0x46/0x70
  [  513.783417]  alloc_pid+0x1b4/0x3e0
  [  513.783421]  copy_process+0x9ef/0x15e0
  [  513.783423]  ? kernel_wait4+0xcf/0x150
  [  513.783425]  kernel_clone+0x9d/0x350
  [  513.783427]  ? __do_sys_wait4+0x84/0x90
  [  513.783429]  ? rt_spin_unlock+0x18/0x50
  [  513.783430]  __do_sys_clone+0x5d/0x80
  [  513.783432]  __x64_sys_clone+0x25/0x30
  [  513.783434]  do_syscall_64+0x61/0xb0
  [  513.783446]  ? handle_mm_fault+0xdf/0x2c0
  [  513.783449]  ? do_user_addr_fault+0x1eb/0x670
  [  513.783452]  ? exit_to_user_mode_prepare+0x37/0xb0
  [  513.783454]  ? irqentry_exit_to_user_mode+0x9/0x20
  [  513.783455]  ? irqentry_exit+0x33/0x40
  [  513.783457]  ? exc_page_fault+0x92/0x1c0
  [  513.783458]  ? asm_exc_page_fault+0x8/0x30
  [  513.783460]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [  513.783462] RIP: 0033:0x7fce804fcb59
  [  513.783464] Code: ed 0f 85 1a 01 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 
31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 0f 87 93 00 00 00 41 89 c5 85 c0 0f 85 a0 00 00
  [  513.783465] RSP: 002b:7ffd36496060 EFLAGS: 0246 ORIG_RAX: 
0038
  [  513.783471] RAX: ffda RBX: 7ffd36496140 RCX: 
7fce804fcb59
  [  513.783472] RDX:  RSI:  RDI: 
01200011
  [  513.783473] RBP:  R08:  R09: 
55eebbfb7140
  [  513.783473] R10: 7fce80019e50 R11: 0246 R12: 

  [  513.783474] R13: a656 R14: 7ffd364965a0 R15: 
7fce7340

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


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

[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  thermal thermal_zone4: failed to read out thermal zone (-61)

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

Bug description:
  Thermald can't read zone4. It's making my fan go crazy, this issue
  seems to be a bit more controlled in 18.10.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  sudo apt-cache policy thermald 
  thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
   *** 1.7.0-5ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  cat /sys/class/thermal/thermal_zone4/type
  iwlwifi

  find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
  /sys/class/thermal/thermal_zone4/uevent
  /sys/class/thermal/thermal_zone4/trip_point_5_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_3_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_4_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_2_type
  passive
  /sys/class/thermal/thermal_zone4/power/runtime_active_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_active_kids
  0
  /sys/class/thermal/thermal_zone4/power/runtime_usage
  0
  /sys/class/thermal/thermal_zone4/power/runtime_status
  unsupported
  /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
  cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/thermal/thermal_zone4/power/async
  disabled
  /sys/class/thermal/thermal_zone4/power/runtime_suspended_time
  0
  /sys/class/thermal/thermal_zone4/power/runtime_enabled
  disabled
  /sys/class/thermal/thermal_zone4/power/control
  auto
  /sys/class/thermal/thermal_zone4/available_policies
  power_allocator user_space bang_bang fair_share step_wise 
  /sys/class/thermal/thermal_zone4/policy
  step_wise
  /sys/class/thermal/thermal_zone4/trip_point_3_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_1_type
  passive
  /sys/class/thermal/thermal_zone4/k_d
  cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
  /sys/class/thermal/thermal_zone4/sustainable_power
  cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
  /sys/class/thermal/thermal_zone4/type
  iwlwifi
  /sys/class/thermal/thermal_zone4/trip_point_7_type
  passive
  /sys/class/thermal/thermal_zone4/offset
  cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
  /sys/class/thermal/thermal_zone4/slope
  cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_2_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_0_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_6_type
  passive
  /sys/class/thermal/thermal_zone4/emul_temp
  cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
  /sys/class/thermal/thermal_zone4/k_po
  cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
  /sys/class/thermal/thermal_zone4/integral_cutoff
  cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
  /sys/class/thermal/thermal_zone4/k_i
  cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
  /sys/class/thermal/thermal_zone4/trip_point_1_temp
  -32768000
  /sys/class/thermal/thermal_zone4/k_pu
  cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
  /sys/class/thermal/thermal_zone4/temp
  46000
  /sys/class/thermal/thermal_zone4/trip_point_7_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_5_type
  passive
  /sys/class/thermal/thermal_zone4/trip_point_0_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_6_temp
  -32768000
  /sys/class/thermal/thermal_zone4/trip_point_4_type
  passive

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


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

[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  Frequently getting thermal warnings and cpu throttling messages in
  syslog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Nov  6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature 
above threshold, cpu clock throttled (total events = 50300) 


 
  Nov  6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature 
above threshold, cpu clock throttled (total events = 50300) 


 
  Nov  6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core 
temperature/speed normal


 
  Nov  6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core 
temperature/speed normal


 
  Nov  6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package 
temperature/speed normal


  
  Nov  6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature 
above threshold, cpu clock throttled (total events = 50316) 


 
  Nov  6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature 
above threshold, cpu clock throttled (total events = 50316) 


 
  Nov  6

[Kernel-packages] [Bug 1786575] Re: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up

** Changed in: thermald (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan
  Spin Up

Status in thermald package in Ubuntu:
  Won't Fix

Bug description:
  Main Problems:

  - Incorrect performance throttling results in Thermal Shutdown Event (~100C 
on CPU) as reported in BIOS log
  - System fan during system idle powers at full speed for 1 second every 
minute or so (could also be GPU fan)

  Environment:

  Dell BIOS: 1.3.0 (Also present in 1.2.0, 1.1.3)
  CPU: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Operating Systems: Ubuntu 18.04.1 LTS
  Thermald Version: 1.7
  Ubuntu Thermald Package: 1.7.0-5ubuntu1
  Kernel: 4.17.14-041714-generic (Also present with 4.15.0-29, 4.15.0-30, 
4.17.11-041711)
  Intel Microcode: 3.20180425.1~ubuntu0.18.04.2
  Nvidia Driver: 396.51-0ubuntu0~gpu18.04.1
  TLP Package: 1.1-2ubuntu1

  I've documented this issue on the thermald Github page with thermald
  debug logs and configuration:
  https://github.com/intel/thermal_daemon/issues/161

  Basically, I've attempted to set the temperature for B0D4 to as low as
  85000 and while the debug log seems to indicate the trip has be made,
  the CPU scailing isn't working to keep the CPU from thermal shutdown.
  Disabling Turbo Boost prevents shutdown of the system.

  I'd expect thermald to performance throttle the CPU correctly to
  prevent it from a thermal overheat event.

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


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

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  Confirmed

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
  [  967.637943] RAX: ffda

[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

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

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Very occasionally systemd panics on reboots of an azure instance. A
  workaround to this issue is described in comment #20

  
  

  
  Description:   In the event a particular Azure cloud instance is rebooted 
it's possible that it may never recover and the instance will break 
indefinitely.

  In My case, it was a kernel panic. See specifics below..

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I had a simple script to reboot an instance (X) amount of times, I
  chose 50, so the machine would power cycle by issuing a "reboot" from
  the terminal prompt just as a user would.   Once the machine came up,
  it captured dmesg and other bits then rebooted again until it reached
  50.

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  this only occurred once in my testing.

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


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

[Kernel-packages] [Bug 1901266] Re: system sluggish, thermal keep frequency at 400MHz

** Changed in: thermald (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  system sluggish, thermal keep frequency at 400MHz

Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  This morning I upgraded to 20.10 from 20.04

  The system was quite slow although I have a fast machine. My virtual windows 
10 on virtualbox became unusable. When I tried to have the virtual machine 
open, I could not participate properly in a zoom call (I could still hear the 
people but they said that my voice was very choppy)
  On 20.04 I was super-happy with the speed and I could have as many apps 
running as I want.

  Based on google I started looking at 
  % journalctl --follow
  and this shows quite a few errors but not repeating often enough to explain 
it.

  Then I googled some more and found that /boot/efi was writing and
  reading.

  Then I googled some more and thought I had trouble with gnome. So I reset it 
to default
  % dconf reset -f /org/gnome/
  and disabled the extensions. This made things slightly better but by far not 
acceptable.

  After lots of searching I checked the frequency of the CPUs and it was at the 
minimum 400Hz (as shown by i7z and also other tools). I tried setting the 
governor with cpufreqctl and similar methods but this did not change anything.
  I then found an old bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried 
  % sudo systemctl stop thermald
  this seems to work. After a few seconds the frequency shown in i7z goes to 
~4500 MHz and the virtual machine seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: thermald 2.3-4
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 01:39:40 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+merion+X66
  InstallationDate: Installed on 2019-09-27 (392 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: thermald
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  mtime.conffile..etc.thermald.thermal-conf.xml: 2020-10-24T01:35:59.781865

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


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

[Kernel-packages] [Bug 1937773] Re: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0

** Changed in: linux (Ubuntu Impish)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

** Changed in: linux (Ubuntu Impish)
 Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Krzysztof Kozlowski 
(krzk)

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

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

Title:
  WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173
  __local_bh_disable_ip+0xce/0xe0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Incomplete

Bug description:
  I just hit this oops running impish:linux-realtime (5.13) inside a kvm
  instance. It looks like there's a locking issue between cgroups (idr
  allocator) and some real-time specific patches:

  [5.278177] DEBUG_LOCKS_WARN_ON(this_cpu_read(softirq_ctrl.cnt))
  [5.278184] WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 
__local_bh_disable_ip+0xce/0xe0
  [5.278189] Modules linked in: nls_utf8 isofs nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua ccp kvm input_leds joydev serio_raw 
mac_hid qemu_fw_cfg sch_fq_codel msr ip_tables x_tables autofs4 btrfs 
blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops cec rc_core virtio_net psmouse virtio_blk i2c_i801 ahci 
net_failover xhci_pci failover xhci_pci_renesas drm libahci i2c_smbus lpc_ich
  [5.278209] CPU: 0 PID: 1 Comm: systemd Not tainted 5.13.0-1001-realtime 
#1-Ubuntu
  [5.278211] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.14.0-2 04/01/2014
  [5.278212] RIP: 0010:__local_bh_disable_ip+0xce/0xe0
  [5.278213] Code: 76 ff ff ff e8 a3 bd 50 00 85 c0 74 a3 8b 05 11 92 0f 02 
85 c0 75 99 48 c7 c6 88 29 3c 9e 48 c7 c7 02 cd 3a 9e e8 7b ee b4 00 <0f> 0b eb 
82 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00
  [5.278214] RSP: 0018:ac46c0013d40 EFLAGS: 00010286
  [5.278216] RAX:  RBX: 0200 RCX: 
0027
  [5.278216] RDX: 0027 RSI: 4000e2df RDI: 
9df4fbc18a58
  [5.278217] RBP: ac46c0013d48 R08: 9df4fbc18a50 R09: 
9f30a523
  [5.278218] R10:  R11: 284e4f5f4e524157 R12: 
9edd1e30
  [5.278218] R13:  R14: 0002 R15: 

  [5.278219] FS:  7f1d42909900() GS:9df4fbc0() 
knlGS:
  [5.278220] CS:  0010 DS:  ES:  CR0: 80050033
  [5.278221] CR2: 561b36c201a0 CR3: 00010280 CR4: 
06f0
  [5.278222] Call Trace:
  [5.278224]  cgroup_idr_alloc.constprop.0+0x38/0xd0
  [5.278226]  css_create+0x117/0x1e0
  [5.278228]  cgroup_apply_control_enable+0x13b/0x160
  [5.278229]  cgroup_mkdir+0xe2/0x1c0
  [5.278230]  kernfs_iop_mkdir+0x5c/0x90
  [5.278232]  vfs_mkdir+0x181/0x220
  [5.278234]  do_mkdirat+0x122/0x150
  [5.278236]  __x64_sys_mkdir+0x1b/0x20
  [5.278237]  do_syscall_64+0x61/0xb0
  [5.278239]  ? syscall_exit_to_user_mode+0x27/0x50
  [5.278241]  ? __x64_sys_mkdir+0x1b/0x20
  [5.278242]  ? do_syscall_64+0x6e/0xb0
  [5.278243]  ? do_syscall_64+0x6e/0xb0
  [5.278244]  ? asm_exc_page_fault+0x8/0x30
  [5.278245]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [5.278246] RIP: 0033:0x7f1d430ca81b
  [5.278247] Code: 8b 05 59 86 0d 00 41 bc ff ff ff ff 64 c7 00 16 00 00 00 
e9 37 ff ff ff e8 c2 0c 02 00 66 90 f3 0f 1e fa b8 53 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 25 86 0d 00 f7 d8 64 89 01 48
  [5.278248] RSP: 002b:7fffaf9cdc78 EFLAGS: 0202 ORIG_RAX: 
0053
  [5.278249] RAX: ffda RBX: 561b36d8d940 RCX: 
7f1d430ca81b
  [5.278249] RDX:  RSI: 01ed RDI: 
561b36db9700
  [5.278250] RBP: 7f1d434ef52f R08:  R09: 

  [5.278250] R10:  R11: 0202 R12: 

  [5.278251] R13: 561b36d8d940 R14: 0001 R15: 
0073
  [5.278252] ---[ end trace 0002 ]---

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


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

[Kernel-packages] [Bug 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs

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

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

Title:
  Enable intel_pstate by default on Trusty EC2 AMIs

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Please can the intel_pstate driver be enabled by default on the Ubuntu
  EC2 AMIs. On instances with support for C-states and P-States [1]
  there is a notable performance impact and lack of support for higher
  clock frequencies available due to the use of the acpi-cpufreq driver.
  For example on a c4.8xlarge the default frequency is limited to 2.9GHz
  when 3.2GHz is supported by the chip [2]. Some additional analysis is
  available here [3] and re-enabling it by default has been discussed
  [4] but this request is specifically for the EC2 AMIs.

  [1] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html
  [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html
  [3] 
http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html
  [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647

  AMI: ami-47a23a30 (eu-west-1)

  $ lsb_release -d
  Description:Ubuntu 14.04.2 LTS

  $ uname -a
  Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  Default configuration (c4.8xl):
  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.90 GHz
available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 
GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 
GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 1.20 GHz and 2.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 
GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 
GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 
GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51%  (5)
boost state support:
  Supported: yes
  Active: yes

  With intel_pstate enabled (c4.8xl):
  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 0.97 ms.
hardware limits: 1.20 GHz - 3.50 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.20 GHz (asserted by call to hardware).
boost state support:
  Supported: yes
  Active: yes
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 12 17:19 seq
   crw-rw 1 root audio 116, 33 Aug 12 17:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [39221.196411] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-47a23a30
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1b
  Ec2InstanceType: c4.8xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=877c5daf-9427-49e3-8656-437c3f30fc84 ro console=tty1 console=ttyS0
  ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty ec2-images
  Uname: Linux

[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC

Any update on this Chris?

** Changed in: thermald (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  thermald often limits CPU frequency while on AC

Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  I'm not entirely sure if this is a thermald issue, but on my laptop
  (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
  is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz
  turbo frequency.

  Restarting thermald (with `systemctl restart thermald`) will let the
  system scale up to the expected ~3.8GHz boost frequency.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thermald 2.4.6-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 19 09:24:56 2021
  InstallationDate: Installed on 2021-06-26 (53 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1876856] Re: xenial: soft lockup in check_unsafe_exec()

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

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

Title:
  xenial: soft lockup in check_unsafe_exec()

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Endless cycle was detected few times during ubuntu 16.04 testing insied 
openvz VMs
  dmesg output and crash dump ivestigation shows that foolowing ubuntu 
16.04.patch is guilty
  commit d6572202d986a84feda4cf7e6ce0bebaa18cb8fe
  Author: Colin Ian King 
  Date:   Fri May 12 15:51:56 2017 +0100
  UBUNTU:SAUCE: exec: ensure file system accounting in check_unsafe_exec is 
correct
  
  BugLink: http://bugs.launchpad.net/bugs/1672819

  fs/exec.c:: check_unsafe_exec()
  ...
  recheck:
  fs_recheck = false;
  t = p;
  n_fs = 1;
  spin_lock(>fs->lock);
  rcu_read_lock();
  while_each_thread(p, t) {
  if (t->fs == p->fs)
  n_fs++;
  if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
  fs_recheck  = true;
  }
  rcu_read_unlock();
   
  if (p->fs->users > n_fs) {
  if (fs_recheck) {
  spin_unlock(>fs->lock);
  goto recheck; << cycles forever
  }
  bprm->unsafe |= LSM_UNSAFE_SHARE;
  } else
  p->fs->in_exec = 1;
  spin_unlock(>fs->lock);

  dmesg example is attached,
  let me know if you want to look at  crash dump image.
  Bug is xenial-specific (4.4 kernel), other kernel branches seems are not 
affected.

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


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

[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

Hi, I updated this bug a couple of months ago to see if recent backport
fixes addressed the issue. If this has helped, please add your notes to
the bug report so we can close the issue.

** Changed in: thermald (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Invalid
Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle

Marking this as Won't Fix as this bug has not been updated for a year.

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

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

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

Title:
  Fan excessively runs, even when idle

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I have a skull canyon NUC as my daily driver and the fan is running
  much higher than it should, even when the machine is completely idle.

  This happened with the 5.3 kernel and also with the 5.4 kernel during
  focal development cycle. It was fixed somewhere along the way prior to
  release but it's back with a vengeance now.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   4523 F pulseaudio
   /dev/snd/controlC0:  dean   4523 F pulseaudio
   /dev/snd/controlC1:  dean   4523 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  1 08:37:23 2020
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (677 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/ubuntu--vg-root 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: Upgraded to focal on 2020-01-07 (145 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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


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

[Kernel-packages] [Bug 1881810] Re: ZFS import cause panic

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  ZFS import cause panic

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  1)
  Ubuntu 20.04 LTS

  2)
  apt policy zfsutils-linux
  zfsutils-linux:
  Installed: 0.8.3-1ubuntu12
  Candidate:0.8.3-1ubuntu12

  3)
  ZFS pool not possible to import, unless using read only.
  If trying to import normal way as write/read, casing panic message

  Expected to be able to import zpool without panic.
  Expected that scrub should not be able to run in read only.
  Expected that somehow be able to restore the zpool somehow.


  
  4)
  # zpool status
  no pools available
  # zpool import
 pool: datastore
   id: 3190464655986727485
state: ONLINE
   status: Some supported features are not enabled on the pool.
   action: The pool can be imported using its name or numeric identifier, though
  some features will not be available without an explicit 'zpool 
upgrade'.
   config:

  datastore   ONLINE
raidz2-0  ONLINE
  sdb ONLINE
  sdc ONLINE
  sdd ONLINE
  sde ONLINE
  sdf ONLINE
  sdg ONLINE

  # zpool import -o readonly=on datastore
  # zpool status
pool: datastore
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub in progress since Sun May 10 00:24:01 2020
  15,1T scanned at 0B/s, 15,1T issued at 0B/s, 15,1T total
  1,44M repaired, 100,01% done, no estimated completion time
  config:

  NAMESTATE READ WRITE CKSUM
  datastore   ONLINE   0 0 0
raidz2-0  ONLINE   0 0 0
  sdb ONLINE   0 0 0
  sdc ONLINE   0 0 0
  sdd ONLINE   0 0 0
  sde ONLINE   0 0 0
  sdf ONLINE   0 0 0
  sdg ONLINE   0 0 0

  errors: No known data errors

  
  Running zdb it always stops ad 2,23T and then aborts.
  # zdb -e -bcsvL datastore
  Traversing all blocks to verify checksums ...
  2.23T completed ( 149MB/s) estimated time remaining: 25hr 06min 25sec
free(): invalid pointer
  Abort (SIGABRT)

  
  #zpool import datastore
  VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (36028797018963967 
< 32768)
  PANIC at zio.c:293:zio_buf_alloc()

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


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

[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

** Changed in: thermald (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  CPU frequency stuck at minimum value

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

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gjditchf   1190 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (10 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre Laptop 13-af0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A2
  dmi.board.vendor: HP
  dmi.board.version: 55.24
  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.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion:

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

2021-10-08 Thread Po-Hsu Lin

** Changed in: ubuntu-kernel-tests
 Assignee: Po-Hsu Lin (cypressyew) => (unassigned)

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  [ Impact ]
  When running the net/rtnetlink.sh selftest from v5.4 on older Ubuntu releases 
(e.g. Bionic 18.04), some of the iproute2 CLI options are not available causing 
the testcase to fail.

  [ Fix ]
  SAUCE patch to detect whether some options not present on older iproute2 
versions are available, skipping or adapting the tests.

  [ Test ]
  Run net/rtnetlink.sh on 5.4 kernels with both Focal and Bionic userspace. The 
test should complete without introducing regressions on Focal and without 
breaking on Bionic.

  [ Where problems could occur ]
  If the checks for the available interfaces are not done correctly, we could 
end up having a smaller coverage on Focal or the tests would still break in 
Bionic.

  [ Original bug description ]
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before 
fixing the false-negative return value of this rtnetlink.sh test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # FAIL: erspan
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   #

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

Proposed fix sent to the ML:

https://lists.ubuntu.com/archives/kernel-team/2021-October/124738.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/1896448

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  [ Impact ]
  When running the net/rtnetlink.sh selftest from v5.4 on older Ubuntu releases 
(e.g. Bionic 18.04), some of the iproute2 CLI options are not available causing 
the testcase to fail.

  [ Fix ]
  SAUCE patch to detect whether some options not present on older iproute2 
versions are available, skipping or adapting the tests.

  [ Test ]
  Run net/rtnetlink.sh on 5.4 kernels with both Focal and Bionic userspace. The 
test should complete without introducing regressions on Focal and without 
breaking on Bionic.

  [ Where problems could occur ]
  If the checks for the available interfaces are not done correctly, we could 
end up having a smaller coverage on Focal or the tests would still break in 
Bionic.

  [ Original bug description ]
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before 
fixing the false-negative return value of this rtnetlink.sh test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # FAIL: erspan
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

** Description changed:

- Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before
- fixing the false-negative return value of this rtnetlink.sh test (bug
- 1890136)
+ [ Impact ]
+ When running the net/rtnetlink.sh selftest from v5.4 on older Ubuntu releases 
(e.g. Bionic 18.04), some of the iproute2 CLI options are not available causing 
the testcase to fail.
+ 
+ [ Fix ]
+ SAUCE patch to detect whether some options not present on older iproute2 
versions are available, skipping or adapting the tests.
+ 
+ [ Test ]
+ Run net/rtnetlink.sh on 5.4 kernels with both Focal and Bionic userspace. The 
test should complete without introducing regressions on Focal and without 
breaking on Bionic.
+ 
+ [ Where problems could occur ]
+ If the checks for the available interfaces are not done correctly, we could 
end up having a smaller coverage on Focal or the tests would still break in 
Bionic.
+ 
+ [ Original bug description ]
+ Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before 
fixing the false-negative return value of this rtnetlink.sh test (bug 1890136)
  
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap
  
-  # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
-  # [ local ADDR ]
-  # [ [i|o]seq ]
-  # [ [i|o]key KEY ]
-  # [ [i|o]csum ]
-  # [ ttl TTL ]
-  # [ tos TOS ]
-  # [ [no]pmtudisc ]
-  # [ [no]ignore-df ]
-  # [ dev PHYS_DEV ]
-  # [ noencap ]
-  # [ encap { fou | gue | none } ]
-  # [ encap-sport PORT ]
-  # [ encap-dport PORT ]
-  # [ [no]encap-csum ]
-  # [ [no]encap-csum6 ]
-  # [ [no]encap-remcsum ]
-  # [ external ]
-  # [ fwmark MARK ]
-  # [ erspan IDX ]
-  #
-  # Where: ADDR := { IP_ADDRESS | any }
-  # TOS := { NUMBER | inherit }
-  # TTL := { 1..255 | inherit }
-  # KEY := { DOTTED_QUAD | NUMBER }
-  # MARK := { 0x0..0x }
-  # Cannot find device "erspan00"
-  # Cannot find device "erspan00"
-  # Cannot find device "erspan00"
-  # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
-  # [ local ADDR ]
-  # [ [i|o]seq ]
-  # [ [i|o]key KEY ]
-  # [ [i|o]csum ]
-  # [ ttl TTL ]
-  # [ tos TOS ]
-  # [ [no]pmtudisc ]
-  # [ [no]ignore-df ]
-  # [ dev PHYS_DEV ]
-  # [ noencap ]
-  # [ encap { fou | gue | none } ]
-  # [ encap-sport PORT ]
-  # [ encap-dport PORT ]
-  # [ [no]encap-csum ]
-  # [ [no]encap-csum6 ]
-  # [ [no]encap-remcsum ]
-  # [ external ]
-  # [ fwmark MARK ]
-  # [ erspan IDX ]
-  #
-  # Where: ADDR := { IP_ADDRESS | any }
-  # TOS := { NUMBER | inherit }
-  # TTL := { 1..255 | inherit }
-  # KEY := { DOTTED_QUAD | NUMBER }
-  # MARK := { 0x0..0x }
-  # Cannot find device "erspan00"
-  # Cannot find device "erspan00"
-  # Cannot find device "erspan00"
-  # FAIL: erspan
-  # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
-  # [ local ADDR ]
-  # [ [i|o]seq ]
-  # [ [i|o]key KEY ]
-  # [ [i|o]csum ]
-  # [ hoplimit TTL ]
-  # [ encaplimit ELIM ]
-  # [ tclass TCLASS ]
-  # [ flowlabel FLOWLABEL ]
-  # [ dscp inherit ]
-  # [ fwmark MARK ]
-  # [ dev PHYS_DEV ]
-  # [ noencap ]
-  # [ encap { fou | gue | none } ]
-  # [ encap-sport PORT ]
-  # [ encap-dport PORT ]
-  # [ [no]encap-csum ]
-  # [ [no]encap-csum6 ]
-  # [ [no]encap-remcsum ]
-  # [ erspan IDX ]
-  #
-  # Where: ADDR := IPV6_ADDRESS
-  # TTL := { 0..255 } (default=64)
-  # KEY := { DOTTED_QUAD | NUMBER }
-  # ELIM := { none | 0..255 }(default=4)
-  # TCLASS := { 0x0..0xff | inherit }
-  # FLOWLABEL := { 0x0..0xf | inherit }
-  # MARK := { 0x0..0x | inherit }
-  # Cannot find device "ip6erspan00"
-  # Cannot find device "ip6erspan00"
-  # Cannot find device "ip6erspan00"
-  # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
-  # [ local ADDR ]
-  # [ [i|o]seq ]
-  # [ [i|o]key KEY ]
-  # [ [i|o]csum ]
-  # [ hoplimit TTL ]
-  # [ encaplimit ELIM ]
-  # [ tclass TCLASS ]
-  # [ flowlabel FLOWLABEL ]
-  # [ dscp inherit ]
-  # [ fwmark MARK ]
-  # [ dev PHYS_DEV ]
-  # [ noencap ]
-  # [ encap { fou | gue | none } ]
-  # [ encap-sport PORT ]
-  # [ encap-dport PORT ]
-  # [ [no]encap-csum ]
-  # [ [no]encap-csum6 ]
-  # [ [no]encap-remcsum ]
-  # [ erspan IDX ]
-  #
-  # Where: ADDR := IPV6_ADDRESS
-  # TTL := { 0..255 } (default=64)
-  #

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted
  before fixing the false-negative return value of this rtnetlink.sh
  test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # FAIL: erspan
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device

[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types

2021-10-08 Thread Tim Gardner

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

** Changed in: linux-azure-5.11 (Ubuntu Bionic)
   Status: New => Invalid

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

** Changed in: linux-azure-5.11 (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure-5.11 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-azure-5.11 (Ubuntu Impish)
   Status: New => Invalid

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

** Changed in: linux-azure-5.4 (Ubuntu Bionic)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux-azure-5.4 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-azure-5.4 (Ubuntu Impish)
   Status: New => Invalid

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

** Changed in: linux-azure-5.4 (Ubuntu Focal)
   Status: In Progress => Invalid

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-5.11 package in Ubuntu:
  Invalid
Status in linux-azure-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-5.11 source package in Bionic:
  Invalid
Status in linux-azure-5.4 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-5.11 source package in Focal:
  In Progress
Status in linux-azure-5.4 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure-5.11 source package in Hirsute:
  Invalid
Status in linux-azure-5.4 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure-5.11 source package in Impish:
  Invalid
Status in linux-azure-5.4 source package in Impish:
  Invalid

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-08 Thread Benjamin Stanger

I just want to confirm this problem also with impish-proposed kernel,
same hardware here and exactly same situation.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946437] Re: snap install lxd fails

2021-10-08 Thread Stéphane Graber

Removing the LXD task as this isn't a LXD bug, the error is coming from
snapd when setting up the apparmor profiles. Most likely explanation is
that there's something pretty wrong going on with your /etc/apparmor.d
on your system. The errors indicate a variety of missing abstractions
files.

** Changed in: lxd (Ubuntu)
   Status: New => Invalid

** No longer affects: lxd (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/1946437

Title:
  snap install lxd fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64

[Kernel-packages] [Bug 1946487] [NEW] laptop trackpad not working with Ubuntu 18.04.06

2021-10-08 Thread Romi

Public bug reported:

1.) Description:Ubuntu 18.04.6 LTS
Release:18.04

2.) N/A --> laptop trackpad not working, no specific package (or
version)

3.) Full use of the trackpad upon installing LTS Ubuntu 18

4.) No functionality for it at all

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-87-generic 5.4.0-87.98~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
Uname: Linux 5.4.0-87-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  8 09:33:09 2021
InstallationDate: Installed on 2021-10-07 (0 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  laptop trackpad not working with Ubuntu 18.04.06

Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  1.) Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  2.) N/A --> laptop trackpad not working, no specific package (or
  version)

  3.) Full use of the trackpad upon installing LTS Ubuntu 18

  4.) No functionality for it at all

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-87-generic 5.4.0-87.98~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
  Uname: Linux 5.4.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 09:33:09 2021
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1942932] Re: oob_net0 up but stops processing Rx packets

This bug is awaiting verification that the linux-bluefield/5.4.0-1020.23
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

Title:
  oob_net0 up but stops processing Rx packets

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  * The oob_net0 interface, managed by the mlxbf_gige driver, will be
up and enabled but can stop processing received packets if three
specific conditions occur:
1) driver has received more than (N * RxRingSize) packets but less
   than (N+1 * RxRingSize) packets where N is an odd number.
   Note: the command "ethtool -g oob_net0" will display the current
   receive ring size, which currently defaults to 128.
2) the driver's interface was disabled via "ifconfig oob_net0 down"
   during the window described in #1.
3) the driver's interface is re-enabled via "ifconfig oob_net0 up"

Without this fix, the driver needs to be unloaded and re-loaded
to correct this condition.

  [Fix]
  * The fix is to ensure that the driver's "valid_polarity" field
is cleared during the open() method so that it always matches
the receive polarity used by hardware.

  [Test Case]
  * To test this fix, need to send in a specific number of packets to
the "oob_net0" interface, then issue "ifconfig oob_net0 down" to
disable the interface.  A subsequent "ifconfig oob_net0 up" command
will succesfully bring up the "oob_net0" interface and start the
processing of received packets.

  [Regression Potential]
  * There is low risk of this fix causing any problems.

  [Other]
  * The mlxbf_gige driver will display v1.25 in modinfo after these changes.

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


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

[Kernel-packages] [Bug 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts

This bug is awaiting verification that the linux-bluefield/5.4.0-1020.23
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

Title:
  "ethtool -S oob_net0" does not report interrupt counts

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  * The command "ethtool -S oob_net0" displays a set of statistics
related to mlxbf_gige driver.  This set of statistics does not
include the driver's interrupt counts.

  [Fix]
  * The fix is to extend the statistics list supported by "ethtool -S"
so that it includes MAC, receive packet, and LLU/PLU interrupt counts.

  [Test Case]
  * The command "ethtool -S oob_net0" should be executed before and 
after this fix to verify that three new fields are displayed:
  mac_intr_count
  rx_intr_count
  llu_plu_intr_count

  [Regression Potential]
  * There is low risk of this fix causing any problems.

  [Other]
  * n/a

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


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

[Kernel-packages] [Bug 1943065] Re: mlxbf_gige: update driver version to 1.25

This bug is awaiting verification that the linux-bluefield/5.4.0-1020.23
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

Title:
  mlxbf_gige: update driver version to 1.25

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  * The mlxbf_gige driver needs a version increase to identify
a driver containing recent important bug fixes.

  [Fix]
  * The driver version implemented by the DRV_VERSION define and
MODULE_VERSION macro will be incremented from 1.24 to 1.25

  [Test Case]
  * To test this fix, need to check the driver version shown in
the output of "modinfo mlxbf_gige" command.

  [Regression Potential]
  * There is low risk of this fix causing any problems.

  [Other]
  * The mlxbf_gige driver will display v1.25 in modinfo after these changes.

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


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

[Kernel-packages] [Bug 1946219] Re: liburing stops working after upgrading to 5.4.0-1012

This bug is awaiting verification that the linux-bluefield/5.4.0-1020.23
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

Title:
  liburing stops working after upgrading to 5.4.0-1012

Status in HWE Next:
  New
Status in linux-bluefield package in Ubuntu:
  In Progress
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  == Impact ==
  After configuration multipath with io uring virtio_blk module is stuck

  == Fix ==
  The issue was introduced by one of the stable updates merged in the base 
kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be 
reproduced any more.

  commit d6757b3e34831b7615edd3268b878536761f8b2e
  Author: Pavel Begunkov 
  Date:   Fri Nov 20 17:10:28 2020 +

  block: don't ignore REQ_NOWAIT for direct IO
  
  BugLink: https://bugs.launchpad.net/bugs/1926490
  
  [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ]
  
  If IOCB_NOWAIT is set on submission, then that needs to get propagated to
  REQ_NOWAIT on the block side. Otherwise we completely lose this
  information, and any issuer of IOCB_NOWAIT IO will potentially end up
  blocking on eg request allocation on the storage side.
  
  Signed-off-by: Pavel Begunkov 
  Signed-off-by: Jens Axboe 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Stefan Bader 

  == Risk of Regression ==
  Medium. The commit has a good reason to be part of the stable updates. 
However the kernel passes Cert and Nvidia tests without the commit so reverting 
the commit should be an acceptable approach for now.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1060.58)

All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1060.58) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
nvidia-graphics-drivers-470/470.63.01-0ubuntu0.20.04.2 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1060.40)

All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1060.40) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
asic0x/1.0.1-1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
v4l2loopback/0.10.0-1ubuntu1.2 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-azure-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

2021-10-08 Thread Kuroš Taheri-Golværzi

Report from last night. Is there anything useful in these recent ones?

** Attachment added: "prevboot-2021-10-07.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531551/+files/prevboot-2021-10-07.txt

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()

2021-10-08 Thread Robert Bordelon

I've hit this bug on a non-encrypted pool. FS scrub also reported no
errors for me. I'm currently on Kernel 5.11.0-37-generic / zfs libs
2.0.2-1ubuntu5.2 (Hirsute), though the corruption may have occurred on a
previous kernel / library. The directory which is triggering the hang
for me was created Jun 7 of this year so it appears to be recent
problem. I've identified the corrupted directory and moved it out of the
way (fortunately is contains nothing important), but I'm unable to
delete it from the filesystem. Any attempts to read or delete the
directory hangs. Setting zfs_recovery=1 does not help. The only way I
can recover from hang is to reboot. I'd like to know if there is any way
to get rid of the corrupted directory other than having to create a new
filesystem and copy over all the other files / dirs except the problem
one?

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

Title:
  PANIC at zfs_znode.c:339:zfs_znode_sa_init()

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing a non-deterministic panic in the ZFS code. Last boot, this
  occurred in systemd-udevd, resulting in a failed boot. The boot before
  that, firefox hit the same thing, and this boot it looks like it's hit
  an Evolution component.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  4988 F pulseaudio
   /dev/snd/controlC1:  chris  4988 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 11 11:49:47 2021
  InstallationDate: Installed on 2021-05-13 (28 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.198
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

The test script fails at the following part:

# test external mode
ip -netns "$testns" link add dev "$DEV_NS" type ip6gretap external
check_err $?

Which executes:

# ip -netns testns link add dev ip6gretap00 type ip6gretap external

Looking at ip-link(8) manpage, the ip6gretap type accepts the following
options:

ip link add DEVICE type { ip6gre | ip6gretap } remote ADDR local ADDR [ 
[i|o]seq ]
  [ [i|o]key KEY ] [ [i|o]csum ] [ hoplimit TTL ] [ encaplimit ELIM 
] [ tclass TCLASS
  ] [ flowlabel FLOWLABEL ] [ dscp inherit ] [ dev PHYS_DEV ]

So "external" is not supported yet in this iproute2 version
(4.15.0-2ubuntu).

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

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted
  before fixing the false-negative return value of this rtnetlink.sh
  test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # FAIL: erspan
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [

[Kernel-packages] [Bug 1946463] Re: Ubuntu 20.04.3 default crashkernel size insufficient for kdump

2021-10-08 Thread Frank Heimes

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

After discussing with the kernel team I'm marking this as duplicate of 
LP#1877533,
since an increase of the default crashkernel size will solve both cases.

** This bug has been marked a duplicate of bug 1877533
   [20.10 FEAT] Increase the crashkernel setting if the root volume is 
luks2-encrypted

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

Title:
  Ubuntu 20.04.3 default crashkernel size insufficient for kdump

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

Bug description:
  ---Problem Description---
  Unable to take a dump using kdump on host, service is enabled and correctly 
configured.
  "[6.110044] Kernel panic - not syncing: System is deadlocked on memory

  ---uname output---
  Linux ilzlnx3.tuc.stglabs.ibm.com 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 
19:07:49 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = S/390 
   
  ---System Hang---
   Once the kdump is unsuccessful, I have to load it from the HMC.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Trigger kdump with a crash by:
  sysctl -w kernel.sysrq=1
  echo c > /proc/sysrq-trigger
   
  *Additional Instructions for vanessa.ba...@ibm.com , finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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


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

[Kernel-packages] [Bug 1946464] Re: Invalid backport to v4.15: missing pgtable_l5_enabled

2021-10-08 Thread Krzysztof Kozlowski

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

Title:
  Invalid backport to v4.15: missing pgtable_l5_enabled

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]

  Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
  1. It adds pgtable_l5_enabled which does not exist in v4.15,
  2. It is marked as v4.17+
  3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.

  allyesconfig in x86_64 fails to build:
  ---
  In file included from ../arch/x86/include/asm/mmu_context.h:12,
   from ../include/linux/mmu_context.h:5,
   from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
  ../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
  ../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ 
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
    185 |  if (!pgtable_l5_enabled)
    |   ^~
    |   movable_node_enabled

  ---

  [Test Plan]

  Compile the x86_64 KVM code.

  [Where problems could occur]

  If backport commit is actually needed, e.g. when we backport 5-level
  page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
  layer at runtime"), this could cause double-free and memory
  corruption.

  When backporting x86_64 5-level pages, we need to bring this commit as
  well.

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


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

[Kernel-packages] [Bug 1946463] Re: Ubuntu20.04.3 default crashkernel size insufficient for kdump

2021-10-08 Thread Frank Heimes

The initial crashkernel size is just a default value - that was in the
past a reasonable good value.

So it's not uncommon that one needs to increase the crashkernel size for a 
particular situation and setup.
The default size is always a trade-off between reserving enough space for all 
possible situations and environments vs. not reserving and wasting too much 
space.

But we already noticed that the default needs an increase nowadays,
which was in general already addressed in LP#1877533. LP#1877533 is not
done yet, since the approach is to do it in alignment with Debian.

Nevertheless, I tend to mark this LP#1946463 as duplicate of LP#1877533
...

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

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

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
Team (canonical-kernel-team)

** Summary changed:

- Ubuntu20.04.3 default crashkernel size insufficient for kdump
+ Ubuntu 20.04.3 default crashkernel size insufficient for kdump

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

Title:
  Ubuntu 20.04.3 default crashkernel size insufficient for kdump

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

Bug description:
  ---Problem Description---
  Unable to take a dump using kdump on host, service is enabled and correctly 
configured.
  "[6.110044] Kernel panic - not syncing: System is deadlocked on memory

  ---uname output---
  Linux ilzlnx3.tuc.stglabs.ibm.com 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 
19:07:49 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = S/390 
   
  ---System Hang---
   Once the kdump is unsuccessful, I have to load it from the HMC.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Trigger kdump with a crash by:
  sysctl -w kernel.sysrq=1
  echo c > /proc/sysrq-trigger
   
  *Additional Instructions for vanessa.ba...@ibm.com , finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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


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

[Kernel-packages] [Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4

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

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

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

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

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

Title:
  seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on
  B-5.4

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

Bug description:
  Issue found on 5.4.0-48.52~18.04.1

  Test build failed with:
   gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
   seccomp_bpf.c: In function ‘get_metadata’:
   seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known
   struct seccomp_metadata md;
   ^~
   seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] 
   Makefile:12: recipe for target 'seccomp_bpf' failed

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


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

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

** Tags added: sru-20210927

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

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted
  before fixing the false-negative return value of this rtnetlink.sh
  test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # FAIL: erspan
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Cannot find device "ip6erspan00"
   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [

[Kernel-packages] [Bug 1944613] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)

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

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

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

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

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

** Also affects: linux-hwe-5.4 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux-hwe-5.4 (Ubuntu Focal)
   Status: New => Invalid

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

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

** Changed in: linux-hwe-5.4 (Ubuntu)
   Status: New => Invalid

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

Title:
  memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown
  type name ‘__u64’)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux-hwe-5.4 source package in Focal:
  Invalid

Bug description:
  [Impact]
  BugLink: https://bugs.launchpad.net/bugs/1944613

  There are build issues in selftests/memfd/fuse_test.c where __u64 is not 
  defined. This is issue is probably due to the fact that in 5.4 there is
  a type include in one of the includes in the file, however this include
  probably was not there for 4.15. Regardless we fix this by including the 
  type file directly. 

  [Fix]
  * selftests/memfd: fix __u64 not defined build issue
  Add #include  to define the type

  [Test Plan]
  Recompile tests to make sure they build and tests pass.

  [Where problems could occur]
  Should be no problems since we are adding an include file that userspace
  files always have access to. 

  --

  
  Failed to build on B/linux-hwe-5.4 5.4.0-85.95~18.04.1. This was observed in 
previous cycles.
  I am working on a fix for it right now.

    13203   fuse_test.c:63:8: error: unknown type name ‘__u64’
    13204static __u64 mfd_assert_get_seals(int fd)
    13205   ^
    13206   fuse_test.c:76:42: error: unknown type name ‘__u64’; 
did you mean ‘__f64’?
    13207static void mfd_assert_has_seals(int fd, __u64 seals)
    13208 ^
    13209 __f64
    13210   fuse_test.c:88:42: error: unknown type name ‘__u64’; 
did you mean ‘__f64’?
    13211static void mfd_assert_add_seals(int fd, __u64 seals)
    13212 ^
    13213 __f64
    13214   fuse_test.c:102:39: error: unknown type name ‘__u64’; 
did you mean ‘__f64’?
    13215static int mfd_busy_add_seals(int fd, __u64 seals)
    13216  ^
    13217  __f64
    13218   fuse_test.c: In function ‘sealing_thread_fn’:
    13219   fuse_test.c:185:6: warning: implicit declaration of 
function ‘mfd_busy_add_seals’; did you mean ‘mfd_assert_get_seals’? 
[-Wimplicit-function-declaration]
    13220 r = mfd_busy_add_seals(global_mfd, F_SEAL_WRITE);
    13221 ^~
    13222 mfd_assert_get_seals
    13223   fuse_test.c:193:3: warning: implicit declaration of 
function ‘mfd_assert_add_seals’; did you mean ‘mfd_assert_get_seals’? 
[-Wimplicit-function-declaration]
    13224  mfd_assert_add_seals(global_mfd, F_SEAL_WRITE);
    13225  ^~~~
    13226  mfd_assert_get_seals
    13227   fuse_test.c: In function ‘main’:
    13228   fuse_test.c:302:2: warning: implicit declaration of 
function ‘mfd_assert_has_seals’; did you mean ‘mfd_assert_get_seals’? 
[-Wimplicit-function-declaration]
    13229 mfd_assert_has_seals(mfd, F_SEAL_WRITE);
    13230 ^~~~
    13231 mfd_assert_get_seals
    13232   make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/fuse_test]
 Error 1
    13233   make: *** [all] Error 2

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

[Kernel-packages] [Bug 1946460] Re: My touchpad is completely not working. Please help.

2021-10-08 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
My touchpad is completely not working. Please help.

Status in linux-signed-hwe-5.11 package in Ubuntu:
New

Bug description:
My touchpad is completely failing me. Help me please.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 8 12:27:52 2021
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946460/+subscriptions

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

[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear

This bug is awaiting verification that the linux-hwe-5.8/5.8.0-66.74
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

Title:
  BCM57800 SRIOV bug causes interfaces to disappear

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  bnx2x driver won't add all devices ports/interfaces.

  [Test case]
  Boot system with bnx2x device and verify all ports/interfaces have been added.

  [Potential regression]
  bnx2x devices won't be properly probed. Devices won't be added or SR-IOV 
won't be correctly supported.

  --- Original Description ---

  Works with focal kernel 5.4.0-80
  Broken with focal kernel 5.4.0-88

  On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network
  cards Kernel 5.11.22-3 causes half of the network interfaces to
  disappear specifically the 1gb ports. Commands like "ip link show" and
  "dmesg" no longer show eno3 and eno4 nor any other interface name for
  these ports. I've read the note in the release notes and this does not
  appear to be a case of the interface changing names, the 3rd and 4th
  interface don't show up at all.

  The card is based on the BCM57800 chipset and has two SFP+ and two
  gigabit ports on the same card. Commands like "ip link show" no longer
  show ports 3 and 4. "lspci" still shows four items. dmesg only shows
  the first two interfaces.

  This problem seems to be known upstream, and seems to be a regression.

  More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558

  This is being seen at a customer during an openstack install. It would
  be appreciated if a workaround could be provided or the fix could be
  prioritized. Using standard Focal 20.04 LTS kernel (it installs ok
  with the working kernel then upgrades to the non-working one -- this
  is done through maas and is difficult to control).

  Tested other kernels like hwe-* and all seem to be affected too.

  Client does not want to disable SRIOV on whole card and also cannot
  disable only ports 3/4 (the bios will not allow it).

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


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

[Kernel-packages] [Bug 1945987] Re: linux: btrfs: fix NULL pointer dereference when deleting device by invalid id

This bug is awaiting verification that the linux-hwe-5.8/5.8.0-66.74
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

Title:
  linux: btrfs: fix NULL pointer dereference when deleting device by
  invalid id

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure-5.8 package in Ubuntu:
  Invalid
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-5.8 source package in Focal:
  In Progress
Status in linux-hwe-5.8 source package in Focal:
  Fix Committed

Bug description:
  [BUG]
  It's easy to trigger NULL pointer dereference, just by removing a
  non-existing device id:

   # mkfs.btrfs -f -m single -d single /dev/test/scratch1 \
 /dev/test/scratch2
   # mount /dev/test/scratch1 /mnt/btrfs
   # btrfs device remove 3 /mnt/btrfs

  Then we have the following kernel NULL pointer dereference:

   BUG: kernel NULL pointer dereference, address: 
   #PF: supervisor read access in kernel mode
   #PF: error_code(0x) - not-present page
   PGD 0 P4D 0
   Oops:  [#1] PREEMPT SMP NOPTI
   CPU: 9 PID: 649 Comm: btrfs Not tainted 5.14.0-rc3-custom+ #35
   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
   RIP: 0010:btrfs_rm_device+0x4de/0x6b0 [btrfs]
btrfs_ioctl+0x18bb/0x3190 [btrfs]
? lock_is_held_type+0xa5/0x120
? find_held_lock.constprop.0+0x2b/0x80
? do_user_addr_fault+0x201/0x6a0
? lock_release+0xd2/0x2d0
? __x64_sys_ioctl+0x83/0xb0
__x64_sys_ioctl+0x83/0xb0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae

  [CAUSE]
  Commit a27a94c2b0c7 ("btrfs: Make btrfs_find_device_by_devspec return
  btrfs_device directly") moves the "missing" device path check into
  btrfs_rm_device().

  But btrfs_rm_device() itself can have case where it only receives
  @devid, with NULL as @device_path.

  In that case, calling strcmp() on NULL will trigger the NULL pointer
  dereference.

  Before that commit, we handle the "missing" case inside
  btrfs_find_device_by_devspec(), which will not check @device_path at all
  if @devid is provided, thus no way to trigger the bug.

  [FIX]
  Before calling strcmp(), also make sure @device_path is not NULL.

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


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

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

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 1946464

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

** Changed in: linux (Ubuntu Bionic)
   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/1946464

Title:
  Invalid backport to v4.15: missing pgtable_l5_enabled

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

Bug description:
  [Impact]

  Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
  1. It adds pgtable_l5_enabled which does not exist in v4.15,
  2. It is marked as v4.17+
  3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.

  allyesconfig in x86_64 fails to build:
  ---
  In file included from ../arch/x86/include/asm/mmu_context.h:12,
   from ../include/linux/mmu_context.h:5,
   from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
  ../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
  ../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ 
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
    185 |  if (!pgtable_l5_enabled)
    |   ^~
    |   movable_node_enabled

  ---

  [Test Plan]

  Compile the x86_64 KVM code.

  [Where problems could occur]

  If backport commit is actually needed, e.g. when we backport 5-level
  page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
  layer at runtime"), this could cause double-free and memory
  corruption.

  When backporting x86_64 5-level pages, we need to bring this commit as
  well.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.65.47)

All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.65.47) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

evdi/1.9.1-1ubuntu4~20.04.1 (ppc64el)
linux-hwe-5.8/5.8.0-65.73 (ppc64el, arm64, amd64, s390x)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-hwe-5.8

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1946464] [NEW] Invalid backport to v4.15: missing pgtable_l5_enabled

2021-10-08 Thread Krzysztof Kozlowski

Public bug reported:

[Impact]

Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
1. It adds pgtable_l5_enabled which does not exist in v4.15,
2. It is marked as v4.17+
3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.

allyesconfig in x86_64 fails to build:
---
In file included from ../arch/x86/include/asm/mmu_context.h:12,
 from ../include/linux/mmu_context.h:5,
 from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ undeclared 
(first use in this function); did you mean ‘movable_node_enabled’?
  185 |  if (!pgtable_l5_enabled)
  |   ^~
  |   movable_node_enabled

---

[Test Plan]

Compile the x86_64 KVM code.

[Where problems could occur]

If backport commit is actually needed, e.g. when we backport 5-level
page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table layer
at runtime"), this could cause double-free and memory corruption.

When backporting x86_64 5-level pages, we need to bring this commit as
well.

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Incomplete


** Tags: bionic

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

** Description changed:

+ [Impact]
+ 
  Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
  1. It adds pgtable_l5_enabled which does not exist in v4.15,
  2. It is marked as v4.17+
  3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.
  
  allyesconfig in x86_64 fails to build:
  ---
  In file included from ../arch/x86/include/asm/mmu_context.h:12,
-  from ../include/linux/mmu_context.h:5,
-  from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
+  from ../include/linux/mmu_context.h:5,
+  from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
  ../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
  ../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ 
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
-   185 |  if (!pgtable_l5_enabled)
-   |   ^~
-   |   movable_node_enabled
+   185 |  if (!pgtable_l5_enabled)
+   |   ^~
+   |   movable_node_enabled
  
  ---
+ 
+ [Test Plan]
+ 
+ Compile the x86_64 KVM code.
+ 
+ [Where problems could occur]
+ 
+ If backport commit is actually needed, e.g. when we backport 5-level
+ page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table layer
+ at runtime"), this could cause double-free and memory corruption.
+ 
+ When backporting x86_64 5-level pages, we need to bring this commit as
+ well.

** Tags added: bionic

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

Title:
  Invalid backport to v4.15: missing pgtable_l5_enabled

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

Bug description:
  [Impact]

  Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
  1. It adds pgtable_l5_enabled which does not exist in v4.15,
  2. It is marked as v4.17+
  3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.

  allyesconfig in x86_64 fails to build:
  ---
  In file included from ../arch/x86/include/asm/mmu_context.h:12,
   from ../include/linux/mmu_context.h:5,
   from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
  ../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
  ../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ 
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
    185 |  if (!pgtable_l5_enabled)
    |   ^~
    |   movable_node_enabled

  ---

  [Test Plan]

  Compile the x86_64 KVM code.

  [Where problems could occur]

  If backport commit is actually needed, e.g. when we backport 5-level
  page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
  layer at runtime"), this could cause double-free and memory
  corruption.

  When backporting x86_64 5-level pages, we need to bring this commit as
  well.

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


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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

2021-10-08 Thread Sebastien Bacher

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Impish)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system
  can't detect them, and couldn't output sound through headphone and
  record sound through Mic.

  [Fix]
  Backport a upstream patch, this will set the Mic to auto-detection
  mode and set the headphone to left location.

  [Test]
  Plug a headset to the headset audio jack, both headphone and mic
  could be detected. And output the sound to headphone, could hear
  the sound, record the sound through Mic, the sound could be recorded.

  [Where problems could occur]
  The patch is specific to Acer Aspire 5 machine, if it could introduce
  regression, it will make the audio like internal mic and internal spk
  stop working. But this possibility is very low.

  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I

[Kernel-packages] [Bug 1946463] sosreport-ilzlnx3-194306-2021-09-02-gudyizi.tar

2021-10-08 Thread bugproxy

Default Comment by Bridge

** Attachment added: "sosreport-ilzlnx3-194306-2021-09-02-gudyizi.tar"
   
https://bugs.launchpad.net/bugs/1946463/+attachment/5531515/+files/sosreport-ilzlnx3-194306-2021-09-02-gudyizi.tar.xz

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

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

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

Title:
  Ubuntu20.04.3 default crashkernel size insufficient for kdump

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Unable to take a dump using kdump on host, service is enabled and correctly 
configured.
  "[6.110044] Kernel panic - not syncing: System is deadlocked on memory

  ---uname output---
  Linux ilzlnx3.tuc.stglabs.ibm.com 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 
19:07:49 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = S/390 
   
  ---System Hang---
   Once the kdump is unsuccessful, I have to load it from the HMC.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Trigger kdump with a crash by:
  sysctl -w kernel.sysrq=1
  echo c > /proc/sysrq-trigger
   
  *Additional Instructions for vanessa.ba...@ibm.com , finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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


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

[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system

2021-10-08 Thread Stefan Bader

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

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

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

Title:
  Fix A yellow screen pops up in an instant (< 1 second) and then
  disappears before loading the system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  *** this issue happen with secure boot on and issue gone when secure boot is 
off***

  After the BIOS loading screen, a yellow screen pops up in an instant
  (< 1 second) and then disappears. Attached a demo video.

  [Fix]
  do what intel_color_commit() does to make sure the bottom color state
  matches whatever out hardware readout produced.
  Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1

  [Test]
  1. Power on the system
  2. Check if any unusual screen shows before and after the system loading 
screen.
  3. No unusual screen shows before and after the system loading screen

  [Regression Potential]
  Medium, maintainer still not totally sure what should do about color 
management
  features here in general.

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


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

[Kernel-packages] [Bug 1946463] [NEW] Ubuntu20.04.3 default crashkernel size insufficient for kdump

2021-10-08 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

---Problem Description---
Unable to take a dump using kdump on host, service is enabled and correctly 
configured.
"[6.110044] Kernel panic - not syncing: System is deadlocked on memory

---uname output---
Linux ilzlnx3.tuc.stglabs.ibm.com 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 
19:07:49 UTC 2021 s390x s390x s390x GNU/Linux
 
Machine Type = S/390 
 
---System Hang---
 Once the kdump is unsuccessful, I have to load it from the HMC.
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Trigger kdump with a crash by:
sysctl -w kernel.sysrq=1
echo c > /proc/sysrq-trigger
 
*Additional Instructions for vanessa.ba...@ibm.com , finne...@us.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on.

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


** Tags: architecture-s39064 bugnameltc-194306 severity-high 
targetmilestone-inin20044
-- 
Ubuntu20.04.3 default crashkernel size insufficient for kdump
https://bugs.launchpad.net/bugs/1946463
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 1946200] Re: With Nvidia-470 there is no option to use Wayland on the login screen

2021-10-08 Thread Daniel van Vugt

I wonder if we should NOT enable nvidia-drm.modeset=1 as it might reduce
the available features in the Nvidia legacy/native driver for Xorg.
Maintaining stability and continuity there is probably more important
than enabling Wayland support by default right now...


** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  With Nvidia-470 there is no option to use Wayland on the login screen

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

Bug description:
  Starting in impish with nvidia-470 and the latest gdm3 and xwayland
  packages, Wayland is fully supported in theory but you never get any
  option to select Wayland on the login screen. There is no session menu
  and you always get Xorg instead.

  WORKAROUND:

  Edit /etc/default/grub and change:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

  and then:

sudo update-grub

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


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

[Kernel-packages] [Bug 1946460] [NEW] My touchpad is completely not working. Please help.

2021-10-08 Thread Daniel Joshua Nyaga

Public bug reported:

My touchpad is completely failing me. Help me please.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  8 12:27:52 2021
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (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 linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1946460

Title:
  My touchpad is completely not working. Please help.

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  My touchpad is completely failing me. Help me please.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 12:27:52 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946460/+subscriptions


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

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-08 Thread paul janssen

Possible work around (not a fix), blacklist module i2c_i801. It works
for me ...

Since I noticed a high amount of CPU time spent in interrupt handling I looked 
at /proc/interrupts (right after the slow boot and slow login):
$ cat /proc/interrupts
CPU0   CPU1   
   0:  9  0  IR-IO-APIC2-edge  timer
   1:  0249  IR-IO-APIC1-edge  i8042
   8:  1  0  IR-IO-APIC8-fasteoi   rtc0
   9:  0   1017  IR-IO-APIC9-fasteoi   acpi
  14:  0591  IR-IO-APIC   14-fasteoi   INT3453:00, INT3453:01, 
INT3453:03
  15:  0  0  IR-IO-APIC   15-fasteoi   INT3453:02
  20:  190734634  0  IR-IO-APIC   20-fasteoi   i801_smbus
  31:   8350  0  IR-IO-APIC   31-fasteoi   idma64.0, 
i2c_designware.0
  39:  0  84628  IR-IO-APIC   39-fasteoi   mmc0
 120:  0  0  DMAR-MSI0-edge  dmar0
 121:  0  0  DMAR-MSI1-edge  dmar1
 122:  0  0  IR-PCI-MSI 311296-edge  PCIe PME
 123:  0  0  IR-PCI-MSI 315392-edge  PCIe PME
 124:  0  0  IR-PCI-MSI 317440-edge  PCIe PME
 125:  0  0  IR-PCI-MSI 294912-edge  ahci[:00:12.0]
 126:  0  3  IR-PCI-MSI 1048576-edge  rtsx_pci
 127:   4171  0  IR-PCI-MSI 344064-edge  xhci_hcd
 128:  0296  INT3453:00   18  ELAN0503:00
 129:  0  0  IR-PCI-MSI 1050624-edge  enp2s0f1
 130:  0 44  IR-PCI-MSI 245760-edge  mei_me
 131:  18279  0  IR-PCI-MSI 1572864-edge  ath10k_pci
 132:  0669  IR-PCI-MSI 229376-edge  snd_hda_intel:card0
 NMI:690 49   Non-maskable interrupts
 LOC: 693366 704015   Local timer interrupts
 SPU:  0  0   Spurious interrupts
 PMI:690 49   Performance monitoring interrupts
 IWI:  31340  91937   IRQ work interrupts
 RTR:  0  0   APIC ICR read retries
 RES:  23071  21772   Rescheduling interrupts
 CAL:  10091   3666   Function call interrupts
 TLB:   2750   4570   TLB shootdowns
 TRM:  0  0   Thermal event interrupts
 THR:  0  0   Threshold APIC interrupts
 DFR:  0  0   Deferred Error APIC interrupts
 MCE:  0  0   Machine check exceptions
 MCP: 10 11   Machine check polls
 ERR:  0
 MIS:  0
 PIN:  0  0   Posted-interrupt notification event
 NPI:  0  0   Nested posted-interrupt event
 PIW:  0  0   Posted-interrupt wakeup event

This lead me to the module i801_smbus which depends on i2c_i801 module (found 
this out using lsmod).
Following this ~similar~ issue 
(https://bbs.archlinux.org/viewtopic.php?id=254885) I decided to give 
blacklisting i2c_i801 a try.

I added "module_blacklist=i2c_i801" to the kernel parameters (via edit
action in grub boot menu), and "viola!" the problem was gone.

Note: I do not fully understand the consequences of not having the
i2C_i801 and i801_smbus modules.

The ?better? way (not via kernel parameter) to blacklist the module
permanently seems to be described here
(https://www.thegeekdiary.com/centos-rhel-how-to-disable-and-blacklist-
linux-kernel-module-to-prevent-it-from-loading-automatically/)

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

Title:
  kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

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

Bug description:
  Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad
  performance and very unresponsive to user input on Lenovo laptop
  Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G).

  When this happens you can read this kind of messages on journal:

  ---
  root@alumne-1-58:~# journalctl | grep "BUG: soft"
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [prometheus-node:4220]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 22s! [swapper/1:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck

[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

2021-10-08 Thread Kent Lin

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

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

Status in intel:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
  [Steps to reproduce]
  1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to 
the system
  2. Boot to desktop
  3. Check if all Ethernet get IP address
  [Expected result]
  All Ethernet Port should up and runing and get the IP address.
  [Actual result]
  I225-IT Ethernet (8086:0d9f) does not work and did not get IP address
  [Failure rate]
  100%
  [Additional information]
  CID: 202109-29492
  SKU: N/A
  system-manufacturer: AAEON
  system-product-name: UPN-EHL01
  bios-version: UNEHAM0D
  CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571] (rev 01)
  kernel-version: 5.13.0-1004-intel

  [Stage]
  Issue reported and logs collected right after it happened

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


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

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

[Kernel-packages] [Bug 1946437] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1946437/+attachment/5531497/+files/PaInfo.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/1946437

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

[Kernel-packages] [Bug 1946437] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1946437/+attachment/5531486/+files/acpidump.txt

** Description changed:

  This is what I get:
  
  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  berend 3841 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ HibernationDevice: RESUME=none
+ InstallationDate: Installed on 2021-10-07 (0 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
+ MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon

[Kernel-packages] [Bug 1946437] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1946437/+attachment/5531507/+files/acpidump.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/1946437

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice:

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice:

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

apport information

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

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10

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

apport information

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

Title:
  snap install lxd fails

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

Bug description:
  This is what I get:

  sudo snap install lxd
  error: cannot perform the following tasks:
  - Setup snap "lxd" (21624) security profiles for auto-connections (cannot 
setup profiles for snap "lxd": cannot load apparmor profiles: exit status 1
  apparmor_parser output:
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.activate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.activate at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.benchmark at line 632: 
Could not open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.buginfo at line 632: Could 
not open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.check-kernel at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.daemon in 
profile /etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.configure in profile 
/etc/apparmor.d/abstractions/nameservice at line 115: Could not open 
'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.hook.remove at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxc in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxc at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd in profile 
/var/lib/snapd/apparmor/profiles/snap.lxd.lxc-to-lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.lxd in 
profile /var/lib/snapd/apparmor/profiles/snap.lxd.lxd at line 632: Could not 
open 'abstractions/dbus-strict'
  AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.lxd.migrate 
in profile /var/lib/snapd/apparmor/profiles/snap.lxd.migrate at line 632: Could 
not open 'abstractions/dbus-strict'
  )
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: lxd
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_cfqyq8@/vmlinuz-5.13.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_cfqyq8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-16-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: 06/25/2021
  dmi.bios.release: 4.2
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.04.02
  dmi.board.name: 880D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.2E.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.46
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.04.02:bd06/25/2021:br4.2:efr48.46:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvr:sku4A6P8PA#ABG:rvnHP:rn880D:rvrKBCVersion30.2E.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
  dmi.product.sku: 4A6P8PA#ABG
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  berend 3841 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice:

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