From nobody Thu Mar 30 03:05:08 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 4Pn7Zn0r7gz42Jg3 for ; Thu, 30 Mar 2023 03:05:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 4Pn7Zl6Gvnz3MsY for ; Thu, 30 Mar 2023 03:05:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=cvMCatAS; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::530) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-ed1-x530.google.com with SMTP id ew6so71049411edb.7 for ; Wed, 29 Mar 2023 20:05:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1680145518; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OsdA27yiCzh2Eym9jM1x3ZCfWIB7z+/B0nI0eLsy32Y=; b=cvMCatAS1k3R7Qvv9QgmhFm0DIX0SQ5yAeYhTePX7aQnGy0Vxj00GVC2qBm7/LGLoe RR7aCtwTOMHLhXPqAU82RuxytZsUCzQ9VWzLw51uklgn30gvJ0MMYLHGjZEVrbP4pKI1 R0+SXELx8BcTsKDv7VBj6LheHPI6lazSCP1j66v6D3JqEXIX6z9fZtbyNzRjKTMQhxdF V4SicSqokzywDQZxOub9lzYLG7tOxAXGsUcEZ6CzAf4a4fO9pyfTFv21/vonnYI7Q5E/ gbibNqMEuQkggyaggHcP1BVuMBCxOsDmqnpCjn3MM8/3U1ARp1q2gm8drUiY+FItA33v wVOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680145518; 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=OsdA27yiCzh2Eym9jM1x3ZCfWIB7z+/B0nI0eLsy32Y=; b=B0RsNarRD9Xj9S018NES+97oQHvB/qzBrrEtCifKUV80xWIG3aNPRUnKalAg6lK9rp yb1i/aXxqnsrhkFO3k6QwqKX1k7fIu0BShkELA8u1QK1e3hJcuMVnVOD5vhUCUeBaYRK 5buBfykJ7M7pCeaZPcLbLlwm2jD7imfnyWusNfyv4NHttSYpsEOYOuqqm+9d5EB+LkP3 b/MLbtaIUdVVqSPc8gXO3NBb2zVQ1Nuju7dXbdtu83dE1vrR+WHjeQv2jlsuBHfej8mD feo67ZyGzvvTAI52X+aNsmGZJ1WztEDQfVKyl6J3Muy8HA7AitcNrDnmrljhVnCbC7jG 28Pw== X-Gm-Message-State: AAQBX9e94TQgo815L96QQHE0H2ez53KK0zw5NLiz5LizZvfuck7NMO/3 fgHO5IiF5SoseWjfsTcUoMhlr+NZ8jOBMRW1FhSPeg== X-Google-Smtp-Source: AKy350YARyg0jrJdCspf5q+VOF7jsM0jv45koOgsEYT6ShbSE4X5PtZfedEQ4DsSRkd8K0gN7Y00TbK6NQ0ml2XS1rQ= X-Received: by 2002:a50:9b5c:0:b0:4fa:e5e0:9466 with SMTP id a28-20020a509b5c000000b004fae5e09466mr11157771edj.7.1680145518599; Wed, 29 Mar 2023 20:05:18 -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> In-Reply-To: From: Warner Losh Date: Wed, 29 Mar 2023 21:05:08 -0600 Message-ID: Subject: Re: Boot stops at loader after build/install cycle To: Steve Rikli Cc: Marcin Cieslak , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000ceb8aa05f8155c56" X-Spamd-Result: default: False [-2.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.995]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::530:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCPT_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] X-Rspamd-Queue-Id: 4Pn7Zl6Gvnz3MsY X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000ceb8aa05f8155c56 Content-Type: text/plain; charset="UTF-8" On Wed, Mar 29, 2023, 9:03 PM Warner Losh wrote: > Also, the sequence looks like the terminal is reporting something, maybe > focus?. That's why it's regular. Though I can't find a sequence that ends > in R. > Do the numbers correspond to the terminal size? Warner > > Warner > > On Wed, Mar 29, 2023, 7:09 PM Steve Rikli wrote: > >> On Thu, Mar 30, 2023 at 12:24:13AM +0000, Marcin Cieslak wrote: >> > On Wed, 29 Mar 2023, bob prohaska wrote: >> > >> > > If not maybe try different hardware (cables, usb-serial adapters, >> > > power supplies and so on) with an eye to any changes of behavior. >> > > At this stage making the problem worse might be more useful than >> > > making it better. Disconnecting the serial-end ground might be >> > > worth a try. If the connection still works it suggests you have >> > > multiple grounds, which can cause trouble. I ended up lifting >> > > the ground on one of my serial connections. AFAIK both Ethernet >> > > and USB power supplies are floating, so multiple grounds are very >> > > unlikely. But something might be faulty. >> > >> > 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 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. >> >> > 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 control >> > 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. >> >> Cheers, >> sr. >> >> --000000000000ceb8aa05f8155c56 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Mar 29, 2023, 9:03 PM Warner Losh <imp@bsdimp.com> wrote:
Also, the sequence looks like the t= erminal is reporting something, maybe focus?. That's why it's regul= ar. Though I can't find a sequence that ends in R.

Do the numbers corr= espond to the terminal size?

Warner

Warner=C2=A0

On Wed, Mar 29, 2023, 7:09 PM Steve Rikli <sr@geny= osha.net> wrote:
On Thu, Mar= 30, 2023 at 12:24:13AM +0000, Marcin Cieslak wrote:
> On Wed, 29 Mar 2023, bob prohaska wrote:
>
> > If not maybe try=C2=A0 different hardware (cables, usb-serial ada= pters,
> > power supplies and so on) with an eye to any changes of behavior.=
> > At this stage making the problem worse might be more useful than<= br> > > making it better. Disconnecting the serial-end ground might be > > worth a try. If the connection still works it suggests you have > > multiple grounds, which can cause trouble. I ended up lifting
> > the ground on one of my serial connections. AFAIK both Ethernet > > and USB power supplies are floating, so multiple grounds are very=
> > unlikely. But something might be faulty.
>
> 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 th= e
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 serial console after boot either.

> Also, uboot autoboot prompt never gets interrupted.
>
> I also noticed that "resizewin" complains about not getting<= br> > 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 control=
> 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.

Cheers,
sr.

--000000000000ceb8aa05f8155c56--