error 14 in mutter-x11-frames
Affected version
- Fedora 40
- Mutter
46~beta-3.fc40
- Wayland
Bug summary
Approximately twice per second, two errors are added on dmesg. The follow the format
mutter-x11-fram: segfault at 0 ip 0000000000000000 sp ... error 14 in mutter-x11-frames[...+3000] likely on CPU N (core N, socket 0)
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Steps to reproduce
- boot
sudo dmesg --follow
What happened
I cannot see any meaningful impact in the user experience, beside the error messages.
What did you expect to happen
No error messages
Relevant logs, screenshots, screencasts etc.
Example of errors:
[ 1292.455754] mutter-x11-fram[92223]: segfault at 0 ip 0000000000000000 sp 00007ffd18905d48 error 14 in mutter-x11-frames[5581934ae000+3000] likely on CPU 15 (core 3, socket 0)
[ 1292.455764] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 1293.005034] mutter-x11-fram[92316]: segfault at 0 ip 0000000000000000 sp 00007ffe676a00f8 error 14 in mutter-x11-frames[55c1bd976000+3000] likely on CPU 4 (core 4, socket 0)
[ 1293.005044] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 1293.557575] mutter-x11-fram[92419]: segfault at 0 ip 0000000000000000 sp 00007ffdc4d5c5b8 error 14 in mutter-x11-frames[559e84c57000+3000] likely on CPU 23 (core 13, socket 0)
[ 1293.557586] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 1294.107207] mutter-x11-fram[92515]: segfault at 0 ip 0000000000000000 sp 00007ffd10745858 error 14 in mutter-x11-frames[55fa48a07000+3000] likely on CPU 23 (core 13, socket 0)
[ 1294.107217] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Edited by Marco Marangoni