panic: deadlres_td_sleep_q: possible deadlock detected on RPI3

[bob prohaska]

On Sun, Jan 26, 2020 at 11:31:47AM +0100, Ralf Wenk wrote:
> On 2020-01-25 at 7:32 -0800 bob prohaska wrote:
> > On Thu, Jan 23, 2020 at 08:44:19AM -0800, bob prohaska wrote:
> > > My Pi3 running -current r356835 reported:
> > > 
> > > panic: deadlres_td_sleep_q: possible deadlock detected for 0xfffffd0000eff000, blocked for 1800305 ticks
> > > 
> > [backtrace omitted]
> 
> I got this panic two times in a row with a r357112 kernel during
> make installworld at the same place. So it looks like I am able to
> reproduce it. 
> 
> # panic: deadlres_td_sleep_q: possible deadlock detected for
>   0xfffffd0000f33560, blocked for 1802833 ticks
> 
> But I think it is just a symptom of the r356776 changes.
> 
> > Attempts to reboot are also rebuffed with 
> > cpu_reset failed
> > leaving a power cycle as the only option, which is new to me.
> > 
> > Does this give any hints as to what's going on?
> 
> After doing the update from r356767 to r356776 my system began to
> show the "cpu_reset failed" message as well.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243464
> 
> Ralf
> 
My machine doesn't get so far as installworld, it panics much
earlier, somewhere in buildworld. In at least one case buildworld
stopped on an error, and the panic happened anyway, somewhat later.

As a possibly-unrelated aside, OOMA kills are back on the same
machine after a lengthy interval of peace and quiet....

Thanks for writing!

bob prohaska