Date: Thu, 13 Apr 2023 22:44:04 -0700 From: Mark Millard <marklmi@yahoo.com> To: Warner Losh <imp@bsdimp.com> Cc: bob prohaska <fbsd@www.zefox.net>, Steve Rikli <sr@genyosha.net>, Marcin Cieslak <saper@saper.info>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Boot stops at loader after build/install cycle Message-ID: <A5663A3A-5D1C-41C8-B982-25F65A476328@yahoo.com> In-Reply-To: <7D3F4842-CC76-4A9A-8488-50B4E6AB440E@yahoo.com> References: <20230327164919.GA65182@www.zefox.net> <CANCZdfrwUXgL8K-ZXMS770oM7W8WyVEPSQt9acbUhFfk1D032A@mail.gmail.com> <ZCHV57OZuXxI5xu3@dragon.home.genyosha.net> <20230327183055.GB65182@www.zefox.net> <44509923-0218-5no7-42pp-90ss0sns9457@fncre.vasb> <20230329164845.GA75320@www.zefox.net> <or45n234-96pp-9sn7-2qpn-s2np14776oo3@fncre.vasb> <ZCThLNuAuBhSSH1h@dragon.home.genyosha.net> <20230330152728.GA79440@www.zefox.net> <CANCZdfo=cq7Axi3giqCuVz68_QHKRFF5M=wbknNn7RV8RbojcQ@mail.gmail.com> <7D3F4842-CC76-4A9A-8488-50B4E6AB440E@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 13, 2023, at 21:49, Mark Millard <marklmi@yahoo.com> wrote: > On Mar 30, 2023, at 10:40, Warner Losh <imp@bsdimp.com> wrote: >=20 >> On Thu, Mar 30, 2023 at 9:27=E2=80=AFAM bob prohaska = <fbsd@www.zefox.net> wrote: >> On Wed, Mar 29, 2023 at 06:09:00PM -0700, Steve Rikli wrote: >>> On Thu, Mar 30, 2023 at 12:24:13AM +0000, Marcin Cieslak wrote: >>>>=20 >>>> The characters look too regular to me, just like a normal terminal >>>> codes, not a line noise. I test the device now powered from the >>>> same USB hub as the USB-serial converter. Rockchip needs 1500000 = bps >>>> console, pretty fest. >>>=20 >>> OK, then let's assume your serial cables & hoods etc. are OK for the >>> moment. What does serial console config on the rpi look like? >>>=20 >>> When I specified the rpi4 serial console speed in the config to = match my >>> serial terminal server, rather than let it "float" (default 9600), = my >>> loader interruptions stopped, and no more stray characters on the = serial >>> console after boot either. >>>=20 >>>> Also, uboot autoboot prompt never gets interrupted. >>>>=20 >>>> I also noticed that "resizewin" complains about not getting >>>> information about the terminal upon login on the serial console >>>> while being in the vt(4) text mode. >>>>=20 >>>> Looks like the bootloader tries to send/receives some terminal = control >>>> sequences and this fails, interupting the autoboot. >>>=20 >>> It may be something along those lines. When I was getting loader = stops >>> during reboot on my rpi4, my guess was the default FreeBSD speed = 9600 >>> vs. my serial terminal server setting of 115200 was causing stray >>> characters on the line during boot, loader interpretted that as a >>> keystroke, so it stopped. >>=20 >> Where are you setting the serial console to 9600 baud? AIUI the >> Pi defaults to 115200, can it be set in config.txt? >=20 > [FYI: my context is 115200 based throughout.] >=20 >> The sequence ending in R is indeed "report cursor location" so it's = the result >> of resizewin not reading it and leaving that around maybe? Or = something else >> sending the Query Cursor Location and then not reading it. >>=20 >> = https://www.cse.psu.edu/~kxc104/class/cmpen472/11f/hw/hw7/vt100ansi.htm >=20 > FYI: I just booted a 2023-Apr-13 snapshot and saw the behavior > for the first time: "0;200R" at the boot prompt (the window > being 60 lines by 200 columns). I had not seen this with the > Apr-06 snapshot or before, although normally my snapshot > updates have been very rare, not two weeks in a row. >=20 > I deleted the 0;200R text and typed boot to manually continue > the boot. (Yes: the "6" was not present.) >=20 > A "shutdown -r now" sequence did not get the problem. >=20 > It leaves me wondering about varaibility in the u-boot > to FreeBSD-loader transition's handling of things or > other sources of variability in the handling in the > loader. >=20 > I'll see if I can get a capture of the byte stream with > an example of the extra text (apparently via power-on). No repetition so far. But I can report that the prior <ESC>[6n (Query Cursor Position) before the FreeBSD loader's OK prompt is during U-Boot activity: part of the escpe sequences just after: Device 0: Vendor: OWC Rev: 0 Prod: Envoy Pro mini =20 Type: Hard Disk Capacity: 228936.5 MB =3D 223.5 GB (468862128 x 512) ... is now current device Scanning usb 0:1... This suggests that U-Boot failed to read/clear some of the Report Cursor Position text --and that the loader accepts what it finds already present (probably so that typing ahead of time would work). So: Looks to me like a probable U-Boot issue for which a FreeBSD workaround to ignore text would have other consequences (lack of effective typeahead for the loader 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?A5663A3A-5D1C-41C8-B982-25F65A476328>