From owner-freebsd-arm@freebsd.org Tue Feb 4 20:59:04 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 DAD742342F8 for ; Tue, 4 Feb 2020 20:59:04 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48BxrR4dBjz4XxT; Tue, 4 Feb 2020 20:59:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 014KxBtI048020 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Feb 2020 12:59:12 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 014KxAUJ048019; Tue, 4 Feb 2020 12:59:10 -0800 (PST) (envelope-from fbsd) Date: Tue, 4 Feb 2020 12:59:10 -0800 From: bob prohaska To: Kyle Evans Cc: Ralf Wenk , "freebsd-arm@freebsd.org" Subject: Re: panic: deadlres_td_sleep_q: possible deadlock detected on RPI3 Message-ID: <20200204205909.GA47943@www.zefox.net> References: <20200123164419.GA81833@www.zefox.net> <20200125153229.GA3768@www.zefox.net> <20200126164211.GB7312@www.zefox.net> <20200130162055.GA21879@www.zefox.net> <20200131152343.GA30158@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 48BxrR4dBjz4XxT X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [1.68 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.06)[ip: (0.26), ipnet: 50.1.16.0/20(0.13), asn: 7065(-0.03), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.33)[0.331,0]; NEURAL_HAM_MEDIUM(-0.61)[-0.608,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:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] 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: Tue, 04 Feb 2020 20:59:04 -0000 I've created a bug report on the deadlock panic, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243876 I wonder if it's related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242732 The hardware and some symptoms are different. Both RPI2 and RPI3 display a "waiting for CAM" message, but I've not seen my RPI2 panic yet. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243464 reports a freeze on RPI3 and attributes it to r356776. I wonder of the freeze might have turned into a panic given enough (~20 mins) time. Thanks for reading, bob prohaska