From owner-freebsd-arm@freebsd.org Sun Jan 26 10:31:50 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4ED1E238610 for ; Sun, 26 Jan 2020 10:31:50 +0000 (UTC) (envelope-from iz-rpi03@hs-karlsruhe.de) Received: from smtp.hs-karlsruhe.de (smtp.HS-Karlsruhe.DE [193.196.64.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4858Ls1Dgyz3Lts for ; Sun, 26 Jan 2020 10:31:48 +0000 (UTC) (envelope-from iz-rpi03@hs-karlsruhe.de) Received: from iz-wera01.hs-karlsruhe.de ([193.196.65.46]) by smtp.hs-karlsruhe.de with esmtp (Exim 4.80.1) (envelope-from ) id 1ivfCl-0073zQ-M1; Sun, 26 Jan 2020 11:31:47 +0100 X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.6 From: Ralf Wenk To: bob prohaska cc: freebsd-arm@freebsd.org Subject: Re: panic: deadlres_td_sleep_q: possible deadlock detected on RPI3 In-reply-to: <20200125153229.GA3768@www.zefox.net> References: <20200123164419.GA81833@www.zefox.net> <20200125153229.GA3768@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jan 2020 11:31:47 +0100 Message-Id: X-Rspamd-Queue-Id: 4858Ls1Dgyz3Lts X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of iz-rpi03@hs-karlsruhe.de has no SPF policy when checking 193.196.64.25) smtp.mailfrom=iz-rpi03@hs-karlsruhe.de X-Spamd-Result: default: False [5.13 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; IP_SCORE(0.10)[asn: 553(0.49), country: EU(-0.01)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[hs-karlsruhe.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.74)[0.735,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[25.64.196.193.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.89)[0.894,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:553, ipnet:193.196.64.0/18, country:EU]; RCVD_COUNT_TWO(0.00)[2]; RBL_SENDERSCORE(2.00)[25.64.196.193.bl.score.senderscore.com] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2020 10:31:50 -0000 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