From nobody Tue Dec 14 11:05:19 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 042EC18DC89F; Tue, 14 Dec 2021 11:05:20 +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 4JCwWz6hs1z3MpQ; Tue, 14 Dec 2021 11:05:19 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639479919; 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=l/J/nw0MVXq3R+CK6a1TvqrmE+vxXgEr7+XAbvxNV1g=; b=MrfK7j11ykzTvCiBNVAd2j4pc0nCPIbMN+m19l/zok+nuiNZk6TYaCiNYOV2FASEWFe8/Z AEg1aQf0Wg5nUg4OF/BQXGYGNZNAFldcL9V3cwFmYUmT40rJB5WRNNkPvVExdjzshOc4RJ SdmBw9+qXOJb9KjjhmoHgFvOtAMSL2wOBrtNVFvcbCnlH2x8ErcSnQD8y4WgurbS+1tnUM Nepsz1R4SRhNpvcLn139s7CDMAs04jcs9KlU15QcPDtPj+ycjua6QLj2W+CIsdR+CvKsBR mXaexvygLrItkcpZLtztsLwszxvmzizrhkZ4GIL8XStFBCMze3I+bu/VnzM7YA== Received: by freefall.freebsd.org (Postfix, from userid 1033) id D70331EB20; Tue, 14 Dec 2021 11:05:19 +0000 (UTC) Date: Tue, 14 Dec 2021 11:05:19 +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> <20211214091427.c531cf51b0284d8a1165b9bb@bidouilliste.com> <20211214112707.9bd528d32d6b8e3f2e3c62fe@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: <20211214112707.9bd528d32d6b8e3f2e3c62fe@bidouilliste.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639479919; 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=l/J/nw0MVXq3R+CK6a1TvqrmE+vxXgEr7+XAbvxNV1g=; b=jsjzHGpuRLtflOq9yAAstBev6ecKj8TP5XoynqkwN0K1/brY5VeSeCu+ymeCK7yVZPcNmA WnrBJ6WnphXcDxRf16dsnmtKa/kVDiNx2r8dolitnkh97pxOBEWupMx+Re12nLyjYrW3nt OTxcJzwXbw5IQqiWoesjLl9ullKPp+dFBAlA7g6AGp+XT+1lu+vZYPbRjRkdKmMKBNjqzm IR5IjUoa6kvL48pnIABrjXPfkc1f3xL0CpJqk2UR6R4lICCz34CwNjc696Q2oDoCgU2R6H AUGfXC0xN2s2CJvuDqWqp/ez3IZkadaHwAtC7C6F7sDpSXYUrDZlqJnjTfrzpw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639479919; a=rsa-sha256; cv=none; b=SHmHkADPpV21NE8LCyJoTTJAml3AD18BWlBRNQLkSH17p9NZtJq1nXVl2eTXAw2VezZmDm J9YlDjqpA/aSCa9f499gvwPad66oqD+lc3fpk+P8sTasaP/V5vH60qt8uUpKEDrqRhuo8J oOIFlU0PxBRL+KVTOHDT2BMnchEkBw7nNusWQ12l1p8QqV8yvb78iiGU54pIdOUA85z/Vq vE0KdttP+ru55D21rd8e2dCNwF3iMR6AwEIj+p1TT1lq5Q9TyuUnnzMVcrEBWwb0kaVdkH jFgbKFXc4eLJhPg5UDw5Awyvbj4aqFJgNNSwOZosbQf51NbWVxe36C+ra7zrQg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Tue, Dec 14, 2021 at 11:27:07AM +0100, Emmanuel Vadot wrote: > On Tue, 14 Dec 2021 10:14:24 +0000 Alexey Dokuchaev wrote: > > ... > > I know that I had problemless desktop some 10-5 years ago, okayish > > desktop ~three years ago, tolerable experience with 4.16.x DRM bits > > and shitty one with current 5.4.x (FWIW, 5.x had been problematic > > for me since the beginning, but previously it was fairly easy to > > build drm-fbsd12.0-kmod on -CURRENT to avoid regressions, now the > > source bases had divered too far enough; it's probably still possible > > to patch, but would take longer time). > > Any PR open for your issues? At first I was going to say something about such PRs would be closed as overcome by events anyways, but I like the change of your tone, so I won't. :) I've just ordered a Full HD IPS screen for my laptop so I could play modern (well, relatively modern) games, thus I expect I'd be sticking my hands into X11 stack deeper. I'll collect my notes and stories in a submittable shape and file them. > Well this telegram chat is still a community one, I don't see how it > makes a difference. Well, it'a a group of actual FreeBSD users vs. Twitter where random people who probably don't even use FreeBSD could see the poll and would gladly click on preloaded correct answer. > Also I can't see the poll result. Hmm, indeed, it does not display results even when viewed via browser, that is, unlogged. OTOH you should really try Telegram, there's nothing better right now on the market. ./danfe