From nobody Thu Jan 05 20:23:32 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NnybW4blPz2p7Ff for ; Thu, 5 Jan 2023 20:23:35 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NnybW3CyQz3N6f for ; Thu, 5 Jan 2023 20:23:35 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 5227B8D4A142; Thu, 5 Jan 2023 20:23:34 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 09A6A5C3A833; Thu, 5 Jan 2023 20:23:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 1XS84srKZAPw; Thu, 5 Jan 2023 20:23:32 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 79B1E5C3A830; Thu, 5 Jan 2023 20:23:32 +0000 (UTC) Date: Thu, 5 Jan 2023 20:23:32 +0000 (UTC) From: "Bjoern A. Zeeb" To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= cc: freebsd-arm@freebsd.org Subject: Re: (RPi) db> reboot -> cpu_reset failed In-Reply-To: <38B92299-2776-476D-A81F-7C8EB4D59A13@googlemail.com> Message-ID: <8o4s9914-sq84-90pq-no3o-59r18n5on14@yvfgf.mnoonqbm.arg> References: <29q7q878-091-r17n-8r3n-o3n68p3646@mnoonqbm.arg> <38B92299-2776-476D-A81F-7C8EB4D59A13@googlemail.com> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1098556516-1840519658-1672950212=:27118" X-Rspamd-Queue-Id: 4NnybW3CyQz3N6f X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-1840519658-1672950212=:27118 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 5 Jan 2023, Klaus Küchemann wrote: > Hi Björn, > ( ..I had a JTAG setup on the PI, but didn’t use it for some time..) > > yes that was a "live“ boot example from today of the cm4(on orig. I/O-board), > it hangs while initializing sdhci, while the boot partition is living on the emmc : > — Ok, I am just wondering given reboot works fine why reset in db> wouldn't. Given you have JTAG setup you can probably debug a lot better than me but also you seem to have a different problem ... too many problems too short time *sigh* >> Am 05.01.2023 um 19:48 schrieb Bjoern A. Zeeb : >> >> On Thu, 5 Jan 2023, Klaus Küchemann wrote: >> >> Hi Klaus, >> >>>> Am 05.01.2023 um 17:37 schrieb Bjoern A. Zeeb : >>>> >>>> Hi, >>>> >>>> given I currently find myself debugging more PIs again, what is needed >>>> to be able to reset from the db> prompt? >>>> >>>> Currently I get "cpu_reset failed" when trying. >>>> >>>> Needing remote hands or an OOB PDU to cycle the PI is not satisfying. >>>> >>>> /bz >>>> >>>> -- >>>> Bjoern A. Zeeb r15:7 >>>> >>> >>> >>> you even cannot be sure to reach the ddb prompt at panic, like here : >>> >>> -- >>> .. >>> KDB: stack backtrace: >>> .. >>> #14 0xffff0000000008b4 at virtdone+0x78 >>> Uptime: 1s >>> -- >>> ..and good night Pi .. >>> >>> halt/resume of CPU is more promising by setting up a JTAG controller. >> >> does this mean you are running into the issue at boot as well or was >> that just a (made up) example? >> >> -- >> Bjoern A. Zeeb r15:7 > > > > -- Bjoern A. Zeeb r15:7 --1098556516-1840519658-1672950212=:27118--