Date: Thu, 5 Jan 2023 20:23:32 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> Cc: freebsd-arm@freebsd.org Subject: Re: (RPi) db> reboot -> cpu_reset failed Message-ID: <8o4s9914-sq84-90pq-no3o-59r18n5on14@yvfgf.mnoonqbm.arg> In-Reply-To: <38B92299-2776-476D-A81F-7C8EB4D59A13@googlemail.com> References: <29q7q878-091-r17n-8r3n-o3n68p3646@mnoonqbm.arg> <F4435E57-1F90-454D-8E75-01DF50DD37DA@googlemail.com> <np4qps4-2o34-3n9n-q4s4-4931p4s7p13@yvfgf.mnoonqbm.arg> <38B92299-2776-476D-A81F-7C8EB4D59A13@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <bzeeb-lists@lists.zabbadoz.net>: >> >> On Thu, 5 Jan 2023, Klaus Küchemann wrote: >> >> Hi Klaus, >> >>>> Am 05.01.2023 um 17:37 schrieb Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net>: >>>> >>>> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8o4s9914-sq84-90pq-no3o-59r18n5on14>