Bug 2335509 - [abrt] trace_event_raw_init: WARNING: CPU: 5 PID: 486 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
Summary: [abrt] trace_event_raw_init: WARNING: CPU: 5 PID: 486 at kernel/trace/trace_e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f0dcc3dd04207fe6f075a34985e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-03 23:51 UTC by Stan King
Modified: 2025-01-16 23:27 UTC (History)
17 users (show)

Fixed In Version: kernel-6.12.9-100.fc40
Clone Of:
Environment:
Last Closed: 2025-01-15 01:40:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stan King 2025-01-03 23:51:24 UTC
Description of problem:
I had just started the system after upgrading the Kernel to 6.12.7-100.fc40.x86_64

Here is a link to the last message of a thread where the fix was discussed.

https://www.spinics.net/lists/stable/msg805001.html

They think it was confined to the Intel xe driver, but I'm virtual certain that I don't have that hardware.  It has UHD Graphics 730.  However, the last message in the error burst does mention xe "event xe_bo_move has unsafe dereference of argument 4".

Additional info:
reporter:       libreport-2.17.15
WARNING: CPU: 5 PID: 486 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
Modules linked in: xe(+) uas usb_storage drm_ttm_helper gpu_sched drm_suballoc_helper drm_gpuvm drm_exec i915 i2c_algo_bit drm_buddy nvme ttm crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni drm_display_helper polyval_generic ghash_clmulni_intel nvme_core sha512_ssse3 sha256_ssse3 sha1_ssse3 cec nvme_auth video wmi pinctrl_tigerlake ip6_tables ip_tables i2c_dev fuse
CPU: 5 UID: 0 PID: 486 Comm: (udev-worker) Not tainted 6.12.7-100.fc40.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. ASUS EXPERTCENTER D700SC_D700SC/D700SC, BIOS D700SC.330 04/01/2024
RIP: 0010:trace_event_raw_init+0x185/0x700
Code: 04 00 00 e8 3d da ff ff 4c 8b 04 24 84 c0 74 11 8b 4c 24 08 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c0 4d 85 c0 0f 84 aa fe ff ff <0f> 0b bb 01 00 00 00 41 f6 c0 01 0f 85 eb 44 ec 00 66 2e 0f 1f 84
RSP: 0000:ffffaba100e77b70 EFLAGS: 00010206
RAX: ffffffffffffffdf RBX: ffffffffc0b47e51 RCX: 0000000000000005
RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffffffc0b47e47
RBP: ffffffffc0b47d60 R08: 0000000000000018 R09: 0000000000000000
R10: 0000000000000039 R11: 00000000000000de R12: 00000000000000f2
R13: 00000000000000f2 R14: ffffffffc0b48e80 R15: 0000000000000000
FS:  00007f62887abbc0(0000) GS:ffff88f3bf480000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f628725b000 CR3: 000000010e3ee004 CR4: 0000000000770ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? trace_event_raw_init+0x185/0x700
 ? __warn.cold+0x93/0xfa
 ? trace_event_raw_init+0x185/0x700
 ? report_bug+0xff/0x140
 ? handle_bug+0x58/0x90
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? trace_event_raw_init+0x185/0x700
 ? event_create_dir+0xda/0x430
 event_init+0x28/0x70
 trace_module_notify+0x19a/0x250
 notifier_call_chain+0x5a/0xd0
 blocking_notifier_call_chain_robust+0x65/0xc0
 load_module+0x1b3f/0x2030
 ? __do_sys_init_module+0x17a/0x1b0
 __do_sys_init_module+0x17a/0x1b0
 do_syscall_64+0x82/0x160
 ? sched_clock_cpu+0xf/0x1f0
 ? clear_bhb_loop+0x25/0x80
 ? clear_bhb_loop+0x25/0x80
 ? clear_bhb_loop+0x25/0x80
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f628918716e
Code: 48 8b 0d ad ac 0c 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 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7a ac 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffc700d6238 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
RAX: ffffffffffffffda RBX: 000055755b406b50 RCX: 00007f628918716e
RDX: 00007f62892a107d RSI: 000000000073690e RDI: 000055755bd71b10
RBP: 00007ffc700d62f0 R08: 000055755b38d010 R09: 0000000000000007
R10: 0000000000000006 R11: 0000000000000246 R12: 00007f62892a107d
R13: 0000000000020000 R14: 000055755b406620 R15: 000055755b4124a0
 </TASK>

Potential duplicate: bug 2333761

Comment 1 Seth Alford 2025-01-04 15:40:25 UTC
Description of problem:
I do not know how this happened, exactly. System rebooted. Window popped up with a problem report. I chose to report it. Here we are.

