You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Starting this as a thread for putting kernel panics that have not yet been identified as being related to a specific issue (if you have an idea what causes it, open new issue for it)
Try and give as much info as you can, for example it panics when running with X argument but not with Y. If you are able to consistently reproduce the bug, give the steps.
The text was updated successfully, but these errors were encountered:
If your machine starts with a "Received SIGSEGV in SIGSEGV handler, aborting stack trace!" in the console, run dmesg to view the kernel log and copy out the full error such as:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 837 at lib/refcount.c:28 refcount_dec_and_test+0x2e/0x34
refcount_t: underflow; use-after-free.
Modules linked in:
CPU: 0 PID: 837 Comm: systemd-udevd Not tainted 5.10.4 #1
Received SIGSEGV in SIGSEGV handler, aborting stack trace!
---[ end trace 9e8cfe9bac429f8b ]---
Describe the bug
Starting this as a thread for putting kernel panics that have not yet been identified as being related to a specific issue (if you have an idea what causes it, open new issue for it)
Try and give as much info as you can, for example it panics when running with X argument but not with Y. If you are able to consistently reproduce the bug, give the steps.
The text was updated successfully, but these errors were encountered: