Date: Fri, 19 Jul 2019 16:07:23 -0700 From: Pete Wright <pete@nomadlogic.org> To: Evilham <contact@evilham.com>, freebsd-current@freebsd.org Subject: Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485 Message-ID: <56603047-4997-1fb5-18e1-3752cdaf3a18@nomadlogic.org> In-Reply-To: <3b186187-c9f6-46d2-939a-eceb6fa0359c@yggdrasil.evilham.com> References: <CAG%2B4yk=DU9o=5oEaFgZ91pufwyUtY9wH1AAhsqG-RhTkB3Zsug@mail.gmail.com> <3b186187-c9f6-46d2-939a-eceb6fa0359c@yggdrasil.evilham.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/19/19 3:54 PM, 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 > interesting. can you post this kernel panic, and any backtraces you are able to get here: https://github.com/FreeBSDDesktop/kms-drm/issues also, are you using the xf86-video-amdgpu driver, or the stock modesetting driver to X? thanks! -pete -- Pete Wright pete@nomadlogic.org 310.309.9298
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56603047-4997-1fb5-18e1-3752cdaf3a18>