From nobody Tue Dec 14 07:11:28 2021 X-Original-To: freebsd-current@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 4472D18D3F58; Tue, 14 Dec 2021 07:11:29 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 4JCqL91W0fz4jXJ; Tue, 14 Dec 2021 07:11:29 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639465889; 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=v3ET69j5wEbHx0RMBbjjnVyhMMSqZuEUqSgM4G38kcs=; b=cPDRnIBIz7Wxu/nMPw0YJ5xk7jta3WF4Owyf+7ca6TbU5CqUgvKc4ROkUdmOraNU1yHJHX iuW0dONwqbAFSBxfhZXSPDTNxPK/LmUhYvVTpFn4bG5OHsU9MEI++IA1vvDzE7ERC7a7hZ DS/ZnwatQUJjoKl+XHO8We5jmS2bhJntQDcBM3zP/HjVINqzuAyPKKYlnHc+XNeVNxhk66 suiYrPwiA0PXaj+8LrycP4Tc9LUmOp/JIqCOdCQxoPj232uRfLYrD/xmsV6XAJrPIZ3evA ba+kVg24Rl+EcFJSb3t6jfok2iQQ6SVblJhWm/SYFCrw0erZJBKDZLqNdlnJsA== Received: by freefall.freebsd.org (Postfix, from userid 1033) id 1041B1DFA7; Tue, 14 Dec 2021 07:11:29 +0000 (UTC) Date: Tue, 14 Dec 2021 07:11:28 +0000 From: Alexey Dokuchaev To: Emmanuel Vadot Cc: John Baldwin , Gleb Smirnoff , "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: References: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org> <20211213183222.f945b2e730f7c22dbe74681c@bidouilliste.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211213183222.f945b2e730f7c22dbe74681c@bidouilliste.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639465889; 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=v3ET69j5wEbHx0RMBbjjnVyhMMSqZuEUqSgM4G38kcs=; b=Hwd8zO9qEh9ju8b3yf98EFKSqJ4yBAOn6SqhGcmlRMfJdmiUusmwd9oAskuFgDFeKtSVzp eq7+yWJ3t6gaMnZMlI9AzJlWkIKZ8YSARM7Qs7dl36mU80Y+1zjEo0UiXrgc5D3r14mwog nB7RmAHPfaY4ZPOKhJpQakK+BY0XFoYy3ujMODLwxWGKgLnOGroTyjWZxanHOKtR0F8V2A GrGZdz+Lu1MURrYaKoeos58U+v8079haZaREGLuqVP+PKS1Qr48aulg5WOwyBYh/wb7u9a L8OgVuCnKAmvoPMw2/Sveh+JtSh9PgEXvuIGfSBOi+/CFe3vejUosvJJb/c2Kw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639465889; a=rsa-sha256; cv=none; b=nu7MXXDyv2Z0zgsjDhnQJ7Y8bWSa1GWElDUF9rozMA3KqzHHDl+ZJSoSK+YfQORPJJVxrM fr+LRAZjNrmP2Rv1uJ+8kqeyNaAjbAm/897SjV9XJ12CCpd7+nZPC2S+qOVgEVlKR6kGp8 lfUC7A9gZy2seZmeArCthYC0v/j4+OmV58U3Ky9HEJVZ6MPOzcU2OU1ZcOsg/1E3I12yqc 8OhaRsRnneqf/RSnZxA2cAsXG6E7ukoZCH80L0MWtorMxMRDT8kIlBN12j31BEwnbFesGU 9ShemFm5GLNxmuOAkMxBm79X0aJYoJuHAGnZLPPF26WeMpzyORsTl5la6TiQAg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Mon, Dec 13, 2021 at 06:32:22PM +0100, Emmanuel Vadot wrote: > On Mon, 13 Dec 2021 17:01:43 +0000 Alexey Dokuchaev wrote: > > 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. :( > > What is this comment about exactly? Oh, you know, it's about steadily deteriorating quality of our gfx stack once we had started pulling things from Linux. > > > 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? > > Because all people who wanted it off wasn't because it wasn't the > right vt100 frequency, they just wanted it off. In FreeBSD chat and with less biased poll than the one Warner had posted on Twitter, most people had actually voted against making it off by default: https://t.me/FreeBSD1/25129. If John's assumption that muting it pessimizes debugging is correct, it really leaves no strong reasons NOT to turn it back on by default. ./danfe