Date: Thu, 30 Jan 2020 08:20:55 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Ralf Wenk <iz-rpi03@hs-karlsruhe.de> Cc: freebsd-arm@freebsd.org Subject: Re: panic: deadlres_td_sleep_q: possible deadlock detected on RPI3 Message-ID: <20200130162055.GA21879@www.zefox.net> In-Reply-To: <20200126164211.GB7312@www.zefox.net> References: <20200123164419.GA81833@www.zefox.net> <20200125153229.GA3768@www.zefox.net> <E1ivfCl-0073zQ-M1@smtp.hs-karlsruhe.de> <20200126164211.GB7312@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Thanks for reading! bob prohaska > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200130162055.GA21879>