Date: Mon, 27 Mar 2023 14:56:29 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Mathias Picker <Mathias.Picker@virtual-earth.de> Cc: Shane Ambler <FreeBSD@ShaneWare.Biz>, FreeBSD-STABLE <freebsd-stable@freebsd.org> Subject: Re: -stable from today dumps core with drm-510-kmod and some graphical clients Message-ID: <20230327145629.3b55eed8@slippy> In-Reply-To: <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com> <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Mar 2023 23:43:35 +0200 Mathias Picker <Mathias.Picker@virtual-earth.de> wrote: > Am 27. M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert <Cy.Schubert@csch= ubert.com>: > >In message <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Shane=20 > >Ambler w > >rites: =20 > >> On 26/3/23 01:37, Mathias Picker wrote: =20 > >> >=20 > >> > Starting sddm works fine, starting my normal session crashes or free= zes > >> > FreeBSD. > >> >=20 > >> > I can find no error messages after a reboot. > >> >=20 > >> > I found out, that I can start xterm or emacs (exwm) without problems, > >> > xrandr works with external screen, but once I start anything more > >> > demanding (I guess demanding of the GPU) everything freezes or FreeB= SD > >> > even reboots. > >> >=20 > >> > =C3=A2=C2=80=C2=9CDemanding=C3=A2=C2=80=C2=9D means even simple thin= gs like qterminal. I tried firefox an =20 > >> d =20 > >> > blender and then I had it with the reboots and didn=C3=A2=C2=80=C2= =99t try anything else. > >> > xedit works fine :) > >> >=20 > >> > I have nothing in the logs, I have no idea where to look or how to d= ebug > >> > this. > >> >=20 > >> > Any ideas, tipps, help greatly apreciated. =20 > >> > >> > >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging > >> > >> https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ > >> > >> Running stable, kernel dumps may already be enabled, look in /var/crash > >> > >> By enabling a kernel dump when it panics (dumpdev=3D"AUTO" in rc.conf)= the > >> kernel core is saved to swap space, then on reboot gets copied to > >> dumpdir (/var/crash) where you can then use kgdb (from devel/gdb) to g= et > >> a stack trace to find where the panic happened. =20 > > > >drm-*-kmod probably needs a rebuild. Likely a data structure changed. In= my=20 > >experience a simple rebuild of the port solves 90% of drm-*-kmod crash=20 > >problems. > > =20 > Hi Cy, >=20 > sorry I didn't mention that, but I did rebuild drm-kmod, I actually do it= after every new kernel build, just to be on the safe side. >=20 > I switched my swap to non-encrypted and will look if I can get any inform= ation from the kernel dump tomorrow. >=20 > Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I didn't menti= on this. It may be worth trying drm-515-kmod as some MFC that works with 515 and not 510 may have been committed. Linux-KPI commits are the usual suspects. I use drm-515 with 14-CURRENT. --=20 Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=3D0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230327145629.3b55eed8>