Version-Release number of selected component:
kernel-core-6.12.7-100.fc40

Additional info:
reporter:       libreport-2.17.15
kernel:         6.12.7-100.fc40.x86_64
crash_function: trace_event_raw_init
reason:         WARNING: CPU: 7 PID: 510 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
type:           Kerneloops
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.7-100.fc40.x86_64 root=UUID=a45b8aad-6fae-41f3-9e37-0cff89bd2c8e ro rootflags=subvol=root rd.luks.uuid=luks-f7674379-f2f1-41ae-aacf-80f8cd1bd58d rhgb quiet
package:        kernel-core-6.12.7-100.fc40
runlevel:       unknown
comment:        I do not know how this happened, exactly. System rebooted. Window popped up with a problem report. I chose to report it. Here we are.

Truncated backtrace:
WARNING: CPU: 7 PID: 510 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
Modules linked in: xe(+) drm_suballoc_helper nouveau(+) i915 mxm_wmi drm_ttm_helper nvme gpu_sched drm_gpuvm nvme_core drm_exec drm_buddy crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel ttm polyval_clmulni polyval_generic hid_multitouch ucsi_acpi ghash_clmulni_intel drm_display_helper sha512_ssse3 typec_ucsi sha256_ssse3 typec cec sha1_ssse3 nvme_auth video i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw fuse
CPU: 7 UID: 0 PID: 510 Comm: (udev-worker) Not tainted 6.12.7-100.fc40.x86_64 #1
Hardware name: LENOVO 82XV/LNVNB161216, BIOS LZCN32WW 09/23/2023
RIP: 0010:trace_event_raw_init+0x185/0x700
Code: 04 00 00 e8 3d da ff ff 4c 8b 04 24 84 c0 74 11 8b 4c 24 08 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c0 4d 85 c0 0f 84 aa fe ff ff <0f> 0b bb 01 00 00 00 41 f6 c0 01 0f 85 eb 44 ec 00 66 2e 0f 1f 84
RSP: 0018:ffffa767405a7b60 EFLAGS: 00010206
RAX: ffffffffffffffdf RBX: ffffffffc12b0e51 RCX: 0000000000000005
RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffffffc12b0e47
RBP: ffffffffc12b0d60 R08: 0000000000000018 R09: 0000000000000000
R10: 0000000000000039 R11: 00000000000000de R12: 00000000000000f2
R13: 00000000000000f2 R14: ffffffffc12b1e80 R15: 0000000000000000
FS:  00007f7f6770fbc0(0000) GS:ffff9a39a7980000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563e18b14000 CR3: 000000010196e000 CR4: 0000000000f50ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? trace_event_raw_init+0x185/0x700
 ? __warn.cold+0x93/0xfa
 ? trace_event_raw_init+0x185/0x700
 ? report_bug+0xff/0x140
 ? handle_bug+0x58/0x90
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? trace_event_raw_init+0x185/0x700
 ? event_create_dir+0xda/0x430
 event_init+0x28/0x70
 trace_module_notify+0x19a/0x250
 notifier_call_chain+0x5a/0xd0
 blocking_notifier_call_chain_robust+0x65/0xc0
 load_module+0x1b3f/0x2030
 ? __do_sys_init_module+0x17a/0x1b0
 __do_sys_init_module+0x17a/0x1b0
 do_syscall_64+0x82/0x160
 ? do_user_addr_fault+0x55a/0x7b0
 ? exc_page_fault+0x7e/0x180
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f7f680eb16e
Code: 48 8b 0d ad ac 0c 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 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7a ac 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffd522a61f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
RAX: ffffffffffffffda RBX: 0000563e17086c00 RCX: 00007f7f680eb16e
RDX: 00007f7f6820507d RSI: 000000000073690e RDI: 0000563e170ae860
RBP: 00007ffd522a62b0 R08: 0000563e17032010 R09: 0000000000000007
R10: 0000000000000001 R11: 0000000000000246 R12: 00007f7f6820507d
R13: 0000000000020000 R14: 0000563e17090710 R15: 0000563e17098ca0
 </TASK>

Comment 2 Chad Feller 2025-01-05 17:16:01 UTC
Description of problem:
booted the system.  happens consistently on boot or reboot

Version-Release number of selected component:
kernel-core-6.12.7-100.fc40

Additional info:
reporter:       libreport-2.17.15
kernel:         6.12.7-100.fc40.x86_64
crash_function: trace_event_raw_init
reason:         WARNING: CPU: 7 PID: 556 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
type:           Kerneloops
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.7-100.fc40.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.luks.uuid=luks-3144dcce-d1a6-4ddf-b1b6-46a7af96a434 rhgb quiet
package:        kernel-core-6.12.7-100.fc40
runlevel:       unknown
comment:        booted the system.  happens consistently on boot or reboot

