Date: Sun, 8 Jan 2023 14:32:34 -0400 From: Mitchell Horne <mhorne@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-arm@freebsd.org Subject: Re: (RPi) db> reboot -> cpu_reset failed Message-ID: <e8dd18bf-df8b-5c62-4860-a2bc946e1d00@freebsd.org> In-Reply-To: <8o4s9914-sq84-90pq-no3o-59r18n5on14@yvfgf.mnoonqbm.arg> 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> <8o4s9914-sq84-90pq-no3o-59r18n5on14@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/5/23 16:23, Bjoern A. Zeeb wrote: > 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* > > The reason for the difference in behaviour here is that the ddb reset command doesn't execute the full list of registered shutdown handlers, it just calls cpu_reset() directly. For whatever reason your combination of RPI hw+fw doesn't support the PSCI shutdown interface, so cpu_reset() fails. I am guessing that it is the bcm2835_watchdog driver that handles the normal reboot. I think it should be just fine to execute such handlers from ddb reset, so you can try my patch: https://reviews.freebsd.org/D37981 Cheers, Mitchell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e8dd18bf-df8b-5c62-4860-a2bc946e1d00>