Public bug reported: ASUS ExpertBook P3 PM3606CHA Ubuntu 26.04 Kernel: 7.0.0-31-generic Audio codec: Realtek ALC256 Vendor ID: 0x10ec0256 Subsystem ID: 0x10433501 Symptoms: - Internal speakers produce no sound. - 3.5 mm headphones also produce no sound. - PipeWire detects Ryzen HD Audio Controller Speaker normally. - ALSA exposes ALC256 Analog playback device. - speaker-test runs normally but produces no audible sound. - Headphone jack detection does not work: pin 0x21 GET_PIN_SENSE returns 0x0 both unplugged and plugged. - Speaker pin 0x14 has PIN_WIDGET_CONTROL=0x40. - EAPD on pin 0x14 is already 0x02. - Manually enabling codec GPIO2 (mask/direction/data = 0x04) does not restore speaker audio. - No CS35L41/TAS2781/etc external amplifier is detected by ACPI. dmesg: ALC256: picked fixup (pin match) autoconfig for ALC256: line_outs=1 (0x14) type:speaker hp_outs=1 (0x21) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 09:46:56 2026 InstallationDate: Installed on 2026-09-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK PM3606CHA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=7b60115e-0170-41c8-8f2f-181cb8f8c35d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 3.4 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: PM3606CHA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: PM3606CHA 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.ec.firmware.release: 3.21 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrPM3606CHA.304:bd03/20/2026:br3.4:efr3.21:svnASUS:pnASUSEXPERTBOOKPM3606CHA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnPM3606CHA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK PM3606CHA dmi.product.version: 1.0 dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167288 Title: No internal speaker or 3.5mm headphone audio on ASUS ExpertBook PM3606CHA - Realtek ALC256 subsystem 1043:3501 Status in linux package in Ubuntu: New Bug description: ASUS ExpertBook P3 PM3606CHA Ubuntu 26.04 Kernel: 7.0.0-31-generic Audio codec: Realtek ALC256 Vendor ID: 0x10ec0256 Subsystem ID: 0x10433501 Symptoms: - Internal speakers produce no sound. - 3.5 mm headphones also produce no sound. - PipeWire detects Ryzen HD Audio Controller Speaker normally. - ALSA exposes ALC256 Analog playback device. - speaker-test runs normally but produces no audible sound. - Headphone jack detection does not work: pin 0x21 GET_PIN_SENSE returns 0x0 both unplugged and plugged. - Speaker pin 0x14 has PIN_WIDGET_CONTROL=0x40. - EAPD on pin 0x14 is already 0x02. - Manually enabling codec GPIO2 (mask/direction/data = 0x04) does not restore speaker audio. - No CS35L41/TAS2781/etc external amplifier is detected by ACPI. dmesg: ALC256: picked fixup (pin match) autoconfig for ALC256: line_outs=1 (0x14) type:speaker hp_outs=1 (0x21) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 09:46:56 2026 InstallationDate: Installed on 2026-09-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK PM3606CHA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=7b60115e-0170-41c8-8f2f-181cb8f8c35d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 3.4 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: PM3606CHA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: PM3606CHA 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.ec.firmware.release: 3.21 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrPM3606CHA.304:bd03/20/2026:br3.4:efr3.21:svnASUS:pnASUSEXPERTBOOKPM3606CHA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnPM3606CHA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK PM3606CHA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167288/+subscriptions
понедельник
[Bug 2142087] Re: simpledrm fails to hand off /dev/dri/card0 to amdgpu on Picasso/Raven2, causing GDM crash and black screen
I have another reproduction of this issue on an HP laptop with AMD Picasso/Raven2 graphics. Hardware: * HP 15s-eq0003nv * Product number: 8RU92EA * Board ID: 86FD * AMD Ryzen 5 3500U * Radeon Vega / Picasso / Raven2 * Kubuntu * Kernel 7.0.0-30 and 7.0.0-31 * BIOS F.79, dated 2026-04-16 After the BIOS update to F.79, normal Linux graphics boot began failing with a black screen and a flashing/reappearing mouse cursor. The failed boot showed: simpledrm initialized on DRM minor 0 Then AMDGPU initialized on minor 1: "amdgpu 0000:04:00.0: initializing kernel modesetting (RAVEN 0x1002:0x15D8 0x103C:0x86FD 0xC2)" "[drm] Initialized amdgpu 3.64.0 for 0000:04:00.0 on minor 1" KWin then failed with: "kwin_wayland_drm: Atomic modeset test failed! No such device" "KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: No such device" "kwin_core: Failed to open /dev/dri/renderD128 device (No such device)" "kwin_wayland_drm: Primary gpu has been removed! Quitting..." I tested both kernels, X11 vs Wayland, blacklisting hp_wmi, and adding amdgpu to the initramfs. None fixed normal KMS boot. The decisive test was: initcall_blacklist=simpledrm_platform_driver_init without nomodeset. That immediately fixed the graphical boot. I then made it permanent with: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash initcall_blacklist=simpledrm_platform_driver_init" After rebooting, including into kernel 7.0.0-31, the system boots normally. Before the workaround, the problematic boot had simpledrm as DRM card0/minor 0 and amdgpu as card1/minor 1. After the workaround, the system has the working amdgpu card0 and renderD128. This looks like another hardware reproduction of the Picasso/Raven2 simpledrm/amdgpu handoff problem. The exact workaround from this report also fixed my machine. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142087 Title: simpledrm fails to hand off /dev/dri/card0 to amdgpu on Picasso/Raven2, causing GDM crash and black screen Status in linux package in Ubuntu: New Bug description: Affects: Ubuntu 24.04.3 LTS, Kernel 6.17.0-14-generic Hardware: AMD Picasso/Raven 2 [Radeon Vega Series] [1002:15d8] Description: On AMD Picasso/Raven2 APUs, the simpledrm framebuffer driver initializes during early boot and claims /dev/dri/card0. When the amdgpu driver loads ~16 seconds later, simpledrm fails to properly hand off the device. This forces amdgpu to register as /dev/dri/card1 instead. GDM/GNOME Shell expects the primary GPU at card0. When it finds simpledrm there (which cannot do hardware-accelerated rendering), it crashes with: Failed to ensure KMS FB ID on /dev/dri/card0: drmModeAddFB failed: No such device GDM automatically retries and eventually discovers card1 (the real amdgpu), but this causes: Login screen crash on first attempt Black screen with cursor for ~5-10 seconds Random boot failures requiring multiple reboots Steps to Reproduce: Boot Ubuntu 24.04.3 with kernel 6.17.0-14 on AMD Picasso/Raven2 hardware Observe black screen after UEFI logo Check ls -la /dev/dri/ from TTY2 → shows only card1 Check dmesg → simpledrm on minor 0, amdgpu on minor 1 Expected: amdgpu should claim /dev/dri/card0, GDM should start cleanly Actual: simpledrm blocks card0, amdgpu gets card1, GDM crashes and retries Workaround: Add to /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="... initcall_blacklist=simpledrm_platform_driver_init" Then sudo update-grub and reboot. This prevents simpledrm from loading, allowing amdgpu to properly claim card0. Attachments: bug-card1-proof.txt (shows card1 without workaround) bug-dmesg-card1.txt (kernel logs showing simpledrm/amdgpu conflict) bug-gnome-crash.txt (GDM crash and retry sequence) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142087/+subscriptions
Re: [Bug 2165859] Re: Infinite connect/disconnect loop with JBL Flip Essential 2
"A short video is attached". Hi, Thanks for the explanation and the reassurance! I understand that the risk is low, but since this is my primary work machine, I came up with a safer workaround to test this for you. I did an experiment: I used VMware Workstation to pass my laptop's physical Bluetooth controller directly to a Windows 10 Virtual Machine (via USB passthrough). Inside the Windows guest, the JBL speaker connected and worked flawlessly. This confirms it's strictly a Linux driver/BlueZ issue and the hardware is fine. My proposal: I will create a fresh Kubuntu VM, pass the Bluetooth hardware directly to it just like I did with Windows, and install the v7.3-rc1 mainline kernel *inside* that guest VM. This will give the RC kernel direct access to the hardware while keeping my host safe. I've also attached a short 10-second video showing the exact connect/disconnect loop behavior on the host for better context. Does this VM testing method work for you? If so, I will proceed with the RC kernel test and report back the results! If so, please let me know what I should install from scratch in VMware—specifically, which system version already includes the kernel with the fix? Best regards On Wed, Sep 9, 2026 at 9:05 PM Benjamin Wheeler <2165859@bugs.launchpad.net> wrote: > Hey Tiago, > Just so you know, RC kernels don't pose a high risk to install > temporarily. Even if is causes other bugs, you can always shut down the > machine and boot into the previous stable release kernel via your > bootloader. I hope that eases your worries a bit :-) Since this an issue > with specific hardware that I don't own, the best I can do is see if newer > versions of the kernel solve your issue. > > Another option could be, if you have a secondary machine, testing it on > that one, with the current kernel and the RC kernel. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2165859 > > Title: > Infinite connect/disconnect loop with JBL Flip Essential 2 > > Status in bluez package in Ubuntu: > New > Status in linux package in Ubuntu: > New > Status in linux-firmware-intel-wireless package in Ubuntu: > New > > Bug description: > Issue: Pairs successfully, but audio stutters/cuts. After 5 to 15 > seconds, it disconnects and enters an infinite connect/disconnect > loop. > > Troubleshooting done: Tested forcing ControllerMode = bredr, wiping > /var/lib/bluetooth/*, and disabling Wi-Fi to rule out coexistence > issues. Bug persists. > > Important Context: Other Bluetooth headphones (JBL Tune) work > perfectly on this machine. The exact same JBL Flip worked fine on this > laptop (Dell Inspiron 3442) when running Windows. > > wi-fi adapter : WiFi card Intel 7260HMW dual band wireless AC 7260 > model 7260WMH > > ProblemType: Bug > DistroRelease: Ubuntu 26.04 > Package: bluez 5.85-4ubuntu0.1 > ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 > Uname: Linux 7.0.0-30-generic x86_64 > ApportVersion: 2.34.1-0ubuntu0.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: KDE > Date: Sun Aug 30 22:01:34 2026 > InstallationDate: Installed on 2026-06-19 (73 days ago) > InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 > (20260423) > InterestingModules: rfcomm bnep btusb bluetooth > MachineType: Dell Inc. Inspiron 3442 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic > root=UUID=8a3bf956-d00f-4316-846a-5cd949643d6b ro > cryptdevice=UUID=2982648c-dcfb-4627-8569-f1e0ab6a495b:luks-2982648c-dcfb-4627-8569-f1e0ab6a495b > root=/dev/mapper/luks-2982648c-dcfb-4627-8569-f1e0ab6a495b splash > SourcePackage: bluez > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/02/2020 > dmi.bios.release: 65.16 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A16 > dmi.board.name: 0P8H6J > dmi.board.vendor: Dell Inc. > dmi.board.version: A16 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Not Specified > dmi.modalias: > dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:pfa: > dmi.product.name: Inspiron 3442 > dmi.product.sku: 0651 > dmi.product.version: Not Specified > dmi.sys.vendor: Dell Inc. > hciconfig: > hci0: Type: Primary Bus: USB > BD Address: 48:51:B7:15:CE:1B ACL MTU: 1021:5 SCO MTU: 96:6 > UP RUNNING PSCAN INQUIRY > RX bytes:2819 acl:37 sco:0 events:183 errors:0 > TX bytes:7301 acl:41 sco:0 commands:123 errors:0 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2165859/+subscriptions > > ** Attachment added: "blue-win10.png" https://bugs.launchpad.net/bugs/2165859/+attachment/6000291/+files/blue-win10.png ** Attachment added: "20260915_003026 (video-converter.com).mp4" https://bugs.launchpad.net/bugs/2165859/+attachment/6000292/+files/20260915_003026%20%28video-converter.com%29.mp4 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165859 Title: Infinite connect/disconnect loop with JBL Flip Essential 2 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-firmware-intel-wireless package in Ubuntu: New Bug description: Issue: Pairs successfully, but audio stutters/cuts. After 5 to 15 seconds, it disconnects and enters an infinite connect/disconnect loop. Troubleshooting done: Tested forcing ControllerMode = bredr, wiping /var/lib/bluetooth/*, and disabling Wi-Fi to rule out coexistence issues. Bug persists. Important Context: Other Bluetooth headphones (JBL Tune) work perfectly on this machine. The exact same JBL Flip worked fine on this laptop (Dell Inspiron 3442) when running Windows. wi-fi adapter : WiFi card Intel 7260HMW dual band wireless AC 7260 model 7260WMH ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: bluez 5.85-4ubuntu0.1 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Aug 30 22:01:34 2026 InstallationDate: Installed on 2026-06-19 (73 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3442 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=UUID=8a3bf956-d00f-4316-846a-5cd949643d6b ro cryptdevice=UUID=2982648c-dcfb-4627-8569-f1e0ab6a495b:luks-2982648c-dcfb-4627-8569-f1e0ab6a495b root=/dev/mapper/luks-2982648c-dcfb-4627-8569-f1e0ab6a495b splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2020 dmi.bios.release: 65.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0P8H6J dmi.board.vendor: Dell Inc. dmi.board.version: A16 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:pfa: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 48:51:B7:15:CE:1B ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN INQUIRY RX bytes:2819 acl:37 sco:0 events:183 errors:0 TX bytes:7301 acl:41 sco:0 commands:123 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2165859/+subscriptions
[Bug 2167217] Re: 26.10 Snapdragon X Elite: Sync concept kernel changes
** Description changed: [ Summary ] Like in the previous cycle we have worked on improving Snapdragon X Elite support in our ~ubuntu-concept project and found a bunch of quality of life improvements and bug fixes that we would like to get into 26.10. We dropped a bunch of patches between 7.0 and 7.3 that I'd like to add back. Notable additions: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver: https://lore.kernel.org/all/20260903-x1e-csi2-phy-v17-0-26606fa9a039@linaro.org/ + Add dt-bindings and PHY updates for CAMSS on x1e80100 silicon: https://lore.kernel.org/all/20260708-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v12-0-f8588da41f16@linaro.org/ arm64: dts: qcom: Add x1e/Hamoa camera DTSI: https://lore.kernel.org/all/20260906-x1e-camss-csi2-phy-dtsi-v6-0-067f2ecc4630@linaro.org/ [ Source ] Most patches come from linux-next the linux-arm-msm mailing list, or the Qualcomm enablement tree at http://github.com/linux-msm/laptops-kernel/. [ Regression Potential ] The bulk of the patches modify only x1e* device trees or Qualcomm specific drivers. The chance that any of those would affect other platforms is slim. The patches are generally well tested as they are shipped as part of our Ubuntu Concept images. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167217 Title: 26.10 Snapdragon X Elite: Sync concept kernel changes Status in linux package in Ubuntu: New Bug description: [ Summary ] Like in the previous cycle we have worked on improving Snapdragon X Elite support in our ~ubuntu-concept project and found a bunch of quality of life improvements and bug fixes that we would like to get into 26.10. We dropped a bunch of patches between 7.0 and 7.3 that I'd like to add back. Notable additions: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver: https://lore.kernel.org/all/20260903-x1e-csi2-phy-v17-0-26606fa9a039@linaro.org/ Add dt-bindings and PHY updates for CAMSS on x1e80100 silicon: https://lore.kernel.org/all/20260708-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v12-0-f8588da41f16@linaro.org/ arm64: dts: qcom: Add x1e/Hamoa camera DTSI: https://lore.kernel.org/all/20260906-x1e-camss-csi2-phy-dtsi-v6-0-067f2ecc4630@linaro.org/ [ Source ] Most patches come from linux-next the linux-arm-msm mailing list, or the Qualcomm enablement tree at http://github.com/linux-msm/laptops- kernel/. [ Regression Potential ] The bulk of the patches modify only x1e* device trees or Qualcomm specific drivers. The chance that any of those would affect other platforms is slim. The patches are generally well tested as they are shipped as part of our Ubuntu Concept images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167217/+subscriptions
[Bug 2167273] Re: ipu-bridge `upside_down_sensor_dmi_ids` type confusion
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167273 Title: ipu-bridge `upside_down_sensor_dmi_ids` type confusion Status in linux package in Ubuntu: New Bug description: On the `master-next` branch of https://code.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/resolute as of `740b32353f43e9b00d0350d6fa7b29a6667deabd`, there is a type confusion issue in `drivers/media/pci/intel/ipu-bridge.c` affecting the `driver_data` field. It seems like ubuntu's own `upside_down_match_info` thing wasn't applied to new upstream changes such as 2c10400e4a233200046d023ab2377bc56fd48dea. Reference: https://gitlab.freedesktop.org/pipewire/pipewire/-/work_items/5468 PS: sorry if this is not the right place, but I couldn't find a better one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167273/+subscriptions
[Bug 2167177] Re: Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci
Update: root-caused into two separate issues; both now worked around After further testing I can split this report into two distinct problems. The original symptom (keyboard unresponsive at boot / during setup) was one of them; a suspend/resume symptom I hit later was a different one. Apologies for the initial conflation. Hardware: Apple MacBook8,1 (MacBook Retina 12-inch, Early 2015, Broadwell M-5Y51) OS: Ubuntu 24.04.5, kernel 7.0.0-31-generic (7.0.0-31.31~24.04.1) Drivers: spi_pxa2xx_pci (PCI glue) + applespi SPI controller: 0000:00:15.4 (Wildcat Point-LP Serial IO GSPI #1, 8086:9ce6) Serial IO DMA: 0000:00:15.0 (8086:9ce0) ================================================================ ISSUE 1 - boot-time keyboard/trackpad failure (fixed by forcing PIO) This is the symptom that led me to the "disable DMA for SPI transfers" patch (spi: pxa2xx: disable DMA for ..., PATCH v16 5/7). Cause: an init ordering race. spi_pxa2xx_pci comes up and can select DMA before the DesignWare DMA controller is usable, so SPI transfers to the Apple input controller time out and driver state is left corrupted. Relevant log from a failing boot: kernel: dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels kernel: pxa2xx_spi_pci 0000:00:15.4: Forcing PIO mode (disabling DMA) kernel: input: Apple SPI Keyboard as .../spi1/spi-APP000D:00/input/input4 kernel: applespi spi-APP000D:00: Received corrupted packet (crc mismatch) kernel: applespi spi-APP000D:00: modeswitch done. kernel: input: Apple SPI Touchpad as .../spi1/spi-APP000D:00/input/input5 I previously also saw -110 transfer timeouts and list_add double add list corruption on the SPI message queue. Workaround 1a - patched module (what I applied): An out-of-tree/DKMS build of spi_pxa2xx_pci with DMA disabled for this controller (forcing PIO), installed to /lib/modules//updates/ so it shadows the in-tree module. The patch adds a force_pio module parameter plus a DMI match on "Apple Inc." / "MacBook8,1". Since applying it, all boots reach a working keyboard. Workaround 1b - no patched module required (simpler, worth noting): The SPI driver falls back to PIO if no DMA engine is bound. Blacklisting the Serial IO DMA controller alone is enough to avoid the race: /etc/modprobe.d/blacklist-dw-dmac.conf: blacklist dw_dmac_pci With 0000:00:15.0 unbound, even the stock in-tree spi_pxa2xx_pci uses PIO. This holds even if a kernel update breaks the DKMS build, so I now run both. Neither of these is a real fix. The proper fix would be in-tree: either the upstream patch, or ordering the SPI probe after the DMA controller is ready. ================================================================ ISSUE 2 - keyboard unresponsive after suspend (fixed by switching to s2idle) This is a DIFFERENT failure and is NOT addressed by the PIO patch. Suspend mode in use was deep (S3). On suspend the kernel logs the suspend entry and then nothing further - no "PM: suspend exit", no "Restarting tasks": kernel: PM: suspend entry (deep) <nothing further in this boot> The next boot reports an unclean shutdown, i.e. a forced power-off: systemd-journald: File .../system.journal corrupted or uncleanly shut down, renaming and replacing. So on the deep/S3 path this machine never completes the suspend or resume transaction. The display comes back (login screen appears) but the input controller does not, which is what I was observing as "keyboard unresponsive after wake". Switching to s2idle fixes it. Two full suspend/resume cycles, both clean: kernel: PM: suspend entry (s2idle) kernel: Restarting tasks: Starting kernel: Restarting tasks: Done kernel: PM: suspend exit kernel: PM: suspend entry (s2idle) kernel: Restarting tasks: Starting kernel: Restarting tasks: Done kernel: PM: suspend exit No "Failed to re-enable GPE handler" errors from applespi, and both "Apple SPI Keyboard" and "Apple SPI Touchpad" are present and functional after wake. Applied persistently via the kernel command line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=s2idle" /sys/power/mem_sleep is now [s2idle] deep. ================================================================ SUMMARY The boot-time issue and the post-suspend issue are two separate bugs. The patch referenced in the original report only affects the first. The post-suspend failure looks like a platform/firmware issue with the S3 (deep) suspend path on this Broadwell MacBook8,1, not an applespi bug: the kernel never reaches the applespi resume callbacks at all, so no driver-side fix would have helped. Forcing s2idle is a viable workaround. Suggestion for discussion (not a demand): should the default suspend mode be reconsidered for this platform, e.g. defaulting to s2idle when the DMI identifies Apple MacBook8,1, or blacklisting the deep path? It may affect other Broadwell Apple machines too. I can provide full journal extracts (journalctl -b -2 -k for the deep hang, journalctl -b 0 -k for the working s2idle cycles), lspci -vv -s 00:15.4, dmidecode output, or test patches if useful. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167177 Title: Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci Status in linux package in Ubuntu: New Bug description: On a MacBook8,1 (2016 12" MacBook, Intel Broadwell), the internal SPI keyboard and trackpad intermittently fail to initialize at boot. A restart always resolves the issue. The failure is caused by a race between dw_dmac_pci and pxa2xx_spi_pci module probe order. Symptoms: Intermittent: keyboard and trackpad not detected after boot (no input: Apple SPI Keyboard / input: Apple SPI Touchpad in dmesg) Restart always fixes it No external keyboard required to reproduce (it's a boot-time race) Root Cause: The spi_pxa2xx_pci driver checks for DMA channel availability at probe time. The outcome depends on whether dw_dmac_pci has already registered its channels: Good boot: pxa2xx_spi_pci probes first → "no DMA channels available, using PIO" → works Bad boot: dw_dmac_pci probes first → SPI sees DMA → uses DMA → transfers time out (-110) → driver re-queues a message still linked in the SPI core's list → list corruption (__list_add_valid_or_report warning) → driver is permanently stuck Failed boot log (kernel 7.0.0-31-generic): dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error reading from device: -110 WARNING: lib/list_debug.c:35 at __list_add_valid_or_report+0xc6/0xe0, CPU#3: spi1/455 spi_queued_transfer+0xed/0x110 __spi_async+0xd5/0x160 spi_async+0xd6/0xe0 applespi_send_cmd_msg+0x17d/0x400 [applespi] applespi_msg_complete+0xc5/0x110 [applespi] applespi_async_read_complete+0x5c/0x60 [applespi] spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 Successful boot log (same kernel, same machine): pxa2xx_spi_pci 0000:00:15.4: no DMA channels available, using PIO dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: Received corrupted packet (crc mismatch) applespi spi-APP000D:00: modeswitch done. input: Apple SPI Touchpad as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input5 Upstream Status: The list-corruption bug (re-queueing applespi->wr_m via spi_async() while still linked in SPI core lists) was identified in the sashiko- bot review of the v4/v5 patch series (Shih-Yuan Lee, July 2026, linux- spi mailing list). The same series adds a force_pio module parameter to spi_pxa2xx_pci as a workaround. Workaround (untested, for reference): # /etc/modprobe.d/spi-force-pio.conf options spi_pxa2xx_pci force_pio=1 (Requires the upstream patch to be applied; the parameter does not exist in 7.0.0-31-generic.) System: Ubuntu 24.04.1 LTS Kernel: 7.0.0-31-generic Hardware: MacBook8,1 (Intel Core M, Broadwell) SPI controller: Intel LPSS at 00:15.4 DMA controller: DesignWare at 00:15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167177/+subscriptions
воскресенье
[Bug 2167202] Re: thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails
This supplemental report documents a new spontaneous failure with native PCIe hot-plug enabled. The capture shows a real Thunderbolt/PCIe Link Down, followed by successful link reconnection but failed PCI resource allocation because the AQC113 appeared after the bridge windows had already been assigned. Its BARs remained unassigned and the Atlantic driver could not probe. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus reassigned the bridge resources and restored 10GbE without rebooting for the second time. ** Attachment added: "additional findings" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167202/+attachment/6000017/+files/supplmental-attachment-additional-findings.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167202 Title: thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails Status in linux package in Ubuntu: New Bug description: A bus-powered JHL7440 Thunderbolt enclosure containing an AQC113 spontaneously disconnects on both USB4 ports. The Thunderbolt device reconnects, but its PCI hierarchy is not restored reliably. In one captured recovery the AQC113 appeared after bridge-window allocation, received no BAR resources, and failed probe with error -5. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus resized the bridge windows and restored 10GbE without rebooting. GEEKOM A7 Max, BIOS 1.26 Ubuntu and 7.0.0-31-generic Wavlink WL-NWU342G, JHL7440, NVM 69.84 AQC113 firmware 1.5.48 Both USB4 ports affected ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 13 16:17:22 2026 InstallationDate: Installed on 2026-08-15 (29 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: GEEKOM A7 Max ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash pcie_aspm.policy=performance iommu=pt pci=nocrs pcie_port_pm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 09/15/2025 dmi.bios.release: 1.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.26 dmi.board.asset.tag: Default string dmi.board.name: A7 Max dmi.board.vendor: Default string 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.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.26:bd09/15/2025:br1.26:efr1.3:svnGEEKOM:pnA7Max:pvrDefaultstring:rvnDefaultstring:rnA7Max:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuGEEKOMA7Max:pfaA...MaxSeries: dmi.product.family: A...Max Series dmi.product.name: A7 Max dmi.product.sku: GEEKOM A7 Max dmi.product.version: Default string dmi.sys.vendor: GEEKOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167202/+subscriptions
[Bug 2167190] Re: [amdgpu][Navi 31] Reboot hangs on HWE 7.0; 6.17 works; blocking amdgpu avoids hang
The output for your command is: linux-firmware: Installed: 20240318.git3b128b60.0ubuntu3.1 Candidate: 20240318.git3b128b60.0ubuntu3.1 Version table: *** 20240318.git3b128b60.0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble-updates/main i386 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2.26 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167190 Title: [amdgpu][Navi 31] Reboot hangs on HWE 7.0; 6.17 works; blocking amdgpu avoids hang Status in linux package in Ubuntu: New Bug description: # Probable AMDGPU-related reboot regression on Ubuntu HWE 7.0 Prepared locally on 2026-09-13. Tested on Linux Mint 22.3 using Ubuntu-provided kernels. This has not yet been reproduced on an Ubuntu installation. ## Summary On Linux Mint 22.3 (Ubuntu 24.04 base), restarting with Ubuntu HWE kernel 7.0 can leave the screen off and fans running/ramping, requiring a power-button reset. Kernel 6.17.0-40 has restarted successfully with graphics enabled and is the current workaround. Normal power-off and restart directly from BIOS have also worked. The strongest comparison is between two text-mode boots of the same 7.0.0-31 kernel: reboot hung with Intel graphics blocked and AMDGPU initialized; reboot succeeded after additionally blocking AMDGPU. This strongly implicates the AMDGPU initialization/shutdown path or its interaction with other kernel components. It does not establish the exact defective function or commit. A malformed earlier blacklist test reportedly restarted with Intel still loaded, so intermittency remains possible. ## Environment - Linux Mint 22.3, Ubuntu noble base, x86_64. - Working installed kernel: 6.17.0-40-generic, package 6.17.0-40.40~24.04.1. - Failing kernel: 7.0.0-31-generic, package 7.0.0-31.31~24.04.1, upstream version reported as 7.0.14. - Also reported failing: 7.0.0-28 and 7.0.0-30. - Discrete GPU: AMD Navi 31, PCI ID 1002:744c, ASRock subsystem 1849:5308. PCI naming covers RX 7900 XT/XTX variants; exact retail model not established here. - Integrated GPU: Intel Alder Lake-S GT1, PCI ID 8086:4680, i915 driver under normal operation. - Motherboard: MSI PRO Z690-A WIFI (MS-7D25). - BIOS: A.D0, dated 2023-07-10. ## Tests and evidence | Test | Boot configuration | Reported result | | --- | --- | --- | | Installed 6.17.0-40 | Normal graphical boot | Reboot worked | | Mint live USB, 6.14.0-37 | Live desktop | Reboot worked | | 7.0.0-31 | Normal desktop | Reboot hung | | 7.0.0-31 | `systemd.unit=multi-user.target` | Reboot hung; LightDM did not start | | 7.0.0-31 | `systemd.unit=multi-user.target nomodeset` | Reboot worked | | Test B, 7.0.0-31 | `systemd.unit=multi-user.target module_blacklist=i915,xe` | Latest test hung | | Test C, 7.0.0-31 | `systemd.unit=multi-user.target module_blacklist=i915,xe,amdgpu` | Reboot worked | Test B on September 13 at 10:26 CDT recorded: ```text Module i915 is blacklisted Module xe is blacklisted [drm] Initialized amdgpu 3.64.0 for 0000:03:00.0 on minor 1 ``` Test C on September 13 at 10:33 CDT recorded: ```text Module i915 is blacklisted Module xe is blacklisted Module amdgpu is blacklisted ``` The preserved journal reaches the final systemd shutdown stage and stops when journald terminates. No preserved stack trace identifies the hang. Reaching reboot.target or seeing Journal stopped alone does not prove a reboot succeeded; success/failure outcomes above come from the user's physical observations. Earlier 7.0 boots logged AMD display REG_WAIT timeouts, but those messages alone do not establish the cause. A temporary EFI reset- method test also hung. Current measurements taken during normal operation did not show overheating; temperatures during the actual hang were not captured. ## Current workaround GRUB defaults to 6.17.0-40-generic with normal graphics drivers enabled. The kernel image and module packages are marked manually installed. Kernel updates remain enabled, but newly installed kernels will not automatically replace this explicit default. Local configuration: - `/etc/default/grub.d/99-working-kernel.cfg`: working default and five-second menu. - `/etc/grub.d/42_reboot_diagnostics`: optional tests A, B, C. Do not use the all-GPU blacklist or nomodeset as the normal daily boot configuration if GPU acceleration is required. ## Suggested maintainer follow-up Review as an AMDGPU-related regression between 6.17 and 7.0. Identify a relevant fixed distribution kernel or request targeted late-shutdown traces. Repeat the B/C comparison if needed because the failure may be intermittent. Further isolation should be based on maintainer guidance rather than changing unrelated BIOS settings or disabling broad power- management features. Related reports found during research involve other AMD hardware and do not establish that the same defect or fix applies here. No specific published fix was verified for this machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167190/+subscriptions
[Bug 2167076] Re: Automatic screen rotation does not apply despite valid IIO accelerometer events
** Package changed: mutter (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167076 Title: Automatic screen rotation does not apply despite valid IIO accelerometer events Status in linux package in Ubuntu: New Bug description: Surface Go 2 on Ubuntu 26.04 Resolute, Wayland. Automatic rotation is enabled: org.gnome.settings-daemon.peripherals.touchscreen orientation-lock = false Mutter reports: PanelOrientationManaged = true HasExternalMonitor = false Display transform remains normal (0). iio-sensor-proxy 3.8 reports HasAccelerometer=true and emits normal, right-up, and left-up orientation changes through monitor-sensor. Restarting the GNOME session did not restore automatic display rotation. Versions: mutter 50.1-0ubuntu2.2 gnome-shell 50.1-0ubuntu1.2 linux-image-7.0.0-31-generic 7.0.0-31.31 The regression was noticed after moving from 7.0.0-30 to 7.0.0-31. The relevant HID sensor-hub module changed; ISH transport and HID 3D accelerometer modules did not. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 19:23:31 2026 InstallationDate: Installed on 2025-11-04 (311 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: mutter UpgradeStatus: Upgraded to resolute on 2026-08-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167076/+subscriptions
[Bug 2167076] [NEW] Automatic screen rotation does not apply despite valid IIO accelerometer events
You have been subscribed to a public bug: Surface Go 2 on Ubuntu 26.04 Resolute, Wayland. Automatic rotation is enabled: org.gnome.settings-daemon.peripherals.touchscreen orientation-lock = false Mutter reports: PanelOrientationManaged = true HasExternalMonitor = false Display transform remains normal (0). iio-sensor-proxy 3.8 reports HasAccelerometer=true and emits normal, right-up, and left-up orientation changes through monitor-sensor. Restarting the GNOME session did not restore automatic display rotation. Versions: mutter 50.1-0ubuntu2.2 gnome-shell 50.1-0ubuntu1.2 linux-image-7.0.0-31-generic 7.0.0-31.31 The regression was noticed after moving from 7.0.0-30 to 7.0.0-31. The relevant HID sensor-hub module changed; ISH transport and HID 3D accelerometer modules did not. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 19:23:31 2026 InstallationDate: Installed on 2025-11-04 (311 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: mutter UpgradeStatus: Upgraded to resolute on 2026-08-29 (12 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- Automatic screen rotation does not apply despite valid IIO accelerometer events https://bugs.launchpad.net/bugs/2167076 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2167202] [NEW] thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails
Public bug reported: A bus-powered JHL7440 Thunderbolt enclosure containing an AQC113 spontaneously disconnects on both USB4 ports. The Thunderbolt device reconnects, but its PCI hierarchy is not restored reliably. In one captured recovery the AQC113 appeared after bridge-window allocation, received no BAR resources, and failed probe with error -5. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus resized the bridge windows and restored 10GbE without rebooting. GEEKOM A7 Max, BIOS 1.26 Ubuntu and 7.0.0-31-generic Wavlink WL-NWU342G, JHL7440, NVM 69.84 AQC113 firmware 1.5.48 Both USB4 ports affected ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 13 16:17:22 2026 InstallationDate: Installed on 2026-08-15 (29 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: GEEKOM A7 Max ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash pcie_aspm.policy=performance iommu=pt pci=nocrs pcie_port_pm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 09/15/2025 dmi.bios.release: 1.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.26 dmi.board.asset.tag: Default string dmi.board.name: A7 Max dmi.board.vendor: Default string 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.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.26:bd09/15/2025:br1.26:efr1.3:svnGEEKOM:pnA7Max:pvrDefaultstring:rvnDefaultstring:rnA7Max:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuGEEKOMA7Max:pfaA...MaxSeries: dmi.product.family: A...Max Series dmi.product.name: A7 Max dmi.product.sku: GEEKOM A7 Max dmi.product.version: Default string dmi.sys.vendor: GEEKOM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute ** Attachment added: "hardware and package versions, topology, spontaneous failure, BAR-allocation failure," https://bugs.launchpad.net/bugs/2167202/+attachment/5999969/+files/ubuntu-thunderbolt-aqc113-bug-report.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167202 Title: thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails Status in linux package in Ubuntu: New Bug description: A bus-powered JHL7440 Thunderbolt enclosure containing an AQC113 spontaneously disconnects on both USB4 ports. The Thunderbolt device reconnects, but its PCI hierarchy is not restored reliably. In one captured recovery the AQC113 appeared after bridge-window allocation, received no BAR resources, and failed probe with error -5. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus resized the bridge windows and restored 10GbE without rebooting. GEEKOM A7 Max, BIOS 1.26 Ubuntu and 7.0.0-31-generic Wavlink WL-NWU342G, JHL7440, NVM 69.84 AQC113 firmware 1.5.48 Both USB4 ports affected ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 13 16:17:22 2026 InstallationDate: Installed on 2026-08-15 (29 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: GEEKOM A7 Max ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash pcie_aspm.policy=performance iommu=pt pci=nocrs pcie_port_pm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 09/15/2025 dmi.bios.release: 1.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.26 dmi.board.asset.tag: Default string dmi.board.name: A7 Max dmi.board.vendor: Default string 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.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.26:bd09/15/2025:br1.26:efr1.3:svnGEEKOM:pnA7Max:pvrDefaultstring:rvnDefaultstring:rnA7Max:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuGEEKOMA7Max:pfaA...MaxSeries: dmi.product.family: A...Max Series dmi.product.name: A7 Max dmi.product.sku: GEEKOM A7 Max dmi.product.version: Default string dmi.sys.vendor: GEEKOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167202/+subscriptions
[Bug 2167197] Re: Cannot control screen brightness
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167197 Title: Cannot control screen brightness Status in linux package in Ubuntu: New Bug description: Include: HP Spectre X360 Converaible Product# W2Q33AV BIOS F.55 Intel HD Graphics 520 (8086:1916). Ubuntu Cinnamon 26.04.1. Kernel versions 7.0.0-30 and 7.0.0-31. /sys/class/backlight/intel_backlight exists. brightnessctl changes 234/937 to 796/937. The hardware panel’s brightness does not change. nomodeset removal successfully enabled i915 but did not restore functional backlight control. I worked this situation using Perplexity and ended up here. The keyboard does change the OSD value but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: max 2042 F.... wireplumber /dev/snd/seq: max 2038 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Sun Sep 13 13:52:54 2026 InstallationDate: Installed on 2026-04-25 (141 days ago) InstallationMedia: Ubuntu-Cinnamon 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: HP HP Spectre x360 Convertible 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=/boot/vmlinuz-7.0.0-31-generic root=UUID=048998cb-c0da-42a1-acfa-55e74d7e24c9 ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2020 dmi.bios.release: 15.55 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.55 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.79 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.79 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.55:bd06/29/2020:br15.55:efr33.79:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.79:cvnHP:ct31:cvrChassisVersion:skuW2Q33AV:pfa103C_5335KVG=NL=CONB=HPS=SPT: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: W2Q33AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167197/+subscriptions
суббота
[Bug 2152056] Re: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152056 Title: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152056/+subscriptions