среда

[Bug 2171811] AlsaInfo.txt

apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2171811/+attachment/6011392/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171811 Title: Intel Wireless-AC 9462 Bluetooth (8087:0aaa, ibt-0040-1020) repeatedly crashes with "Hardware error 0x0c" Status in linux package in Ubuntu: New Bug description: The Intel Bluetooth controller on an ASUS Vivobook 14 (X1404VA) crashes repeatedly while a Bluetooth HID device is connected. Each crash logs "Bluetooth: hci0: Hardware error 0x0c" followed by "Exception info". The connected mouse/keyboard disconnects and reconnects a second or two later, which can happen every few seconds. Sometimes the controller stops responding entirely and the kernel resets it: Bluetooth: hci0: Opcode 0x2042 failed: -110 Bluetooth: hci0: command 0x2042 tx timeout Bluetooth: hci0: Initiating acpi reset method Bluetooth: hci0: Reset after hardware error failed (-19) After that, the controller comes back as hci1 and loads its firmware again. Steps to reproduce: 1. Pair and connect a Bluetooth mouse (reproduced with a Logitech MX Master 3S and a Logi M196; also a Logitech MX Mechanical keyboard). 2. Use the computer normally. 3. Watch: journalctl -k -f | grep -i bluetooth Expected: the Bluetooth connection stays stable. Actual: "Hardware error 0x0c" appears anywhere from every few seconds to every few minutes, and the HID devices reconnect after each error. Observations: - Reproduced on kernels 7.0.0-14, 7.0.0-15 and 7.0.0-38-generic (crashes since April 2026), so it does not look like a regression from one kernel update. - Happens only while a Bluetooth HID device is connected, with different mice from different product lines. The frequency varies a lot: some multi-day sessions had no errors. - Persists after a full power-off and cold boot. - Wi-Fi is connected on 5 GHz (channel 161), so 2.4 GHz Wi-Fi/Bluetooth coexistence seems unlikely to be the cause. iwlwifi bt_coex_active is at its default (Y). - Bluetooth USB autosuspend is not active (power/control = on). System: - Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic (7.0.0-38.38) - ASUSTeK Vivobook X1404VA, BIOS X1404VA.313 (07/22/2025) - Wi-Fi: Intel Wireless-AC 9462 (CNVi, PCI 8086:51f1), Raptor Lake PCH - Bluetooth: USB 8087:0aaa, firmware intel/ibt-0040-1020.sfi, firmware version 151-5.24 (timestamp 2024.5, build 151) - linux-firmware 20260319.git217ca6e4.1ubuntu - BlueZ 5.85 --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: junior 3443 F.... wireplumber /dev/snd/seq: junior 3438 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-04-28 (176 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 2b7e:b868 Sonix Technology Co., Ltd. ASUS HD webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X1404VA_X1404VA Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: Upgraded to resolute on 2026-04-28 (176 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sudo uinput users _MarkForUpload: True dmi.bios.date: 07/22/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X1404VA.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X1404VA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX1404VA.313:bd07/22/2025:br5.27:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX1404VA_X1404VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX1404VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobook: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop X1404VA_X1404VA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171811/+subscriptions

Комментариев нет:

Отправить комментарий