panic: deadlres_td_sleep_q: possible deadlock detected on RPI3

[Paul Mather]

On Jan 30, 2020, at 11:20 AM, bob prohaska <fbsd at www.zefox.net> wrote:

> On Sun, Jan 26, 2020 at 08:42:11AM -0800, bob prohaska wrote:
>> On Sun, Jan 26, 2020 at 11:31:47AM +0100, Ralf Wenk wrote:
>>> 
>>> 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
>>> 
>> 
> My Pi3 still panics at r357204, but ntp seems to work fine.
> One other oddity: During the loader countdown to boot, time
> seems to run about 5x slower than it should, each second
> on the screen taking about five seconds. The string 
> deadlres_td_sleep_q turns up in sys/kern/kern_clock.c,
> might there be a connection between the panic and the
> very slow boot countdown?


I don't get a panic on my Pi 3, but the really odd thing is that for quite a while I USED to get that slow boot loader countdown that you describe.  Now, it has gone away.  I first noticed it gone at r357051, and it is still gone after I updated very recently due to the security advisories.  (I'm now at r357230 on 12-STABLE.)

Cheers,

Paul.