Date: Mon, 9 Jan 2023 12:36:28 -0800 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> Cc: Mitchell Horne <mhorne@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Subject: Re: (RPi) db> reboot -> cpu_reset failed Message-ID: <718AAC84-353A-4187-A6F1-57CB2AE644E0@yahoo.com> In-Reply-To: <2FB2DA46-7BED-46BA-905D-DEAA33E9E1E8@yahoo.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> <8o4s9914-sq84-90pq-no3o-59r18n5on14@yvfgf.mnoonqbm.arg> <e8dd18bf-df8b-5c62-4860-a2bc946e1d00@freebsd.org> <5A57DF73-FEC0-41C9-96D2-A4EED7695EEF@googlemail.com> <2EAD00FA-22AE-4BE8-98B1-BEBB3848C486@yahoo.com> <38B9AB9D-BDA8-4186-AEA7-6F63530FCC68@googlemail.com> <2FB2DA46-7BED-46BA-905D-DEAA33E9E1E8@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 9, 2023, at 11:45, Mark Millard <marklmi@yahoo.com> wrote: > On Jan 9, 2023, at 11:13, Klaus K=C3=BCchemann = <maciphone2@googlemail.com> wrote: >=20 >> Am 09.01.2023 um 17:21 schrieb Mark Millard <marklmi@yahoo.com>: >>> =E2=80=A6 >>> .. >>>=20 >>> I expect the new output text was only the text after the "reset" >>> command: >>>=20 >>> QUOTE >>> Waiting (max 60 seconds) for system process `vnlru' to stop... done >>> Uptime: 1m51s >>> END QUOTE >>> =E2=80=A6. >>>=20 >>> =3D=3D=3D >>> Mark Millard >>> marklmi at yahoo.com >>=20 >>=20 >> Mark, I also don`t see the new expected output text=E2=80=A6 >> do you see any effect , have you tested on an RPI?, >=20 > I've only been reading along, not testing the patches. > (For one, my normal environment has its own patches > involved, making for a unclean test environment if > used.) >=20 >> I would be very happy if I=E2=80=99m mistaken and if it would work.. >> - >> O.K., now tested the new Diff 114868 of D37981, >> Also no effect to =E2=80=9Areset=E2=80=98 by an provocated early = boot panic=E2=80=A6 >>=20 >> I think you`ll need a real hardware debugger to e.g. track the issue = that the software debugger can=E2=80=99t=20 >> execute shutdown_reset(NULL, howto); >=20 > I have no access to such. >=20 >> safely in early boot stage without calling the bcm2835_watchdog = directly :-), >> and you would need it anyway for board bringup issues.. >> Afaik that=E2=80=99s normal on embedded >>=20 >> Please consider this only as a test report, not as a scientific = statement, >> I don`t have any knowledge of db_command.c=20 Given the BOOTTRACE(...) usage that I see, having: kern.boottrace.enabled=3D1 in /boot/loader.conf (or set via the loader?) might prove interesting during the reboot attempt from the db> prompt. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?718AAC84-353A-4187-A6F1-57CB2AE644E0>