Truncated backtrace:
WARNING: CPU: 7 PID: 556 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x185/0x700
Modules linked in: xe(+) drm_ttm_helper gpu_sched drm_suballoc_helper drm_gpuvm drm_exec hid_logitech_hidpp hid_logitech_dj i915 i2c_algo_bit drm_buddy ttm nvme drm_display_helper nvme_core crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ucsi_acpi ghash_clmulni_intel hid_multitouch sha512_ssse3 typec_ucsi sha256_ssse3 sha1_ssse3 typec cec video nvme_auth i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw ip6_tables ip_tables nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 fuse i2c_dev
CPU: 7 UID: 0 PID: 556 Comm: (udev-worker) Not tainted 6.12.7-100.fc40.x86_64 #1
Hardware name: LENOVO 21HMCTO1WW/21HMCTO1WW, BIOS N3XET57W (1.32 ) 10/09/2024
RIP: 0010:trace_event_raw_init+0x185/0x700
Code: 04 00 00 e8 3d da ff ff 4c 8b 04 24 84 c0 74 11 8b 4c 24 08 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c0 4d 85 c0 0f 84 aa fe ff ff <0f> 0b bb 01 00 00 00 41 f6 c0 01 0f 85 eb 44 ec 00 66 2e 0f 1f 84
RSP: 0018:ffffbaec80b8fbb0 EFLAGS: 00010206
RAX: ffffffffffffffdf RBX: ffffffffc0efee51 RCX: 0000000000000005
RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffffffc0efee47
RBP: ffffffffc0efed60 R08: 0000000000000018 R09: 0000000000000000
R10: 0000000000000039 R11: 00000000000000de R12: 00000000000000f2
R13: 00000000000000f2 R14: ffffffffc0effe80 R15: 0000000000000000
FS:  00007efcc9aa8bc0(0000) GS:ffff9926df180000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005620ba68ab58 CR3: 000000010fefe000 CR4: 0000000000f50ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? trace_event_raw_init+0x185/0x700
 ? __warn.cold+0x93/0xfa
 ? trace_event_raw_init+0x185/0x700
 ? report_bug+0xff/0x140
 ? handle_bug+0x58/0x90
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? trace_event_raw_init+0x185/0x700
 ? event_create_dir+0xda/0x430
 event_init+0x28/0x70
 trace_module_notify+0x19a/0x250
 notifier_call_chain+0x5a/0xd0
 blocking_notifier_call_chain_robust+0x65/0xc0
 load_module+0x1b3f/0x2030
 ? __do_sys_init_module+0x17a/0x1b0
 __do_sys_init_module+0x17a/0x1b0
 do_syscall_64+0x82/0x160
 ? __irq_exit_rcu+0x4a/0xb0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7efcca48416e
Code: 48 8b 0d ad ac 0c 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 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7a ac 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffee7163808 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
RAX: ffffffffffffffda RBX: 00005620ba63f0c0 RCX: 00007efcca48416e
RDX: 00007efcca59e07d RSI: 000000000073690e RDI: 00005620ba698cf0
RBP: 00007ffee71638c0 R08: 00005620ba5f6010 R09: 0000000000000007
R10: 0000000000000004 R11: 0000000000000246 R12: 00007efcca59e07d
R13: 0000000000020000 R14: 00005620ba63e740 R15: 00005620ba64eaf0
 </TASK>

Comment 3 Stan King 2025-01-05 23:31:56 UTC
I'll correct my initial comment: Apparently the Intel UHD Graphics 730 GPU on my i5-11400 CPU is a form of xe graphics, xe-lp for low power, if I'm reading wikipedia correctly.  Until now, the string "xe" has not appeared in any log file messages related to kernel or X start-up, so its xe nature was not at all obvious.

Comment 4 Peter Bieringer 2025-01-08 05:17:44 UTC
potential duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2333761

Comment 5 Fedora Update System 2025-01-09 21:13:01 UTC
FEDORA-2025-c131f515c1 (kernel-6.12.9-100.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c131f515c1

Comment 6 Fedora Update System 2025-01-10 03:36:52 UTC
FEDORA-2025-c131f515c1 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c131f515c1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c131f515c1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-01-15 01:40:01 UTC
FEDORA-2025-c131f515c1 (kernel-6.12.9-100.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Stan King 2025-01-16 23:27:38 UTC
With 6.12.9-100.fc40.x86_64, the error is gone.  Everything seems to work fine, including extremetuxracer, the most intensive graphics test available to me.  Thanks.


Note You need to log in before you can comment on or make changes to this bug.