From nobody Fri Sep 9 14:14:44 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 4MXqby06Ylz4cD6p for ; Wed, 21 Sep 2022 20:23:10 +0000 (UTC) (envelope-from lists@nrd.fr) Received: from 15.mo584.mail-out.ovh.net (15.mo584.mail-out.ovh.net [91.121.62.11]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MXqbx0DMtz3kRx for ; Wed, 21 Sep 2022 20:23:09 +0000 (UTC) (envelope-from lists@nrd.fr) Received: from player168.ha.ovh.net (unknown [10.109.156.34]) by mo584.mail-out.ovh.net (Postfix) with ESMTP id 03D9E24C97 for ; Wed, 21 Sep 2022 20:23:06 +0000 (UTC) Received: from dagorret.eu (lfbn-bay-1-335-219.w90-54.abo.wanadoo.fr [90.54.54.219]) (Authenticated sender: benat@dagorret.eu) by player168.ha.ovh.net (Postfix) with ESMTPSA id 802B92ED1A6E9; Wed, 21 Sep 2022 20:23:05 +0000 (UTC) X-OVh-ClientIp:90.54.54.219 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 Date: Fri, 09 Sep 2022 16:14:44 +0200 From: =?UTF-8?Q?Be=C3=B1at_Dagorret?= To: jbeich@FreeBSD.org Cc: Freebsd X11 Subject: Re: Problem Report: i915 driver most probably causing freezes on FreeBSD 13.1-RELEASE Reply-To: lists@nrd.fr Mail-Reply-To: lists@nrd.fr In-Reply-To: References: Message-ID: X-Sender: lists@nrd.fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Ovh-Tracer-Id: 8262416470623519950 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvfedrfeefuddgudehtdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeggfffhvfevufhrjghfkfigtgfgsehtkehjtddttdejnecuhfhrohhmpeeuvgpirghtpgffrghgohhrrhgvthcuoehlihhsthhssehnrhgurdhfrheqnecuggftrfgrthhtvghrnhepvdfffeeugefhjefgvefgfeegfeeutddtteejleefudeiieehffeuvddvfeeuleelnecuffhomhgrihhnpehfrhgvvgguvghskhhtohhprdhorhhgnecukfhppedtrddtrddtrddtpdeltddrheegrdehgedrvdduleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtpdhhvghlohepphhlrgihvghrudeikedrhhgrrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpehlihhsthhssehnrhgurdhfrhdpnhgspghrtghpthhtohepuddprhgtphhtthhopehfrhgvvggsshguqdiguddusehfrhgvvggsshgurdhorhhgpdfovfetjfhoshhtpehmohehkeeg X-Rspamd-Queue-Id: 4MXqbx0DMtz3kRx X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@nrd.fr designates 91.121.62.11 as permitted sender) smtp.mailfrom=lists@nrd.fr X-Spamd-Result: default: False [-2.39 / 15.00]; DATE_IN_PAST(1.00)[294]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; R_SPF_ALLOW(-0.20)[+ptr:mail-out.ovh.net]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[91.121.62.11:from]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[nrd.fr]; PREVIOUSLY_DELIVERED(0.00)[freebsd-x11@freebsd.org]; HAS_REPLYTO(0.00)[lists@nrd.fr]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; RCVD_IN_DNSWL_NONE(0.00)[91.121.62.11:from]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-x11@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N On 2022-09-21 21:00, Jan Beich wrote: > (Disclaimer: I'm on wlroots (Wayland), so can't help much with Xorg > (X11) issues) > Hi Jan. Thank you for replying, any hint is much appreciated indeed. > Beñat 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? I don't know these tools but I will look further and give them a try to see what happens. >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x06 hdr=0x00 vendor=0x8086 >> device=0x0402 subvendor=0x103c subdevice=0x21d0 >> vendor = 'Intel Corporation' >> device = 'Xeon E3-1200 v3/4th Gen Core Processor Integrated >> Graphics Controller' >> class = display >> subclass = VGA >> bar [10] = type Memory, range 64, base 0xf7800000, size 4194304, >> enabled >> bar [18] = type Prefetchable Memory, range 64, base 0xe0000000, >> size 268435456, enabled >> bar [20] = type I/O Port, range 32, base 0xf000, size 64, >> enabled >> cap 05[90] = MSI supports 1 message enabled with 1 message >> cap 01[d0] = powerspec 2 supports D0 D3 current D0 >> cap 13[a4] = PCI Advanced Features: FLR TP > > 0x0402 is Haswell, so OpenGL is driven by either i965 or crocus. In > graphics/mesa-dri > crocus is currently disabled by default unless > MESA_LOADER_DRIVER_OVERRIDE=crocus, see > https://gitlab.freedesktop.org/mesa/mesa/-/commit/988762679ccf Yes it is Haswell. When the xf86-video-intel driver is loaded, instead of modesetting, i965 gets loaded too. > src/loader/meson.build: > _prefer_crocus = get_option('prefer-crocus') > if _prefer_crocus == 'auto' > _prefer_crocus = 'false' > endif > > Maybe try crocus from graphics/mesa-devel. i965 is gone upstream (Mesa > >= 22.0.0). > Thank you for the tip. I think I remember seeing crocus in Xorg.0.log once I booted the system from a live Linux distro. I didn't know what it was and where it was coming from (I had radeon/glamor cards until now). I will check the Xorg.log from the Linux distro again and definitely give crocus a try. >> [ 11.994] >> 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). Will try this too, it's a fresh install so nothing to lose and so much to learn :-) >> [ 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? I didn't see anything suspicious either, and the xf86-video-intel version of the Xorg.log is quite clean too. And yes, I think it is the log from Xorg (located at /var/log/Xorg.0.log). But it's not modified by the crash: no messages are appended when the server freezes. Unless I'm missing something here. Thank you again, I'm pretty confident about the crocus option. Regards.