Manjaro freeze kernel bug

Support Kernel
1

I tried to configure a bluetooth device using Blueman, but ran into freeze of system (restored after reboot). Seems it is connected to kernel bug. I saw a description of a similar bug on RHEL9 - bug 1977561 on Red Hat Bugzilla site. Why did it happen?

kernel BUG at mm/slub.c:316!
invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
CPU: 4 PID: 1580 Comm: gsd-rfkill Tainted: P           OE     5.13.19-2-MANJARO #1

RIP: 0010:__slab_free+0x2ce/0x4f0
Code: 04 25 28 00 00 00 0f 85 e9 01 00 00 48 8d 65 d8 4c 89 e6 4c 89 f7 ba 01 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d e9 c2 10 00 00 <0f> 0b 41 f7 46 08 00 0d 21 00 0f 85 0c ff ff ff>
RSP: 0018:ffffaef2c392bcd0 EFLAGS: 00010246
RAX: ffffa05b02993270 RBX: ffffa05b02993200 RCX: ffffa05b02993200
RDX: 0000000080200019 RSI: ffffd2a3040a6480 RDI: ffffa05b001fe100
RBP: ffffaef2c392bd80 R08: 0000000000000001 R09: ffffffffc0edba91
R10: 0000000000000000 R11: 0000000000000004 R12: ffffd2a3040a6480
R13: ffffa05b02993200 R14: ffffa05b001fe100 R15: ffffa05b02993200
FS:  00007efdc2e93500(0000) GS:ffffa05e4e300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000034b9df52a278 CR3: 00000001608bc002 CR4: 00000000007706e0
PKRU: 55555554
Call Trace:
? del_timer_sync+0x6f/0xb0
? prepare_to_wait_event+0x76/0x190
? finish_wait+0x42/0x80
kmem_cache_free+0x46a/0x4a0
? btusb_shutdown_intel_new+0x31/0x50 [btusb]
btusb_shutdown_intel_new+0x31/0x50 [btusb]
hci_dev_do_close+0x422/0x570 [bluetooth]
hci_rfkill_set_block+0x4c/0x90 [bluetooth]
rfkill_set_block+0x8f/0x160 [rfkill]
rfkill_fop_write+0x146/0x1f0 [rfkill]
vfs_write+0xb9/0x270
ksys_write+0xaf/0xe0
do_syscall_64+0x3d/0x80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7efdc318993f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 09 56 f9 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08>
RSP: 002b:00007ffe9d9abff0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007efdc2e93488 RCX: 00007efdc318993f
RDX: 0000000000000008 RSI: 000055e28e104080 RDI: 0000000000000008
RBP: 00007ffe9d9ac040 R08: 0000000000000000 R09: 000000000000000b
R10: aaaaaaaaaaaaaaab R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffe9d9ac0a0 R14: 0000000000000000 R15: 000055e28e0ef820
Modules linked in: wacom usbhid ccm rfcomm cmac algif_hash snd_hda_codec_realtek algif_skcipher af_alg snd_hda_codec_generic bnep btusb btrtl btbcm btintel uvcvideo bluetooth videob>
дек 03 17:17:18 Murz kernel:  crc32_pclmul ip6t_REJECT ghash_clmulni_intel mac80211 drm_kms_helper snd_hda_codec_hdmi snd_pcm_dmaengine nf_reject_ipv6 aesni_intel crypto_simd libarc4 cryptd snd_hda_intel cec sn>
nf_conntrack_broadcast video int3403_thermal int340x_thermal_zone nf_nat_ftp nf_nat tpm int3400_thermal acpi_thermal_rel rng_core nf_conntrack_ftp acpi_pad acpi_tad nf_conntrack nf>
---[ end trace 3fa0a607e43c042b ]---
2

You are using an EOL kernel, try using the current 5.15 kernel or the last LTS kernel which is 5.10.

1 Like
3

If the kernel is tainted ─ meaning that you’ve loaded a proprietary module into the kernel ─ then there’s no way to verify what caused the bug. The upstream kernel developers will even ignore such bug reports, because they know there’s nothing they can do about it.

4

Thanks for your comments! I’ll update the kernel.

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.