From owner-freebsd-x11@freebsd.org Thu Oct 10 17:54:31 2019 Return-Path: Delivered-To: freebsd-x11@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 59C8814540A for ; Thu, 10 Oct 2019 17:54:31 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46pzHW1h1dz4NhL; Thu, 10 Oct 2019 17:54:31 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 118CD130FF; Thu, 10 Oct 2019 17:54:31 +0000 (UTC) From: Jan Beich To: John Kennedy Cc: freebsd-x11@freebsd.org Subject: Re: sway-1.2_1 crashes References: <20191007165337.GA85696@phouka1.phouka.net> <20191007232340.GB85696@phouka1.phouka.net> <20191008172007.GA89365@phouka1.phouka.net> Date: Thu, 10 Oct 2019 19:54:28 +0200 In-Reply-To: <20191008172007.GA89365@phouka1.phouka.net> (John Kennedy's message of "Tue, 8 Oct 2019 10:20:07 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2019 17:54:31 -0000 John Kennedy writes: > On Mon, Oct 07, 2019 at 04:23:40PM -0700, John Kennedy wrote: > >> In any case, this AM, I crunched up the latest 12.1b3 (r353280), upgraded to >> this mornings ports (since I saw wlroots bump up), made sure about the DRM >> driver and have been doing a stress test of sorts. In this case, a poudriere >> run of my ~520 ports and getting my load average up to 12+. Up 2.41 hours >> so far. Previous record was more in tens of minutes as I was doing stuff. > > It made it ~24 hours before I screwed it up (alt-shift-F# console switching). > Looks more like the keyboard was disabled (tested via caps-lock-light test) vs > any kind of video problem. Have to try your trick next time. VT switching is broken in Sway, see https://github.com/swaywm/sway/issues/3612 Other than direct session Sway can use ConsoleKit2 if wlroots is built with CONSOLEKIT port option enabled. But I don't remember if it helps VT swich issue. Or did you mean X11? If so try xf86-video-intel + bug 236003 patch + SNA enabled. Maybe Intel didn't push workarounds for old iGPUs from DDX into kernel. > Any idea if previous crashing might fall under llvm90-compiler issues? i965 unlike iris doesn't use LLVM, so recent LLVM_DEFAULT update should have no impact on Intel iGPUs. Unless CC/CXX is set by user llvm90 is mainly used for libraries, not compiler. > I'm assuming the drm kernel module was fine since X11 seemed happy > with it. I'm mostly running the same old X11 apps (xterm, firefox, > etc) on top of wayland that are fine under X. No clue. Investigating *why* something went wrong is harder than fixing. One way is to make snapshots of the working and non-working state then bisect between those.