Arch Linux

Hubbleexplorer

Member

Registered: 2021-05-15

Posts: 89

Crash with following message: "kernel BUG at mm/usercopy.c:102!"

So, I was just using Firefox, and my PC crashed with a weird traceback about kwin_wayland and the kernel.
I don't know if this is the right place to report this, but I will still attempt to post here.

Traceback

jan 30 16:39:25 hubble NetworkManager[849]: <info>  [1706632765.5517] dhcp4 (wlan0): state changed new lease, address=192.168.1.69
jan 30 16:39:25 hubble systemd[1]: Starting Network Manager Script Dispatcher Service...
jan 30 16:39:25 hubble systemd[1]: Started Network Manager Script Dispatcher Service.
jan 30 16:39:35 hubble systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
jan 30 16:39:59 hubble kdeconnectd[10331]: new capabilities for  "Redmi Note 8"
jan 30 16:42:18 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:18 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:37 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:37 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:37 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:37 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:39 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:39 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:42:39 hubble rtkit-daemon[1499]: Successfully made thread 48875 of process 45093 owned by '1000' RT at priority 10.
jan 30 16:42:39 hubble rtkit-daemon[1499]: Supervising 9 threads of 6 processes of 1 users.
jan 30 16:43:14 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:14 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:24 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:24 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:36 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:36 hubble rtkit-daemon[1499]: Supervising 8 threads of 5 processes of 1 users.
jan 30 16:43:41 hubble kernel: usercopy: Kernel memory overwrite attempt detected to SLUB object 'task_struct' (offset 6940, size 80)!
jan 30 16:43:41 hubble kernel: ------------[ cut here ]------------
jan 30 16:43:41 hubble kernel: kernel BUG at mm/usercopy.c:102!
jan 30 16:43:41 hubble kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
jan 30 16:43:41 hubble kernel: CPU: 10 PID: 9984 Comm: kwin_wayland Tainted: P S         OE      6.7.2-arch1-1 #1 a8cc6217560401daa1a3b2de3f94ad139a093ff5
jan 30 16:43:41 hubble kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506IU_FA506IU/FA506IU, BIOS FA506IU.320 06/01/2022
jan 30 16:43:41 hubble kernel: RIP: 0010:usercopy_abort+0x6c/0x80
jan 30 16:43:41 hubble kernel: Code: e0 94 51 48 c7 c2 f2 fc e2 94 41 52 48 c7 c7 58 a6 e9 94 48 0f 45 d6 48 c7 c6 76 39 e0 94 48 89 c1 49 0f 45 f3 e8 54 7b d4 ff <0f> 0b 49 c7 c1 8c 26 e0 94 4d 89 ca 4d 89 c8 eb a8 0f 1f 00 90 90
jan 30 16:43:41 hubble kernel: RSP: 0018:ffff8f6080dc1a40 EFLAGS: 00010246
jan 30 16:43:41 hubble kernel: RAX: 0000000000000067 RBX: 0000000000001b1c RCX: 0000000000000000
jan 30 16:43:41 hubble kernel: RDX: 0000000000000000 RSI: ffff8f639f8a16c0 RDI: ffff8f639f8a16c0
jan 30 16:43:41 hubble kernel: RBP: 0000000000000050 R08: 0000000000000000 R09: ffff8f6080dc18e0
jan 30 16:43:41 hubble kernel: R10: 0000000000000003 R11: ffffffff956ca768 R12: ffff8f6080212300
jan 30 16:43:41 hubble kernel: R13: 0000000000000000 R14: ffff8f6080dc1b10 R15: 00005c434fc96d68
jan 30 16:43:41 hubble kernel: FS:  0000746dac4818c0(0000) GS:ffff8f639f880000(0000) knlGS:0000000000000000
jan 30 16:43:41 hubble kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 30 16:43:41 hubble kernel: CR2: 00005ea950bdffc8 CR3: 00000001d8492000 CR4: 0000000000350ef0
jan 30 16:43:41 hubble kernel: Call Trace:
jan 30 16:43:41 hubble kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device ccm intel_rapl_msr intel_rapl_common snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof>
jan 30 16:43:41 hubble kernel:  snd_timer snd i2c_nvidia_gpu soundcore joydev xfs vfat fat asus_wireless mousedev hid_logitech_dj mac_hid fuse loop dm_mod nfnetlink ip_tables x_tables pkcs8_key_parser usbhid amdgpu crct10dif_pclmul crc32_>
jan 30 16:43:41 hubble kernel: ---[ end trace 0000000000000000 ]---
jan 30 16:43:41 hubble kernel: RIP: 0010:usercopy_abort+0x6c/0x80
jan 30 16:43:41 hubble kernel: Code: e0 94 51 48 c7 c2 f2 fc e2 94 41 52 48 c7 c7 58 a6 e9 94 48 0f 45 d6 48 c7 c6 76 39 e0 94 48 89 c1 49 0f 45 f3 e8 54 7b d4 ff <0f> 0b 49 c7 c1 8c 26 e0 94 4d 89 ca 4d 89 c8 eb a8 0f 1f 00 90 90
jan 30 16:43:41 hubble kernel: RSP: 0018:ffff8f6080dc1a40 EFLAGS: 00010246
jan 30 16:43:41 hubble kernel: RAX: 0000000000000067 RBX: 0000000000001b1c RCX: 0000000000000000
jan 30 16:43:41 hubble kernel: RDX: 0000000000000000 RSI: ffff8f639f8a16c0 RDI: ffff8f639f8a16c0
jan 30 16:43:41 hubble kernel: RBP: 0000000000000050 R08: 0000000000000000 R09: ffff8f6080dc18e0
jan 30 16:43:41 hubble kernel: R10: 0000000000000003 R11: ffffffff956ca768 R12: ffff8f6080212300
jan 30 16:43:41 hubble kernel: R13: 0000000000000000 R14: ffff8f6080dc1b10 R15: 00005c434fc96d68
jan 30 16:43:41 hubble kernel: FS:  0000746dac4818c0(0000) GS:ffff8f639f880000(0000) knlGS:0000000000000000
jan 30 16:43:41 hubble kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 30 16:43:41 hubble kernel: CR2: 00005ea950bdffc8 CR3: 00000001d8492000 CR4: 0000000000350ef0

i found some posts about

kernel BUG at mm/usercopy.c:102!

but they are old so don't think that are related

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,892

Re: Crash with following message: "kernel BUG at mm/usercopy.c:102!"

Sounds like RAM issues... Test your memory with memtest for at least one night or day or whatever (the longer the better): https://wiki.archlinux.org/title/Stress … MemTest86+

Hubbleexplorer

Member

Registered: 2021-05-15

Posts: 89

Re: Crash with following message: "kernel BUG at mm/usercopy.c:102!"

Sounds like RAM issues... Test your memory with memtest for at least one night or day or whatever (the longer the better): https://wiki.archlinux.org/title/Stress … MemTest86+

Sorry for the delayed answer, after running MemTest86+ for one night no issues where found.
Could it be the CPU or the integrated GPU, if so how could i test that?