[РЕШЕНО] Ошибка № ...

среда

[Bug 2172915] Re: HDMI output on Intel Iris Plus G1 (Ice Lake) with NVIDIA MX130 hangs system and shows “No signal” on kernel 7.0.0-42 (Ubuntu 26.04.1)

** 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/2172915 Title: HDMI output on Intel Iris Plus G1 (Ice Lake) with NVIDIA MX130 hangs system and shows “No signal” on kernel 7.0.0-42 (Ubuntu 26.04.1) Status in linux package in Ubuntu: New Bug description: Hardware: HP Laptop 15-dw2xxx (product number 2T772EA, BIOS F.01, Insyde), Intel Core i5-1035G1, Intel Iris Plus Graphics G1 (Ice Lake, PCI 00:02.0), NVIDIA GeForce MX130 (GM108M, PCI 01:00.0). Software: Ubuntu 26.04.1 LTS, kernel 7.0.0-42-generic (also reproduced with 7.0.0-38-generic), NVIDIA driver 580.178.04 when installed. Problem: when an external monitor is connected to the laptop’s HDMI port while the desktop is running, the internal screen goes black, the external monitor reports “No signal detected”, and the system freezes completely (in some cases the Caps Lock LED blinks). A forced power- off is required. Booting without the cable works normally. The HDMI ports (card1-HDMI-A-1 and card1-HDMI-A-2) are attached to the Intel GPU (0000:00:02.0) according to /sys/class/drm. Working comparison: the same cable and monitor work with Windows on another laptop. Ubuntu 23.04 Live from USB (kernel 6.2.0-20-generic) also works with the same hardware, with the external monitor showing the image correctly. In that session the Intel GPU uses the i915 driver and the NVIDIA GPU uses nouveau. Things already tried without success: kernel parameters i915.enable_psr=0 and i915.enable_dc=0 (confirmed active via /proc/cmdline), nvidia-drm.modeset=0, booting the older 7.0.0-38 kernel, and updating all pending packages. Log excerpts from the failed boot (journalctl -b -1 -k), relevant lines: “ACPI BIOS Error (bug): Attempt to CreateField of length zero” and “ACPI Error: Aborting method _SB.WMID.WQBC ...” followed by “hp_bioscfg: Returned error 0x3004”, with no kernel error recorded at the moment of the freeze. The log ends at 12:34:59 with a Wi-Fi warning, which suggests the freeze happens with no log output. I can attach the full output of journalctl -b -1 -k and lspci -k on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172915/+subscriptions

[Bug 2172971] Re: Hotplug doesnt work as expected

** 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/2172971 Title: Hotplug doesnt work as expected Status in linux package in Ubuntu: New Bug description: Hotplugging as is or after adding grub parameter "intel_iommu=on" hotplug on drives stops working - unplugging works fine, the devices disappear without issue but when I hot plug them in, they do not always reappear back. Rebooting the machine restores the drives. Removing "intel_iommu=on" or using "intel_iommu=off" fixes the issue. In BIOS Hotplug and VMD were enabled. Since adding "intel_iommu=on" in grub has no effect, I assume it is on by default. Doing hotplug few times (even with wait time between the plugs) will cause the OS to hang completely requiring force reset. Another workaround is to add "iommu=pt". ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: user 34901 F.... pipewire CasperMD5CheckResult: pass Date: Wed Nov 4 15:56:24 2026 InstallationDate: Installed on 2026-11-04 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Intel Corporation BeechnutCity ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=f738f84f-7ae7-49c5-97e0-dab197e7a2bc ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2024 dmi.bios.vendor: Intel Corporation dmi.bios.version: BHSDREL1.IPC.0034.D65.2407302228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BeechnutCity dmi.board.vendor: Intel Corporation dmi.board.version: 0.02 dmi.chassis.asset.tag: .................... dmi.chassis.type: 23 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: ............ dmi.modalias: dmi:bvnIntelCorporation:bvrBHSDREL1.IPC.0034.D65.2407302228:bd07/30/2024:svnIntelCorporation:pnBeechnutCity:pvr....................:rvnIntelCorporation:rnBeechnutCity:rvr0.02:cvnIntelCorporation:ct23:cvr............:skuSKUNumber:pfaFamily: dmi.product.family: Family dmi.product.name: BeechnutCity dmi.product.sku: SKU Number dmi.product.version: .................... dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172971/+subscriptions

[Bug 2173009] Re: Resolute update: upstream stable patchset 2026-11-02

