From owner-freebsd-current@freebsd.org Sat Dec 9 20:48:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49AA2E97DA2 for ; Sat, 9 Dec 2017 20:48:04 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C084975172; Sat, 9 Dec 2017 20:48:03 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.223.140]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M0QAP-1fBblf1MIX-00uY1b; Sat, 09 Dec 2017 21:47:54 +0100 Date: Sat, 9 Dec 2017 21:47:46 +0100 From: "O. Hartmann" To: Warner Losh Cc: Michael Tuexen , "O. Hartmann" , FreeBSD CURRENT Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard Message-ID: <20171209214746.1debb72e@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> <728FB521-24EE-4628-9816-EB3DF0ACA14E@freebsd.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/PP.mSn=08Gpc/um65A/e0xy"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:TEJgSnx3YrOlwbFZMODXwQdQaF27FeOr9uq7bgb4wmH35R7yQuq vkrLKVeHmFgrXg9DsSW6QJCmc5/dqnyBOhQV3e1t/t9sTl2Yvkl+1ncUStjLhTf6JwWRYDy X0s/8xahqWVBAQl8g6MBVVEpdPpfViVhYBbYHp/b2wjPJXQAxbYmPzNiSwElHu72YHg0LBs yLP0+nfmXW/w+fSR7b2Eg== X-UI-Out-Filterresults: notjunk:1;V01:K0:lLD6oW/9r2A=:bwJ3nBWAGh78jLcFpPO9u5 xyxWexEjgKSF+y3K2Ka7Yz6RzHaz+k7x3zP3cL8Sp8ABCkZZqwc/6zSPYUzKju3TGUE0MgiUX 4U7cFvRRO/XP6RhCjeZUagzXaf7k8CsLeDWuCf/4rXdVqMGbBkwqX99lCvRn/4B4sjqbcN4lV 9LdSPUzkLGKWbH2NS/JBaAXu+TI1qHgoKi8lEH0dA9lTcunxcCDfr9wzkK+i6wL8mmlXijQpo HgJdI9FqR2WG8lOSBmljf37njeBxHYynbcf61qRFEom2kZ5yua0nl7Ad15a0P7bGOduMEoqdO 5pVU8K1XQHKfOhFVrrt8yKy2TrJbRIGSnLjkIIZgsODr7qTGRZRpvOCoU3i3u1R/DrWPQ/Cw1 H8MlCFqmjShm/xR6lzt+z768jZj3o1UzhykVTNy7eZ4DGTsi0cjli9/72j+tsrgRsAFe2u8M/ XgPQjPphYCdcZv93GtX+PTlJAQHkYZuwW8tacQA+SpR8Z9Lau8LnaN4ixUqtw70oo68oNbvzF tG1cFJ1rlrgEAUJHK6Z/fXT4igb6/PquEtDkdB8/1BHPNOzagNBZarTtRBoJgZiZz2T9QK6pE wHjH4OLKrZbSfZQ2JLwCo2V8vvlNp3tcVCeOTyDKxEL6/I38Z8Z4oyOdjKyaw82gDfVp9LsjJ 0n6pIcR1bw1KR2A/IEf3VPDWsYX6bVUDMexXWy01yT0h1agoyNu10DIkik3VITfhEvZtna2Lk /W1lUv4CV0p7nsaApCvfuQMy5kF9iGy+GENQ1qdGrOUzdW177ZOojXa2ioVCMJ3UBeCwI36tm 0UUbqF8KHydb83sXGAyq1G5IEulsg== X-Mailman-Approved-At: Sun, 10 Dec 2017 02:43:11 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2017 20:48:04 -0000 --Sig_/PP.mSn=08Gpc/um65A/e0xy Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sat, 9 Dec 2017 13:00:12 -0700 Warner Losh schrieb: > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen wrot= e: >=20 > > > On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to bo= ot, =20 > > it gets stuck at =20 > > > the very first messages on the serial console prompting > > > > > > Consoles: internal video/keyboard > > > > > > and then nothing more. =20 > > I don't think it is a general problem with r326734. I'm running on the > > same hardware > > that revision (with some modifications to the TCP I'm testing): =20 > > > uname -a =20 > > FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: Sat > > Dec 9 20:03:59 CET 2017 tuexen@nf3.testbed:/usr/home/ > > tuexen/head/sys/amd64/compile/TCP amd64 > > =20 >=20 > Hi Michael, >=20 > What's your boot setup? BIOS vs UEFI? UFS vs ZFS? GELI? GPT vs MBR? Plants > vs Zombies? And did you update your boot blocks or not? >=20 > Warner All right, I got your point here, my bad, my apaologies. I boot from a NanoBSD-prepared image residing on a SD card. The partiton sc= heme is GPT, non UEFI (the SeaBIOS, latest version available for the APU2C2 available) d= oesn't support UEFI. NanoBSD scripts (legacy.sh) has been modified to fit our requests. The modifications target at most the creation of a GPT partition scheme lay= out, installing boot/pmbr as bootcode and boot/gptboot on a freebsd-boot partiti= on as well as boot/boot1.efifat onto a dedicated efi-type partition. The UEFI partition i= s usually created before(!) the freebsd-boot partition, but in this specific version,= there is NO EFI partition, only the gptboot containing partition. The binaries of the a= bove mentioned bootcode/efi code images are taken from the newly build world. I do not use= boot0sio, the portion where it is installed is excluded by some "if GPT; then" clause. The last known-good version I reported in working is the image I backuped l= ast time. I lost the USB 2.0 flash device today containing the last version, that was n= ot far from r326218, the version that corrupted FreeBSD, I guess it was r326184, but I = really do not know and I havn't a backup of that image. The buildworld process is maintained by a bunch of WITHOUT_ statements in a= file driving NanoBSD. This just for the record just in case FreeBSD build system changed something significantly. Building a world takes 90 minutes or more, so bi-secting the problem would = be a pain in the arse (that said, I imply that world and kernel need to be in sync). I would appreciate hints or tipps where to look after or how to increase ve= rbosity especially at the first boot stage. The PCengines APU with the most recent SeaBIOS isn't capable of booting Fre= eBSD from USB 3.0 devices. Even from USB 2.0 flashdrives working images fail at the boot = loader with "failed with error 19". >=20 >=20 >=20 > > Best regards > > Michael =20 > > > > > > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:53= =20 > > CEST 2017 amd64 =20 > > > works fine. > > > > > > What the heck has changed? > > > > > > Kind regards, > > > > > > oh > > > > > > -- > > > O. Hartmann > > > > > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3= =BCr > > > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 2= 8 Abs. 4 =20 > > BDSG). > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > > =20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/PP.mSn=08Gpc/um65A/e0xy Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWixL8gAKCRDS528fyFhY lBKrAgCOm0dSEWsaeuAnkJDcQYsEDIwllj1ywDS9jDpujRmVTsIOtGqz0u/yV5Lp YAfOHoq1m+9yEBJtIdio+6torB50Af0W0C7MYtEnUyEWWvJKxdPDelJotY1YE3IX cE3x/sprmtybyYunOPuJbxziN16Gf3GNrOtal5rk5xxbVpmT2VRQ =Irk4 -----END PGP SIGNATURE----- --Sig_/PP.mSn=08Gpc/um65A/e0xy--