On Sat, Jan 15, 2022 at 08:14:43PM -0500, Ryan Kavanagh wrote:
> On Sun, Jan 16, 2022 at 09:41:26AM +1100, Jonathan Gray wrote:
> > On Sat, Jan 15, 2022 at 01:36:55PM -0500, Agnosto Dvonik wrote:
> > > I have also noticed that the fans in the system start to whirr a bit
> > > more when this happens than in normal usage. [...]
> > >     panic: kernel diagnostic assertion "p -> p_wchan == NULL" failed: file
> > > "/usr/src/sys/kern/kern_sched.c", line 355
> 
> Could this be related to the bug I reported on 2022-01-13 in
> <[email protected]>? I got the same panic
> involving the same line number, albeit after following the sequence of
> steps described there. I also get the system fan starting to whirr right
> after the panic. I can still reproduce this bug on #253 (the latest
> snapshot that was available to me via sysupgrade just now).

This report I believe is related to the recent drm changes.
Your snapshot and mail are before that was committed.

> 
> > Can you try with 'sysctl kern.splassert=2' that should print a stack
> > trace to show where this is coming from.
> 
> I tried doing so, but got no stack trace after the lockup. The last
> message in ttyC0 before my system locks up is the above panic. I have
> seen similar splassert messages at other times though and will provide a
> stack trace the next time I see them.
> 
> Best,
> Ryan
> 
> -- 
> |)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
> |\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A
> 
> 

Reply via email to