From nobody Wed Sep 21 19:00:13 2022 X-Original-To: freebsd-x11@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 4MXnmL5d4Yz4dH7s for ; Wed, 21 Sep 2022 19:00:18 +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) 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 4MXnmL4xwgz3dCy; Wed, 21 Sep 2022 19:00:18 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663786818; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xSCs0tMBKUmr0ucuMBzKoxlgUsaB0fYjxUVj6hvFQ2w=; b=wklS3g5kwl7IwbUG82z9bodWcaowLfIP+kVpN6EYAZcg1lQjAI9cp/oIYmOcRycZSbWStw bZFeSmUfDabAP9jNbkO36uCienpRgDebp061JClAJswCZHjU2v5dt5gcBkP4UHmP4VZX5x hBlLeBROxBTUD5Szfxj/0Ys32XlUXlf/mlqVdqz/1nhk1dTE/4kY7T4HxlGPexzlrajCcb HrZ2XHEwOtSVWAJ/DqANGfVOL2xwFENjShAHaCLXiF/xXCdSaC0sF/FtG17zDRH+N5lItt ULWMEbIcX3wqoBU6YS/IOHc5UHUWGx/7cLO6YkehTSxQKkr1RJvjZ1g03IbuIw== Received: by freefall.freebsd.org (Postfix, from userid 1354) id 8474F1F728; Wed, 21 Sep 2022 19:00:18 +0000 (UTC) From: Jan Beich To: =?utf-8?Q?Be=C3=B1at?= Dagorret Cc: freebsd-x11@freebsd.org Subject: Re: Problem Report: i915 driver most probably causing freezes on FreeBSD 13.1-RELEASE In-Reply-To: (=?utf-8?Q?=22Be?= =?utf-8?Q?=C3=B1at?= Dagorret"'s message of "Fri, 09 Sep 2022 12:42:53 +0200") References: Date: Wed, 21 Sep 2022 21:00:13 +0200 Message-ID: List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663786818; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xSCs0tMBKUmr0ucuMBzKoxlgUsaB0fYjxUVj6hvFQ2w=; b=VuJVyXNRQ07431ngyaXgg4/5kytzP8C8lwu6VblmOHv+sZBIXPd0AlcAxrb6ILsu3fY0EQ wzw1XharFCl8iUV8FRnsbqkUng/TFYdGl0RyaBJyxc+5CBEWq67U/YCv+KG5U56+k/XSvZ AmWwRy50cgQKYo+/HpWFyDRnsENgBLMzyGHhS6U0OUaSWoHvEh8rn7Xx8xJsiPueICKUnZ d7aUWBP+96wjKqyYNWIQRZzUtmVr9Y8LFaioc9HzDrJ5i/w6nD4SBgNzk/sGXisCNKwJm+ R4SukeoIVdAhurGpp4yCB3M+4nLc4ybhuQqLVay+5e61cJuPWXatoe0J28DiWw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1663786818; a=rsa-sha256; cv=none; b=bK+z71H8R1UCpkS+EVDA0ze6JDPaf+T0kT8W3D5zyPF8VXfG95eB0+ZY5Gs3GqG4tvDPfj Eb/h0Kbu/9wL2pvutGAxMrnCjEVTglvnerX4RzwOLdAfM5QoQ3Arxft557lOmJmt6D27eI BBNiBPyrWTHRHqiQ1XC7jcZqtaC9UtlqZmeSR1upolIYKJ4hiZ62xv/iJ9D9ojzohenwSi S/vwM2q1VATF5uhZxDa0L5ZLF+ecOe1DWR5b5YU/19tEauDOWSJP4YSnueo7VaK4dI/OdH F1UIgvImbX4PUhn6M1RBEMmCqIzaL7IsP/wq/c1Z3wjCNeKsl3TBz/kDJHrrmQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N (Disclaimer: I'm on wlroots (Wayland), so can't help much with Xorg (X11) i= ssues) Be=C3=B1at Dagorret writes: > Hello, > > I'm having an issue with the i915kms driver on a fresh FreeBSD > 13.1-RELEASE install. The system boots and shows the Display Manager > (LightDM) without any problem, but after logging in, X crashes leaving > a black screen and a dead keyboard. The crash occurs always about 3 > seconds after user login, no matter there was any user activity. I > need to shutdown the system remotely from my laptop through ssh. Can you trigger OpenGL crash via graphics/kmscube or glmark2-drm from benchmarks/glmark2 when running under console? > vgapci0@pci0:0:2:0: class=3D0x030000 rev=3D0x06 hdr=3D0x00 vendor=3D0x808= 6 device=3D0x0402 subvendor=3D0x103c subdevice=3D0x21d0 > vendor =3D 'Intel Corporation' > device =3D 'Xeon E3-1200 v3/4th Gen Core Processor Integrated Gra= phics Controller' > class =3D display > subclass =3D VGA > bar [10] =3D type Memory, range 64, base 0xf7800000, size 4194304, = enabled > bar [18] =3D type Prefetchable Memory, range 64, base 0xe0000000, s= ize 268435456, enabled > bar [20] =3D type I/O Port, range 32, base 0xf000, size 64, enabled > cap 05[90] =3D MSI supports 1 message enabled with 1 message > cap 01[d0] =3D powerspec 2 supports D0 D3 current D0 > cap 13[a4] =3D PCI Advanced Features: FLR TP 0x0402 is Haswell, so OpenGL is driven by either i965 or crocus. In graphic= s/mesa-dri crocus is currently disabled by default unless MESA_LOADER_DRIVER_OVERRIDE= =3Dcrocus, see https://gitlab.freedesktop.org/mesa/mesa/-/commit/988762679ccf src/loader/meson.build: _prefer_crocus =3D get_option('prefer-crocus') if _prefer_crocus =3D=3D 'auto' _prefer_crocus =3D 'false' endif Maybe try crocus from graphics/mesa-devel. i965 is gone upstream (Mesa >=3D= 22.0.0). > [ 11.994]=20 > X.Org X Server 1.20.14 > X Protocol Version 11, Revision 0 Try upgrading xorg-server to 21.1.4 by switching to /latest package repo. 1.20.14 on /quarterly will be unsupported after 2022Q3 branch EOL around 2022-10-01 (~1 week from now). > [ 12.593] (II) event5 - Logitech USB Optical Mouse, class 0/0, rev 2.= 00/72.00, addr 3: is tagged by udev as: Mouse > [ 12.594] (II) event5 - Logitech USB Optical Mouse, class 0/0, rev 2.= 00/72.00, addr 3: device is a pointer Looking at the end of Xorg.log I don't see anything suspicious. Is it really the log from when Xorg crashed and not from a separate instance run by the Display Manager?