[Kernel-packages] [Bug 1960016] Re: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout '
Not a huge fan of copy-pasta but this may be more useful here. +1 AX200 ``` 07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084] Kernel driver in use: iwlwifi Kernel modules: iwlwifi ``` ``` [ 25.711840] Bluetooth: Core ver 2.22 [ 25.711860] NET: Registered PF_BLUETOOTH protocol family [ 25.711861] Bluetooth: HCI device and connection manager initialized [ 25.711864] Bluetooth: HCI socket layer initialized [ 25.711866] Bluetooth: L2CAP socket layer initialized [ 25.711869] Bluetooth: SCO socket layer initialized [ 25.788390] iwlwifi :07:00.0: loaded firmware version 66.f1c864e0.0 cc-a0-66.ucode op_mode iwlmvm [ 27.783372] Bluetooth: hci0: command 0xfc05 tx timeout [ 27.783378] Bluetooth: hci0: Reading Intel version command failed (-110) [ 28.785728] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 28.785731] Bluetooth: BNEP filters: protocol multicast [ 28.785733] Bluetooth: BNEP socket layer initialized ``` ``` celiyah@darkunicorn:~$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-26 16:43:43 CST; 12min ago Docs: man:bluetoothd(8) Main PID: 28973 (bluetoothd) Status: "Running" Tasks: 1 (limit: 76959) Memory: 668.0K CPU: 38ms CGroup: /system.slice/bluetooth.service └─28973 /usr/lib/bluetooth/bluetoothd ``` ``` celiyah@darkunicorn:~$ bluetoothctl Agent registered [bluetooth]# scan on No default controller available quitetooth]# ``` It's popping up in Ubuntu forums e.g. https://askubuntu.com/questions/1448731/bluetooth-not-working-no-controller-available | Reloading `btusb` module several times makes it working. Any specific steps for this? I have not been able to get it to work. Issue persists despite reboots incl. hard power off/on. This happened suddenly. ``` celiyah@darkunicorn:~$ uname -a Linux darkunicorn 5.15.0-56-lowlatency #62-Ubuntu SMP PREEMPT Wed Nov 23 09:50:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux celiyah@darkunicorn:~$ lsmod | grep bt btusb 61440 0 btrtl 24576 1 btusb btbcm 24576 1 btusb btintel40960 1 btusb bluetooth 708608 12 btrtl,btintel,btbcm,bnep,btusb ``` (I believe the bleeding cutting edge 23.04.1 is the only available bunty release with a 6 kernel line. Could be wrong.) Note the workaround in the askubuntu question: https://askubuntu.com/a/1456898/253482 (for transparency, I'm linking to my own answer). -- 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/1960016 Title: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' Status in linux package in Ubuntu: Confirmed Bug description: With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot. With a Cold boot it is working. My hardware: $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well. https://bugzilla.redhat.com/show_bug.cgi?id=2027071 https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 For example on Fedora35 my Bluetooth did not initialize correctly after warm boot between versions 5.14.18 > 5.15.14. After a cold boot it worked. (Turned off the desktop PC and disconnected it from power for a few seconds.) Kernel 5.15.15 changed that and since then everything went fine again. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 The fix is mentioned there… https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf1948...@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 Direct-Link to commit mentioned in the above discussion… https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-20.04 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 12:26:46 2022 InstallationDate: Installed on 2022-02-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1960016] Re: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout '
Yes.. I'm a little confused. For example the previously mentioned thread (id=215167) is still very much ongoing, with some people reporting that certain kernel versions fix this and others reporting it showing up in regressions as late as 6.2. They referenced a message https://lore.kernel.org/all/20211202162256.31837-1-ti...@suse.de/ refers to commit 95655456e7cee858a23793f67025765b4c4c227b upstream, which was merged into 5.16 mainline last year. https://lkml.org/lkml/2022/1/14/195 -- I will post back in the bugzilla thread later that this seems to be unrelated. I believe on the Ubuntu side patching from 5.11 to 5.15 caused this problem for me. And it would appear that 5.19 has it as well. But needless to say in "stable LTS" (22.04.2/5.15) this is still happening, breaking bluetooth for Ubuntu users. -- 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/1960016 Title: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' Status in linux package in Ubuntu: Confirmed Bug description: With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot. With a Cold boot it is working. My hardware: $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well. https://bugzilla.redhat.com/show_bug.cgi?id=2027071 https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 For example on Fedora35 my Bluetooth did not initialize correctly after warm boot between versions 5.14.18 > 5.15.14. After a cold boot it worked. (Turned off the desktop PC and disconnected it from power for a few seconds.) Kernel 5.15.15 changed that and since then everything went fine again. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 The fix is mentioned there… https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf1948...@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 Direct-Link to commit mentioned in the above discussion… https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-20.04 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 12:26:46 2022 InstallationDate: Installed on 2022-02-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F51d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960016/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Can confirm on 22.10, Lenovo Yoga 720 (4k display). Is there no fix for this other than trying to mess with initramfs compression settings? Is that expected to be the normal user case? -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Committed Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200 000F ACPI_Recl 41B3-41BFEFFF 00CF 000F BS_Data41BFF000-41BF 0001 000F Available 0001-0002AB7F 001AB800 000F Reserved 000A-000F 0060 Reserved
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Update: Last night I tried as far back as 18.04 and it turns out this has been backported everywhere. I've had these controllers since 2016-ish, have never had a problem before. Now I can't even work around by installing older kernels (s/a 5.3 used for 18.04.5). Finding other HWRAID controllers is not a solution for me. Here's the good news: https://github.com/torvalds/linux/commit/1e41e693f458eef2d5728207dbd327cd3b16580a ...has been merged into 6.1-rc4. So, help is on the way. -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Deleted #31 as it may not be relevant. Has this been merged into the 6.1 kernel RC? thx, sorry for multiples, catching up here -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Also, @khfeng —if asking people to beta test a random kernel from an S3 bucket, would you mind providing some original checksums? :) -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Flashed two LTS install drives today both with the same issue. 2xSATA
JMicron controllers (HWRAID), /dev/sda and /dev/sdb are taking turns
throwing buffer I/O errors ("Buffer I/O error on dev sdb, logical block
0, async page read") and the system never boots. Any idea when the fix
will be in main-line?
--
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/1970074
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something wrong with ata driver in dmesg found:
[1.980693] kernel:
[1.980699] kernel: fbcon: Taking over console
[1.980703] kernel: UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
[1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
[1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted
5.15.0-25-generic #25-Ubuntu
[1.980716] kernel: Hardware name: System manufacturer System Product
Name/P5Q3, BIOS 110206/11/2010
[1.980718] kernel: Call Trace:
[1.980721] kernel:
[1.980723] kernel: show_stack+0x52/0x58
[1.980729] kernel: dump_stack_lvl+0x4a/0x5f
[1.980734] kernel: dump_stack+0x10/0x12
[1.980736] kernel: ubsan_epilogue+0x9/0x45
[1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49
[1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci]
[1.980748] kernel: ata_qc_issue+0x135/0x240
[1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580
[1.980754] kernel: ? vprintk_default+0x1d/0x20
[1.980759] kernel: ata_exec_internal+0x67/0xa0
[1.980762] kernel: sata_pmp_read+0x8d/0xc0
[1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90
[1.980768] kernel: sata_pmp_attach+0x8b/0x310
[1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0
[1.980775] kernel: ata_eh_recover+0x6b6/0xb30
[1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci]
[1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci]
[1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci]
[1.980792] kernel: ?
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
[1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560
[1.980799] kernel: sata_pmp_error_handler+0x23/0x40
[1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci]
[1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600
[1.980810] kernel: ata_scsi_error+0x9c/0xd0
[1.980813] kernel: scsi_error_handler+0xa1/0x180
[1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0
[1.980820] kernel: kthread+0x12a/0x150
[1.980823] kernel: ? set_kthread_struct+0x50/0x50
[1.980826] kernel: ret_from_fork+0x22/0x30
[1.980831] kernel:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eugene16798 F pulseaudio
/dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio
/dev/snd/controlC1: eugene16798 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Apr 24 05:13:34 2022
HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
InstallationDate: Installed on 2019-04-13 (1106 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
IwConfig:
lono wireless extensions.
enp2s0no wireless extensions.
virbr0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=uk_UA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet
splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-25-generic N/A
linux-backports-modules-5.15.0-25-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago)
dmi.bios.date: 06/11/2010
dmi.bios.release: 11.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis
