From nobody Thu Mar 30 17:40:27 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 4PnW0n20LWz42509 for ; Thu, 30 Mar 2023 17:40:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PnW0m6ydJz4YKd for ; Thu, 30 Mar 2023 17:40:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x533.google.com with SMTP id i5so79785469eda.0 for ; Thu, 30 Mar 2023 10:40:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1680198039; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Qq8cPvtoOYwZaWicwZIoeAZVI1aPlzahEYvjRPXhPRg=; b=ZVW2YGai/+Q87afxDNp/uyVmAjDMAuuZmS07dx/gmJIPgVGrDzvBBrIFlPJ8UmD2Cf +OG5sb2pWNDTM3KVQR8tODQ4cnbkEgw3cjcHxLHqTMvMn7O6O75GQnk+WnrguiB6nYzC 51p8febmLFtJ4UrgOV43/wiY73HpGoGkUEvr6iHzhFRVjV8P2/OFX7xT8cmKLvSwduhf 3NTIgc9sZUX8Ou3TXpodcyXOWnLI8MdHbj0RiYg31FF2b0vp827XTkJmUftqYu26WoG/ rApaZt0I7HxHIfNti3KZPV/lgc1XWovqDEW1i21og6nafc/fRfGXNg9HB0MPEhJ9v0QL jALg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680198039; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Qq8cPvtoOYwZaWicwZIoeAZVI1aPlzahEYvjRPXhPRg=; b=OatnoMW/v1VABD5jQO9RRe0r1c5XOTthOjKeD7wUKZLdusLP9nBWr32bNebJVfs0PS cmnhqSoSO0vqtduyaXVD3ZdkUhLZ23hp8z56/5kkrp94BqXyWCKtMyPmE6jOXnFoonSX QFksovlu9IxHImyL42+3DjIO6kQbzr8qD0sE5xv71XwEgjwQBLslLj/olhE0rz7/Qb6a BgUD7a6yxrXP9HXUh0YGSCK7iTlg1+ZmcytiYYxnRK8QjPwFS/xztnmE0i9Sy2Dvgapa a4B0V0ruOHW2OnpWNoHQz5nvxKhDt+qgqfjiZFwkAtDT5ZIeca+t6jxwJdEWcH8ac5dz EqkA== X-Gm-Message-State: AAQBX9cUbuWtA+Iyms9SCJSe814Ai/8lkiVMyfj3sXhsWzuY0Rzc6nqs LsKmg4+oxPTDBVXBq3H7L1zf9tIUtWPQKNTxga8QVZjEeQ7NtAxGFSI= X-Google-Smtp-Source: AKy350aror0A/2LM3k8LmsFqiOqIjdZG6dJKsLmuOkV3dkRUMfX9bGXIUDgv/QJ/PBbvMF1/UK9x3SGTidNl098x6V0= X-Received: by 2002:a50:9f09:0:b0:501:d3a2:b4ae with SMTP id b9-20020a509f09000000b00501d3a2b4aemr11875965edf.7.1680198038952; Thu, 30 Mar 2023 10:40:38 -0700 (PDT) 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 References: <20230327164919.GA65182@www.zefox.net> <20230327183055.GB65182@www.zefox.net> <44509923-0218-5no7-42pp-90ss0sns9457@fncre.vasb> <20230329164845.GA75320@www.zefox.net> <20230330152728.GA79440@www.zefox.net> In-Reply-To: <20230330152728.GA79440@www.zefox.net> From: Warner Losh Date: Thu, 30 Mar 2023 11:40:27 -0600 Message-ID: Subject: Re: Boot stops at loader after build/install cycle To: bob prohaska Cc: Steve Rikli , Marcin Cieslak , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="00000000000043ac8605f8219774" X-Rspamd-Queue-Id: 4PnW0m6ydJz4YKd X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000043ac8605f8219774 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 30, 2023 at 9:27=E2=80=AFAM bob prohaska w= rote: > 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: > > > > > > 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. > > > > 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? > > > > When I specified the rpi4 serial console speed in the config to match m= y > > serial terminal server, rather than let it "float" (default 9600), my > > loader interruptions stopped, and no more stray characters on the seria= l > > console after boot either. > > > > > Also, uboot autoboot prompt never gets interrupted. > > > > > > 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. > > > > > > Looks like the bootloader tries to send/receives some terminal contro= l > > > sequences and this fails, interupting the autoboot. > > > > 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. > > Where are you setting the serial console to 9600 baud? AIUI the > Pi defaults to 115200, can it be set in config.txt? > 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 els= e sending the Query Cursor Location and then not reading it. https://www.cse.psu.edu/~kxc104/class/cmpen472/11f/hw/hw7/vt100ansi.htm Warner --00000000000043ac8605f8219774 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 30, 2023 at 9:27=E2=80=AF= AM bob prohaska <fbsd@www.zefox.ne= t> 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:
> >
> > The characters look too regular to me, just like a normal termina= l
> > 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.
>
> OK, then let's assume your serial cables & hoods etc. are OK f= or the
> moment. What does serial console config on the rpi look like?
>
> 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 seri= al
> console after boot either.
>
> > Also, uboot autoboot prompt never gets interrupted.
> >
> > I also noticed that "resizewin" complains about not get= ting
> > information about the terminal upon login on the serial console > > while being in the vt(4) text mode.
> >
> > Looks like the bootloader tries to send/receives some terminal co= ntrol
> > sequences and this fails, interupting the autoboot.
>
> 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<= br> > 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.

Where are you setting the serial console to 9600 baud? AIUI the
Pi defaults to 115200, can it be set in config.txt?
The sequence ending in R is indeed "report cursor locatio= n" so it's the result
of resizewin not reading it and le= aving that around maybe? Or something else
sending the Query Curs= or Location and then not reading it.


Warner
--00000000000043ac8605f8219774--