[Kernel-packages] [Bug 1950577] Re: wifi stopped working on HP Laptop with RTL8821CE Adapter
Works again with Kernel 5.13.0-25. Temporarily installed driver manually, search for Realtek RTL8821CE. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1950577 Title: wifi stopped working on HP Laptop with RTL8821CE Adapter Status in linux package in Ubuntu: Fix Released Bug description: Hello, I have a problem with the wifi connection on Linux Mint 20.2 Cinnamon with Kernel 5.11.0-40. Kernel 5.11.0-38 works fine. The same problem exists also with Kernel 5.13.0-21. My WIFI network adapter is then following: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ce I hope this information helps. If you have further questions, please let me know. Thanks for your great support. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reiner 1161 F pulseaudio /dev/snd/controlC0: reiner 1161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2019-09-26 (776 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 MachineType: HP HP Laptop 17-ca1xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=45bb260a-1a77-4622-887f-1ef5c4be2c55 ro quiet splash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip disk lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/29/2019 dmi.bios.release: 15.41 dmi.bios.vendor: AMI dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85B3 dmi.board.vendor: HP dmi.board.version: 91.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 91.40 dmi.modalias: dmi:bvnAMI:bvrF.41:bd05/29/2019:br15.41:efr91.40:svnHP:pnHPLaptop17-ca1xxx:pvr:sku6PR94EA#ABD:rvnHP:rn85B3:rvr91.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-ca1xxx dmi.product.sku: 6PR94EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950577/+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 1957150] [NEW] no response/black screen when waking up from suspend
Public bug reported: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. ** 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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: New Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957154] [NEW] Can't boot after kernel 5.11.0-44 update
Public bug reported: - With kernel 5.11.0-41 everything is ok. - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch lines at top of screen and instant reboot. - It may be related to nvidia-driver-470? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1523 F mate-settings-d adam 1928 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jan 12 10:00:59 2022 InstallationDate: Installed on 2021-10-03 (101 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision T3600 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957154 Title: Can't boot after kernel 5.11.0-44 update Status in linux package in Ubuntu: New Bug description: - With kernel 5.11.0-41 everything is ok. - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch lines at top of screen and instant reboot. - It may be related to nvidia-driver-470? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1523 F mate-settings-d adam 1928 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jan 12 10:00:59 2022 InstallationDate: Installed on 2021-10-03 (101 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision T3600 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957154/+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 1956238] Re: [BlueField] Unable to set TCP MD5SIG option on socket
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/1956238 Title: [BlueField] Unable to set TCP MD5SIG option on socket Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: $ grep TCP_MD5SIG /boot/config-5.4.0-1022-bluefield # CONFIG_TCP_MD5SIG is not set Expected: CONFIG_TCP_MD5SIG=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1956238/+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
Thank you everyone for the feedback!
@mldytech, it's likely that your system has a different issue that's preventing
it from booting. Could you please open a bug report so we can better
investigate it? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
Invalid
Status in linux source package in Impish:
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 1956748] Re: Long loading time on boot (black screen with blinking stripe)
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Hello Sven, Thank you for the bug report. This seems to be the same issue as reported on bug 1956401, which was fixed with kernel 5.13.0-25. I will mark this bug as a duplicate. Please feel free to undo it in case your issue was not fixed by this kernel update. ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956748 Title: Long loading time on boot (black screen with blinking stripe) Status in linux package in Ubuntu: New Bug description: Since I installed 5.13.0-23 the boot time increased by 1 or 2 minutes. This is after the boot icon of linux mint. A black screen appears and the logon screen will be visible after a while. This is also with the previous versions of this kernel. 5.11* is ok for me. Problemdevice: Asus FX505DU version.log output: Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956748/+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 1957160] [NEW] BlueZ release 5.63
Public bug reported: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1957160 Title: BlueZ release 5.63 Status in bluez package in Ubuntu: In Progress Bug description: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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
This fix (afd18180c070 drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.) is already applied to devel kernel series
(jammy:linux).
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Changed in: linux (Ubuntu Jammy)
Status: Invalid => 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/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 1957160] Re: BlueZ release 5.63
** Attachment added: "bluez_5.63-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+attachment/5553550/+files/bluez_5.63-0ubuntu1.debian.tar.xz ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1957160 Title: BlueZ release 5.63 Status in bluez package in Ubuntu: Fix Committed Bug description: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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 1957160] Re: BlueZ release 5.63
** Attachment added: "bluez_5.63.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+attachment/5553549/+files/bluez_5.63.orig.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1957160 Title: BlueZ release 5.63 Status in bluez package in Ubuntu: Fix Committed Bug description: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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 1957160] Re: BlueZ release 5.63
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1957160 Title: BlueZ release 5.63 Status in bluez package in Ubuntu: Fix Committed Bug description: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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 1954420] Re: Backport the privacy screen changeset from 5.17
After discussion we are dropping that request to minimize work. In practice only few configurations have the corresponding hardware at the moment and the LTS will use 5.17 for oem kernel which will also be available to normal Ubuntu was part of the hwe updates, that should be enough ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954420 Title: Backport the privacy screen changeset from 5.17 Status in linux package in Ubuntu: Won't Fix Bug description: The feature is a request from oem and desktop, we would need the new privacy-screen changes that landed upstream for 5.17 to be backported to the Ubuntu kernel the LTS will include The corresponding changeset is https://patchwork.freedesktop.org/patch/457641/ Corresponding drm/i915 changes just landed yesterday on drm-intel-next yesterday and should flow back to linux-next today Corresponding userland changes will be part of the new GNOME this cycle It's also worth noting that we will need tweaks to the initrd generation as reported on https://bugs.launchpad.net/bugs/1954320 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954420/+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 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
** Changed in: juju Milestone: 2.9.23 => 2.9.24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error Status in OpenStack RabbitMQ Server Charm: Invalid Status in juju: In Progress Status in ubuntu-fan package in Ubuntu: New Bug description: Hi, Using manual provider on top of VMWare. Juju: 2.9.14 VM: Focal Containers: Bionic I've noticed that, in a given Focal host, 2x Bionic containers may have different behavior: one successfully completes cloud-init whereas the other fails. The failed container errors at "apt update" in cloud- init with: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Something wicked happened resolving 'PROXY_IP:' (-9 - Address family for hostname not supported) (Likely this is the line where it breaks: https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436) Failed container, full cloud-init-output.log: https://pastebin.canonical.com/p/hKNw49mvJP/ Successful container, full cloud-init-output.log: https://pastebin.canonical.com/p/P6MZdQPrWd/ Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/ I can see that, on the host, dnsmasq served the FAN IP to the broken container after the "apt-update" was called. - FAILED CONTAINER -: Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.198 00:16:3e:da:dd:c4 apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds. - SUCCESSFUL CONTAINER -: Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.253 00:16:3e:d7:6b:ef apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds. In the case of the Failed Container, the DHCPOFFER arrived 1s after the "apt update" was requested, whereas the Successful Container logged a DHCPOFFER 30s before the "apt update". To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+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
The revert of the gcc-11 patch mentioned above results in working kernel builds, which load zfs.ko built-into-kernel and built via zfs-dkms as well. ** Description changed: [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 ** Summary changed: - jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 + 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 ** Description changed: [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. -- 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/ope
[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
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: s390x ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Changed in: ubuntu-z-systems Importance: Undecided => Critical -- 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 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
Sorry about that, I'm investigating. -- 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 1949770] Re: Enable arm64 for Hyper-V guests
** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-meta-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-meta-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-signed-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-signed-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-meta-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-meta-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-signed-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-signed-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: In Progress Status in linux-signed-azure package in Ubuntu: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-meta-azure source package in Hirsute: Fix Released Status in linux-signed-azure source package in Hirsute: Fix Released Status in linux-azure source package in Impish: In Progress Status in linux-meta-azure source package in Impish: In Progress Status in linux-signed-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: In Progress Status in linux-signed-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+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 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot
This bug is awaiting verification that the linux/5.11.0-47.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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 T
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
This bug is awaiting verification that the linux/5.11.0-47.52 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
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 Committed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
* The s390x diagnose 318 instruction sets the control program name
code (CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.
* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
[Fix]
* In general the following 4 commits are needed:
* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
* For jammy, hirsute and impish only the first commit is needed, the
others are already in.
* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.
[Test Case]
* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
* And setup an Ubuntu KVM virtual on top.
* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.
* The CPNC will always be 4 (denotes Linux environment).
* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.
[Where problems could occur]
* The approach here is to provide additional debug and diagnose
information on top.
* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.
* The changes themselves are relatively discernible and mostly
introduce new structures.
* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the
verification later is targeted at.
* Since diag318 is s390x specific, all the modifications touch s390x
code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
diag.h). At least no other other architecture will be affected.
* Well, there is one tiny bit of a common code change, but it's just a
new define statement in include/uapi/linux/kvm.h ('#define
KVM_CAP_S390_DIAG318 186').
[Other]
* Request was to add the patches to focal / 20.04, but to avoid
potential regressions on upgrades, the patches need to be added to
jammy, impish and hirsute, too.
* As mentioned above,
[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
This bug is awaiting verification that the linux/5.11.0-47.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress 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 Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] If any sub-test in this icmp_redirect.sh is failing but not expected to fail. The script will complain: ./icmp_redirect.sh: line 72: [: 1: unary operator expected This is because when the sub-test is not expected to fail, we won't pass any value for the xfail local variable in log_test() and thus it's empty. Fix this by passing 0 as the 4th variable to log_test() for non-xfail cases. This issue can be found on our KVM kernel with SRU tests, they're failing because of missing some kernel configs. [Fix] * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()" This patch can be cherry-picked into all of the affected kernels. [Test Plan] Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm), and this "unary operator expected" error message should no longer exist. [Where problems could occur] Change limited to test script, it won't have any impact to real kernel function. And this issue is most likely specific to KVM kernels. == Original Bug Report == icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47 # selftests: net: icmp_redirect.sh # # ### # Legacy routing # ### # # TEST: IPv4: redirect exception [ OK ] # TEST: IPv6: redirect exception [ OK ] # TEST: IPv4: redirect exception plus mtu [ OK ] # TEST: IPv6: redirect exception plus mtu [ OK ] # TEST: IPv4: routing reset [ OK ] # TEST: IPv6: routing reset [ OK ] # TEST: IPv4: mtu exception [ OK ] # TEST: IPv6: mtu exception [ OK ] # TEST: IPv4: mtu exception plus redirect [ OK ] # TEST: IPv6: mtu exception plus redirect [XFAIL] # # ### # Legacy routing with VRF # ### # # Error: Unknown device type. # Cannot find device "red" # Error: argument "red" is wrong: Invalid VRF # # Error: argument "red" is wrong: Invalid VRF # # Cannot find device "red" # Cannot find device "red" # Error: argument "red" is wrong: Not a valid VRF name # # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception plus mtu [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception plus mtu [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: routing reset [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: routing reset [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary op
[Kernel-packages] [Bug 1950666] Re: system crash when removing ipmi_msghandler module
This bug is awaiting verification that the linux/5.11.0-47.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1950666 Title: system crash when removing ipmi_msghandler module Status in linux package in Ubuntu: In Progress 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 Committed Status in linux source package in Jammy: In Progress Bug description: [IMPACT] Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier) pushes the removal of an ipmi_user into the system's workqueue. Whenever an ipmi_user struct is about to be removed it is scheduled as a work on the system's workqueue to guarantee the free operation won't be executed in atomic context. When the work is executed the free_user_work() function is invoked which frees the ipmi_user. When ipmi_msghandler module is removed in cleanup_ipmi() function, there is no check if there are any pending works to be executed. Therefore, there is a potential race condition : An ipmi_user is scheduled for removal and shortly after to remove the ipmi_msghandler module. If the scheduled work delays execution for any reason and the module is removed first, then when the work is executed the pages of free_user_work() are gone and the system crashes with the following : BUG: unable to handle page fault for address: c05c3450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0 Oops: 0010 [#1] SMP PTI CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 5.4.0-77-generic #86~18.04.1-Ubuntu Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 05/23/2019 Workqueue: events 0xc05c3450 RIP: 0010:0xc05c3450 Code: Bad RIP value. RSP: 0018:b721333c3e88 EFLAGS: 00010286 RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8 RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0 RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080 R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700 R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070 FS: () GS:92a95f54() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? process_one_work+0x20f/0x400 worker_thread+0x34/0x410 kthread+0x121/0x140 ? process_one_work+0x400/0x400 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler] CR2: c05c3450 [TEST CASE] The user who reported the issue can reproduce reliably by stopping the ipmi related services and then removing the ipmi modules. I could reproduce the issue only when turning the normal 'work' to delayed work. [WHERE PROBLEMS COULD OCCUR] The fixing patch creates a dedicated workqueue for the remove_work struct of ipmi_user when loading the ipmi_msghandler modules and destroys the workqueue when removing the module. Therefore any potential problems would occur during these two operations or when scheduling works on the dedicated workqueue. [OTHER] Upstream patches : 1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue) 5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+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)
This bug is awaiting verification that the linux/5.11.0-47.52 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/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
[Kernel-packages] [Bug 1956857] Re: Mouse not working after boot
Removing USB hub solved problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956857 Title: Mouse not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Mouse does not work/load on boot, requires reboot and then loads. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 09:40:45 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2017-01-21 (1814 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2907 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 xserver.bootTime: Fri Oct 20 08:03:20 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956857/+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 1951011] Re: linux-aws: Make a signed kernel
** Also affects: linux-aws-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-aws-5.11 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-aws-5.11 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-aws-5.11 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws-5.11 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-aws-5.11 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-aws-5.11 (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws-5.11 package in Ubuntu: Invalid Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-5.11 source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: In Progress Status in linux-aws-5.11 source package in Bionic: Invalid Status in linux-aws-hwe source package in Bionic: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.11 source package in Focal: Fix Committed Status in linux-aws-hwe source package in Focal: Invalid Status in linux-aws source package in Hirsute: In Progress Status in linux-aws-5.11 source package in Hirsute: Invalid Status in linux-aws-hwe source package in Hirsute: Invalid Status in linux-aws source package in Impish: In Progress Status in linux-aws-5.11 source package in Impish: Invalid Status in linux-aws-hwe source package in Impish: Invalid Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+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 1951011] Re: linux-aws: Make a signed kernel
** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Also affects: linux-aws-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-aws-5.13 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-aws-5.13 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-aws-5.13 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-aws-5.13 (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws-5.11 package in Ubuntu: Invalid Status in linux-aws-5.13 package in Ubuntu: Invalid Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-5.11 source package in Xenial: Invalid Status in linux-aws-5.13 source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws-5.11 source package in Bionic: Invalid Status in linux-aws-5.13 source package in Bionic: Invalid Status in linux-aws-hwe source package in Bionic: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.11 source package in Focal: Fix Committed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-aws-hwe source package in Focal: Invalid Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws-5.11 source package in Hirsute: Invalid Status in linux-aws-5.13 source package in Hirsute: Invalid Status in linux-aws-hwe source package in Hirsute: Invalid Status in linux-aws source package in Impish: In Progress Status in linux-aws-5.11 source package in Impish: Invalid Status in linux-aws-5.13 source package in Impish: Invalid Status in linux-aws-hwe source package in Impish: Invalid Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+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 1951011] Re: linux-aws: Make a signed kernel
** Changed in: linux-aws (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws-5.11 package in Ubuntu: Invalid Status in linux-aws-5.13 package in Ubuntu: Invalid Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-5.11 source package in Xenial: Invalid Status in linux-aws-5.13 source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws-5.11 source package in Bionic: Invalid Status in linux-aws-5.13 source package in Bionic: Invalid Status in linux-aws-hwe source package in Bionic: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.11 source package in Focal: Fix Committed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-aws-hwe source package in Focal: Invalid Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws-5.11 source package in Hirsute: Invalid Status in linux-aws-5.13 source package in Hirsute: Invalid Status in linux-aws-hwe source package in Hirsute: Invalid Status in linux-aws source package in Impish: In Progress Status in linux-aws-5.11 source package in Impish: Invalid Status in linux-aws-5.13 source package in Impish: Invalid Status in linux-aws-hwe source package in Impish: Invalid Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+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: kernel panic after upgrading to kernel 5.13.0-23
Matthew, thanks a lot. I can confirm the issue is gone. There is a bunch of preexisting errors related to the BIOS as far as I can see, but these were present in .22 too. Please go right ahead with the patch submission and hopefully it'll make it into .26 kernel. vadikmironov@MINIPC-PN50:~$ uname -rv 5.13.0-23-generic #23+TEST1956519v20220112b1-Ubuntu SMP Wed Jan 12 00:24:19 UTC 20 vadikmironov@MINIPC-PN50:~$ sudo dmesg | grep -i bug [0.159485] ACPI BIOS Error (bug): Failure creating named object [\SMIB], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.160771] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.M291.WLAN], AE_NOT_FOUND (20210331/dswload2-162) [0.162718] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.VER1], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162742] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CCI0], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162748] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CCI1], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162753] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CCI2], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162758] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CCI3], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162779] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL0], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162785] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL1], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162790] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL2], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162795] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL3], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162800] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL4], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162805] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL5], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162811] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL6], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162817] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.CTL7], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162840] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI0], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162846] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI1], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162852] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI2], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162857] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI3], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162863] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI4], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162869] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI5], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162874] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI6], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162880] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI7], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162885] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI8], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162891] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGI9], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162897] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGIA], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162902] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGIB], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162908] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGIC], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162913] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGID], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162919] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGIE], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162925] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGIF], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162950] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGO0], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162956] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0.MGO1], AE_ALREADY_EXISTS (20210331/dsfield-637) [0.162961] ACPI BIOS Error (bug): Failure creating named object
[Kernel-packages] [Bug 1957196] Re: webcam doesn't work
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957196/+attachment/5553606/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957196 Title: webcam doesn't work Status in linux package in Ubuntu: New 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 1957196] [NEW] webcam doesn't work
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: usbwebcam webcam ** Attachment added: "lsusb -v.txt" https://bugs.launchpad.net/bugs/1957196/+attachment/5553605/+files/lsusb%20-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/1957196 Title: webcam doesn't work Status in linux package in Ubuntu: New 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 1957198] [NEW] HDMI audio no longer working on Pi4 after 5.13.0-1011
Public bug reported: Confirming reports made in the UbuntuMATE forums. HDMI audio no longer shows as available on kernels beginning with 5.13.0-1011 After reverting to kernel 5.13.0-1008 HDMI audio is available. Pi4 4GB ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1008-raspi 5.13.0-1008.9 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed Jan 12 10:56:22 2022 ImageMediaBuild: 20201028 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-09-26 (107 days ago) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish raspi-image -- 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/1957198 Title: HDMI audio no longer working on Pi4 after 5.13.0-1011 Status in linux-raspi package in Ubuntu: New Bug description: Confirming reports made in the UbuntuMATE forums. HDMI audio no longer shows as available on kernels beginning with 5.13.0-1011 After reverting to kernel 5.13.0-1008 HDMI audio is available. Pi4 4GB ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1008-raspi 5.13.0-1008.9 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed Jan 12 10:56:22 2022 ImageMediaBuild: 20201028 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-09-26 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1957198/+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
Works for me as well. Thank you for the quick fix. I thought I was going
to have a run a -proposed kernel package for a few weeks.
--
You 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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
Hi @tjaalton and @vicamo: So 5.14.21 will be coming on Jan 31st. Have you been able to identify what went wrong? If so, is there any chance the fix will appear before the 31st? Thanks again for rapid assistance! -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1920847] Re: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529)
I have this issue as well on a Dell XFR booting from a CD made by Cubic. I did find if I used the kernel that came with the disk (5.11.0-27 vs 5.11.0-48) it would boot and allow install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1920847 Title: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: ACPI Error on boot: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529) Occurred on fresh install of 21.04 Computer: Dell Inspiron 5401 P130G Ubuntu Version: Description: Ubuntu 20.04.2 LTS Release: 20.04 Package Version: linux-signed-hwe-5.8 What i expected to happen: Not have this error appear What Happened: This error Appeared. A dump of the ACPI table has been provided. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 22 23:34:08 2021 InstallationDate: Installed on 2021-03-23 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.13/5.13.0.25.26~20.04.12)
All autopkgtests for the newly accepted linux-meta-hwe-5.13 (5.13.0.25.26~20.04.12) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.14 (amd64, s390x, ppc64el) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
I have a laptop that was installed soon after 21.10 release with full disk encryption and ZFS, after several crazy issues, I've found this thread - this explains it.. 1:-What can I do to properly re-install the system? (fix all corrupted files.) 2:-how can I even clean-install disk encrypted system if the 21.10 bootable iso is corrupting stuff wint ZFS? -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
...maybe installing from scratch with the current 22.04 build from https://cdimage.ubuntu.com/daily-live/current/ can solve my problem? - will that dev install eventually become a real release? (or is using a dev upgraded after release, somehow worse than a release?) -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Hi @dgatwood, @ja, The test kernels have finished building and are ready for you to try. Like I said before, they are 5.11.0-44-generic for Focal HWE and Hirsute, and 5.13.0-23-generic for Impish, with just the one commit reverted: commit 5caa90d5fedfcdf57a42c272896cfd0ef6b5c667 commit-upstream: 5255660b208aebfdb71d574f3952cf48392f4306 Author: Jonathan Bell Date: Fri Oct 8 12:25:44 2021 +0300 Subject: xhci: add quirk for host controllers that don't update endpoint DCS Link: https://github.com/torvalds/linux/commit/5255660b208aebfdb71d574f3952cf48392f4306 Let's see if this is the commit which is causing you issues. Could you please install a test kernel and let me know if your USB ports work again? Please note, these test packages are NOT SUPPORTED by Canonical and are for TEST PURPOSES ONLY. ONLY install in a dedicated test environment. Instructions to install: 1) sudo add-apt-repository ppa:mruffell/lp1956849-test 2) sudo apt update For Focal HWE and Hirsute users: 3) sudo apt install linux-image-unsigned-5.11.0-44-generic linux-modules-5.11.0-44-generic linux-modules-extra-5.11.0-44-generic linux-headers-5.11.0-44-generic For Impish users: 3) sudo apt install linux-image-unsigned-5.13.0-23-generic linux-modules-5.13.0-23-generic linux-modules-extra-5.13.0-23-generic linux-headers-5.13.0-23-generic 4) sudo reboot 5) uname -rv Focal: 5.11.0-44-generic #48~20.04.2+TEST1956849v20220112b1-Ubuntu SMP Wed Jan 12 02:26:0 Hirsute: 5.11.0-44-generic #48+TEST1956849v20220112b1-Ubuntu SMP Wed Jan 12 02:31:07 UTC 20 Impish: 5.13.0-23-generic #23+TEST1956849v20220112b1-Ubuntu SMP Wed Jan 12 02:37:08 UTC 20 If you are asked to abort the current kernel removal, say no. You may need to change your grub config to boot the correct kernel. You can follow these instructions to do that: https://paste.ubuntu.com/p/WGpCWTPyTj/ Please make sure the uname is correct on boot. Sometimes newer kernels get pulled in due to metapackage dependencies not liking the linux- image-unsigned package. Let me know if your USB ports start to work again. If they do, we can revert the commit in the Ubuntu kernels, and go and report the issue upstream and get it fixed. If it doesn't, then we will need to do some more tests to try find the commit which introduced the regression. 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: New Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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
** Summary changed: - kernel panic after upgrading to kernel 5.13.0-23 + amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot ** Description changed: - After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest - kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails - with the panic halfway through the boot process (which got overall - suspiciously slow): + BugLink: https://bugs.launchpad.net/bugs/1956519 - [1.359465] BUG: kernel NULL pointer dereference, address: 000c - [1.359498] #PF: supervisor write access in kernel mode - [1.359519] #PF: error_code(0x0002) - not-present page - [1.359540] PGD 0 P4D 0 - [1.359553] Oops: 0002 [#1] SMP NOPTI - [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu - [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 - [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] - [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d - [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 - [1.359750] RAX: RBX: RCX: - [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c - [1.359804] RBP: bf71c099fa20 R08: R09: 0006 - [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 - [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 - [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: - [1.359915] CS: 0010 DS: ES: CR0: 80050033 - [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 - [1.359964] Call Trace: - [1.359976] ? __pci_set_master+0x5f/0xe0 - [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] - [1.360021] local_pci_probe+0x48/0x80 - [1.360038] pci_device_probe+0x105/0x1c0 - [1.360056] really_probe+0x24b/0x4c0 - [1.360073] driver_probe_device+0xf0/0x160 - [1.360091] device_driver_attach+0xab/0xb0 - [1.360110] __driver_attach+0xb2/0x140 - [1.360126] ? device_driver_attach+0xb0/0xb0 - [1.360145] bus_for_each_dev+0x7e/0xc0 - [1.360161] driver_attach+0x1e/0x20 - [1.360177] bus_add_driver+0x135/0x1f0 - [1.360194] driver_register+0x95/0xf0 - [1.360210] ? 0xc03d2000 - [1.360225] __pci_register_driver+0x57/0x60 - [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] - [1.360266] do_one_initcall+0x48/0x1d0 - [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 - [1.360306] do_init_module+0x62/0x290 - [1.360323] load_module+0xa8f/0xb10 - [1.360340] __do_sys_finit_module+0xc2/0x120 - [1.360359] __x64_sys_finit_module+0x18/0x20 - [1.360377] do_syscall_64+0x61/0xb0 - [1.361638] ? ksys_mmap_pgoff+0x135/0x260 - [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 - [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 - [1.365343] ? __x64_sys_mmap+0x33/0x40 - [1.366550] ? do_syscall_64+0x6e/0xb0 - [1.367749] ? do_syscall_64+0x6e/0xb0 - [1.368923] ? do_syscall_64+0x6e/0xb0 - [1.370079] ? syscall_exit_to_user_mode+0x27/0x50 - [1.371227] ? do_syscall_64+0x6e/0xb0 - [1.372359] ? exc_page_fault+0x8f/0x170 - [1.373478] ? asm_exc_page_fault+0x8/0x30 - [1.374584] entry_SYSCALL_64_after_hwframe+0x44/0xae - [1.375684] RIP: 0033:0x7ff0ec73a94d - [1.376767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 - [1.377926] RSP: 002b:7ffd00724ba8 EFLAGS: 0246 ORIG_RAX: 0139 - [1.379076] RAX: ffda RBX: 55e130084390 RCX: 7ff0ec73a94d - [1.380225] RDX: RSI: 7ff0ec8ca3fe RDI: 0005 - [1.381363] RBP: 0002 R08: R09: - [1.382488] R10: 0005 R11: 0246 R12: 7ff0ec8ca3fe - [1.383598] R13: 55e130083370 R14: 55e130084480 R15: 55e130086cb0 - [1.384698] Modules linked in: ahci(+) libahci i2c_piix4(+) r8169(+) amd_sfh(+) i2c_hid_acpi realtek i2c_hid xhci_pci(+) xhci_pci_renesas wmi(+) video(+) fjes(+) hid - [1.385841] CR2: 000c - [1.386955] ---[ end trace b2ebcacf74b788da ]--- - [1.388064] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] - [1.389176] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d -
[Kernel-packages] [Bug 1957452] [NEW] package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.1
You have been subscribed to a public bug: I was trying to install a wifi driver for my usb wifi catcher. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-utils-470 (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 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-470:amd64: Install nvidia-utils-470:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 13 01:27:08 2022 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 InstallationDate: Installed on 2022-01-09 (3 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: nvidia-graphics-drivers-470 Title: package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 https://bugs.launchpad.net/bugs/1957452 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot
Hi Vadik,
Thanks for running that test kernel, and its great to hear that it fixes
your issue.
I have written up a proper SRU template for the bug, and I tidied up the
patches and submitted them for SRU to the Ubuntu Kernel team mailing
list:
https://lists.ubuntu.com/archives/kernel-team/2022-January/127102.html
https://lists.ubuntu.com/archives/kernel-team/2022-January/127103.html
The next steps are for the kernel team to review the patches. We need
two acks from Senior Kernel Team members to be accepted into the next
kernel SRU cycle.
Once we have two acks, the patch will be applied to the Impish kernel
git tree, and built into the next kernel update, and placed into
-proposed for verification. When this happens, I will need you to test
the kernel in -proposed and again make sure it fixes your issue. If it
does, I will mark the Launchpad bug as verified and the kernel will be
released to -updates at the end of the cycle.
Looking at https://kernel.ubuntu.com/, we see the next patch deadline is
the 26th of Jan, hopefully we will get a review by then, the kernel team
will build the kernel between 31st Jan and 4th of Feb, and the kernel
will be in -proposed between 7th Feb and 18th of Feb, with a release
hopefully 21st Feb, give or take a few days if any CVEs turn up.
I will keep you informed of each step, and I will write back when its
time to test the kernel in -proposed.
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:
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,
&cl_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, h
[Kernel-packages] [Bug 1957452] Re: package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108
** Package changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu) -- 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/1957452 Title: package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I was trying to install a wifi driver for my usb wifi catcher. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-utils-470 (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 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-470:amd64: Install nvidia-utils-470:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 13 01:27:08 2022 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 InstallationDate: Installed on 2022-01-09 (3 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: nvidia-graphics-drivers-470 Title: package nvidia-utils-470 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.108-0ubuntu5.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1957452/+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 1957714] [NEW] Computer off, discharge battery
Public bug reported: After having updated the Kernel version to this 5.11.0.46 the battery drains when the computer is off and charges when it is turned on. I tried to see what it could be and in Windows they point to the Intel Management Engine Interface driver ** 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/1957714 Title: Computer off, discharge battery Status in linux package in Ubuntu: New Bug description: After having updated the Kernel version to this 5.11.0.46 the battery drains when the computer is off and charges when it is turned on. I tried to see what it could be and in Windows they point to the Intel Management Engine Interface driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix 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 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-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Another OEM also need this linux-firmware SRU(because the two additional firmwares: rampatch_usb_00130200.bin and nvm_usb_00130200.bin): https://bugs.launchpad.net/sutton/+bug/1939648/comments/10 And I confirmed the package in linux-firmware(1.187.25) can fix the issue #1939648, the OEM schedule just need the package lands to focal- updates from focal-proposed ASAP. -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-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-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-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: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.ve
[Kernel-packages] [Bug 1956857] Re: Mouse not working after boot
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1956857 Title: Mouse not working after boot Status in linux package in Ubuntu: Invalid Bug description: Mouse does not work/load on boot, requires reboot and then loads. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 09:40:45 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2017-01-21 (1814 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2907 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 xserver.bootTime: Fri Oct 20 08:03:20 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956857/+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 1955689] Re: Add Bluetooth support for Qualcomm WCN6856
** Tags added: oem-priority originate-from-1939648 sutton -- 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/1955689 Title: Add Bluetooth support for Qualcomm WCN6856 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Backport firmware blobs and driver support to make it work by loading correct firmwares. [Test] Bluetooth scanning and pairing work, and continue to do so after several suspend/resume cycles. [Where problems could occur] The upstream version of btusb_generate_qca_nvm_name() adds several missing le*_to_cpu() macros, so if this device was ever used on a Big Endian system, this is a behavioral change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955689/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@Shengyao, Please check LP: #1955689 instead. -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-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-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-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: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.
[Kernel-packages] [Bug 1957019] Re: ACPI failure on Ryzen laptops
Hi Jay, can you give the test kernel in comment #15 from bug 1956519 to see if you're having the same issue? Thanks ** 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/1957019 Title: ACPI failure on Ryzen laptops Status in linux package in Ubuntu: Incomplete Bug description: I have a Ryzen 4700U laptop. I'm staying on 5.13.0-22 kernel because the -23 and -25 both have ACPI failures and will hang if you shutdown or reboot the PC. I have a DMESG log showing failures: BUG: kernel NULL pointer dereference, address: 000c #PF: supervisor write access in kernel mode [1.607078] #PF: error_code(0x0002) - not-present page [1.607081] PGD 0 P4D 0 [1.607085] Oops: 0002 [#1] SMP NOPTI [1.607088] CPU: 2 PID: 205 Comm: systemd-udevd Not tainted 5.13.0-25-generic #26~20.04.1-Ubuntu [1.607093] Hardware name: HP HP ENVY x360 Convertible 13-ay0xxx/876E, BIOS F.20 07/30/2021 [1.607096] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.607107] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 a3 06 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 70 59 [1.607111] RSP: 0018:bd1d00acb9e0 EFLAGS: 00010246 [1.607115] RAX: RBX: RCX: [1.607117] RDX: 0020 RSI: c0440249 RDI: 88e00031 [1.607120] RBP: bd1d00acba28 R08: R09: 88e00052 [1.607123] R10: 0007 R11: d00f R12: 000fffe0 [1.607125] R13: 95ae94acad98 R14: 95ae812210c8 R15: 0002 [1.607128] FS: 7fdc24e64880() GS:95b17f68() knlGS: [1.607131] CS: 0010 DS: ES: CR0: 80050033 [1.607134] CR2: 000c CR3: 00011558a000 CR4: 00350ee0 [1.607136] Call Trace: [1.607140] ? __pci_set_master+0x5f/0xe0 [1.607148] amd_mp2_pci_probe+0xa8/0x140 [amd_sfh] [1.607154] local_pci_probe+0x48/0x80 [1.607158] pci_device_probe+0x10f/0x1c0 [1.607163] really_probe+0x1dc/0x440 [1.607168] driver_probe_device+0xf0/0x160 [1.607171] device_driver_attach+0x5d/0x70 [1.607174] __driver_attach+0xb2/0x140 [1.607177] ? device_driver_attach+0x70/0x70 [1.607180] bus_for_each_dev+0x7e/0xc0 [1.607185] driver_attach+0x1e/0x20 [1.607187] bus_add_driver+0x152/0x1f0 [1.607192] driver_register+0x74/0xd0 [1.607195] ? 0xc042d000 [1.607197] __pci_register_driver+0x57/0x60 [1.607201] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.607206] do_one_initcall+0x48/0x1d0 [1.607212] ? __cond_resched+0x19/0x30 [1.607218] ? kmem_cache_alloc_trace+0x37c/0x440 [1.607224] do_init_module+0x62/0x260 [1.607228] load_module+0x125d/0x1440 [1.607233] __do_sys_finit_module+0xc2/0x120 [1.607236] ? __do_sys_finit_module+0xc2/0x120 [1.607240] __x64_sys_finit_module+0x1a/0x20 [1.607243] do_syscall_64+0x61/0xb0 [1.607249] ? do_syscall_64+0x6e/0xb0 [1.607252] ? do_syscall_64+0x6e/0xb0 [1.607255] ? exc_page_fault+0x8f/0x170 [1.607259] ? asm_exc_page_fault+0x8/0x30 [1.607263] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.607266] RIP: 0033:0x7fdc253e689d [1.607270] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48 [1.607275] RSP: 002b:7ffdbbe4f6d8 EFLAGS: 0246 ORIG_RAX: 0139 [1.607279] RAX: ffda RBX: 55ca49d610a0 RCX: 7fdc253e689d [1.607282] RDX: RSI: 7fdc252c3ded RDI: 0005 [1.607284] RBP: 0002 R08: R09: [1.607287] R10: 0005 R11: 0246 R12: 7fdc252c3ded [1.607290] R13: R14: 55ca49d70ac0 R15: 55ca49d610a0 [1.607293] Modules linked in: amd_sfh(+) xhci_pci(+) i2c_piix4(+) nvme_core(+) i2c_hid xhci_pci_renesas rtsx_pci(+) wmi(+) video(+) fjes(+) hid [1.607306] CR2: 000c [1.607309] ---[ end trace 26f62dba0942f2c8 ]--- [1.607312] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.607316] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 a3 06 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 70 59 [1.607321] RSP: 0018:bd1d00acb9e0 EFLAGS: 00010246 [1.607324] RAX: RBX: 000
[Kernel-packages] [Bug 1957160] Re: BlueZ release 5.63
This bug was fixed in the package bluez - 5.63-0ubuntu1
---
bluez (5.63-0ubuntu1) jammy; urgency=medium
* New upstream release 5.63 (LP: #1957160):
- Fix issue with storing IRK causing invalid read access.
- Fix issue with disconnecting due to GattCharacteristic1.MTU.
- Add support for Device{Found,Lost} of advertising monitoring.
* Drop upstreamed patches:
- 0001-obexd-plugins-import-PBAP-ebook-support-from-upstrea.patch
- 0001-obexd-plugins-port-ebook-support-to-the-latest-EDS.patch
- CVE-2021-41229.patch
* Refreshed patches:
- allow-using-obexd-without-systemd-in-the-user-sessio.patch
-- Daniel van Vugt Wed, 12 Jan 2022
18:28:06 +0800
** Changed in: bluez (Ubuntu)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41229
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1957160
Title:
BlueZ release 5.63
Status in bluez package in Ubuntu:
Fix Released
Bug description:
http://www.bluez.org/release-of-bluez-5-63/
https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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 1957160] Re: BlueZ release 5.63
** CVE removed: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2021-41229 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1957160 Title: BlueZ release 5.63 Status in bluez package in Ubuntu: Fix Released Bug description: http://www.bluez.org/release-of-bluez-5-63/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+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 1914228] Re: the indicator light of the shift key works correctly but the change from upper case to lower case is not done correctly so I have to display my password to see if i
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914228 Title: the indicator light of the shift key works correctly but the change from upper case to lower case is not done correctly so I have to display my password to see if it is upper case or lower case Status in linux package in Ubuntu: Expired Bug description: the indicator light of the shift key works correctly but the change from upper case to lower case is not done correctly so I have to display my password to see if it is upper case or lower case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914228/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Re-installing from scratch should resolve the issue. I suspect in most cases if you install with the 21.10 installer (even though it has the old kernel) as long as you install updates during the install this issue probably won't hit you. It mostly seems to occur after a reboot and it's loading data back from disk again. As per some of the other comments you'll have a bit of a hard time copying data off the old broken install.. you need to work through which files/folders are corrupt and reboot and then exclude those from the next rsync. You could use the 22.04 daily build, it will eventually upgrade into the final release. However not usually recommended as there may be bugs or other problems in those daily images and/or it's not uncommon for the development release to sometimes break during the development cycle. Most of the time it doesn't and it usually works most of the time, but it's much more likely than using 21.10. I'd try a re-install with 21.10 as I described. Obviously you'll need to backup all of your data from the existing install first. -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_l
[Kernel-packages] [Bug 1957744] [NEW] Unable to set correct resolutions on virtual displays
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1957744 Title: Unable to set correct resolutions on virtual displays Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Hirsute: New Status in linux-oracle source package in Impish: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1957744/+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 1957714] 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 1957714 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/1957714 Title: Computer off, discharge battery Status in linux package in Ubuntu: Incomplete Bug description: After having updated the Kernel version to this 5.11.0.46 the battery drains when the computer is off and charges when it is turned on. I tried to see what it could be and in Windows they point to the Intel Management Engine Interface driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957714/+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 1957154] 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/1957154 Title: Can't boot after kernel 5.11.0-44 update Status in linux package in Ubuntu: Confirmed Bug description: - With kernel 5.11.0-41 everything is ok. - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch lines at top of screen and instant reboot. - It may be related to nvidia-driver-470? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1523 F mate-settings-d adam 1928 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jan 12 10:00:59 2022 InstallationDate: Installed on 2021-10-03 (101 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision T3600 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957154/+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] 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 1957196 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/1957196 Title: webcam doesn't work Status in linux package in Ubuntu: Incomplete 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 1957150] 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 1957150 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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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] 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 1957002
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/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
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 1956561] 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 1956561 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/1956561 Title: 5.15 kernel selftest srv6_end_dt46_l3vpn_test.sh failure Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error (it seems to be an upstream issue): 15187 19:34:40 DEBUG| [stdout] # 15188 19:34:40 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15189 19:34:40 DEBUG| [stdout] # 15190 19:34:41 DEBUG| [stdout] # 15191 19:34:41 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [ OK ] 15192 19:34:45 DEBUG| [stdout] # 15193 19:34:45 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15194 19:34:45 DEBUG| [stdout] # 15195 19:34:45 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [ OK ] 15196 19:34:49 DEBUG| [stdout] # 15197 19:34:49 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15198 19:34:50 DEBUG| [stdout] # 15199 19:34:50 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [ OK ] 15200 19:34:54 DEBUG| [stdout] # 15201 19:34:54 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15202 19:34:54 DEBUG| [stdout] # 15203 19:34:54 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [ OK ] 15204 19:34:58 DEBUG| [stdout] # 15205 19:34:58 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956561/+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 1956562] 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 1956562 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/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue): 15321 19:35:52 DEBUG| [stdout] # 15322 19:35:52 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15323 19:35:52 DEBUG| [stdout] # 15324 19:35:56 DEBUG| [stdout] # 15325 19:35:56 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15326 19:36:00 DEBUG| [stdout] # 15327 19:36:00 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15328 19:36:04 DEBUG| [stdout] # 15329 19:36:04 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15330 19:36:08 DEBUG| [stdout] # 15331 19:36:08 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] 15332 19:36:08 DEBUG| [stdout] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956562/+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 1956559] 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 1956559
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/1956559
Title:
sleep/wake-up timeout issue
Status in linux package in Ubuntu:
Incomplete
Bug description:
I have a unexpected issue that related in sleep/wake-up timeout for task,
while device driver develop.
my code use kernel function 'wait_for_completion_interruptible_timeout' when
there is a reason for task sleep, this function parameter need input 'want
timeout in jiffies', so i have try that input any value like
"msecs_to_jiffies(255 * 1000)" for sleep task 255seconds.
I expected this function 'wait_for_completion_interruptible_timeout' return
zero when after almost exactly 255seconds. but I measured the actual time, it
was additionally delayed maximum almost 11 seconds(final time 266 seconds) in
my test case.
so result of have additional test, the additionally delayed time is
different, but the result is the same.
additionally delayed time range was random in 1ms ~ 11seconds.
this issue occur in kernel function 'msleep(255 * 1000)' too... because
schedule_timeout() used in 'wait_for_completion_interruptible_timeout' and
msleep.
※A additionally delayed time occurs even if a different number is
entered like 1ms or 1seconds..
I think it "additionally delayed time" was mean that wake-up task but time to
task racing until active run in cpu. am i guessing right? or not am i doing
something wrong?
If my thoughts are right, How do I get the correct time?
Below is the sample code I tested.
struct completion cmp;
static long g_jiffies = 0;
static int _open(struct inode *inode, struct file *file)
{
init_completion(&cmp);
g_jiffies = 0;
return 0;
}
static ssize_t _read(struct file *filp, char __user *buffer, size_t count,
loff_t *ppos)
{
long sch = 0;
reinit_completion(&cmp);
printk(KERN_NOTICE "start checking\n");
g_jiffies = jiffies;
sch = wait_for_completion_interruptible_timeout(&cmp,
msecs_to_jiffies(255 * 1000));
//msleep(255 * 1000)
printk(KERN_NOTICE "delay time = %ld\n", jiffies_to_msecs(jiffies -
g_jiffies));
return 0;
}
result dmesg :
[목 1월 6 13:05:30 2022] start checking
[목 1월 6 13:09:52 2022] delay time = 261808
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956559/+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 1956849] 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 1956849 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: Incomplete Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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 1956998] 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 1956998 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/1956998 Title: kvm SGX numa support Status in linux package in Ubuntu: Incomplete Bug description: The basic SGX patches were merged into Qemu release, the left NUMA function for SGX should be enabled. The patch1 implemented the SGX NUMA ACPI to enable NUMA in the SGX guest. Since Libvirt need detailed host SGX EPC sections info to decide how to allocate EPC sections for SGX NUMA guest, the SGXEPCSection list is introduced to show detailed sections info in the monitor or HMP interface. Please help review this patchset, the link also can be found: https://github.com/intel/qemu-sgx upstream Platform: Ice Lake qemu 6.2 110581238 numa: Enable numa for SGX EPC sections 4755927ae numa: Support SGX numa in the monitor and Libvirt interfaces d1889b360 doc: Add the SGX numa description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956998/+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 1956760] 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 1956760 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956760 Title: xHCI (xhci_hcd) host controller not working after unattended kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: After the unattended-upgrade on January 5th (i.e. 5.4.0-92.103~18.04.2, automatic), the xHCI (xhci_hcd) host controller stopped working (i.e. no USB device is working): ===>dmesg log: linux1804 kernel: xhci_hcd :00:14.0: Abort failed to stop command ring: -110 linux1804 kernel: xhci_hcd :00:14.0: xHCI host controller not responding, assume dead linux1804 kernel: xhci_hcd :00:14.0: HC died; cleaning up linux1804 kernel: xhci_hcd :00:14.0: Timeout while waiting for setup device command linux1804 kernel: usb 4-1: device not accepting address 2, error -108 linux1804 kernel: usb usb4-port1: couldn't allocate usb_device linux1804 kernel: usb usb3-port1: couldn't allocate usb_device ===>unattended-upgrade info: Start-Date: 2022-01-05 11:08:54 Commandline: /usr/bin/unattended-upgrade Install: linux-image-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules- extra-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-headers-5.4.0-92 -generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-hwe-5.4-headers-5.4.0-92:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic) Upgrade: linux-headers-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-image-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82) End-Date: 2022-01-05 11:09:29 ===>lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ===>Workaround: This happens on any boot after power off. If I restart the computer, the problem is not reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956760/+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 1956830] 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 1956830 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1956830 Title: Problems with fprind (various readers) Jammy and earlier Status in linux package in Ubuntu: Incomplete Bug description: The fingerprint reader is not working. I have tried 2 an elan and a digital persona U.4500.U both fail to recognize the fingerprint. I downloaded the latest Beta available to date. I also tried with Ubuntu Mate 20.04.3 and other live Ubuntu. [CODE] ubuntu@ubuntu:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8644:800e Intenso GmbG USB Flash Disk Bus 001 Device 004: ID 04f3:0c28 Elan Microelectronics Corp. fingerprint sensor [FeinTech FPS00200] Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ubuntu@ubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 Enrolling right-index-finger finger. Enroll result: enroll-stage-passed Enroll result: enroll-swipe-too-short Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-swipe-too-short Enroll result: enroll-swipe-too-short Enroll result: enroll-stage-passed Enroll result: enroll-swipe-too-short Enroll result: enroll-swipe-too-short Enroll result: enroll-completed ubuntu@ubuntu:~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-retry-scan (not done) Verify result: verify-swipe-too-short (not done) Verify result: verify-swipe-too-short (not done) Verify result: verify-no-match (done) ubuntu@ubuntu:~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-swipe-too-short (not done) Verify result: verify-retry-scan (not done) Verify result: verify-no-match (done) ubuntu@ubuntu:~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-swipe-too-short (not done) Verify result: verify-no-match (done) ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ba:000a DigitalPersona, Inc. Fingerprint Reader Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ubuntu@ubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 Enrolling right-index-finger finger. Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-completed ubuntu@ubuntu:~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-match (done) ubuntu@ubuntu:~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-no-match (done) ubuntu@ubuntu:~$ [/CODE] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956830/+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 1956780] 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 1956780
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/1956780
Title:
5.15 stuck at boot on c4.large
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
c4.large instances are stuck at boot with kernel 5.15.0-15.15.
[Test case]
Simply deploy a c4.large instance and install the latest jammy kernel
(5.15.0-15.15).
[Fix]
It looks like the offending commit is the following:
02c70033b98b ("PCI/MSI: Mask MSI-X vectors only on success")
Reverting the commit fixes the problem.
[Regression potential]
It looks like the commit was fixing a potential breakage with broken
Marvell NVME devices, so we may see crashes in presence of these
devices. However, reverting the commit we are simply restoring the
previous behavior, so potential regressions should be limited to these
broken devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956780/+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 1950195] 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/1950195 Title: [amdgpu] Wayland session unresponsive on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: My laptop, HP model 17-y028cy, does not resume after the display has been shut off for inactivity. The computer starts back up and the display does turn on, but nothing is displayed on my screen. It doesn't appear to respond to any key presses so I have to force it to power down and back up by holding the power button until it shuts off. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 11:10:58 2021 DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221] InstallationDate: Installed on 2021-08-18 (82 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago) dmi.bios.date: 01/16/2017 dmi.bios.release: 15.37 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8221 dmi.board.vendor: HP dmi.board.version: 85.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 85.39 dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1MF63UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+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] 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 1933301 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/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 1956964] 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/1956964 Title: iwlwifi connection drops using AX200 Status in linux package in Ubuntu: Confirmed Bug description: I get occasional (sometimes once per hour, sometimes more often) connection drops on my Thinkpad T14s Gen 1 (which uses an Intel AX 200 chipset). dmesg reports a microcode SW error and seems to restart the adapter. I recently moved, so I'm not sure if it's caused by the environment or an update. I'm using a Fritzbox 7530 AX router and got an older model (7490) and another Thinkpad (T450s) with an intel chipset available for testing if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonas 2455 F pulseaudio /dev/snd/controlC1: jonas 2455 F pulseaudio /dev/snd/controlC3: jonas 2455 F pulseaudio /dev/snd/controlC0: jonas 2455 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Mon Jan 10 13:50:22 2022 InstallationDate: Installed on 2021-01-22 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001QGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-29 (41 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET60W(1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrR1CET60W(1.29):bd11/30/2020:br1.29:efr1.29:svnLENOVO:pn20UH001QGE:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QGE dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956964/+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 1957112] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1956426] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1956426 Title: MIssing firmware for Intel Visual Sensing Controller Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on Intel Alder Lake platforms. [Fix] Two commits from upstream repo https://github.com/intel/ivsc-firmware main branch. While Intel has no plan to upstream their IPU6 driver before kernel camera API is out, the firmware blobs will probably stay where they are until the plan changed. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel has not yet published these ivsc fw for redistribution. Focal is nomiated to support oem-5.14 kernel. == original bug report == This is a followup for bug 1955383 that ivsc firmware was not publicly released at the time submitting other Intel IPU6 works for Alder Lake platform. They're now available in https://github.com/intel/ivsc- firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1956426/+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 1955689] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1955689 Title: Add Bluetooth support for Qualcomm WCN6856 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Backport firmware blobs and driver support to make it work by loading correct firmwares. [Test] Bluetooth scanning and pairing work, and continue to do so after several suspend/resume cycles. [Where problems could occur] The upstream version of btusb_generate_qca_nvm_name() adds several missing le*_to_cpu() macros, so if this device was ever used on a Big Endian system, this is a behavioral change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955689/+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 1955613] Re: Add basic Wifi support for Qualcomm WCN6856
This bug was fixed in the package linux-firmware - 1.187.25 --- linux-firmware (1.187.25) focal; urgency=medium * SAUCE: Camera bins release on 2021-11-01 for Alder Lake (LP: #1955383) * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - QCA: Add Bluetooth firmware for WCN685x - QCA: Update Bluetooth firmware for WCN685x - QCA: Add Bluetooth firmware for WCN685x - QCA: Add Bluetooth default nvm file for WCN685x * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 -- Juerg Haefliger Mon, 10 Jan 2022 11:19:19 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1955613 Title: Add basic Wifi support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Qualcomm WCN6856 doens't work. [Fix] Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the scope of this SRU. [Test] The system can connect to Wifi. Wifi still works after several rounds of suspend/resume cycles. [Where problems could occur] The change is limited to ath11k, which is also the only user of mhi bus, so the scope of risk is limited. Let alone it never worked before, so there's not much room to go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955613/+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 1955689] Re: Add Bluetooth support for Qualcomm WCN6856
This bug was fixed in the package linux-firmware - 1.187.25 --- linux-firmware (1.187.25) focal; urgency=medium * SAUCE: Camera bins release on 2021-11-01 for Alder Lake (LP: #1955383) * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - QCA: Add Bluetooth firmware for WCN685x - QCA: Update Bluetooth firmware for WCN685x - QCA: Add Bluetooth firmware for WCN685x - QCA: Add Bluetooth default nvm file for WCN685x * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 -- Juerg Haefliger Mon, 10 Jan 2022 11:19:19 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1955689 Title: Add Bluetooth support for Qualcomm WCN6856 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Backport firmware blobs and driver support to make it work by loading correct firmwares. [Test] Bluetooth scanning and pairing work, and continue to do so after several suspend/resume cycles. [Where problems could occur] The upstream version of btusb_generate_qca_nvm_name() adds several missing le*_to_cpu() macros, so if this device was ever used on a Big Endian system, this is a behavioral change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955689/+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 1955613] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1955613 Title: Add basic Wifi support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Qualcomm WCN6856 doens't work. [Fix] Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the scope of this SRU. [Test] The system can connect to Wifi. Wifi still works after several rounds of suspend/resume cycles. [Where problems could occur] The change is limited to ath11k, which is also the only user of mhi bus, so the scope of risk is limited. Let alone it never worked before, so there's not much room to go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955613/+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 1955383] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-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-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-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) UserG
[Kernel-packages] [Bug 1956426] Re: MIssing firmware for Intel Visual Sensing Controller
This bug was fixed in the package linux-firmware - 1.187.25 --- linux-firmware (1.187.25) focal; urgency=medium * SAUCE: Camera bins release on 2021-11-01 for Alder Lake (LP: #1955383) * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - QCA: Add Bluetooth firmware for WCN685x - QCA: Update Bluetooth firmware for WCN685x - QCA: Add Bluetooth firmware for WCN685x - QCA: Add Bluetooth default nvm file for WCN685x * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 -- Juerg Haefliger Mon, 10 Jan 2022 11:19:19 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1956426 Title: MIssing firmware for Intel Visual Sensing Controller Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on Intel Alder Lake platforms. [Fix] Two commits from upstream repo https://github.com/intel/ivsc-firmware main branch. While Intel has no plan to upstream their IPU6 driver before kernel camera API is out, the firmware blobs will probably stay where they are until the plan changed. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel has not yet published these ivsc fw for redistribution. Focal is nomiated to support oem-5.14 kernel. == original bug report == This is a followup for bug 1955383 that ivsc firmware was not publicly released at the time submitting other Intel IPU6 works for Alder Lake platform. They're now available in https://github.com/intel/ivsc- firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1956426/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
This bug was fixed in the package linux-firmware - 1.187.25 --- linux-firmware (1.187.25) focal; urgency=medium * SAUCE: Camera bins release on 2021-11-01 for Alder Lake (LP: #1955383) * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - QCA: Add Bluetooth firmware for WCN685x - QCA: Update Bluetooth firmware for WCN685x - QCA: Add Bluetooth firmware for WCN685x - QCA: Add Bluetooth default nvm file for WCN685x * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 -- Juerg Haefliger Mon, 10 Jan 2022 11:19:19 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Kernel-packages] [Bug 1957150] Re: no response/black screen when waking up from suspend
apport information ** Tags added: apport-collected una ** Description changed: - On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as - basically all kernels since 5.11) and linux mint cinnamon, there's a - problem where if the computer sleeps/suspends at all (either - automatically or when I press the button), any attempt to wake up the - computer is futile. In order to keep using the computer, I have to hard - shut-off by holding down the power button, and turn it on again. This - problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is - what I've been using. + On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tauren 1378 F pulseaudio + /dev/snd/controlC2: tauren 1378 F pulseaudio + /dev/snd/controlC0: tauren 1378 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2021-12-22 (22 days ago) + InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 + MachineType: Acer Swift SF314-42 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-25-generic N/A + linux-backports-modules-5.13.0-25-generic N/A + linux-firmware 1.187.24 + Tags: una + Uname: Linux 5.13.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/13/2021 + dmi.bios.release: 1.10 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V1.10 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: Kona_RN + dmi.board.vendor: RO + dmi.board.version: V1.10 + dmi.chassis.type: 10 + dmi.chassis.vendor: Acer + dmi.chassis.version: V1.10 + dmi.ec.firmware.release: 1.6 + dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: + dmi.product.family: Swift 3 + dmi.product.name: Swift SF314-42 + dmi.product.sku: + dmi.product.version: V1.10 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553709/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (
[Kernel-packages] [Bug 1957150] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553715/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553714/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553718/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553719/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553712/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553713/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553727/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553726/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553720/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553725/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553711/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553722/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553717/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553721/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553723/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553710/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1957150] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553724/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
Hi Vinay, This is Michael from Marvell. This bug was brought to our attention and we would like to help resolve this issue. We analyzed the logs attached to this bug and below is our analysis : err_warn_bitmap=:0040 - 22 BIT means FCOE_ERROR_CODE_FCP_RSP_INVALID_PAYLOAD_SIZE 0040: - BIT 38 set - means FCOE_ERROR_CODE_COMMON_INCORRECT_SEQ_CNT So it appears that there is something wrong with either the target or the fabric as the firmware is reporting invalid payload size and sequence count errors. To debug the issue further we would need a wire trace between the IOM and the target. Also TCP dump on the adapter ports of the system along with driver logs again. It will also be helpful if you can enable driver debug. Steps to enable driver debug: Load the driver with following parameters modprobe -v qedf debug=1 Thanks, Michael. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Incomplete Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+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 1957150] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1957150/+attachment/5553716/+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/1957150 Title: no response/black screen when waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: On my laptop (an AMD Acer Swift 3) using kernel 5.13.0-25 (as well as basically all kernels since 5.11) and linux mint cinnamon, there's a problem where if the computer sleeps/suspends at all (either automatically or when I press the button), any attempt to wake up the computer is futile. In order to keep using the computer, I have to hard shut-off by holding down the power button, and turn it on again. This problem doesn't exist with kernel 5.11.0-44 or 5.11.0-46, so that is what I've been using. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tauren 1378 F pulseaudio /dev/snd/controlC2: tauren 1378 F pulseaudio /dev/snd/controlC0: tauren 1378 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-12-22 (22 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=fd1f7db7-d2d0-48dd-8527-8b64f26abaff ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.24 Tags: una Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/13/2021 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957150/+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
