On ds., jul. 20 2019, Evilham wrote:
Serious issue:
I was just debugging this right now, more infos with a proper
bug
report will come, but I think the system encounters a deadlock
sometimes with the drm-kmod / amdgpu which results in a kernel
panic.
It is a serious issue, but it allows me to use the computer
for
work,
it doesn't happen every couple hours, but it does happen a
couple
times a day.
FWIW, this is part of the crashlog:
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/wrkdirs/usr/ports/graphics/drm-fbsd12.0-kmod/work/kms-drm-6365030/drivers/gpu/drm/drm_atomic_helper.c:821
[Multiple times...]
kernel trap 22 with interrupts disabled
kernel trap 22 with interrupts
disabled
kernel trap 22 with interrupts disabled
kernel trap 22 with interrupts disabled
panic: spin lock held too long
And this is why I wanted to do more debugging before raising an
issue :-).
It kept happening without drm-kmod but the backtrace was
different, which allowed me to reduce it to a piece of alpha
Software I use pretty much all the time: WireGuard.
See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239351
So, update: there is no *serious* issue when using the ThinkPad
A485, it works mostly fine with minor annoyances (including the
fact that installation media won't work out of the box).
--
Evilham
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
