Date: Mon, 27 Mar 2023 23:43:35 +0200 From: Mathias Picker <Mathias.Picker@virtual-earth.de> To: Cy Schubert <Cy.Schubert@cschubert.com>, Shane Ambler <FreeBSD@ShaneWare.Biz> Cc: FreeBSD-STABLE <freebsd-stable@freebsd.org> Subject: =?US-ASCII?Q?Re=3A_-stable_from_today_dumps_core_with_?= =?US-ASCII?Q?drm-510-kmod_and_some__graphical_clients?= Message-ID: <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> In-Reply-To: <20230327210535.9ED5A1D7@slippy.cwsent.com> References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 27=2E M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert <Cy=2ESchubert@cs= chubert=2Ecom>: >In message <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare=2EBiz>, Shane= =20 >Ambler w >rites: >> On 26/3/23 01:37, Mathias Picker wrote: >> >=20 >> > Starting sddm works fine, starting my normal session crashes or freez= es >> > FreeBSD=2E >> >=20 >> > I can find no error messages after a reboot=2E >> >=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 FreeBS= D >> > even reboots=2E >> >=20 >> > =C3=A2=C2=80=C2=9CDemanding=C3=A2=C2=80=C2=9D means even simple thing= s like qterminal=2E I tried firefox an >> d >> > blender and then I had it with the reboots and didn=C3=A2=C2=80=C2=99= t try anything else=2E >> > xedit works fine :) >> >=20 >> > I have nothing in the logs, I have no idea where to look or how to de= bug >> > this=2E >> >=20 >> > Any ideas, tipps, help greatly apreciated=2E >> >> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging >> >> https://docs=2Efreebsd=2Eorg/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=2Econf= ) 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 ge= t >> a stack trace to find where the panic happened=2E > >drm-*-kmod probably needs a rebuild=2E Likely a data structure changed=2E= In my=20 >experience a simple rebuild of the port solves 90% of drm-*-kmod crash=20 >problems=2E > Hi Cy, 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=2E I switched my swap to non-encrypted and will look if I can get any informa= tion from the kernel dump tomorrow=2E Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I didn't mentio= n this=2E Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?044587F7-4BA9-4585-A789-F4B53E8D02A2>