From nobody Mon Dec 13 17:01:43 2021
X-Original-To: x11@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 35C3B18DBF53;
	Mon, 13 Dec 2021 17:01:44 +0000 (UTC)
	(envelope-from danfe@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (4096 bits) client-digest SHA256)
	(Client CN "freefall.freebsd.org", Issuer "R3" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4JCSTh122Rz4Yhb;
	Mon, 13 Dec 2021 17:01:44 +0000 (UTC)
	(envelope-from danfe@freebsd.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim;
	t=1639414904;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=e7zXsd8QaIirnRlS8GswGsFCSg6Z13zQFY6CmdlwWus=;
	b=uWdM3DItRbcTLIm1TITDX5K6XoybHcFw4k6Ti7A1dJYoQjTsW9ixfuBmvyy9hPCMwIeT6a
	uamnwX3WzIJzG1wHxF76LxAkMxT9BbKjo3IgO6UiPcP8ba8vtrZ22FquzllHFdJcj1OuKd
	4i9DhYrct/ZSVvj5KHhBog4agPbr9DIwFccbl8ySibEDLNt/f933oRR0jeGNKlGu+O33Lt
	8JyiNB6ZelVKzQJ4DkPg43pR+Z4jSlUACDt3f8Kx1j8ykGXTPJP/oPi/smwsIPjRwoWIgS
	txA1Sq9kLLRpnKheVOEWgqQyBalc4N17aZ/kShbjcj0nG2yU/eG6X04KXG7r5A==
Received: by freefall.freebsd.org (Postfix, from userid 1033)
	id E4F191B6B0; Mon, 13 Dec 2021 17:01:43 +0000 (UTC)
Date: Mon, 13 Dec 2021 17:01:43 +0000
From: Alexey Dokuchaev <danfe@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Cc: Gleb Smirnoff <glebius@freebsd.org>,
	"freebsd-current@freebsd.org" <freebsd-current@freebsd.org>,
	x11@freebsd.org
Subject: Re: smr inp breaks some jail use cases and panics with i915kms don't
 switch to the console anymore
Message-ID: <Ybd8d5nzx25w9cAV@FreeBSD.org>
References: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org>
List-Id: X11 <freebsd-x11.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-x11
List-Help: <mailto:x11+help@freebsd.org>
List-Post: <mailto:x11@freebsd.org>
List-Subscribe: <mailto:x11+subscribe@freebsd.org>
List-Unsubscribe: <mailto:x11+unsubscribe@freebsd.org>
Sender: owner-freebsd-x11@freebsd.org
X-BeenThere: freebsd-x11@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org>
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org;
	s=dkim; t=1639414904;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=e7zXsd8QaIirnRlS8GswGsFCSg6Z13zQFY6CmdlwWus=;
	b=eUmw//TmdeQQQfEIYvaHrm1xoexmi3Afvm/TMkanbseVcPb5EaN9Wu5tBBkr5C83gQ0Y28
	1ajxitwGGoKerA1WI4j2DofG0T39jS8C+9Y+H+fOVIcl0Rw1T35fFkEhYHTYIcALVYjdoy
	NGwRZxD+bXVZ6ddY7aX/Zj5H08qFOR8o+dp039pBmKB4AsQTn9KTorohsT0Sk68wMt5ugG
	MDkTk0jIeYijX1BW+LFTOl3urMaHTa54XLeoh4v202ozUH9bb2gAqHnHSSzi/RYeJGOSxD
	Xwg9kF97dfe1Em6Hd7n4UdtcGiN9tkdp0AoY65Yn5QA+7MG78CKk1Z70nsh6GQ==
ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639414904; a=rsa-sha256; cv=none;
	b=s/VheBQ0XtFc4yURLPQt3kFA5qb3O66Vocv9hWfylMUj7ECwExB+ueSyz0i6jsyFHOgBpA
	9pIiZMMOSdEHK6dGBo/PRGoAGOdgDnZKNlcmWIb8S+rF96A08AEGHSl9f1en7qhLUq6/hd
	EAHXVKfJO+iRz14GwVXnwtFsaxNb0xYnvtYdoUwPxxOaIlwBLsVqe09BFuo+kKUaoke5ER
	hK1LpLRbmKnmOchCW2oYABDTLRHFJWsxb/4SJjq2rledMZqvSkmJDfY1PqxipD4XZSW7Jr
	COemGF9DGZkZJWZks5CTLDNQBdiIlweDWelgf7UGtyJvmTFezgV8aX5aio0GjA==
ARC-Authentication-Results: i=1;
	mx1.freebsd.org;
	none
X-ThisMailContainsUnwantedMimeParts: N

On Mon, Dec 13, 2021 at 07:45:07AM -0800, John Baldwin wrote:
> ...
> However, it was a bit harder to see this originally as the 915kms driver
> tries to do a malloc(M_WAITOK) from cn_grab() when entering DDB which
> recursively panics (even a malloc(M_NOWAIT) from cn_grab() is probably a
> bad idea).

Funny how these new Linuxish DRM bits could affect so many things. :(

> The fact that that sysbeep is off so I couldn't tell if typing in commands
> was doing anything vs emitting errors probably didn't improve trying to
> diagnose the hang as "sitting in ddb" initially, though I don't know if
> DDB itself emits a beep for invalid commands, etc.

Now that Warner had fixed the beeper frequency, why we still didn't enable
it back on by default?

./danfe