From owner-freebsd-current@freebsd.org Sun Jul 21 16:07:18 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 55607B6E87 for ; Sun, 21 Jul 2019 16:07:18 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49411855C3 for ; Sun, 21 Jul 2019 16:07:17 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (p200300C27F4C6B00EA6A64FFFECACA55.dip0.t-ipconnect.de [IPv6:2003:c2:7f4c:6b00:ea6a:64ff:feca:ca55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 45s8l23rMhz3wts for ; Sun, 21 Jul 2019 18:07:10 +0200 (CEST) From: Evilham To: freebsd-current@freebsd.org Subject: Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485 References: <3b186187-c9f6-46d2-939a-eceb6fa0359c@yggdrasil.evilham.com> <56603047-4997-1fb5-18e1-3752cdaf3a18@nomadlogic.org> <64f3212b-cbe7-4c8f-84df-48f14a0bf44f@yggdrasil.evilham.com> In-reply-to: <64f3212b-cbe7-4c8f-84df-48f14a0bf44f@yggdrasil.evilham.com> Date: Sun, 21 Jul 2019 18:07:06 +0200 Message-ID: <7f93a34e-0603-410b-850a-ab2708e19273@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 49411855C3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-4.47 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.74)[asn: 196752(-3.71), country: NL(0.01)]; MX_GOOD(-0.01)[yggdrasil.evilham.com,mail.evilham.com]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; NEURAL_HAM_SHORT(-0.92)[-0.918,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2019 16:07:18 -0000 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