a lot of freezing ... crash? i915+powersave?

Bug #2106297 reported by Manfred Herrmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe-6.11 (Ubuntu)
New
Undecided
Unassigned

Bug Description

journal -b

...
Apr 05 13:24:25 tpt490 kernel: ------------[ cut here ]------------
Apr 05 13:24:25 tpt490 kernel: memcpy: detected field-spanning write (size 28) of single field "xattrstart" at /build/linux-hwe-6.11-56AUoP/linux-hwe-6.11-6.11.0/debian/build/build-generic/>
Apr 05 13:24:25 tpt490 kernel: WARNING: CPU: 0 PID: 800 at /build/linux-hwe-6.11-56AUoP/linux-hwe-6.11-6.11.0/debian/build/build-generic/____________________________________________________>
Apr 05 13:24:25 tpt490 kernel: Modules linked in: parport_pc ppdev lp parport nvme_fabrics nvme_keyring efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) mmc_block sn>
Apr 05 13:24:25 tpt490 kernel: CPU: 0 UID: 0 PID: 800 Comm: systemd-random- Tainted: P O 6.11.0-21-generic #21~24.04.1-Ubuntu
Apr 05 13:24:25 tpt490 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Apr 05 13:24:25 tpt490 kernel: Hardware name: LENOVO 20N2004EGE/20N2004EGE, BIOS N2IETA5W (1.83 ) 06/20/2024
Apr 05 13:24:25 tpt490 kernel: RIP: 0010:zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: Code: 01 0f 85 69 ff ff ff 31 c9 48 c7 c2 d0 68 e3 c0 4c 89 c6 4c 89 45 c8 48 c7 c7 78 62 e3 c0 c6 05 5f 51 13 00 01 e8 c5 9b ec df <0f> 0b 4c 8b 45 c8 e9 3b >
Apr 05 13:24:25 tpt490 kernel: RSP: 0018:ffffb8b2c17f7940 EFLAGS: 00010246
Apr 05 13:24:25 tpt490 kernel: RAX: 0000000000000000 RBX: ffff918150f18000 RCX: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: RBP: ffffb8b2c17f7980 R08: 0000000000000000 R09: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff91814bae9ed8
Apr 05 13:24:25 tpt490 kernel: R13: ffff918157543000 R14: ffff9181414df6c0 R15: ffff9181403bf0e0
Apr 05 13:24:25 tpt490 kernel: FS: 0000741bd5a65440(0000) GS:ffff918a96400000(0000) knlGS:0000000000000000
Apr 05 13:24:25 tpt490 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 05 13:24:25 tpt490 kernel: CR2: 0000741bd6a30590 CR3: 000000010ad88005 CR4: 00000000003706f0
Apr 05 13:24:25 tpt490 kernel: Call Trace:
Apr 05 13:24:25 tpt490 kernel: <TASK>
Apr 05 13:24:25 tpt490 kernel: ? show_regs+0x6c/0x80
Apr 05 13:24:25 tpt490 kernel: ? __warn+0x88/0x140
Apr 05 13:24:25 tpt490 kernel: ? zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: ? report_bug+0x182/0x1b0
Apr 05 13:24:25 tpt490 kernel: ? handle_bug+0x6e/0xb0
Apr 05 13:24:25 tpt490 kernel: ? exc_invalid_op+0x18/0x80
Apr 05 13:24:25 tpt490 kernel: ? asm_exc_invalid_op+0x1b/0x20
Apr 05 13:24:25 tpt490 kernel: ? zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: ? txg_rele_to_quiesce+0x33/0x40 [zfs]
Apr 05 13:24:25 tpt490 kernel: zfs_sa_set_xattr+0x366/0x3d0 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_set_sa+0x100/0x1f0 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_set+0x23b/0x280 [zfs]
Apr 05 13:24:25 tpt490 kernel: __zpl_xattr_user_set+0x128/0x170 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_user_set+0x22/0x40 [zfs]
Apr 05 13:24:25 tpt490 kernel: __vfs_removexattr+0x81/0xd0
Apr 05 13:24:25 tpt490 kernel: __vfs_removexattr_locked+0xe5/0x1a0
Apr 05 13:24:25 tpt490 kernel: ? ksys_lseek+0x7d/0xd0
Apr 05 13:24:25 tpt490 kernel: vfs_removexattr+0x59/0x110
Apr 05 13:24:25 tpt490 kernel: __do_sys_fremovexattr+0x12a/0x1b0
Apr 05 13:24:25 tpt490 kernel: __x64_sys_fremovexattr+0x15/0x20
Apr 05 13:24:25 tpt490 kernel: x64_sys_call+0x2049/0x25f0
Apr 05 13:24:25 tpt490 kernel: do_syscall_64+0x7e/0x170
Apr 05 13:24:25 tpt490 kernel: ? __count_memcg_events+0x86/0x160
Apr 05 13:24:25 tpt490 kernel: ? count_memcg_events.constprop.0+0x2a/0x50
Apr 05 13:24:25 tpt490 kernel: ? handle_mm_fault+0x1df/0x2d0
Apr 05 13:24:25 tpt490 kernel: ? do_user_addr_fault+0x5d5/0x870
Apr 05 13:24:25 tpt490 kernel: ? irqentry_exit_to_user_mode+0x43/0x250
Apr 05 13:24:25 tpt490 kernel: ? irqentry_exit+0x43/0x50
Apr 05 13:24:25 tpt490 kernel: ? clear_bhb_loop+0x15/0x70
Apr 05 13:24:25 tpt490 kernel: ? clear_bhb_loop+0x15/0x70
Apr 05 13:24:25 tpt490 kernel: ? clear_bhb_loop+0x15/0x70
Apr 05 13:24:25 tpt490 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Apr 05 13:24:25 tpt490 kernel: RIP: 0033:0x741bd662683b
Apr 05 13:24:25 tpt490 kernel: Code: 73 01 c3 48 8b 0d dd 45 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 c7 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 >
Apr 05 13:24:25 tpt490 kernel: RSP: 002b:00007fff85ea3718 EFLAGS: 00000246 ORIG_RAX: 00000000000000c7
Apr 05 13:24:25 tpt490 kernel: RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000741bd662683b
Apr 05 13:24:25 tpt490 kernel: RDX: 000000000000001a RSI: 00005a32b0e7f08b RDI: 0000000000000005
Apr 05 13:24:25 tpt490 kernel: RBP: 00007fff85ea3850 R08: 0000000000000028 R09: 0000000000000030
Apr 05 13:24:25 tpt490 kernel: R10: 00005a32c5a15f50 R11: 0000000000000246 R12: 0000000000000004
Apr 05 13:24:25 tpt490 kernel: R13: 0000000000000001 R14: 00005a32b0e7f08b R15: 0000000000000001
Apr 05 13:24:25 tpt490 kernel: </TASK>
Apr 05 13:24:25 tpt490 kernel: ---[ end trace 0000000000000000 ]---

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.11.0-21-generic 6.11.0-21.21~24.04.1+1
ProcVersionSignature: Ubuntu 6.11.0-21.21~24.04.1-generic 6.11.11
Uname: Linux 6.11.0-21-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 5 14:00:27 2025
InstallationDate: Installed on 2025-04-04 (1 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: linux-signed-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Manfred Herrmann (herrmann-manfred) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.