Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Mar 2023 14:05:35 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        Shane Ambler <FreeBSD@ShaneWare.Biz>
Cc:        Mathias Picker <Mathias.Picker@virtual-earth.de>, FreeBSD-STABLE <freebsd-stable@freebsd.org>
Subject:   Re: -stable from today dumps core with drm-510-kmod and some  graphical clients
Message-ID:  <20230327210535.9ED5A1D7@slippy.cwsent.com>
In-Reply-To: <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>
References:  <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Shane 
Ambler w
rites:
> On 26/3/23 01:37, Mathias Picker wrote:
> > 
> > Starting sddm works fine, starting my normal session crashes or freezes
> > FreeBSD.
> > 
> > I can find no error messages after a reboot.
> > 
> > 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 FreeBSD
> > even reboots.
> > 
> > “Demanding” means even simple things like qterminal. I tried firefox an
> d
> > blender and then I had it with the reboots and didn’t try anything else.
> > xedit works fine :)
> > 
> > I have nothing in the logs, I have no idea where to look or how to debug
> > this.
> > 
> > Any ideas, tipps, help greatly apreciated.
>
>
> 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="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 get
> a stack trace to find where the panic happened.

drm-*-kmod probably needs a rebuild. Likely a data structure changed. In my 
experience a simple rebuild of the port solves 90% of drm-*-kmod crash 
problems.


-- 
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=0





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230327210535.9ED5A1D7>