[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
One more case: - Hardware: Mainboard "Asus Prime B-560M-A" - Software: Debian GNU/Linux 11 (bullseye); Kernel Linux 5.10.0-10-amd64 - systemd-journald messages: Jan 12 09:57:53 system systemd-journald[79944]: Missed 12 kernel messages ░░ Subject: Journal messages have been missed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ Kernel messages have been lost as the journal system has been unable ░░ to process them quickly enough. - Kernel messages (dmesg) that make systemd-journald to collapse: [19209.926816] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [19209.926817] pcieport :00:1c.5: device [8086:43bd] error status/mask=0001/2000 [19209.926817] pcieport :00:1c.5:[ 0] RxErr Workaround: Adding "pcie_aspm=off" to GRUB_CMDLINE_LINUX parameter at /etc/default/grub and run: sudo update-grub Next reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Not a long term fix but just proposing this as this saved me from not
booting in pop_os! 21.10.
Disable either the trackpad or trackpoint in BIOS. I disabled my
trackpoint and I am able to boot again.
Just so that other users who end up here have some temporary workaround,
as to update the kernel to fix this requires booting off usb or with
this method.
--
You 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:
Fix Committed
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
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 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
FYI looking in dmesg and boot.log I could see the long wait was for
systemd. Using journalctl I could see the long pause was zfs-import-
cache & zfs-load-module waiting for systemd-udev-settle (which is
presumably hanging due to the amd related kernel problem). I am not
using zfs so I systemctl disabled systemd-udev-settle zfs-import-cache,
zfs-load-module & zfs-mount (which is what depended on those two) which
now results in my system booting quickly. This is not a good general
solution (as people might need zfs, but I don't) and the system still
hangs when shutting down. I just wanted to document this here in case it
proves useful to anyone else.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957847] 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 1957847 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957847 Title: display output detection problem Status in linux package in Ubuntu: Incomplete Bug description: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957847] [NEW] display output detection problem
Public bug reported: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957847 Title: display output detection problem Status in linux package in Ubuntu: New Bug description: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957843] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957843 Title: package linux-headers-5.4.0-88 5.4.0-88.99 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: was running apt install get -f to try to fix a problem that was preventing a chrome update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-88 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wiley 2178 F pulseaudio /dev/snd/controlC1: wiley 2178 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 13 17:37:33 2022 DpkgHistoryLog: Start-Date: 2022-01-13 17:33:45 Commandline: apt-get install -f Requested-By: wiley (1000) Install: linux-image-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94:amd64 (5.4.0-94.106, automatic), linux-modules-extra-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-modules-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.86.90, 5.4.0.94.98), linux-image-generic:amd64 (5.4.0.88.92, 5.4.0.94.98), linux-generic:amd64 (5.4.0.88.92, 5.4.0.94.98) DuplicateSignature: package:linux-headers-5.4.0-88:5.4.0-88.99 Unpacking linux-headers-generic (5.4.0.94.98) over (5.4.0.86.90) ... dpkg: error processing package linux-headers-5.4.0-88 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-11-06 (799 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6440 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=708f76df-25d9-43a2-98c0-fc1aa8ae33ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux Title: package linux-headers-5.4.0-88 5.4.0-88.99 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0YX2X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd05/19/2017:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn0YX2X3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957843] [NEW] package linux-headers-5.4.0-88 5.4.0-88.99 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf
Public bug reported: was running apt install get -f to try to fix a problem that was preventing a chrome update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-88 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wiley 2178 F pulseaudio /dev/snd/controlC1: wiley 2178 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 13 17:37:33 2022 DpkgHistoryLog: Start-Date: 2022-01-13 17:33:45 Commandline: apt-get install -f Requested-By: wiley (1000) Install: linux-image-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94:amd64 (5.4.0-94.106, automatic), linux-modules-extra-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-modules-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.86.90, 5.4.0.94.98), linux-image-generic:amd64 (5.4.0.88.92, 5.4.0.94.98), linux-generic:amd64 (5.4.0.88.92, 5.4.0.94.98) DuplicateSignature: package:linux-headers-5.4.0-88:5.4.0-88.99 Unpacking linux-headers-generic (5.4.0.94.98) over (5.4.0.86.90) ... dpkg: error processing package linux-headers-5.4.0-88 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-11-06 (799 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6440 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=708f76df-25d9-43a2-98c0-fc1aa8ae33ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux Title: package linux-headers-5.4.0-88 5.4.0-88.99 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0YX2X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd05/19/2017:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn0YX2X3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957843 Title: package linux-headers-5.4.0-88 5.4.0-88.99 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: New Bug description: was running apt install get -f to try to fix a problem that was preventing a chrome update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-88 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wiley 2178 F pulseaudio /dev/snd/controlC1: wiley 2178 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 13 17:37:33 2022 DpkgHistoryLog: Start-Date: 2022-01-13 17:33:45 Commandline: apt-get install -f Requested-By: wiley (1000) Install: linux-image-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94:amd64 (5.4.0-94.106, automatic), linux-modules-extra-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-headers-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic), linux-modules-5.4.0-94-generic:amd64 (5.4.0-94.106, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.86.90, 5.4.0.94.98), linux-image-generic:amd64 (5.4.0.88.92, 5.4.0.94.98), linux-generic:amd64 (5.4.0.88.92, 5.4.0.94.98) DuplicateSignature: package:linux-headers-5.4.0-88:5.4.0-88.99 Unpacking linux-headers-generic (5.4.0.94.98) over (5.4.0.86.90) ... dpkg: error processing package linux-headers-5.4.0-88 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state;
[Kernel-packages] [Bug 1957842] Re: Hirsute update: upstream stable patchset 2022-01-13
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2022-01-13
-upstream stable patchset 2022-01-13
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v5.10.85, v5.15.8
+
+ from git://git.kernel.org/
+
+ usb: gadget: uvc: fix multiple opens
+ HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
+ HID: google: add eel USB id
+ HID: add hid_is_usb() function to make it simpler for USB detection
+ HID: add USB_HID dependancy to hid-prodikeys
+ HID: add USB_HID dependancy to hid-chicony
+ HID: add USB_HID dependancy on some USB HID drivers
+ HID: bigbenff: prevent null pointer dereference
+ HID: wacom: fix problems when device is not a valid USB device
+ HID: check for valid USB device for many HID drivers
+ nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
+ IB/hfi1: Insure use of smp_processor_id() is preempt disabled
+ IB/hfi1: Fix early init panic
+ IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
+ can: kvaser_usb: get CAN clock frequency from device
+ can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
+ can: sja1000: fix use after free in ems_pcmcia_add_card()
+ x86/sme: Explicitly map new EFI memmap table as encrypted
+ drm/amd/amdkfd: adjust dummy functions' placement
+ drm/amdkfd: separate kfd_iommu_resume from kfd_resume
+ drm/amdgpu: add amdgpu_amdkfd_resume_iommu
+ drm/amdgpu: move iommu_resume before ip init/resume
+ drm/amdgpu: init iommu after amdkfd device init
+ drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
+ nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
+ selftests: netfilter: add a vrf+conntrack testcase
+ vrf: don't run conntrack on vrf with !dflt qdisc
+ bpf, x86: Fix "no previous prototype" warning
+ bpf: Fix the off-by-two error in range markings
+ ice: ignore dropped packets during init
+ bonding: make tx_rebalance_counter an atomic
+ nfp: Fix memory leak in nfp_cpp_area_cache_add()
+ seg6: fix the iif in the IPv6 socket control block
+ udp: using datalen to cap max gso segments
+ netfilter: conntrack: annotate data-races around ct->timeout
+ iavf: restore MSI state on reset
+ iavf: Fix reporting when setting descriptor count
+ IB/hfi1: Correct guard on eager buffer deallocation
+ devlink: fix netns refcount leak in devlink_nl_cmd_reload()
+ net/sched: fq_pie: prevent dismantle issue
+ KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush
hypercall
+ mm: bdi: initialize bdi_min_ratio when bdi is unregistered
+ ALSA: ctl: Fix copy of updated id with element read/write
+ ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
+ ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
+ ALSA: pcm: oss: Fix negative period/buffer sizes
+ ALSA: pcm: oss: Limit the period size to 16MB
+ ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
+ scsi: qla2xxx: Format log strings only if needed
+ btrfs: clear extent buffer uptodate when we fail to write it
+ btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
+ md: fix update super 1.0 on rdev size change
+ nfsd: fix use-after-free due to delegation race
+ nfsd: Fix nsfd startup race (again)
+ tracefs: Have new files inherit the ownership of their parent
+ mmc: renesas_sdhi: initialize variable properly when tuning
+ clk: qcom: regmap-mux: fix parent clock lookup
+ drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
+ can: pch_can: pch_can_rx_normal: fix use after free
+ can: m_can: Disable and ignore ELO interrupt
+ libata: add horkage for ASMedia 1092
+ wait: add wake_up_pollfree()
+ UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
+ binder: use wake_up_pollfree()
+ signalfd: use wake_up_pollfree()
+ aio: keep poll requests on waitqueue until completed
+ aio: fix use-after-free due to missing POLLFREE handling
+ net: mvpp2: fix XDP rx queues registering
+ tracefs: Set all files to the same group ownership as the
[Kernel-packages] [Bug 1957842] [NEW] Hirsute update: upstream stable patchset 2022-01-13
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2022-01-13
Ported from the following upstream stable releases:
v5.10.85, v5.15.8
from git://git.kernel.org/
usb: gadget: uvc: fix multiple opens
HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
HID: google: add eel USB id
HID: add hid_is_usb() function to make it simpler for USB detection
HID: add USB_HID dependancy to hid-prodikeys
HID: add USB_HID dependancy to hid-chicony
HID: add USB_HID dependancy on some USB HID drivers
HID: bigbenff: prevent null pointer dereference
HID: wacom: fix problems when device is not a valid USB device
HID: check for valid USB device for many HID drivers
nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
IB/hfi1: Insure use of smp_processor_id() is preempt disabled
IB/hfi1: Fix early init panic
IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
can: kvaser_usb: get CAN clock frequency from device
can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
can: sja1000: fix use after free in ems_pcmcia_add_card()
x86/sme: Explicitly map new EFI memmap table as encrypted
drm/amd/amdkfd: adjust dummy functions' placement
drm/amdkfd: separate kfd_iommu_resume from kfd_resume
drm/amdgpu: add amdgpu_amdkfd_resume_iommu
drm/amdgpu: move iommu_resume before ip init/resume
drm/amdgpu: init iommu after amdkfd device init
drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
selftests: netfilter: add a vrf+conntrack testcase
vrf: don't run conntrack on vrf with !dflt qdisc
bpf, x86: Fix "no previous prototype" warning
bpf: Fix the off-by-two error in range markings
ice: ignore dropped packets during init
bonding: make tx_rebalance_counter an atomic
nfp: Fix memory leak in nfp_cpp_area_cache_add()
seg6: fix the iif in the IPv6 socket control block
udp: using datalen to cap max gso segments
netfilter: conntrack: annotate data-races around ct->timeout
iavf: restore MSI state on reset
iavf: Fix reporting when setting descriptor count
IB/hfi1: Correct guard on eager buffer deallocation
devlink: fix netns refcount leak in devlink_nl_cmd_reload()
net/sched: fq_pie: prevent dismantle issue
KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush
hypercall
mm: bdi: initialize bdi_min_ratio when bdi is unregistered
ALSA: ctl: Fix copy of updated id with element read/write
ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
ALSA: pcm: oss: Fix negative period/buffer sizes
ALSA: pcm: oss: Limit the period size to 16MB
ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
scsi: qla2xxx: Format log strings only if needed
btrfs: clear extent buffer uptodate when we fail to write it
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
md: fix update super 1.0 on rdev size change
nfsd: fix use-after-free due to delegation race
nfsd: Fix nsfd startup race (again)
tracefs: Have new files inherit the ownership of their parent
mmc: renesas_sdhi: initialize variable properly when tuning
clk: qcom: regmap-mux: fix parent clock lookup
drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
can: pch_can: pch_can_rx_normal: fix use after free
can: m_can: Disable and ignore ELO interrupt
libata: add horkage for ASMedia 1092
wait: add wake_up_pollfree()
UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
binder: use wake_up_pollfree()
signalfd: use wake_up_pollfree()
aio: keep poll requests on waitqueue until completed
aio: fix use-after-free due to missing POLLFREE handling
net: mvpp2: fix XDP rx queues registering
tracefs: Set all files to the same group ownership as the mount option
block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc()
scsi: scsi_debug: Fix buffer size of REPORT ZONES command
qede: validate non LSO skb length
PM: runtime: Fix pm_runtime_active() kerneldoc comment
ASoC: rt5682: Fix crash due to out of scope stack vars
ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
ASoC: codecs: wsa881x: fix return values from kcontrol put
ASoC: codecs: wcd934x: handle channel mappping list correctly
ASoC: codecs: wcd934x: return correct value from mixer put
RDMA/hns: Do not halt commands during reset until later
RDMA/hns: Do not destroy QP resources in the hw resetting phase
clk: imx: use
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I have a Ryzen 7 4700U (laptop class) mini PC running 20.10 impish (with ubuntu
studio sources and packages added). With the 5.13.0-23 kernel (I use the
lowlatency kernel) update I started seeing an (approximately) 2 minute hang
during boot if I hit F12 all I see is: '/dev/nvem0n1p2: clean...' during the
hang after which it seems to proceed as normal. Once booted, everything seems
to work fine. Additionally when I shutdown the system hangs (pressing F12 has
no effect and the splash screen freezes: I have to power the computer down
manually.
I installed the 5.13.0-25 kernel (again, low latency) update but the
problem remains unchanged: same long hang on boot, same indefinite hang
on shutdown.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956093] Re: Some Fn+F* and dot keys on keyboard stop working after resume from suspend mode
For those who'll get the same bug: building vanilla 5.15.x kernel (5.15.13 in my case) using .config from the ubuntu's default (and then make oldconfig with all default choices) seemed to fix the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956093 Title: Some Fn+F* and dot keys on keyboard stop working after resume from suspend mode Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu MATE 21.10 KERNEL: Linux 5.13.0-22-generic HW: asus vivobook pro 15 oled M3500QA L1063T (ryzen 5 5600h, radeon gfx) After going to suspend mode and then returning from it, the following keys stop working: - screen brightness control (Fn+F4/F5) - touchpad on/off (Fn+F6) - keyboard brightness control (Fn+F7) - dot key on main keyboard: '>.' - dot/delete key on numpad Other Fn+F* keep working: - Sound on/off (Fn+F1) - Sound volume control (Fn+F2/F3) Dot keys also stop working in text console (Ctrl+Alt+F1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot
Hi Vadik, Oliver, Iestyn,
The kernel team has reviewed the patches, and we have two acks from
Senior kernel team members:
https://lists.ubuntu.com/archives/kernel-team/2022-January/127108.html
https://lists.ubuntu.com/archives/kernel-team/2022-January/127111.html
The patch has now been applied to the Impish kernel git tree:
https://lists.ubuntu.com/archives/kernel-team/2022-January/127117.html
We are all set, and accepted into the next SRU cycle. I will likely
write back around the 7th of Feb, when there is a new kernel in
-proposed for you to test and verify.
Thanks,
Matthew
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956519
Title:
amd_sfh: Null pointer dereference on early device init causes early
panic and fails to boot
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1956519
[Impact]
A regression was introduced into 5.13.0-23-generic for devices using
AMD Ryzen chipsets that incorporate AMD Sensor Fusion Hub (SFH) HID
devices, which are mostly Ryzen based laptops, but desktops do have
the SOC embedded as well.
On early boot, when the driver initialises the device, it hits a null
pointer dereference with the following stack trace:
BUG: kernel NULL pointer dereference, address: 000c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0
Oops: 0002 [#1] SMP NOPTI
CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu
RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh]
Call Trace:
? __pci_set_master+0x5f/0xe0
amd_mp2_pci_probe+0xad/0x160 [amd_sfh]
local_pci_probe+0x48/0x80
pci_device_probe+0x105/0x1c0
really_probe+0x24b/0x4c0
driver_probe_device+0xf0/0x160
device_driver_attach+0xab/0xb0
__driver_attach+0xb2/0x140
? device_driver_attach+0xb0/0xb0
bus_for_each_dev+0x7e/0xc0
driver_attach+0x1e/0x20
bus_add_driver+0x135/0x1f0
driver_register+0x95/0xf0
? 0xc03d2000
__pci_register_driver+0x57/0x60
amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh]
do_one_initcall+0x48/0x1d0
? kmem_cache_alloc_trace+0xfb/0x240
do_init_module+0x62/0x290
load_module+0xa8f/0xb10
__do_sys_finit_module+0xc2/0x120
__x64_sys_finit_module+0x18/0x20
do_syscall_64+0x61/0xb0
? ksys_mmap_pgoff+0x135/0x260
? exit_to_user_mode_prepare+0x37/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? __x64_sys_mmap+0x33/0x40
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? do_syscall_64+0x6e/0xb0
? exc_page_fault+0x8f/0x170
? asm_exc_page_fault+0x8/0x30
entry_SYSCALL_64_after_hwframe+0x44/0xae
This causes a panic and the system is unable to continue booting, and
the user must select an older kernel to boot.
[Fix]
The issue was introduced in 5.13.0-23-generic by the commit:
commit d46ef750ed58cbeeba2d9a55c99231c30a172764
commit-impish 56559d7910e704470ad72da58469b5588e8cbf85
Author: Evgeny Novikov
Date: Tue Jun 1 19:38:01 2021 +0300
Subject:HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/d46ef750ed58cbeeba2d9a55c99231c30a172764
The issue is pretty straightforward, amd_sfh_client.c attempts to
dereference cl_data, but it is NULL:
$ eu-addr2line -ifae
./usr/lib/debug/lib/modules/5.13.0-23-generic/kernel/drivers/hid/amd-sfh-hid/amd_sfh.ko
amd_sfh_hid_client_init+0x47
0x0767
amd_sfh_hid_client_init
/build/linux-k2e9CH/linux-5.13.0/drivers/hid/amd-sfh-hid/amd_sfh_client.c:147:27
134 int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata)
135 {
...
146
147 cl_data->num_hid_devices = amd_mp2_get_sensor_num(privdata,
_data->sensor_idx[0]);
148
...
The patch moves the call to amd_sfh_hid_client_init() before
privdata->cl_data is actually allocated by devm_kzalloc, hence cl_data
being NULL.
+ rc = amd_sfh_hid_client_init(privdata);
+ if (rc)
+ return rc;
+
privdata->cl_data = devm_kzalloc(>dev, sizeof(struct
amdtp_cl_data), GFP_KERNEL);
if (!privdata->cl_data)
return -ENOMEM;
...
- return amd_sfh_hid_client_init(privdata);
+ return 0;
The issue was fixed upstream in 5.15-rc4 by the commit:
commit 88a04049c08cd62e698bc1b1af2d09574b9e0aee
Author: Basavaraj Natikar
Date: Thu Sep 23 17:59:27 2021 +0530
Subject: HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/88a04049c08cd62e698bc1b1af2d09574b9e0aee
The fix places the call to amd_sfh_hid_client_init() after
privdata->cl_data is allocated, and it changes the order of
amd_sfh_hid_client_init() to happen
[Kernel-packages] [Bug 1957832] Re: Impish update: upstream stable patchset 2022-01-13
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2022-01-13
+
+ Ported from the following upstream stable releases:
+ v5.10.85, v5.15.8
+
from git://git.kernel.org/
usb: gadget: uvc: fix multiple opens
HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
HID: google: add eel USB id
HID: add hid_is_usb() function to make it simpler for USB detection
HID: add USB_HID dependancy to hid-prodikeys
HID: add USB_HID dependancy to hid-chicony
HID: add USB_HID dependancy on some USB HID drivers
HID: bigbenff: prevent null pointer dereference
HID: wacom: fix problems when device is not a valid USB device
HID: check for valid USB device for many HID drivers
nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
IB/hfi1: Insure use of smp_processor_id() is preempt disabled
IB/hfi1: Fix early init panic
IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
can: kvaser_usb: get CAN clock frequency from device
can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
can: sja1000: fix use after free in ems_pcmcia_add_card()
x86/sme: Explicitly map new EFI memmap table as encrypted
nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
selftests: netfilter: add a vrf+conntrack testcase
vrf: don't run conntrack on vrf with !dflt qdisc
bpf, x86: Fix "no previous prototype" warning
bpf: Fix the off-by-two error in range markings
ice: ignore dropped packets during init
bonding: make tx_rebalance_counter an atomic
nfp: Fix memory leak in nfp_cpp_area_cache_add()
seg6: fix the iif in the IPv6 socket control block
udp: using datalen to cap max gso segments
netfilter: conntrack: annotate data-races around ct->timeout
iavf: restore MSI state on reset
iavf: Fix reporting when setting descriptor count
IB/hfi1: Correct guard on eager buffer deallocation
devlink: fix netns refcount leak in devlink_nl_cmd_reload()
net/sched: fq_pie: prevent dismantle issue
KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush
hypercall
mm: bdi: initialize bdi_min_ratio when bdi is unregistered
ALSA: ctl: Fix copy of updated id with element read/write
ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
ALSA: pcm: oss: Fix negative period/buffer sizes
ALSA: pcm: oss: Limit the period size to 16MB
ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
scsi: qla2xxx: Format log strings only if needed
btrfs: clear extent buffer uptodate when we fail to write it
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
md: fix update super 1.0 on rdev size change
nfsd: fix use-after-free due to delegation race
nfsd: Fix nsfd startup race (again)
tracefs: Have new files inherit the ownership of their parent
mmc: renesas_sdhi: initialize variable properly when tuning
clk: qcom: regmap-mux: fix parent clock lookup
drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
can: pch_can: pch_can_rx_normal: fix use after free
can: m_can: Disable and ignore ELO interrupt
libata: add horkage for ASMedia 1092
wait: add wake_up_pollfree()
UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
binder: use wake_up_pollfree()
signalfd: use wake_up_pollfree()
aio: keep poll requests on waitqueue until completed
aio: fix use-after-free due to missing POLLFREE handling
net: mvpp2: fix XDP rx queues registering
tracefs: Set all files to the same group ownership as the mount option
block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc()
scsi: scsi_debug: Fix buffer size of REPORT ZONES command
qede: validate non LSO skb length
PM: runtime: Fix pm_runtime_active() kerneldoc comment
ASoC: rt5682: Fix crash due to out of scope stack vars
ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
ASoC: codecs: wsa881x: fix return values from kcontrol put
ASoC: codecs: wcd934x: handle channel mappping list correctly
ASoC: codecs: wcd934x: return correct value from mixer put
RDMA/hns: Do not halt commands during reset until later
RDMA/hns: Do not destroy QP resources in the hw resetting phase
clk: imx: use module_platform_driver
i40e: Fix failed opcode appearing if handling messages from VF
i40e: Fix pre-set max number of
[Kernel-packages] [Bug 1957832] Re: Impish update: upstream stable patchset 2022-01-13
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2022-01-13
+ from git://git.kernel.org/
-upstream stable patchset 2022-01-13
-from git://git.kernel.org/
+ usb: gadget: uvc: fix multiple opens
+ HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
+ HID: google: add eel USB id
+ HID: add hid_is_usb() function to make it simpler for USB detection
+ HID: add USB_HID dependancy to hid-prodikeys
+ HID: add USB_HID dependancy to hid-chicony
+ HID: add USB_HID dependancy on some USB HID drivers
+ HID: bigbenff: prevent null pointer dereference
+ HID: wacom: fix problems when device is not a valid USB device
+ HID: check for valid USB device for many HID drivers
+ nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
+ IB/hfi1: Insure use of smp_processor_id() is preempt disabled
+ IB/hfi1: Fix early init panic
+ IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
+ can: kvaser_usb: get CAN clock frequency from device
+ can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
+ can: sja1000: fix use after free in ems_pcmcia_add_card()
+ x86/sme: Explicitly map new EFI memmap table as encrypted
+ nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
+ selftests: netfilter: add a vrf+conntrack testcase
+ vrf: don't run conntrack on vrf with !dflt qdisc
+ bpf, x86: Fix "no previous prototype" warning
+ bpf: Fix the off-by-two error in range markings
+ ice: ignore dropped packets during init
+ bonding: make tx_rebalance_counter an atomic
+ nfp: Fix memory leak in nfp_cpp_area_cache_add()
+ seg6: fix the iif in the IPv6 socket control block
+ udp: using datalen to cap max gso segments
+ netfilter: conntrack: annotate data-races around ct->timeout
+ iavf: restore MSI state on reset
+ iavf: Fix reporting when setting descriptor count
+ IB/hfi1: Correct guard on eager buffer deallocation
+ devlink: fix netns refcount leak in devlink_nl_cmd_reload()
+ net/sched: fq_pie: prevent dismantle issue
+ KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush
hypercall
+ mm: bdi: initialize bdi_min_ratio when bdi is unregistered
+ ALSA: ctl: Fix copy of updated id with element read/write
+ ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
+ ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
+ ALSA: pcm: oss: Fix negative period/buffer sizes
+ ALSA: pcm: oss: Limit the period size to 16MB
+ ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
+ scsi: qla2xxx: Format log strings only if needed
+ btrfs: clear extent buffer uptodate when we fail to write it
+ btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
+ md: fix update super 1.0 on rdev size change
+ nfsd: fix use-after-free due to delegation race
+ nfsd: Fix nsfd startup race (again)
+ tracefs: Have new files inherit the ownership of their parent
+ mmc: renesas_sdhi: initialize variable properly when tuning
+ clk: qcom: regmap-mux: fix parent clock lookup
+ drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
+ can: pch_can: pch_can_rx_normal: fix use after free
+ can: m_can: Disable and ignore ELO interrupt
+ libata: add horkage for ASMedia 1092
+ wait: add wake_up_pollfree()
+ UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
+ binder: use wake_up_pollfree()
+ signalfd: use wake_up_pollfree()
+ aio: keep poll requests on waitqueue until completed
+ aio: fix use-after-free due to missing POLLFREE handling
+ net: mvpp2: fix XDP rx queues registering
+ tracefs: Set all files to the same group ownership as the mount option
+ block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
+ scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc()
+ scsi: scsi_debug: Fix buffer size of REPORT ZONES command
+ qede: validate non LSO skb length
+ PM: runtime: Fix pm_runtime_active() kerneldoc comment
+ ASoC: rt5682: Fix crash due to out of scope stack vars
+ ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
+ ASoC: codecs: wsa881x:
[Kernel-packages] [Bug 1957832] [NEW] Impish update: upstream stable patchset 2022-01-13
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-13 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1957832 Title: Impish update: upstream stable patchset 2022-01-13 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-13 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
And since the installation issue is independent from this particular LP
bug here, I suggest to open a separate LP for it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions on upgrades).
__
Toleration support for new IBM Z crypto hardware - Backport to focal
(20.04)
Patch from kernel 5.14:
Summary: s390/AP: support new dynamic AP bus size limit
Description: This patch provides support for new dynamic AP bus
message limit with the existing zcrypt device driver
and AP bus core code. There is support for a new
field 'ml' from the TAPQ query which indicates the
per card AP bus message size limit. This TAPQ
improvement will come with an updated firmware and
this patch exploits this new field and thus makes
it possible to send/receive AP messages greater
than the current limit of 12K.
Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
Hi Harald, I'm sorry to read that you have problems with installing Ubuntu
20.04.
But let's be constructive please and let us know more details, so that we can
look at solving the situation.
Which Ubuntu image did you used for the installation?
The very latest 20.04 ISO image is always available from here:
https://cdimage.ubuntu.com/releases/20.04/release/
(There are also ready to use Cloud images available).
Please notice that the way to install 20.04 differs from the previous Ubuntu
releases,
see more details here: https://ubuntu.com/server/docs/installation
Where did you want to install: LPAR, z/VM or KVM?
Have you tried an interactive or non-interactive (autoinstall)?
And especially: Can you share the logs?
The interactive installer is a live installer, and even if you run into a
problem, you can usually enter the installer shell (which give you access to a
fully-fledged Ubuntu/Linux system).
Ideally share the entire /var/log/installer folder and (in case not empty)
/var/crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions
[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown
same on -25 with ryzen 7 5700u. Can't shutdown or reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic, the system cannot be powered down or rebooted, just hangs indefinitely. A screenshot with the final screen is shown here: https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff I can restore the previous behavior (i.e. a correct shutdown) with choosing the previous kernel in the grub menu on boot. Is there anything I can do to provide more information and debug this further? My system information: Description: Ubuntu 21.10 Release: 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petr 1146 F pulseaudio /dev/snd/controlC0: petr 1146 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-07 (62 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgxubuntu-root ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 04/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
Thanks, Frank! I managed to install the jammy kernel, but the zfs module still loads successfully. Here is some information from the manually built module: $ strings module/zfs/zfs.ko|grep -e vermagic= -e GCC -e ^version=|sort -u GCC: (Ubuntu 11.2.0-14ubuntu1) 11.2.0 vermagic=5.15.0-16-generic SMP mod_unload modversions version=2.1.99-678_gda9c6c033 We could probably try to hunt down the difference between our environments, but I'm wondering if you could just share your VM image with me? -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: New Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954680] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2022-01-13 11:17 EDT---
unable to install a system with ubuntu 20.04 or whatever ... looks like jet
another 'improvement' in your installation system. Maybe we should start
selling teddy bears instead of claiming to be a company able to provide
'software solutions'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions on upgrades).
__
Toleration support for new IBM Z crypto hardware - Backport to focal
(20.04)
Patch from kernel 5.14:
Summary: s390/AP: support new dynamic AP bus size limit
Description: This patch provides support for new dynamic AP bus
message limit with the existing zcrypt device driver
and AP bus core code. There is support for a new
field 'ml' from the TAPQ query which indicates the
per card AP bus message size limit. This TAPQ
improvement will come with an updated firmware and
this patch exploits this new field and thus makes
it possible to
[Kernel-packages] [Bug 1957813] Re: nvidia-driver-460 haven't transit to 470 but linux-modules-nvidia-460-* transited
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Hirsute) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1957813 Title: nvidia-driver-460 haven't transit to 470 but linux-modules- nvidia-460-* transited Status in nvidia-graphics-drivers-460 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-460 source package in Bionic: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Triaged Status in nvidia-graphics-drivers-470 source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Hirsute: Triaged Status in nvidia-graphics-drivers-470 source package in Hirsute: In Progress Bug description: # apt show linux-modules-nvidia-460-oem-20.04d Package: linux-modules-nvidia-460-oem-20.04d Version: 5.14.0-1018.19 ... Depends: linux-modules-nvidia-470-oem-20.04d --- # apt show nvidia-driver-460 Package: nvidia-driver-460 Version: 460.91.03-0ubuntu0.20.04.1 Priority: optional Section: restricted/libs Source: nvidia-graphics-drivers-460 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1509 kB Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-cfg1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460 (= 460.91.03-0ubuntu0.20.04.1) Recommends: nvidia-settings, nvidia-prime (>= 0.8), libnvidia-compute-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-gl-460:i386 (= 460.91.03-0ubuntu0.20.04.1) --- The nvidia-driver-460 (460.91.03-0ubuntu0.20.04.1) is now failed to be compiled on 5.14.0-1018-oem (at least) because `struct task_struct->state` changed to ->__state[1]. [1] Author: Peter
[Kernel-packages] [Bug 1957812] [NEW] nvidia-driver-460 haven't transit to 470 but linux-modules-nvidia-460-* transited
Public bug reported: # apt show linux-modules-nvidia-460-oem-20.04d Package: linux-modules-nvidia-460-oem-20.04d Version: 5.14.0-1018.19 ... Depends: linux-modules-nvidia-470-oem-20.04d --- # apt show nvidia-driver-460 Package: nvidia-driver-460 Version: 460.91.03-0ubuntu0.20.04.1 Priority: optional Section: restricted/libs Source: nvidia-graphics-drivers-460 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1509 kB Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-cfg1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460 (= 460.91.03-0ubuntu0.20.04.1) Recommends: nvidia-settings, nvidia-prime (>= 0.8), libnvidia-compute-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-gl-460:i386 (= 460.91.03-0ubuntu0.20.04.1) --- The nvidia-driver-460 (460.91.03-0ubuntu0.20.04.1) is now failed to be compiled on 5.14.0-1018-oem (at least) because `struct task_struct->state` changed to ->__state[1]. [1] Author: Peter Zijlstra Date: Fri Jun 11 10:28:17 2021 +0200 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1957812 Title: nvidia-driver-460 haven't transit to 470 but linux-modules- nvidia-460-* transited Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: # apt show linux-modules-nvidia-460-oem-20.04d Package: linux-modules-nvidia-460-oem-20.04d Version: 5.14.0-1018.19 ... Depends: linux-modules-nvidia-470-oem-20.04d --- # apt show nvidia-driver-460 Package: nvidia-driver-460 Version: 460.91.03-0ubuntu0.20.04.1 Priority: optional Section: restricted/libs Source: nvidia-graphics-drivers-460 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1509 kB Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-cfg1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460 (= 460.91.03-0ubuntu0.20.04.1) Recommends: nvidia-settings, nvidia-prime (>= 0.8), libnvidia-compute-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-gl-460:i386 (= 460.91.03-0ubuntu0.20.04.1) --- The nvidia-driver-460 (460.91.03-0ubuntu0.20.04.1) is now failed to be compiled on 5.14.0-1018-oem (at least) because `struct task_struct->state` changed to ->__state[1]. [1] Author: Peter Zijlstra Date: Fri Jun 11 10:28:17 2021 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1957812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957813] [NEW] nvidia-driver-460 haven't transit to 470 but linux-modules-nvidia-460-* transited
Public bug reported: # apt show linux-modules-nvidia-460-oem-20.04d Package: linux-modules-nvidia-460-oem-20.04d Version: 5.14.0-1018.19 ... Depends: linux-modules-nvidia-470-oem-20.04d --- # apt show nvidia-driver-460 Package: nvidia-driver-460 Version: 460.91.03-0ubuntu0.20.04.1 Priority: optional Section: restricted/libs Source: nvidia-graphics-drivers-460 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1509 kB Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-cfg1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460 (= 460.91.03-0ubuntu0.20.04.1) Recommends: nvidia-settings, nvidia-prime (>= 0.8), libnvidia-compute-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-gl-460:i386 (= 460.91.03-0ubuntu0.20.04.1) --- The nvidia-driver-460 (460.91.03-0ubuntu0.20.04.1) is now failed to be compiled on 5.14.0-1018-oem (at least) because `struct task_struct->state` changed to ->__state[1]. [1] Author: Peter Zijlstra Date: Fri Jun 11 10:28:17 2021 +0200 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nvidia-graphics-drivers-460 (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: nvidia-graphics-drivers-470 (Ubuntu Bionic) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-graphics-drivers-460 (Ubuntu Focal) Importance: Undecided Status: Triaged ** Affects: nvidia-graphics-drivers-470 (Ubuntu Focal) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-graphics-drivers-460 (Ubuntu Hirsute) Importance: Undecided Status: Triaged ** Affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1957813 Title: nvidia-driver-460 haven't transit to 470 but linux-modules- nvidia-460-* transited Status in nvidia-graphics-drivers-460 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-460 source package in Bionic: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Triaged Status in nvidia-graphics-drivers-470 source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Hirsute: Triaged Status in nvidia-graphics-drivers-470 source package in Hirsute: In Progress Bug description: # apt show linux-modules-nvidia-460-oem-20.04d Package: linux-modules-nvidia-460-oem-20.04d Version: 5.14.0-1018.19 ... Depends: linux-modules-nvidia-470-oem-20.04d --- # apt show nvidia-driver-460 Package: nvidia-driver-460 Version: 460.91.03-0ubuntu0.20.04.1 Priority: optional Section: restricted/libs Source: nvidia-graphics-drivers-460 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1509 kB Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-cfg1-460
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
Hi Ilya, there is a 5.15 kernel for jammy aka 22.04 in the proposed section of the archive. Just enable proposed with: "sudo add-apt-repository "deb http://us.ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main" (for the src use "sudo add-apt-repository "deb-src http://us.ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main") Do an "sudo apt update" (if not automatically triggered) and you will find new packages listed by: "apt list --upgradable" You can just install all of them (e.g. with "sudo apt full-upgrade"), or just selectively install an updated package, like the kernel (e.g. "sudo apt install linux-generic"). With that you will get the Ubuntu jammy version of the 5.15 kernel. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: New Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957810] [NEW] impish: ddebs build take too long and times out
Public bug reported: [ Impact ] In impish we switched from xz compression to zstd compression for debs and ddebs. This change seems to have increased a lot the build time without giving any evident benefit for the kernel packages. This can cause time out when doing full builds on launchpad. [ Fix ] Explicitly enforce xz compression for kernel ddebs to prevent timeout issues during the build. [ Where problems could occur ] If the patch has issues it can break the build while doing full builds. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957810 Title: impish: ddebs build take too long and times out Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: In Progress Bug description: [ Impact ] In impish we switched from xz compression to zstd compression for debs and ddebs. This change seems to have increased a lot the build time without giving any evident benefit for the kernel packages. This can cause time out when doing full builds on launchpad. [ Fix ] Explicitly enforce xz compression for kernel ddebs to prevent timeout issues during the build. [ Where problems could occur ] If the patch has issues it can break the build while doing full builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
** Changed in: oem-priority Status: Triaged => Fix Released -- 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/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951422] Re: Ucore kernel snap size: netronome smartnic fw
** Description changed: - The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and + [ Impact ] + + Pi kernel snaps are big in part due to included firmware binaries. A lot + of these binaries are not needed/required by the Pi kernel. The size of + the snap has a negative impact on boot speed. + + [ Fix ] + + Parse modinfo data from all modules to determine the list of required + firmware files and remove the ones that are not necessary. + + [ Test Case ] + + On core20 before: + $ du -sh /lib/firmware/ + 602M /lib/firmware/ + + And after: + $ du -sh /lib/firmware/ + 58M /lib/firmware/ + + [ Where Problems Could Occur ] + + We might accidentally drop needed firmware which might render the + relevant HW unusable. Firmware load failures should be visible in the + kernel log though. + + [ Original Description ] + + The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. - stulluk ~/tmp $ ls -lah pi-kernel_353.snap + stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [ Impact ] Pi kernel snaps are big in part due to included firmware binaries. A lot of these binaries are not needed/required by the Pi kernel. The size of the snap has a negative impact on boot speed. [ Fix ] Parse modinfo data from all modules to determine the list of required - firmware files and remove the ones that are not necessary. + firmware files and remove the ones that are not necessary during snap + build time. [ Test Case ] On core20 before: $ du -sh /lib/firmware/ 602M /lib/firmware/ And after: $ du -sh /lib/firmware/ 58M /lib/firmware/ [ Where Problems Could Occur ] We might accidentally drop needed firmware which might render the relevant HW unusable. Firmware load failures should be visible in the kernel log though. [ Original Description ] - The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and + The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1951422 Title: Ucore kernel snap size: netronome smartnic fw Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: [ Impact ] Pi kernel snaps are big in part due to included firmware binaries. A lot of these binaries are not needed/required by the Pi kernel. The size of the snap has a negative impact on boot speed. [ Fix ] Parse modinfo data from all modules to determine the list of required firmware files and remove the ones that are not necessary during snap build time. [ Test Case ] On core20 before: $ du -sh /lib/firmware/ 602M /lib/firmware/ And
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
I don't seem to be able to reproduce this. What I tried so far: 1. Installed a clean VM using an image from http://ftp.uni- kl.de/pub/linux/ubuntu-dvd/ubuntu-server/daily-live/pending/, ran apt install zfs-dkms - zfs.ko initialization successful. 2. Built zfs master myself and loaded the modules manually - zfs.ko initialization is successful. 3. Installed v5.15 kernel from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.15/ and ran apt install zfs-dkms - zfs.ko initialization successful. 4. Built zfs master myself again (for v5.15 this time) and loaded the modules manually - zfs.ko initialization is successful. Am I missing something? One thing is that zfs.ko from https://kernel.ubuntu.com/~arighi/zfs/ has vermagic=5.15.0-15-generic, whereas mine has vermagic=5.15.0-051500-generic. Is there another v5.15 kernel build that I can try? The default repos seem to have only v5.13: $ apt search linux-image-generic ... linux-image-generic/jammy,now 5.13.0.19.30 s390x [installed,automatic] Generic Linux kernel image ... -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: New Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957808] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957808 Title: Kernel soft lockup after resume Status in linux package in Ubuntu: Confirmed Bug description: Sometimes the kernel hangs after resuming from suspend. It might be a problem when suspending, while the DELL thunderbolt dock is connected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-25-generic 5.13.0-25.26 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: minni 5443 F pulseaudio /dev/snd/pcmC0D0c: minni 5443 F...m pulseaudio /dev/snd/pcmC0D0p: minni 5443 F...m pulseaudio /dev/snd/timer: minni 5443 f pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 15:53:19 2022 InstallationDate: Installed on 2020-12-19 (389 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957808] [NEW] Kernel soft lockup after resume
Public bug reported: Sometimes the kernel hangs after resuming from suspend. It might be a problem when suspending, while the DELL thunderbolt dock is connected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-25-generic 5.13.0-25.26 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: minni 5443 F pulseaudio /dev/snd/pcmC0D0c: minni 5443 F...m pulseaudio /dev/snd/pcmC0D0p: minni 5443 F...m pulseaudio /dev/snd/timer: minni 5443 f pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 15:53:19 2022 InstallationDate: Installed on 2020-12-19 (389 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957808 Title: Kernel soft lockup after resume Status in linux package in Ubuntu: Confirmed Bug description: Sometimes the kernel hangs after resuming from suspend. It might be a problem when suspending, while the DELL thunderbolt dock is connected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-25-generic 5.13.0-25.26 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: minni 5443 F pulseaudio /dev/snd/pcmC0D0c: minni 5443 F...m pulseaudio /dev/snd/pcmC0D0p: minni 5443 F...m pulseaudio /dev/snd/timer: minni 5443 f pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 15:53:19 2022 InstallationDate: Installed on 2020-12-19 (389 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957807] [NEW] Fix ct_state nat matching and nat action not being executed
Public bug reported: * Explain the bug Netfilter conntrack maintains NAT flags per connection indicating whether NAT was configured for the connection. Openvswitch maintains NAT flags on the per packet flow key ct_state field, indicating whether NAT was actually executed on the packet. When a packet misses from tc to ovs the conntrack NAT flags are set. However, NAT was not necessarily executed on the packet because the connection's state might still be in NEW state. As such, openvswitch wrongly assumes that NAT was executed and sets an incorrect flow key NAT flags. This can lead to incorrect matching on ct_state nat flags, and nat not being executed by ovs. * How to test Create OVS bridge (br-ovs below) with 2 devices $dev1, $dev2 (can be any devices), with hw offload enabled. Configure NAT connection tracking OpenFlow rules which would only be partially offloaded to tc/hw because of dp_hash/hash (groups in openflow) not being offloaded, so we would have misses from tc to ovs: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl -O OpenFlow12 add-group ovs-br \ 'group_id=2,type=select,bucket=ct(table=4,zone=5,nat(src=1.1.1.128),commit)' #rules ovs-ofctl del-flows ovs-br ovs-ofctl add-flow ovs-br "table=0, arp, action=normal" ovs-ofctl add-flow ovs-br "table=0, ip, nw_src=1.1.1.1 actions=ct(zone=5,table=1,nat)" ovs-ofctl add-flow ovs-br "table=1, in_port=1, actions=group:2" ovs-ofctl add-flow ovs-br "table=4, ip, nw_src=1.1.1.128 actions=2" #good flow ovs-ofctl add-flow ovs-br "table=4, ip, nw_src=1.1.1.1 actions=drop" #bad flow Run single sided UDP traffic from $dev1 to $dev2, and observe source nat not being done, and hit of drop rule in table=4. With the fix, the src nat will be done, and table=4 rule which matches new ip (128) will be hit. * What it could break. NA ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/1957807 Title: Fix ct_state nat matching and nat action not being executed Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug Netfilter conntrack maintains NAT flags per connection indicating whether NAT was configured for the connection. Openvswitch maintains NAT flags on the per packet flow key ct_state field, indicating whether NAT was actually executed on the packet. When a packet misses from tc to ovs the conntrack NAT flags are set. However, NAT was not necessarily executed on the packet because the connection's state might still be in NEW state. As such, openvswitch wrongly assumes that NAT was executed and sets an incorrect flow key NAT flags. This can lead to incorrect matching on ct_state nat flags, and nat not being executed by ovs. * How to test Create OVS bridge (br-ovs below) with 2 devices $dev1, $dev2 (can be any devices), with hw offload enabled. Configure NAT connection tracking OpenFlow rules which would only be partially offloaded to tc/hw because of dp_hash/hash (groups in openflow) not being offloaded, so we would have misses from tc to ovs: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl -O OpenFlow12 add-group ovs-br \ 'group_id=2,type=select,bucket=ct(table=4,zone=5,nat(src=1.1.1.128),commit)' #rules ovs-ofctl del-flows ovs-br ovs-ofctl add-flow ovs-br "table=0, arp, action=normal" ovs-ofctl add-flow ovs-br "table=0, ip, nw_src=1.1.1.1 actions=ct(zone=5,table=1,nat)" ovs-ofctl add-flow ovs-br "table=1, in_port=1, actions=group:2" ovs-ofctl add-flow ovs-br "table=4, ip, nw_src=1.1.1.128 actions=2" #good flow ovs-ofctl add-flow ovs-br "table=4, ip, nw_src=1.1.1.1 actions=drop" #bad flow Run single sided UDP traffic from $dev1 to $dev2, and observe source nat not being done, and hit of drop rule in table=4. With the fix, the src nat will be done, and table=4 rule which matches new ip (128) will be hit. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1957807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954680] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2022-01-13 09:38 EDT---
I am about to set up a system and will try to verify asap.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions on upgrades).
__
Toleration support for new IBM Z crypto hardware - Backport to focal
(20.04)
Patch from kernel 5.14:
Summary: s390/AP: support new dynamic AP bus size limit
Description: This patch provides support for new dynamic AP bus
message limit with the existing zcrypt device driver
and AP bus core code. There is support for a new
field 'ml' from the TAPQ query which indicates the
per card AP bus message size limit. This TAPQ
improvement will come with an updated firmware and
this patch exploits this new field and thus makes
it possible to send/receive AP messages greater
than the current limit of 12K.
Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
Meanwhile: commit "s390/pci: fix zpci_zdev_put() on reserve" landed as ce2a0d2c8fb5 in impish via upstream stable (it's in Ubuntu-5.13.0-23 and newer), hence all patches needed are included now and the impish entry can be updated to Fix Released. and commit "s390/pci: fix zpci_zdev_put() on reserve" landed as 7476a573c040 in hirsute via upstream stable (it's in Ubuntu-5.11.0-42.46 and newer), hence all patches needed are included now and the hirsute entry can be updated to Fix Released. Finally the ticket is closed. ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug", too. * Fortunately the modifications are quite minimal and thereby traceable, * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, hence are specific to the s390x platform only and there again to "plugging" of zPCI devices. * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device structure" * The function zpci_remove_device
[Kernel-packages] [Bug 1957797] [NEW] package linux-headers-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/exec-cmd
Public bug reported: dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.11.0-46-g eneric_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/orc_dump .o.dpkg-new': Operation not permitted Segmentation fault ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 12 12:02:19 2022 DuplicateSignature: package:linux-headers-5.11.0-46-generic:(not installed) Unpacking linux-modules-extra-5.11.0-46-generic (5.11.0-46.51~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kpdm4S/2-linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/dvb-frontends/isl6423.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/exec-cmd.o.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-11-11 (62 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/exec-cmd.o.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1957797 Title: package linux-headers-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-46-generic/tools/objtool/exec-cmd.o.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.11.0-46-g eneric_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/orc_dump .o.dpkg-new': Operation not permitted Segmentation fault ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 12 12:02:19 2022 DuplicateSignature: package:linux-headers-5.11.0-46-generic:(not installed) Unpacking linux-modules-extra-5.11.0-46-generic (5.11.0-46.51~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kpdm4S/2-linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/dvb-frontends/isl6423.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/exec-cmd.o.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-11-11 (62 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-46-generic/tools/objtool/exec-cmd.o.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1957797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957196] Re: webcam doesn't work
I can't perform 'apport-collect 1957196' because I roll back my system through the 'TimeShift' to the kernel I had before. I needed my camera working because of my work ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => 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/1957196 Title: webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: As I reported in bugs: 1957112, 1956461, after installing kernels 5.13.0.25, 5.4.0-94, 5.4.0-92 my USB Webcam Bus 001 Device 003: ID 041e:4095 Creative Technology, Ltd Live! Cam Sync HD [VF0770] /known as Creative HD720p stop working this way that the microphone of the camera is capturing sound but at the same time there is no image captured by this device. For instance VLC report that it can't open MRL 'v4l2://' and in the folder 'dev' there is no folder 'vl4' (/dev/vl4). When I used to use kernel 5.4.0-91 there was no problem with this webcam at all. I'm using Linux Mint 20.3 I need some help. The camera is quite new and I need it to my work as a teacher for remote teaching in google Meet an MS Teams. Without camera I can't work. PLEASE correct this regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Submitted the patch to the kernel team mailing list https://lists.ubuntu.com/archives/kernel-team/2022-January/127109.html for both Impish and Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: In Progress Status in kunpeng920 ubuntu-22.04 series: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Incomplete Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957786] [NEW] Enable CONFIG_NO_HZ_FULL in relatime kernel
Public bug reported: nohz_full should be enabled by default as it improves certain workloads. No actual data was given, just strong opinion nohz_full is needed. CONFIG_NO_HZ_FULL is also in Intel’s BSP for Yocto RT. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Krzysztof Kozlowski (krzk) Status: Fix Committed ** Tags: jammy realtime ** Tags added: realtime ** Tags added: jammy ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) 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/1957786 Title: Enable CONFIG_NO_HZ_FULL in relatime kernel Status in linux package in Ubuntu: Fix Committed Bug description: nohz_full should be enabled by default as it improves certain workloads. No actual data was given, just strong opinion nohz_full is needed. CONFIG_NO_HZ_FULL is also in Intel’s BSP for Yocto RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957788] [NEW] Enable CONFIG_RT_GROUP_SCHED in relatime kernel
Public bug reported: CONFIG_RT_GROUP_SCHED makes sense in realtime workloads, especially ones involving multiple realtime tasks. It is also enabled in Intel’s BSP for Yocto RT. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Krzysztof Kozlowski (krzk) Status: In Progress ** Tags: jammy realtime ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Tags added: jammy realtime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957788 Title: Enable CONFIG_RT_GROUP_SCHED in relatime kernel Status in linux package in Ubuntu: In Progress Bug description: CONFIG_RT_GROUP_SCHED makes sense in realtime workloads, especially ones involving multiple realtime tasks. It is also enabled in Intel’s BSP for Yocto RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957784] [NEW] package linux-modules-extra-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/d
Public bug reported: dpkg: error processing package linux-generic-hwe-20.04 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-generic-hwe-20.04 linux-generic-hwe-20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.11.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-modules-extra-5.11.0-46-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 13 13:02:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb ... Unpacking linux-modules-extra-5.11.0-46-generic (5.11.0-46.51~20.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-12-12 (32 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-extra-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1957784 Title: package linux-modules-extra-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg- new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: dpkg: error processing package linux-generic-hwe-20.04 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-generic-hwe-20.04 linux-generic-hwe-20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.11.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-modules-extra-5.11.0-46-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 13 13:02:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb ... Unpacking linux-modules-extra-5.11.0-46-generic (5.11.0-46.51~20.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-modules-extra-5.11.0-46-generic_5.11.0-46.51~20.04.1_amd64.deb (--unpack): unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-12-12 (32 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-extra-5.11.0-46-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-46-generic/kernel/drivers/media/i2c/dw9768.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1957784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956519
Title:
amd_sfh: Null pointer dereference on early device init causes early
panic and fails to boot
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1956519
[Impact]
A regression was introduced into 5.13.0-23-generic for devices using
AMD Ryzen chipsets that incorporate AMD Sensor Fusion Hub (SFH) HID
devices, which are mostly Ryzen based laptops, but desktops do have
the SOC embedded as well.
On early boot, when the driver initialises the device, it hits a null
pointer dereference with the following stack trace:
BUG: kernel NULL pointer dereference, address: 000c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0
Oops: 0002 [#1] SMP NOPTI
CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu
RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh]
Call Trace:
? __pci_set_master+0x5f/0xe0
amd_mp2_pci_probe+0xad/0x160 [amd_sfh]
local_pci_probe+0x48/0x80
pci_device_probe+0x105/0x1c0
really_probe+0x24b/0x4c0
driver_probe_device+0xf0/0x160
device_driver_attach+0xab/0xb0
__driver_attach+0xb2/0x140
? device_driver_attach+0xb0/0xb0
bus_for_each_dev+0x7e/0xc0
driver_attach+0x1e/0x20
bus_add_driver+0x135/0x1f0
driver_register+0x95/0xf0
? 0xc03d2000
__pci_register_driver+0x57/0x60
amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh]
do_one_initcall+0x48/0x1d0
? kmem_cache_alloc_trace+0xfb/0x240
do_init_module+0x62/0x290
load_module+0xa8f/0xb10
__do_sys_finit_module+0xc2/0x120
__x64_sys_finit_module+0x18/0x20
do_syscall_64+0x61/0xb0
? ksys_mmap_pgoff+0x135/0x260
? exit_to_user_mode_prepare+0x37/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? __x64_sys_mmap+0x33/0x40
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? do_syscall_64+0x6e/0xb0
? exc_page_fault+0x8f/0x170
? asm_exc_page_fault+0x8/0x30
entry_SYSCALL_64_after_hwframe+0x44/0xae
This causes a panic and the system is unable to continue booting, and
the user must select an older kernel to boot.
[Fix]
The issue was introduced in 5.13.0-23-generic by the commit:
commit d46ef750ed58cbeeba2d9a55c99231c30a172764
commit-impish 56559d7910e704470ad72da58469b5588e8cbf85
Author: Evgeny Novikov
Date: Tue Jun 1 19:38:01 2021 +0300
Subject:HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/d46ef750ed58cbeeba2d9a55c99231c30a172764
The issue is pretty straightforward, amd_sfh_client.c attempts to
dereference cl_data, but it is NULL:
$ eu-addr2line -ifae
./usr/lib/debug/lib/modules/5.13.0-23-generic/kernel/drivers/hid/amd-sfh-hid/amd_sfh.ko
amd_sfh_hid_client_init+0x47
0x0767
amd_sfh_hid_client_init
/build/linux-k2e9CH/linux-5.13.0/drivers/hid/amd-sfh-hid/amd_sfh_client.c:147:27
134 int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata)
135 {
...
146
147 cl_data->num_hid_devices = amd_mp2_get_sensor_num(privdata,
_data->sensor_idx[0]);
148
...
The patch moves the call to amd_sfh_hid_client_init() before
privdata->cl_data is actually allocated by devm_kzalloc, hence cl_data
being NULL.
+ rc = amd_sfh_hid_client_init(privdata);
+ if (rc)
+ return rc;
+
privdata->cl_data = devm_kzalloc(>dev, sizeof(struct
amdtp_cl_data), GFP_KERNEL);
if (!privdata->cl_data)
return -ENOMEM;
...
- return amd_sfh_hid_client_init(privdata);
+ return 0;
The issue was fixed upstream in 5.15-rc4 by the commit:
commit 88a04049c08cd62e698bc1b1af2d09574b9e0aee
Author: Basavaraj Natikar
Date: Thu Sep 23 17:59:27 2021 +0530
Subject: HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/88a04049c08cd62e698bc1b1af2d09574b9e0aee
The fix places the call to amd_sfh_hid_client_init() after
privdata->cl_data is allocated, and it changes the order of
amd_sfh_hid_client_init() to happen before devm_add_action_or_reset()
fixing the actual null pointer dereference which caused these commits
to exist.
This patch also landed in 5.14.10 -stable, but it seems it was omitted
from being backported to impish, likely due to it sharing the exact
same subject line as the regression commit, so it was likely dropped
as a duplicate?
[Testcase]
You need an AMD Ryzen based system that has a AMD Sensor Fusion Hub
HID device built in to test this.
Simply booting the system is enough to
[Kernel-packages] [Bug 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot
Boot tests with hirsure/linux 5.11.0-47.52 were all successful. Marking as verified. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956984 Title: hirsute:linux 5.11.0-45.49 fails to boot Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able to boot a VM with the following commit reverted: 327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP has hwpoisoned subpage for PMD page fault [ Additional Info ] On an affected VM, after a bit more than 1 hour after booting I get the following soft lockup which helped identify a suspicious commit: [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-journal:478] [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover i2c_piix4 pata_acpi floppy [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 5.11.0-45-generic #49-Ubuntu [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [12164.211653] RIP: 0010:xas_load+0x33/0x80 [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246 [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: b17440c7fb78 [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 92d28674b750 [12164.211666] R10: R11: R12: 003b [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 61c8864680b583eb [12164.211669] FS: 7fdf28760900() GS:92d2fdc8() knlGS: [12164.211670] CS: 0010 DS: ES: CR0: 80050033 [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 06e0 [12164.211675] Call Trace: [12164.211678] find_get_entry+0x5a/0x160 [12164.211682] find_lock_entry+0x2d/0x120 [12164.211685] shmem_getpage_gfp+0xe8/0x8c0 [12164.211687] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [12164.211691] shmem_fault+0x7b/0x220 [12164.211693] ? file_update_time+0x62/0x140 [12164.211696] __do_fault+0x3c/0xe0 [12164.211699] do_shared_fault+0x19/0xb0 [12164.211701] do_fault+0x1cd/0x1f0 [12164.211704] handle_pte_fault+0x1e5/0x260 [12164.211706] __handle_mm_fault+0x59a/0x7c0 [12164.211709] ? timerqueue_add+0x68/0xa0 [12164.211711] handle_mm_fault+0xd7/0x2b0 [12164.211714] do_user_addr_fault+0x1a0/0x450 [12164.211717] exc_page_fault+0x69/0x150 [12164.211720] ? asm_exc_page_fault+0x8/0x30 [12164.211722] asm_exc_page_fault+0x1e/0x30 [12164.211723] RIP: 0033:0x7fdf28fbece1 [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287 [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 7fdf28521fd8 [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 7fdf28522018 [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 0003afd8 [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 002b [12164.211734] R13: 23e0650ff2b8eb94 R14: R15: 7fffd18c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553768/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553769/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553758/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553759/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553765/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553766/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553770/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553767/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553760/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553764/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553761/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553762/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553763/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553756/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553755/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553754/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553757/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553753/+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/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-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: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
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: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Re: tp-link AC1300 not working in 21.10
apport information
** Tags added: apport-collected impish wayland-session
** Description changed:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: norbert1472 F pulseaudio
+ /dev/snd/controlC1: norbert1472 F pulseaudio
+ /dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2022-01-09 (3 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ MachineType: LENOVO 20AMS4SL00
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=de_DE.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
+ RebootRequiredPkgs: Error: path contained symlinks.
+ RelatedPackageVersions:
+ linux-restricted-modules-5.13.0-23-generic N/A
+ linux-backports-modules-5.13.0-23-generic N/A
+ linux-firmware 1.201.3
+ Tags: wayland-session impish
+ Uname: Linux 5.13.0-23-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: 08/27/2014
+ dmi.bios.release: 2.26
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: GIET76WW (2.26 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20AMS4SL00
+ 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: Not Available
+ dmi.ec.firmware.release: 1.13
+ dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
+ dmi.product.family: ThinkPad X240
+ dmi.product.name: 20AMS4SL00
+ dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
+ dmi.product.version: ThinkPad X240
+ dmi.sys.vendor: LENOVO
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1957002/+attachment/5553752/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware
[Kernel-packages] [Bug 1949065] Re: Wireless-AC 9260 iwlwifi unstable and connection drops
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1949065 Title: Wireless-AC 9260 iwlwifi unstable and connection drops Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: Ubuntu 22.04 development branch @ 28/10/2021 with kernel 5.13.0-19-generic My wifi with chipset Wireless-AC 9260 and iwlwifi are unstable and when browsing around the web a lot, i'm getting connections drops iwlwifi :02:00.0: No beacon heard and the time event is over already... and wlp2s0: Connection to AP 38:35:fb:19:91:da lost in journal logs driver=iwlwifi driverversion=5.13.0-19-generic firmware=46.6b541b68.0 9260-th-b0-jf-b0- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 1.202 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 2310 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 11:23:52 2021 Dependencies: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.202 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1949065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
Fix already in jammy. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Also affects: linux-oem-5.10 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released 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 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 source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
verified linux/impish version 5.13.0-26.27.
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Won't Fix
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:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
verified linux/impish version 5.13.0-26.27.
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1954930
Title:
AMD: Suspend not working when some cores are disabled through cpufreq
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
some cpu cores offline using cpufreq gadgets or via sysfs may hang the
system.
[Fix]
In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
dead in C3 state") fixes this issue.
[Test Case]
As stated in aforementioned bug url, setup cpufreq extention to take
down a few cpu cores, and trigger system suspend. There are ~50% chances
that networking/input/... would hang and the user can only reboot by
sysrq keys.
[Where problems could occur]
According to the patch discussion thread in
https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
not have a practical meaning, but simply C2 was the deepest supported
then.
[Other Info]
While this is currently only available in v5.16-rc1 and affects AMD
Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
== original bug report ==
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1188 F pulseaudio
/dev/snd/controlC2: ubuntu 1188 F pulseaudio
/dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9011-oem N/A
linux-backports-modules-5.14.0-9011-oem N/A
linux-firmware 1.187.23+staging.38
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-9011-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/30/2021
dmi.bios.release: 19.1
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RLD1005B_AB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Celadon-CZN
dmi.board.vendor: AMD
dmi.board.version:
[Kernel-packages] [Bug 1957753] 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 1957753 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: Incomplete Bug description: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot
Thanks a lot Matthew. Alright, no problems at all, I'll stick to .22
kernel for now and will wait for updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956519
Title:
amd_sfh: Null pointer dereference on early device init causes early
panic and fails to boot
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
In Progress
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1956519
[Impact]
A regression was introduced into 5.13.0-23-generic for devices using
AMD Ryzen chipsets that incorporate AMD Sensor Fusion Hub (SFH) HID
devices, which are mostly Ryzen based laptops, but desktops do have
the SOC embedded as well.
On early boot, when the driver initialises the device, it hits a null
pointer dereference with the following stack trace:
BUG: kernel NULL pointer dereference, address: 000c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0
Oops: 0002 [#1] SMP NOPTI
CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu
RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh]
Call Trace:
? __pci_set_master+0x5f/0xe0
amd_mp2_pci_probe+0xad/0x160 [amd_sfh]
local_pci_probe+0x48/0x80
pci_device_probe+0x105/0x1c0
really_probe+0x24b/0x4c0
driver_probe_device+0xf0/0x160
device_driver_attach+0xab/0xb0
__driver_attach+0xb2/0x140
? device_driver_attach+0xb0/0xb0
bus_for_each_dev+0x7e/0xc0
driver_attach+0x1e/0x20
bus_add_driver+0x135/0x1f0
driver_register+0x95/0xf0
? 0xc03d2000
__pci_register_driver+0x57/0x60
amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh]
do_one_initcall+0x48/0x1d0
? kmem_cache_alloc_trace+0xfb/0x240
do_init_module+0x62/0x290
load_module+0xa8f/0xb10
__do_sys_finit_module+0xc2/0x120
__x64_sys_finit_module+0x18/0x20
do_syscall_64+0x61/0xb0
? ksys_mmap_pgoff+0x135/0x260
? exit_to_user_mode_prepare+0x37/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? __x64_sys_mmap+0x33/0x40
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? do_syscall_64+0x6e/0xb0
? syscall_exit_to_user_mode+0x27/0x50
? do_syscall_64+0x6e/0xb0
? exc_page_fault+0x8f/0x170
? asm_exc_page_fault+0x8/0x30
entry_SYSCALL_64_after_hwframe+0x44/0xae
This causes a panic and the system is unable to continue booting, and
the user must select an older kernel to boot.
[Fix]
The issue was introduced in 5.13.0-23-generic by the commit:
commit d46ef750ed58cbeeba2d9a55c99231c30a172764
commit-impish 56559d7910e704470ad72da58469b5588e8cbf85
Author: Evgeny Novikov
Date: Tue Jun 1 19:38:01 2021 +0300
Subject:HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/d46ef750ed58cbeeba2d9a55c99231c30a172764
The issue is pretty straightforward, amd_sfh_client.c attempts to
dereference cl_data, but it is NULL:
$ eu-addr2line -ifae
./usr/lib/debug/lib/modules/5.13.0-23-generic/kernel/drivers/hid/amd-sfh-hid/amd_sfh.ko
amd_sfh_hid_client_init+0x47
0x0767
amd_sfh_hid_client_init
/build/linux-k2e9CH/linux-5.13.0/drivers/hid/amd-sfh-hid/amd_sfh_client.c:147:27
134 int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata)
135 {
...
146
147 cl_data->num_hid_devices = amd_mp2_get_sensor_num(privdata,
_data->sensor_idx[0]);
148
...
The patch moves the call to amd_sfh_hid_client_init() before
privdata->cl_data is actually allocated by devm_kzalloc, hence cl_data
being NULL.
+ rc = amd_sfh_hid_client_init(privdata);
+ if (rc)
+ return rc;
+
privdata->cl_data = devm_kzalloc(>dev, sizeof(struct
amdtp_cl_data), GFP_KERNEL);
if (!privdata->cl_data)
return -ENOMEM;
...
- return amd_sfh_hid_client_init(privdata);
+ return 0;
The issue was fixed upstream in 5.15-rc4 by the commit:
commit 88a04049c08cd62e698bc1b1af2d09574b9e0aee
Author: Basavaraj Natikar
Date: Thu Sep 23 17:59:27 2021 +0530
Subject: HID: amd_sfh: Fix potential NULL pointer dereference
Link:
https://github.com/torvalds/linux/commit/88a04049c08cd62e698bc1b1af2d09574b9e0aee
The fix places the call to amd_sfh_hid_client_init() after
privdata->cl_data is allocated, and it changes the order of
amd_sfh_hid_client_init() to happen before devm_add_action_or_reset()
fixing the actual null pointer dereference which caused these commits
to exist.
This patch also landed in 5.14.10 -stable, but it seems it was omitted
from being backported to impish, likely due to it sharing the exact
same subject line as the regression commit, so it was likely dropped
as a duplicate?
[Testcase]
You need an AMD Ryzen based system that has a AMD Sensor Fusion Hub
HID device built in to test this.
Simply
[Kernel-packages] [Bug 1952823] Re: Screen blinks when entering suspend
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) -- 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/1952823 Title: Screen blinks when entering suspend Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: [Summary] The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957753] [NEW] net/mlx5e: EPERM on vlan 0 programming
Public bug reported: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: New Bug description: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1955903] Re: Dell XPS 13 9370 never wakes from sleep
How do I do a dist-upgrade? dist-upgrade is not a valid command. On Tue, Jan 11, 2022 at 5:10 AM Kai-Chuan Hsieh <1955...@bugs.launchpad.net> wrote: > I did the following operation on XPS 9370, I can get eDP back to on > after resume. > > ubuntu@oem-4-4-somerville-xps13-italia-201708-25696-rt-dongle:/sys/class/drm$ > cat card0-eDP-1/dpms > On > ubuntu@oem-4-4-somerville-xps13-italia-201708-25696-rt-dongle:/sys/class/drm$ > sudo -s > root@oem-4-4-somerville-xps13-italia-201708-25696-rt-dongle:/sys/class/drm# > rtcwake -m freeze -s 15 > rtcwake: assuming RTC uses UTC ... > rtcwake: wakeup from "freeze" using /dev/rtc0 at Tue Jan 11 03:55:00 2022 > root@oem-4-4-somerville-xps13-italia-201708-25696-rt-dongle:/sys/class/drm# > cat card0-eDP-1/dpms > On > > Here is my software info: > BIOS: 1.17.0 > kernel: 5.11.0-46-generic > > Could you try dist-upgrade to latest kernel? Also I saw some > snd_hda_intel error, the audio might be broken. > > ** Attachment added: "eDP-resume.log" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955903/+attachment/5553231/+files/eDP-resume.log > > ** Changed in: linux (Ubuntu) > Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1955903 > > Title: > Dell XPS 13 9370 never wakes from sleep > > Status in linux package in Ubuntu: > New > > Bug description: > Every so often, whether I close the lid of the laptop or not, the > screen will go blank and neither pressing a key nor moving the mouse > will show anything. The only thing I can do to recover is hold the > power button down for 10 seconds to restart. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 > Uname: Linux 5.4.0-91-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Dec 28 08:25:44 2021 > DistUpgraded: 2020-05-08 07:44:41,528 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistributionChannelDescriptor: ># This is a distribution channel descriptor ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-xenial-amd64-20160624-2 > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Once a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: Dell UHD Graphics 620 [1028:07e6] > InstallationDate: Installed on 2018-03-12 (1387 days ago) > InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary > 20160624-10:47 > MachineType: Dell Inc. XPS 13 9370 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic > root=UUID=d9d0f137-4a05-4e95-aac6-c6835b632839 ro locale=en_US > alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 > mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash > vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to focal on 2020-05-08 (599 days ago) > dmi.bios.date: 10/07/2021 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.17.0 > dmi.board.name: 0F6P3V > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.17.0:bd10/07/2021:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9370 > dmi.product.sku: 07E6 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 > version.libdrm2: libdrm2 2.4.105-3~20.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 > version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 > 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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1957026 -- 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/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952823] Re: Screen blinks when entering suspend
** Changed in: oem-priority Importance: Undecided => Medium -- 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/1952823 Title: Screen blinks when entering suspend Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: [Summary] The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
