Re: drm panic after new world

On Fri, Jun 06, 2025 at 07:29:27PM -0700, Steve Kargl wrote:
> 
> I've narrowed the range to
> 
> Good: 2025-04-24 9b2a503a1179 - main - e6000sw: add support for 88E6190X
>  Bad: 2025-04-29 6c3a4b5f9b7b - main - alloca.3: move to share/man/man3
> 
> Good means boots and startx does not panic.  dump_stack() in evergreen.c
> reports one initialization event.
> 
> Bad means boots and startx panics. dump_stack() in evergreen.c shows that
> radeon is trying to initialized twice.
> 
> The commit 28efbf9d2f67 is within this range, but I've run out of time
> until monday.
> 

Coming full circle.  Comment #19 from 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287165


I found it.  It's markj's commit about jiffies.  The four consecutive
commits are 

4fa275a5f357 -main- queue(3): Add simple tests for...  Olivier Certner
325aa4dbd10d -main- linuxkpi: Introduce a properly typed jiffies Mark Johnston
901256f6ea3c -main- mlx5: jiffies is unsigned long Mark Johnston
87e57632bf88 -main- ofed: jiffies is unsigned long Mark Johnston

4fa275a boots, I can kldload radeonkms.ko, and startx brings up my desktop.
In fact, I'm typing this in firefox at the moment.  There is only dump_stack()
message from evergreen.c

87e5763 boots, I can kldload radeonkmd.ko, and startx causes a panic.
My custom kernel uses neither mlx5 nor ofed.  That leaves 325aa4d as
the commit causing an issue. There are two dump_stack() message from
evergreen.c in /var/crash/core.txt.3


-- 
Steve