** 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/2173009 Title: Resolute update: upstream stable patchset 2026-11-02 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2026-11-02 Ported from the following upstream stable releases: v6.18.59, v7.2.13 from git://git.kernel.org/ ALSA: ctxfi: Rename SPDIFI1 to SPDIFI_BAY ALSA: ctxfi: Use correct DAIO type for da_desc ax25: bound REJ-driven fast retransmits with the existing N2 counter rose: purge rose_neigh->queue on final teardown i2c: qcom-geni: Restore the source-clock selection policy soc/tegra: fuse: Add missing newline to APBMISC error message ARM: dts: ti/omap: dra7: fix PCIe PHY clock divider definition power: supply: Fix maintenance charge table kernel-doc power: supply: ds2780: Fix ds2780_get_capacity() returning raw value Drivers: hv: Avoid infinite retry loop in init_vp_index() x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() Drivers: hv: Don't reset VMBus connection state on error/exit paths pinctrl: qcom: qcs8300: Fix intr_target_width pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 tools/power turbostat: Fix fd_perf leak on reset tools/power turbostat: Fix CWF PMT off-by-one tools/power turbostat: Fix PMT error path fd handling tools/power turbostat: Fix add_counter issue if > 24 counters. power: supply: generic-adc-battery: Fix temperature IIO channel conversion power: supply: core: prevent unregistering a power supply while a callback runs pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 pinctrl: sunxi: dt: do not accumulate npins across probe attempts drm/vc4: hdmi: Move packet RAM enable to PM runtime gpio: nct6694: Mark the GPIO controller as sleeping vsock: treat TCP_CLOSING as once-established net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure ASoC: Intel: avs: Reset the stream unless it is already prepared ASoC: stm32: spdifrx: fix synchronization state check ASoC: cs42l56: Put the Limiter Cushion control on the limiter register ASoC: cs42l52: Fix the NG Type Switch bit ASoC: pcm3168a: Fix the DAC zero flag polarity bit ASoC: max98371: Fix the Speaker DHT Min Volume bits ASoC: wm8978: Fix the 128x oversampling switch bits ASoC: nau8822: Fix the 128x oversampling switch bits regmap: Drop map lock during cache init and exit netlink: reset skb headers before unicast and multicast filtering accel/rocket: clear rdev on device init failure net/mlx5: HWS, release L2 to L3 tunnel reformats to their own pool net/mlx5: HWS, fix flow meter offset within its bulk ASoC: amd: yc: disable MSI on resume drm/xe: skip eviction of a BO with no resource drm/xe/oa: Zero OA buffer at allocation spi: tegra114: assert CS GPIO for every transfer in a message nios2: fix __wsum type degradation in csum_fold() scsi: st: Save the visited block for the partition the drive is in scsi: target: iscsi: Fix race in discovery auth updates drm/panthor: fix immortalis condition ocfs2/dlm: Protect the recovery list during debugfs reads samples: pidfd: fix userprogs typo pipe: preserve existing fasync readers on writer setup failure tracing: probes: error if BTF is required but unavailable scsi: libsas: Fix SMP IO deadlock during HA resume netlink: avoid hashing the network namespace pointer net: bcmgenet: unshare the skb before writing the control block calipso: keep BIG TCP payload_len in calipso_skbuff_setattr() gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths gpio: mxc: fix race between chained IRQ handler install and probe completion gpio: mxc: fix both_edges bit operations gpio: mxc: use BIT() macro gpio: mxc: fix wakeup_pads bit operations gpio: mxc: fix race between gpiochip registration and IRQ domain setup perf: Fix perf_pmu_migrate_context() leaving events behind printk: Postpone kthread startup PCI: Don't treat ~0 as ready in pci_dev_wait() with RRS SV accel/rocket: search every core slot when a core is removed afs: free the super info after a grace period autofs: ignore notification errors from a replaced pipe bootconfig: give the footer size static_assert a message unicode: free the map after a grace period watch_queue: Fix note pool publication race in watch_queue_set_size() x86/kvm: Don't consume async #PF flags on a kernel #PF in NMI context KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry fsnotify: prevent mark additions during connector teardown pid_namespace: make zap_pid_ns_processes() freezable eventfs: Free the eventfs_inode after an rcu grace period too namei: test for a negative dentry the way traverse_mounts() does lib/crypto: arm64: Fix lost Poly1305 carry when resuming NEON state lib/crypto: poly1305: Use memzero_explicit() in poly1305_final() net/sched: fix use-after-free in __tcf_action_put() net: rds: fix uninitialized trans dereference in CM event handler pinctrl: amd: Clear S4 wake bits when firmware has _AEI sctp: revalidate output stream after association connect wait tools: gpio: fix building from the top level with O= tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields i2c: qcom-cci: Fix HALT_ACK reset request being dropped i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe() perf: Track the perf mlock gift separately perf: Update cgroup time when rotating multiplexed events ring-buffer: Do not show buffer_meta for CPUs without a buffer ring-buffer: Fix the sub-buffer array base in rb_meta_subbuf_idx() ring-buffer: Fix false warning in ring_buffer_map_get_reader() scsi: bsg: Pass reply_len to bsg_setup_queue() to fit UFS ARPMB replies scsi: xen/scsifront: Check for a NULL shadow entry on a backend response scsi: libiscsi: Reject a negative task index from parse_pdu_itt scsi: libiscsi: Validate the ITT reflected in a Reject PDU scsi: libiscsi: Validate the task named by a management response drm/amd/pm: add zero fan stop temperature support on smu 14.0.2 drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr drm/amdgpu: report the BO alignment in bytes in GEM_LIST_HANDLES drm/exec: don't immediately add prelocked obj to array of locked objs drm/i915/cx0_phy: Fix ARL-S host bridge detection drm/i915/dmc: Add sanity check for DMC load address drm/xe: Bump LRU for external objects on exec and rebind tracing: Fix the shift out of bounds in the log2 histogram modifier tracing: Take trace_types_lock when dropping the buffer_meta reference tracing: Check operator stack capacity before pushing tracing: Do not initialize tracefs work if tracing is disabled tracing: Fix hist trigger timestamps for buffered events wifi: p54: validate firmware record lengths tcp: fix use-after-free in do_tcp_getsockopt(TCP_CONGESTION) tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO) cgroup: fix spurious SIGKILL of CLONE_INTO_CGROUP children cifs: don't update i_size in cifs_do_truncate without a cached handle dm cache: fix demotion stats in passthrough mode dm cache: fix issue with background work locking dm-crypt: fix a tiny race condition in crypt_dec_pending dm-ebs: fix incorrect device offset check in ebs_ctr() dm-integrity: fix infinite loop on discard with large tag size dm-integrity: require stable writes for internal hash modes mac802154: fix data race and NULL deref on local->assoc_dev net/iucv: fix the recvmsg window update xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf xfs: fix capability check in xfs xfs: fix zoned write iomap flags assignments netlink: specs: fix the conntrack filter type netlink: specs: add missing mask attributes for conntrack dump workqueue: Use raise_softirq() to trigger softirq in irq_work handler workqueue: Annotate cb_lock nesting when draining a dead BH pool tipc: protect node reset trace dump with node lock sctp: validate chunk length in the inqueue parser page_pool: keep frag_offset aligned for odd-sized requests s390/ctcm: Prevent XID null dereference s390/pci: Fix leak of uninitialized kernel data in SCLP report ipv4: avoid divide by zero in fib_rebalance drm/amdgpu: Fix VCE 3 ring align_mask netfilter: nft_byteorder: remove multi-register support KVM: x86/mmu: Preserve nested TDP shadow page tables if they are used as roots KVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes drm/amdgpu: keep the eviction fence until the last handle is closed futex: Fix mm reuse handling for FUT_OFF_MMSHARED ASoC: SOF: ipc4-topology: Fix shift-out-of-bounds for aggregated ALH capture ext4: free the sbi after a grace period net: bridge: mcast: don't truncate the port group walk on teardown net: psp: do not inherit the Rx association on clone ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in net/sched: cls_flower: validate mask pointer after nla_next() smb: client: fix heap overflow in cifs_do_set_acl() smb: client: fix multiuser mount with krb5 scsi: st: Fix use-after-free race between st_remove() and st_open() ntfs3: free the sbi after a grace period drm/i915/dmc: Harden DMC firmware payload parsing sched_ext: idle: Respect task affinity in restricted CPU selection tracing: Fix ignored return value of resize_buffer_duplicate_size() tracing: Keep the predicate limit separate from program capacity drm/amdgpu: free the userptr ranges when a CS fails after parser_bos sched_ext: Fix stall when a task enqueued with SCX_ENQ_LAST lands back on its CPU's local DSQ smb/client: refresh allocation size after duplicate extents cifs: add revalidation on FSCTL failure in smb2_duplicate_extents() io_uring/cancel: don't spin on local work the task can't run workqueue: release pwq pools by pool type workqueue: Fix unbound pool lifetime for pending pwqs vsock/virtio: validate packet source for connected sockets ipv4: udp: Create exceptions before socket matching vsock/vmci: validate packet source for connected sockets smb: client: fix data corruption with concurrent writes and O_TRUNC smb: client: drain outstanding I/O before truncating on O_TRUNC open ARM: configs: sama5: enable current Microchip KSZ DSA symbols pinctrl: qcom: spmi-gpio: make direction changes exclusive tools/power turbostat: Warn, but don't Err on out-dated perf systems accel/amdxdna: Fix Kconfig invalid configuration sched/core: Call wakeup_preempt() for queued tasks during class change iommupt/kunit: Use if_changed_rule for the kunit exit: fix lost-update race on the child_subreaper bitfields ring-buffer: Skip si_mem_available() for persistent and remote buffers ring-buffer: Use subbuf_order in available memory estimation net: stmmac: dwmac1000: clear the RGMII status interrupt perf/x86/intel/uncore: Fix DMR CXL CM invert filter x86/insn-eval: Fix shadowed segment index in get_seg_reg_override_idx() firewire: core: fix race condition in split transaction handling accel/rocket: search every core slot when looking up a scheduler ASoC: SOF: sof-client: Use event-handler mutex consistently ipc: drop the mqueue mount with kern_unmount() on setup failure mshv_vtl: Check per-CPU register page before mmap power: sequencing: qcom-wcn: power off WLAN at probe spi: imx: fix slab corruption from undersized DMA bounce buffers tools/power turbostat: Read complete CPU lists gpio: shared: fix use-after-free bug when adding shared proxies gpio: shared: gracefully handle no-device lookup of shared GPIOs drm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set drm/amdgpu: destroy mutex when tearing down ttm buffer entity drm/amdgpu: fix GEM object leak on ENOMEM in userptr ioctl drm/amdgpu: fix sched entity leak in ttm buffer entity init tracing: Fix crash in print_graph_function_event() selinux: fix BPF token permission checks s390/pai: Handle multiple PMU stop callback invocations drm/amdgpu: correct reservation fence slots for userq per-vm BOs eviction drm/amdgpu/userq: actually validate userq BOs smb: client: reject SetEA requests that do not fit the request buffer drm/amdgpu: Remove the bo list mutex UBUNTU: Upstream stable to v6.18.59, v7.2.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173009/+subscriptions

