From nobody Thu Mar 30 03:03:46 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 4Pn7YF00QSz42JJZ for ; Thu, 30 Mar 2023 03:04:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 4Pn7YD5Q43z3MTn for ; Thu, 30 Mar 2023 03:04:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52f.google.com with SMTP id ek18so71103092edb.6 for ; Wed, 29 Mar 2023 20:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1680145437; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5Sdv3flPmP3hlwOIbxiyCA/dqX40XbmeX7ETnt16JDE=; b=uaoYKZuG44t+3j8lsdbleb7I4RERqwhHkeGN6/DFW9Ab7nyhpo2wuj/yd84TTTVqb8 QCilVPaewm889Z05jYymX/kEyXeq3xMBlpLgMuGigd4LMFaFi85NHH59HVxlTtVx+JFE o8WrsbHx8VTwqFDC8qHLHzvZl2Mm0gI4EYdWghNqK/pxvdPohapwiFmuHbKar5HvQ/7w pIBSdUi8oAMyS/c/GDGf7gISlbBrLkrRaWrFV60woncooT1vWKFYSftAqM+wNQt56aVT Mks2LXhPjAcV33C87a9naLRnR852PjRFYoODQsLi+U8X3YGQDZTRUpv81ymdW+b73NA0 C4tA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680145437; 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=5Sdv3flPmP3hlwOIbxiyCA/dqX40XbmeX7ETnt16JDE=; b=NhFhjtA51HEVM63QsibZJuwCS2KwdW+v8d4daRmWldSmwDuYHTUGkfAhjb08o7Qvvw jxyp+KBc8aGQyGbHExbmC0kCiI0TqdnZXaesWLspsToFoIfaSYhoT6Nn8sfwaGnR4CrN xDdbki++67NyYVD7c+kKU88FQvRKcYz/Nfcm0X1jXKgcmds9y3lv2KLcuq0Yw05vxiar m7jvE8tre0iNJ+oOA9sc/ex2/GYj4nSLlkUKZRRJEM+YSOR6uHx2tcwQM5GN4ePcsF+7 y+18bLIKQ5VnIBU8EVa8Eln3+aKVkYZv3XVwRLZ78HtBf6CVick/AAKNYLaxZCHZze3i 3Jeg== X-Gm-Message-State: AAQBX9d1ejOjLP+/eTrusJLOrS+QVosu4UbapCt7x5kYEHxH+lg2dOFv OCA3aOMMP+yOgJiBcfUk8fqgr/uJAxdbjiR7elQfMCG0hbpDTKNO1rPfUg== X-Google-Smtp-Source: AKy350Z7dED0lUjKXV9l+Kw4SDF5t7dry1cuZoEoqDhs4/DYugcuks+k2MPesLtewiaQqMq2VozpD5cftKgCp9Cb/Sk= X-Received: by 2002:a17:907:160e:b0:946:a095:b314 with SMTP id hb14-20020a170907160e00b00946a095b314mr4725953ejc.2.1680145436950; Wed, 29 Mar 2023 20:03:56 -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:03:46 -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="000000000000f0d56e05f81557fa" X-Rspamd-Queue-Id: 4Pn7YD5Q43z3MTn 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 --000000000000f0d56e05f81557fa Content-Type: text/plain; charset="UTF-8" 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. 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. > > --000000000000f0d56e05f81557fa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Also, the sequence looks like the terminal is reporting s= omething, maybe focus?. That's why it's regular. Though I can't= find a sequence that ends in R.

Warner=C2=A0

On Wed, Mar 29, 2023, 7:09 PM Steve Rikli <sr@genyosha.net> wrote:
On Thu, Mar 30, 2023 at 12:24:13AM +0000, Marcin Ci= eslak 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.

--000000000000f0d56e05f81557fa--