Date: Mon, 13 Dec 2021 18:32:22 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: John Baldwin <jhb@freebsd.org>, 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: <20211213183222.f945b2e730f7c22dbe74681c@bidouilliste.com> In-Reply-To: <Ybd8d5nzx25w9cAV@FreeBSD.org> References: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org> <Ybd8d5nzx25w9cAV@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Dec 2021 17:01:43 +0000 Alexey Dokuchaev <danfe@freebsd.org> 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 <manu@bidouilliste.com> <manu@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211213183222.f945b2e730f7c22dbe74681c>