[Bug 2173012] Re: Resolute update: upstream stable patchset 2026-11-04

[Bug 2169102] Re: [Regression] Window flickering and blanking on Electron/Chromium apps under Wayland with legacy radeon driver (Radeon HD 7670M) on kernel 7.0.0-34-generic

Title: Screen tearing and visual flickering in Electron/Chromium apps (Gemini, Opera, Spotify) on legacy AMD Radeon HD 7670M with Wayland/Xwayland Description: I am experiencing severe visual flickering and screen tearing in web-based and Electron applications (such as Gemini desktop, Opera, and Spotify) on an Ubuntu system running on a laptop with an AMD Radeon HD 7670M discrete GPU combined with an Intel Core i7 processor. Technical Details: Hardware: AMD Radeon HD 7670M (legacy architecture using the free radeon kernel driver) + Intel Core i7. Symptom: UI elements in Electron/Chromium apps flicker constantly or exhibit severe rendering artifacts when hardware acceleration is enabled. Root Cause Analysis: The legacy radeon driver lacks modern explicit synchronization support required by modern compositors and Chromium/Electron rendering pipelines under Wayland/Xwayland environments. Workaround applied: Forcing software rendering via --disable-gpu resolves the visual artifacting by routing rendering tasks to the CPU, but introduces a heavy performance penalty. Steps to Reproduce: Run Ubuntu on a machine equipped with a legacy AMD Radeon HD 7670M GPU. Launch any Electron-based application (e.g., Gemini, Spotify, Opera) with default hardware acceleration. Observe the screen tearing and flickering during window interaction or scrolling. Expected Behavior: Smooth rendering without flickering, or seamless fallback handling for legacy GPUs lacking explicit sync. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169102 Title: [Regression] Window flickering and blanking on Electron/Chromium apps under Wayland with legacy radeon driver (Radeon HD 7670M) on kernel 7.0.0-34-generic Status in linux package in Ubuntu: New Bug description: Problem Description: After updating to kernel 7.0.0-34-generic, specific applications (specifically Chromium/Electron-based apps with hardware acceleration enabled) experience severe window flickering, blanking, and intermittent black screens during redraws. The desktop shell remains responsive, but the client window contents intermittently fail to present or render black frames. Hardware & Environment Information: - Host: Toshiba Satellite S855 - Kernel: 7.0.0-34-generic - Display Server: Wayland (echo $XDG_SESSION_TYPE -> wayland) - GPU: AMD/ATI Thames [Radeon HD 7500M/7600M Series] (Radeon HD 7670M) [1002:6840] (rev ff) - Subsystem: Toshiba Corporation [1179:fb22] - Active Driver: radeon (DRM 2.51.0 / KMS Turks) Relevant dmesg / DRM logs: [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1179:0xFB22 0x00). [drm] Detected VRAM RAM=2048M, BAR=256M [drm] Loading TURKS Microcode radeon 0000:01:00.0: [drm] PCIE GART of 1024M enabled. radeon 0000:01:00.0: [drm] fb0: radeondrmfb frame buffer device Steps to Reproduce: 1. Boot with kernel 7.0.0-34-generic into a default Wayland session. 2. Launch a hardware-accelerated application (e.g., Google Chrome, Gemini PWA/Electron, VS Code). 3. Interact with the window or hover over UI elements. 4. The window content rapidly flickers between the rendered page and solid black. Expected Behavior: Window surfaces should redraw cleanly without buffer flickering or black frames under the legacy radeon KMS driver. Observed Behavior: Window rendering intermittently collapses to a black surface during buffer swaps under Wayland. Regression: This issue was introduced with the recent kernel update. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: daby 4597 F.... wireplumber /dev/snd/controlC1: daby 4597 F.... wireplumber /dev/snd/seq: daby 4581 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 17:17:42 2026 InstallationDate: Installed on 2025-02-25 (583 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) IwDevWlp8s0Link: Not connected. MachineType: TOSHIBA Satellite S855 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-34-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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.release: 6.70 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 6.20 dmi.modalias: dmi:bvnInsydeCorp.:bvr6.70:bd04/15/2013:br6.70:efr6.20:svnTOSHIBA:pnSatelliteS855:pvrPSKFWU-002002:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKFWU:pfaDakar10F/FG: dmi.product.family: Dakar 10F/FG dmi.product.name: Satellite S855 dmi.product.sku: PSKFWU dmi.product.version: PSKFWU-002002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169102/+subscriptions

