https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028
--- Comment #338 from Mark Millard <marklmi26-f...@yahoo.com> ---
(In reply to George Mitchell from comment #337)
It again has the "WARNING !drm_modeset_is_locked . . ." lines
before there is any trap or panic notice:
. . .
[drm] Initialized amdgpu 3.40.0 20150101 for drmn0 on minor 0
WARNING !drm_modeset_is_locked(&crtc->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:619
WARNING !drm_modeset_is_locked(&crtc->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:619
WARNING !drm_modeset_is_locked(&crtc->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:619
WARNING !drm_modeset_is_locked(&crtc->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:619
WARNING !drm_modeset_is_locked(&dev->mode_config.connection_mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:669
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
WARNING !drm_modeset_is_locked(&plane->mutex) failed at
/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/drm/drm_atomic_helper.c:894
kernel trap 22 with interrupts disabled
kernel trap 22 with interrupts disabled
panic: modlist_lookup: a prior tqe_next changed!
. . .
I do not see how to get useful information from the
attempted use of the hwatchpoint monitoring for the
unexpected tqe_next field value change. The above may
be evidence that a detection happened but that the
handling does not mix well with the drm/amdgpu operation
in some way.
--
You are receiving this mail because:
You are the assignee for the bug.
