From owner-freebsd-current@freebsd.org Thu Jan 28 22:20:48 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 704654EEDC8; Thu, 28 Jan 2021 22:20:48 +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 4DRZg3121Cz4mCX; Thu, 28 Jan 2021 22:20:46 +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 10SMKeTG097716 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 28 Jan 2021 14:20:41 -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 10SMKeDZ097715; Thu, 28 Jan 2021 14:20:40 -0800 (PST) (envelope-from sgk) Date: Thu, 28 Jan 2021 14:20:40 -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: <20210128222040.GA97667@troutmask.apl.washington.edu> References: <20200710192736.GA69592@troutmask.apl.washington.edu> <20210128191510.GA96585@troutmask.apl.washington.edu> <20210128204806.77d1e676a592ec638a82d5be@bidouilliste.com> <20210128200255.GA96914@troutmask.apl.washington.edu> <20210128212213.a7e14bc4b469c745b522ea0a@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210128212213.a7e14bc4b469c745b522ea0a@bidouilliste.com> X-Rspamd-Queue-Id: 4DRZg3121Cz4mCX 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 [-1.99 / 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(-0.99)[-0.995]; 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 22:20:48 -0000 On Thu, Jan 28, 2021 at 09:22:13PM +0100, Emmanuel Vadot wrote: > On Thu, 28 Jan 2021 12:02:55 -0800 > Steve Kargl wrote: > > > 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. > > > > No I meant does the previous version of the ports works or was it > since today's update ? > I lost the information about which version of drm-current-kmod I had previouslu installed. The 2 Dec 2020 world/kernel/drm worked without an issue. Looking at 'svn log' on the Makefile for 'drm-current-kmod' shows 5.4.62.g20201003 for 2020-10-03 and an update to latest version on 2020-11-09 (but no version number info). So, I was likely running the 2020-11-09, and so that version did not have the chip reset message. The issue may be in the linuxkpi and not directly drm-current-kmod. I was hoping that by reporting 'chip reset on rcs0' would ring a bell for someone. This is all likely academic as I just saw John Baldwin's email that stated i386 support is being dropped in FreeBSD-current. I suppose my next update will move the laptop to amd64. -- Steve