[Bug 2165407] Re: resolute: llvm-21-dev build-depends breaks cross-builds

** Tags removed: verification-needed-resolute-linux-nvidia ** Tags added: verification-done-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165407 Title: resolute: llvm-21-dev build-depends breaks cross-builds Status in linux package in Ubuntu: New Status in linux-nvidia package in Ubuntu: Invalid Status in linux-nvidia-bos package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Fix Committed Status in linux source package in Resolute: Fix Released Status in linux-nvidia source package in Resolute: Fix Committed Status in linux-nvidia-bos source package in Resolute: Fix Released Status in linux-riscv source package in Resolute: Fix Released Bug description: Commit e66125ce24f6 ("UBUNTU: [Packaging] Add llvm-21-dev to build-depends for perf", LP: #2138328) added llvm-21-dev as an unqualified Build-Depends entry to enable LLVM-accelerated addr2line() in perf. Because llvm-21-dev is not annotated with :native or an architecture restriction, dpkg attempts to satisfy it for the target (cross) architecture during cross-compilation (e.g. arm64 from amd64). Since the llvm-21-dev package is not available for all cross targets or cannot co-install alongside the native toolchain, cross-builds fail to resolve build dependencies. The fix (already applied in stonking as commit 2aebbf625fd4) makes three changes to debian.master/control.stub.in: - Replaces "llvm-21-dev" with "llvm-21-tools:native <!stage1>" so the LLVM dependency is satisfied from the build host architecture. - Adds "libllvm21 <!stage1>" as a separate library dependency. - Adds "libstd-rust-dev" with an explicit architecture list. This needs to be cherry-picked to resolute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165407/+subscriptions

[Bug 2172702] Re: Kernel panic in __run_timers (timer list corruption) when launching Thunderbird on Alder Lake-N, 7.3.0-9 and 7.3.0-10

Can't reproduce on Kubuntu 26.04 in VirtualBox with kernel linux-oem-7.3 7.3.0-1004.4. So I guess something about my (rather radically different than yours) setup dodges the issue. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172702 Title: Kernel panic in __run_timers (timer list corruption) when launching Thunderbird on Alder Lake-N, 7.3.0-9 and 7.3.0-10 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 26.10, kernels 7.3.0-9-generic and 7.3.0-10-generic. Hardware: Teclast laptop (DMI "Teclast Default string", BIOS tPAD3.05 04/10/2024) GPU: Intel Alder Lake-N iGPU (8086:46d2), i915, GuC 70.49.4, GuC submission enabled Wi-Fi: Realtek RTL8821CE (rtw88_8821ce) PROBLEM Launching Thunderbird (snap) causes a kernel panic ("Fatal exception in interrupt") a few seconds later, nearly every time. It also happened once while using Brave (snap). EFI pstore has kept the logs of more than a dozen crashes since 2026-10-13; the 13 I checked all have the same signature. The same symptom continues after updating to 7.3.0-10-generic. STEPS TO REPRODUCE 1. Boot 7.3.0-9-generic or 7.3.0-10-generic. 2. Launch Thunderbird. 3. The system panics within a few seconds. CRASH SIGNATURE (pstore, 7.3.0-9-generic) WARNING: kernel/workqueue.c:2432 at __queue_work+0x422/0x540, CPU#1: gfxtest/5832 delayed_work_timer_fn+0x19/0x30 call_timer_fn+0x30/0x160 __run_timers+0x1c0/0x2b0 run_timer_softirq+0x8a/0x100 handle_softirqs+0xd7/0x340 ... BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor write access in kernel mode Oops: 0002 [#1] SMP NOPTI RIP: 0010:__run_timers+0x1e9/0x2b0 RAX: dead000000000122 RDX: 0000000000000000 R13: ffff8d0243bc2a88 Kernel panic - not syncing: Fatal exception in interrupt Across crashes the oops RIP is __run_timers+0x1e1, +0x1e9 or +0x1f1. In detach_timer() the timer being removed already has entry.next == LIST_POISON2 and entry.pprev == NULL: a timer that was already detached is still linked in the timer wheel. R13 in the oops is exactly 0x20 after RBX in the preceding WARN (ffff8d0243bc2a68), so it appears to be the timer of the same delayed_work. This looks like a delayed_work being freed or re-initialized while still pending (use-after-free). The task running at the time was "gfxtest", a short-lived process that appears to be started by Thunderbird at launch to probe the GPU. That makes i915 a suspect, but it is not confirmed. ALREADY TESTED (crash still happens) - Airplane mode (Wi-Fi off) - options rtw88_pci disable_aspm=1 - LIBGL_ALWAYS_SOFTWARE=1 thunderbird NOT TESTED YET - Booting with nomodeset - An older kernel The full pstore log of the latest crash is attached. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-10-generic 7.3.0-10.10 ProcVersionSignature: Ubuntu 7.3.0-10.10-generic 7.3.0 Uname: Linux 7.3.0-10-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: henry-crisbeth 2984 F.... wireplumber /dev/snd/seq: henry-crisbeth 2980 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:27:35 2026 InstallationDate: Installed on 2025-06-23 (496 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 062a:9013 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 003: ID b349:b181 KYT-240222-A USB Camera Bus 001 Device 004: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Teclast Default string ProcEnviron: LANG=es_ES.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.3.0-10-generic root=UUID=01057e0e-86fe-4455-994c-88065f563a6d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to stonking on 2026-09-29 (33 days ago) dmi.bios.date: 04/10/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: tPAD3.05 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrtPAD3.05:bd04/10/2024:br5.27:svnTeclast:pnDefaultstring:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuF1P2_A1:pfa: dmi.product.name: Default string dmi.product.sku: F1P2_A1 dmi.product.version: Default string dmi.sys.vendor: Teclast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172702/+subscriptions

[Bug 2162917] Re: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios"

Verification for linux-nvidia/6.8.0-1066.69, I ran the reproducer from comment #7 on this kernel. It indicates that this kernel is indeed patched: noble/linux-nvidia 6.8.0-1066-nvidia $ ./gupbench -p 512 -r 5 -i 200 1 8 32 128 page size: 4K, pages/thread: 512, reps: 5, iters: 200 get_user_pages_fast_only() verdict: gupfast (alloc_page+vm_insert_page): 512/512 anon (control) : 512/512 pin_user_pages_fast(FOLL_WRITE) median ns/page: threads gupfast anon 1 29.3 23.0 8 23.3 30.9 32 22.1 21.9 128 21.6 21.6 RESULT: PASS - GUP-fast accepts NULL-mapping order-0 folios (fixed) ** Tags removed: verification-needed-noble-linux-nvidia ** Tags added: verification-done-noble-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162917 Title: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios" Status in linux package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in linux-nvidia-bos package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Fix Committed Status in linux-nvidia-bos source package in Noble: Invalid Status in linux source package in Resolute: Fix Committed Status in linux-nvidia source package in Resolute: Fix Released Status in linux-nvidia-7.0 source package in Resolute: Invalid Status in linux-nvidia-bos source package in Resolute: Fix Released Status in linux source package in Stonking: Fix Released Status in linux-nvidia source package in Stonking: Invalid Status in linux-nvidia-bos source package in Stonking: Invalid Bug description: SRU Justification [Impact] There is a performance regression seen for calls to get_user_pages() on single-page NULL-mapping folios, introduced by commit f002882ca369 ("mm: merge folio_is_secretmem() and folio_fast_pin_allowed() into gup_fast_folio_allowed()"). When either CONFIG_SECRETMEM=y, or when the folio is a long-term writable pin, the current implementation requires that the mapping be checked as either a secretmem mapping or a file-backed one. If it is either, or if the mapping is NULL, the slow path is forced. However, when the mapping is NULL, the folio cannot be a secretmem mapping. Thus, as long as the folio is NOT a long-term writable pin, the fast path can still be used. This performance regression was initially observed during GPU Direct Storage (GDS) workloads. [Fix] The upstream commit c494788faffe ("mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios") resolves the performance regression by changing gup_fast_folio_allowed() to allow the fast path for the case described above, where the folio is NOT a long-term writable pin and its mapping field is NULL. [Test Plan] Build and boot tested. The performance regression and subsequent fix can be verified with a GDS workload. The original bug report also describes a test kernel module that uses the `alloc_page` + `vm_insert_page` + `pin_user_pages_fast(..., FOLL_WRITE, ...)` functions to emulate GDS behavior, and using `get_user_pages_fast_only()` on that to validate that the fast path is now allowed in this scenario. [Where problems could occur] The fix affects the get_user_pages*() path of the mm subsystem, which is used heavily. The fix has been reviewed and applied in upstream Linux. ------------------------------------------------------- Original report: Clean cherry-pick from linux-next: ``` (cherry picked from commit ae75e88d8c258fd849de594e7d468b5263e7b3e3 linux-next) ``` John Hubbard, Acked-by David Hildenbrand, applied by Andrew Morton. [Lore thread](https://lore.kernel.org/all/20260708005745.164928-1-jhubbard@nvidia.com/). ## Problem `f002882ca369` (present on this branch) made `gup_fast_folio_allowed()` bail to the slow path for *any* order-0 folio with a NULL `->mapping` when `CONFIG_SECRETMEM=y`. Pages from `alloc_page()` + `vm_insert_page()` legitimately have a NULL mapping, so every `pin_user_pages_fast()` over such a range misses the fast path — nvidia-fs (GPUDirect Storage) allocates its shadow buffers exactly this way. The NULL check was meant to catch truncated file-backed pages, not secretmem. Secretmem folios are published via `filemap_add_folio()`, which always sets `->mapping`, so a NULL mapping proves the folio is *not* secretmem. Returning `!reject_file_backed` keeps long-term writable pins on the slow path and restores the fast path otherwise — exactly the pre-`f002882ca369` behaviour. `CONFIG_SECRETMEM=y` on amd64 and arm64, so this is live on every flavour we ship. ## Measurement (GH200, 288 cores) A module reproducing the nvidia-fs pattern (`alloc_page` + `vm_insert_page`, then `pin_user_pages_fast(..., FOLL_WRITE, ...)`), with an anonymous-memory control the patch cannot affect. `get_user_pages_fast_only()` gives the GUP-fast verdict directly: **0/N unpatched, N/N patched**. Median ns/page, 512 pages/thread, 5 reps: | threads | 4K unpatched → patched | 64K unpatched → patched | |--------:|-----------------------:|------------------------:| | 1 | 34 → 34 (1.0x) | 33 → 30 (1.1x) | | 8 | 74 → 33 (**2.2x**) | 1920 → 31 (**62x**) | | 32 | 95 → 33 (**2.9x**) | 4792 → 33 (**145x**) | | 128 | 500 → 218 (noisy) | 16673 → 76 (**219x**) | The anon control held at 30-35 ns/page across all four kernels, so only the affected range moved. Stock `7.0.0-1015-nvidia-64k` independently reproduces the unpatched 64K numbers (8 threads: 1176 vs 37), so this isn't a test-config artefact. Single-threaded it's a wash; the win is under concurrency. `perf` on the unpatched 64K kernel shows the slow path is ~90% lock contention (`queued_spin_lock_slowpath` 72%), gone entirely once patched — contention that scales with thread count, not a fixed per-page cost. ## Risk Low. One line in a static function with three callers, all in GUP-fast. Only `reject_file_backed == false && check_secretmem && mapping == NULL` changes behaviour; long-term writable pins are untouched. A secretmem folio caught mid-truncate can't happen here: `secretmem_setattr()` refuses to shrink, there's no `.fallocate` (so no punch-hole), and `secretmem_migrate_folio()` returns `-EBUSY`. Only inode eviction remains, which requires every VMA gone — no VMA, no PTE for GUP-fast to walk. Raised by David Hildenbrand on v1 and resolved before he Acked. ## Testing Applies cleanly; built arm64 4K/64K and x86_64, no new warnings; verified in the binary (unpatched `mov w0, #0x0` vs patched `eor w0, w0, #0x1`); benchmarked as above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162917/+subscriptions

[Bug 2172581] Re: [Regression] amdgpu: horizontal stripe glitches on DisplayPort monitor with RX 9060 XT on 7.0.0-38 (OK on 7.0.0-30)

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/2172581 Title: [Regression] amdgpu: horizontal stripe glitches on DisplayPort monitor with RX 9060 XT on 7.0.0-38 (OK on 7.0.0-30) Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 7.0.0-38.38 was installed (Oct 14, 2026), I get brief display glitches on an AMD Radeon RX 9060 XT. Booting back into 7.0.0-30.30 makes them disappear completely. Mesa (26.0.8-1ubuntu0.3, installed Aug 26) and linux-firmware-amd-graphics (last updated Jul 25) were unchanged between the two kernels. Symptom: A split-second horizontal stripe or flash across the full width of the screen, drawn over all windows. It appears several times a day, typically when: - moving or resizing windows - scrolling - opening applications (e.g. LibreOffice, Teams) - pressing Enter at the SDDM login screen after a cold boot (seen with both a wrong and a correct password; not seen on logout/login without reboot) Which monitor: - In-session glitches appear only on the left monitor. After swapping the primary monitor so applications open on the right one, the glitches stayed on the left monitor regardless of which apps were there. - Moving the left monitor's cable to a different DisplayPort output on the GPU did not change anything. - One login glitch was observed on both monitors at the same moment. System: - Kubuntu 26.04 LTS, KDE Plasma 6.6.6, Frameworks 6.24.0, Qt 6.10.2, Wayland - GPU: AMD Radeon RX 9060 XT 16 GB [1002:7590, subsystem 1458:2429], gfx1200, DCN 4.0.1, VBIOS 113-R906XTGO-F2 - CPU: Ryzen 9 7900X (integrated GPU disabled in BIOS) - Board: MSI B650 GAMING PLUS WIFI (MS-7E26), 32 GB RAM - Monitors (both DisplayPort): - Left: [model, resolution, refresh rate, VRR on/off] - Right: [model, resolution, refresh rate, VRR on/off] - Kernel cmdline extras: amdgpu.gpu_recovery=1 amdgpu.runpm=0 Tried on 7.0.0-38 without effect: - power_dpm_force_performance_level=high (set via udev at boot) - amdgpu.dcdebugmask=0x20000 - Disabling the CPU's integrated GPU - Reseating the cable / changing the GPU port Hardware seems fine: a Unigine Heaven run (OpenGL, 1440p, Ultra, extreme tessellation) showed no hardware-type artifacts, and everything is clean on 7.0.0-30. Possibly related (though not 100% sure), also only on 7.0.0-38: the Android Emulator (37.2.12, hardware graphics) alternates between the current and a stale frame when pulling down its notification shade. This is reliably reproducible, and gone on 7.0.0-30. dmesg at boot on 7.0.0-38 shows: amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc401_disable_crtc line:235 (Not yet checked whether this also appears on 7.0.0-30.) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Oct 30 11:19:08 2026 InstallationDate: Installed on 2025-08-14 (441 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) MachineType: Micro-Star International Co., Ltd. MS-7E26 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-7.0.0-38-generic root=UUID=3502296e-5c13-4e5a-a0d3-1ecd4f4367ad ro rootflags=subvol=@ quiet splash resume=UUID=e059f494-d020-4881-b09c-874773a0d2d8 amdgpu.gpu_recovery=1 amdgpu.runpm=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-24 (158 days ago) dmi.bios.date: 06/19/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.L0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B650 GAMING PLUS WIFI (MS-7E26) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.L0:bd06/19/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E26:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB650GAMINGPLUSWIFI(MS-7E26):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E26 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172581/+subscriptions

[Bug 2172971] [NEW] Hotplug doesnt work as expected

Public bug reported: Hotplugging as is or after adding grub parameter "intel_iommu=on" hotplug on drives stops working - unplugging works fine, the devices disappear without issue but when I hot plug them in, they do not always reappear back. Rebooting the machine restores the drives. Removing "intel_iommu=on" or using "intel_iommu=off" fixes the issue. In BIOS Hotplug and VMD were enabled. Since adding "intel_iommu=on" in grub has no effect, I assume it is on by default. Doing hotplug few times (even with wait time between the plugs) will cause the OS to hang completely requiring force reset. Another workaround is to add "iommu=pt". ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: user 34901 F.... pipewire CasperMD5CheckResult: pass Date: Wed Nov 4 15:56:24 2026 InstallationDate: Installed on 2026-11-04 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Intel Corporation BeechnutCity ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=f738f84f-7ae7-49c5-97e0-dab197e7a2bc ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2024 dmi.bios.vendor: Intel Corporation dmi.bios.version: BHSDREL1.IPC.0034.D65.2407302228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BeechnutCity dmi.board.vendor: Intel Corporation dmi.board.version: 0.02 dmi.chassis.asset.tag: .................... dmi.chassis.type: 23 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: ............ dmi.modalias: dmi:bvnIntelCorporation:bvrBHSDREL1.IPC.0034.D65.2407302228:bd07/30/2024:svnIntelCorporation:pnBeechnutCity:pvr....................:rvnIntelCorporation:rnBeechnutCity:rvr0.02:cvnIntelCorporation:ct23:cvr............:skuSKUNumber:pfaFamily: dmi.product.family: Family dmi.product.name: BeechnutCity dmi.product.sku: SKU Number dmi.product.version: .................... dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute ** Attachment added: "Additional logs, platform information" https://bugs.launchpad.net/bugs/2172971/+attachment/6014910/+files/Ubuntu_26.04.1-2026.10.29.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172971 Title: Hotplug doesnt work as expected Status in linux package in Ubuntu: New Bug description: Hotplugging as is or after adding grub parameter "intel_iommu=on" hotplug on drives stops working - unplugging works fine, the devices disappear without issue but when I hot plug them in, they do not always reappear back. Rebooting the machine restores the drives. Removing "intel_iommu=on" or using "intel_iommu=off" fixes the issue. In BIOS Hotplug and VMD were enabled. Since adding "intel_iommu=on" in grub has no effect, I assume it is on by default. Doing hotplug few times (even with wait time between the plugs) will cause the OS to hang completely requiring force reset. Another workaround is to add "iommu=pt". ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: user 34901 F.... pipewire CasperMD5CheckResult: pass Date: Wed Nov 4 15:56:24 2026 InstallationDate: Installed on 2026-11-04 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Intel Corporation BeechnutCity ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=f738f84f-7ae7-49c5-97e0-dab197e7a2bc ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2024 dmi.bios.vendor: Intel Corporation dmi.bios.version: BHSDREL1.IPC.0034.D65.2407302228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BeechnutCity dmi.board.vendor: Intel Corporation dmi.board.version: 0.02 dmi.chassis.asset.tag: .................... dmi.chassis.type: 23 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: ............ dmi.modalias: dmi:bvnIntelCorporation:bvrBHSDREL1.IPC.0034.D65.2407302228:bd07/30/2024:svnIntelCorporation:pnBeechnutCity:pvr....................:rvnIntelCorporation:rnBeechnutCity:rvr0.02:cvnIntelCorporation:ct23:cvr............:skuSKUNumber:pfaFamily: dmi.product.family: Family dmi.product.name: BeechnutCity dmi.product.sku: SKU Number dmi.product.version: .................... dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172971/+subscriptions

вторник

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-6.8/6.8.0-1071.79~22.04.1+1)

All autopkgtests for the newly accepted linux-restricted-modules-gcp-6.8 (6.8.0-1071.79~22.04.1+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/470.256.02-0ubuntu0.22.04.6 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-gcp-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions