[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
> Was it it more than a red line in systemctl status output? Does it have annoying logging behaviour or break some other service if it isn't running? Red lines and an avoidable boot delay while trying to restart and failing a bunch of times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
I don't think that's enough since it also gets pulled in by ubuntu- desktop and ubuntu-desktop-minimal as recommends. It would also be nice if we found a solution that fixes the issue on existing installations since upgrades from mantic to noble will trigger the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2054296] Re: Don't restrict to linux-laptop
It looks like this change did indeed cause issues for non-qualcomm hardware, see https://bugs.launchpad.net/ubuntu/+source/ubuntu- meta/+bug/206266 We should definitely check if we can restrict the service to supported qualcomm devices only. Currently it causes systemd errors and a noticeable boot delay on at least raspi and apple silicon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: Fix Released Status in qrtr package in Ubuntu: Fix Released Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
Looking at the diff between mantic and noble I think the regression was cause by a change to pd-mapper.service.in for https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
Can confirm that this is was a major annoyance on my m2 air after upgrading to noble. it seems like this worked better in previous releases. Looking at my logs it seems like it was already installed on mantic but didn't cause startup problems. I think it gets pulled in by being in Recommends for ubuntu-desktop. I'm all for making it device specific instead. IMO there is no point in having it installed on non Qualcomm devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2044657] Re: zfs block cloning file system corruption
FreeBSD has released an official advisory for the issue today: https://lists.freebsd.org/archives/freebsd- stable/2023-November/001726.html -- 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/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: zfs block cloning file system corruption
Below is a potential fix/workaround for noble. This includes the two upstream commits https://github.com/openzfs/zfs/commit/03e9caaec006134b3db9d02ac40fe9369ee78b03 and https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f to make block cloning optional and then disable it by default. The same should also work for mantic. Please let me know if there is a better way to submit the fix. ** Patch added: "0001-Fix-block-cloning-corruption-bug.patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+attachment/5723679/+files/0001-Fix-block-cloning-corruption-bug.patch -- 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/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: New Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: zfs block cloning file system corruption
There is also a CVE that seems to be caused by the same bug: https://nvd.nist.gov/vuln/detail/CVE-2023-49298 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298 -- 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/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: New Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] [NEW] zfs block cloning file system corruption
Public bug reported: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: New Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2042573] [NEW] arm64 atomic issues cause disk corruption
Public bug reported: The 6.5 kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions. An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 This is fixed by https://lore.kernel.org/linux-arm- kernel/20230920142201.GG348037@frogsfrogsfrogs/T/ ** 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/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: New Bug description: The 6.5 kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions. An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 This is fixed by https://lore.kernel.org/linux-arm- kernel/20230920142201.GG348037@frogsfrogsfrogs/T/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 2035147] [NEW] amdgpu hangs
Public bug reported:
With the new mantic kernel the kernel after a while gets into a state
where amdgpu hangs when starting any game. My suspicion is that it might
happen after waking up from suspend but I am not entirely sure about
that yet. After rebooting It will work for a while until it doesn't.
The exact symptom is that any game running in full screen mode will hang
up and not update the display. It is clear that the game is running
because audio works as intended. When opening the gnome window overview
it does render correctly in the preview.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.3.0-7-generic 6.3.0-7.7+4
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 23:14:36 2023
InstallationDate: Installed on 2023-01-11 (243 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.3.0-7-generic N/A
linux-backports-modules-6.3.0-7-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-08-29 (13 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: Z170 PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
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/2035147
Title:
amdgpu hangs
Status in linux package in Ubuntu:
New
Bug description:
With the new mantic kernel the kernel after a while gets into a state
where amdgpu hangs when starting any game. My suspicion is that it
might happen after waking up from suspend but I am not entirely sure
about that yet. After rebooting It will work for a while until it
doesn't.
The exact symptom is that any game running in full screen mode will
hang up and not update the display. It is clear that the game is
running because audio works as intended. When opening the gnome window
overview it does render correctly in the preview.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.3.0-7-generic 6.3.0-7.7+4
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 23:14:36 2023
InstallationDate: Installed on 2023-01-11 (243 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.3.0-7-generic N/A
linux-backports-modules-6.3.0-7-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-08-29 (13 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: Z170 PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Kernel-packages] [Bug 1974162] Re: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU]
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974162 Title: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Status in linux package in Ubuntu: New Bug description: Hi, attaching a Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] on the machines usb port and connecting to a wifi spot seems to work fine. The system seems to have a physical connection to the other end (connection manager shows successfully established link with aquired ip/subnet, link speed and loaded driver) but no data will be transfered over the device. Having a closer look at the kernel messages, i found this: [ 2049.163706] [ 2049.163773] UBSAN: array-index-out-of-bounds in /build/linux-WD899k/linux-5.15.0/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:502:15 [ 2049.163789] index 13 is out of range for type 'rtl_tid_data [9]' [ 2049.163799] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 2049.163810] Hardware name: Default string Default string/Default string, BIOS $(AMI_ROM_NAME)_Trtl$(2021)$(03)$(12)$(18)$(44) 03/12/2021 [ 2049.163815] Call Trace: [ 2049.163821] [ 2049.163830] show_stack+0x52/0x58 [ 2049.163868] dump_stack_lvl+0x4a/0x5f [ 2049.163896] dump_stack+0x10/0x12 [ 2049.163912] ubsan_epilogue+0x9/0x45 [ 2049.163928] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 2049.163950] rtl92cu_tx_fill_desc+0x515/0x530 [rtl8192cu] [ 2049.164000] _rtl_usb_tx_preprocess+0xdf/0x180 [rtl_usb] [ 2049.164016] rtl_usb_tx+0x60/0x1a0 [rtl_usb] [ 2049.164030] rtl_op_tx+0xb0/0xd0 [rtlwifi] [ 2049.164064] ieee80211_tx_frags+0x16a/0x240 [mac80211] [ 2049.164273] __ieee80211_tx+0x78/0x170 [mac80211] [ 2049.164454] ? invoke_tx_handlers_late+0x201/0x310 [mac80211] [ 2049.164636] ieee80211_tx+0xfa/0x150 [mac80211] [ 2049.164818] ieee80211_xmit+0xc0/0xf0 [mac80211] [ 2049.164997] __ieee80211_tx_skb_tid_band+0x6d/0x80 [mac80211] [ 2049.165178] ieee80211_rx_h_action_return+0xf9/0x160 [mac80211] [ 2049.165357] ieee80211_rx_handlers+0x3c6/0x590 [mac80211] [ 2049.165537] ieee80211_prepare_and_rx_handle+0x159/0x480 [mac80211] [ 2049.165719] ? sta_info_hash_lookup+0xac/0x100 [mac80211] [ 2049.165892] __ieee80211_rx_handle_packet+0x19b/0x310 [mac80211] [ 2049.166069] ? ieee80211_rx_monitor+0x10d/0x4f0 [mac80211] [ 2049.166248] ieee80211_rx_list+0x227/0x380 [mac80211] [ 2049.166425] ? rtl_process_phyinfo+0xe1/0x2f0 [rtlwifi] [ 2049.166457] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 2049.166636] _rtl_usb_rx_process_noagg+0x1a7/0x1e0 [rtl_usb] [ 2049.166653] _rtl_rx_work+0x69/0x120 [rtl_usb] [ 2049.14] tasklet_action_common.constprop.0+0xbd/0xf0 [ 2049.166679] tasklet_action+0x22/0x30 [ 2049.166688] __do_softirq+0xd6/0x2e3 [ 2049.166701] irq_exit_rcu+0x8c/0xb0 [ 2049.166711] common_interrupt+0x8a/0xa0 [ 2049.166723] [ 2049.166726] [ 2049.166730] asm_common_interrupt+0x1e/0x40 [ 2049.166739] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 2049.166754] Code: 3d c4 4b 1e 4a e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 2049.166761] RSP: 0018:b52f400d3e28 EFLAGS: 0246 [ 2049.166771] RAX: 8b14bbcb0f00 RBX: 8b14425e9400 RCX: [ 2049.166777] RDX: RSI: RDI: [ 2049.166781] RBP: b52f400d3e78 R08: 01dd1baa4837 R09: [ 2049.166786] R10: R11: 071c71c71c71c71c R12: b74e60a0 [ 2049.166792] R13: 0003 R14: 0003 R15: 01dd1baa4837 [ 2049.166801] ? cpuidle_enter_state+0xc8/0x620 [ 2049.166810] ? tick_nohz_stop_tick+0x166/0x1d0 [ 2049.166824] cpuidle_enter+0x2e/0x40 [ 2049.166832] cpuidle_idle_call+0x13e/0x1e0 [ 2049.166843] do_idle+0x83/0xf0 [ 2049.166850] cpu_startup_entry+0x20/0x30 [ 2049.166857] start_secondary+0x12a/0x180 [ 2049.166868] secondary_startup_64_no_verify+0xc2/0xcb [ 2049.166883] [ 2049.166888] System details are: Linux computer 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Bus 001 Device 009: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Module info is: filename:
