From owner-freebsd-current@freebsd.org Thu Jan 28 20:03:04 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0ABDE4EBB66; Thu, 28 Jan 2021 20:03:04 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRWc703qrz4d82; Thu, 28 Jan 2021 20:03:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 10SK2tH9096971 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 28 Jan 2021 12:02:55 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 10SK2tVk096970; Thu, 28 Jan 2021 12:02:55 -0800 (PST) (envelope-from sgk) Date: Thu, 28 Jan 2021 12:02:55 -0800 From: Steve Kargl To: Emmanuel Vadot Cc: freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: i915kms and chip resets on rsc0? Message-ID: <20210128200255.GA96914@troutmask.apl.washington.edu> References: <20200710192736.GA69592@troutmask.apl.washington.edu> <20210128191510.GA96585@troutmask.apl.washington.edu> <20210128204806.77d1e676a592ec638a82d5be@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210128204806.77d1e676a592ec638a82d5be@bidouilliste.com> X-Rspamd-Queue-Id: 4DRWc703qrz4d82 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MAILMAN_DEST(0.00)[freebsd-x11,freebsd-current]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM, none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 20:03:04 -0000 On Thu, Jan 28, 2021 at 08:48:06PM +0100, Emmanuel Vadot wrote: > On Thu, 28 Jan 2021 11:15:10 -0800 > Steve Kargl wrote: > > > All, > > > > I have finally gotten my old laptop somewhat back to it > > 2 Dec 2020 working state. The kernel/world/drm-current-kmod > > from 2 Dec 2020 worked wonderfully. Sadly, the two week > > recover from a failed update has one final hurdle. > > > > With nearly top-of-tree src/ and ports/ > > > > % cd /usr/src > > % git log | more > > commit 0e01ea872ee475d7aef11d21588504e2ef4eb32c > > Author: Cy Schubert > > Date: Wed Jan 27 21:52:08 2021 -0800 > > > > % pkg info | grep kmod > > drm-current-kmod-5.4.62.g20210128 DRM modules for the linuxkpi-based KMS components > > gpu-firmware-kmod-g20201213 Firmware modules for the linuxkpi-based KMS components > > (snip) > > Asynchronous wait on fence i915:Xorg[100156]:4 timed out (hint:0x24ad37f0S) > > drmn0: GPU recovery timed out, cancelling all in-flight rendering. > > drmn0: Resetting chip for hang on rcs0 > > > > Does 5.4.62.g20210118 works ? It works to the extent that the X server loads and the fvwm2 window manager comes up with my normal desktop. In fact, I'm typing this in a xterm at that moment. What I don't know is if the X server is ignoring the GPU. It is unclear to me if the last "drmn0: Resetting chip for hang on rcs0" is disabling some functionality. xwininfo reports % xwininfo xwininfo: Window id: 0xef (the root window) (has no name) Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 1400 Height: 1050 Depth: 24 Visual: 0x21 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+0 -0+0 -0-0 +0-0 -geometry 1400x1050+0+0 which looks like what I expect for 'startx -- -depth 24'. -- Steve