From nobody Mon Dec 13 17:32:22 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 79B3618E28C4; Mon, 13 Dec 2021 17:32:25 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mail.blih.net [212.83.155.74]) (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 (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JCT945xCPz4fl8; Mon, 13 Dec 2021 17:32:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1639416743; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fU+I89Wjj2X85Kap/m6L5c+PYT8nTsrwsLd1Z1L/NUk=; b=mKtfbKrA/i2qjEpcO8P/fwB+7LeP6fH2Q6mcDgoT/YxrNp0rvmWCF5FtzAXjsN35Oqh9gw Zo6mQ03sGyZZGemWD+S79prMrc3S/f3GSO0O0c6YqOgiLvK3N0SKkZExLOvPwAiEqFE5RA yR7yex6CaME0n2uyj3N7rquH8cIOJGY= Received: from amy (lfbn-idf2-1-1163-183.w90-92.abo.wanadoo.fr [90.92.222.183]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 88fb658f (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 13 Dec 2021 17:32:22 +0000 (UTC) Date: Mon, 13 Dec 2021 18:32:22 +0100 From: Emmanuel Vadot To: Alexey Dokuchaev 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: <20211213183222.f945b2e730f7c22dbe74681c@bidouilliste.com> In-Reply-To: References: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4JCT945xCPz4fl8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N 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 ? > > 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 > Because all people who wanted it off wasn't because it wasn't the right vt100 frequency, they just wanted it off. -- Emmanuel Vadot