Date: Wed, 1 Mar 2017 15:01:12 -0500 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Odd-looking serial console prompt on RPI2 Message-ID: <20170301200112.ymwkfd64tzz5f3b2@mutt-hbsd> In-Reply-To: <20170227195647.GA91329@www.zefox.net> References: <20170227195647.GA91329@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--z7oxin37jixdcfqx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 27, 2017 at 11:56:47AM -0800, bob prohaska wrote: > Recently the serial console prompt on an RPI2 running =20 > FreeBSD 12.0-CURRENT #15 r314322 >=20 > has become corrupted. The initial output from U-boot and > the early part of the boot phase looks normal, but here it goes off: >=20 > Release APs > WARNING: WITNESS option enabled, expect reduced performance. > random: unblocking device. > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > warning: no time-of-day clock registered, system time will not be set acc= urately > Setting hostid: 0x908fd2cStarting file system che/dev/mmcsd0s2a: FILE SYS= N; SKIPPKS > /dev2a: clea66 free rags, 13cks, 1.9ntation)/dev/da0p3: FILE SYSTEM KIPPI= NG /dev/da0n, 45357(260308 34432 bl2% fragm) > /dev/da0p4: FILE SYSTEM KIPPING /dev/da0n, 3663539 fragsblocks, 0gmentati= /dev/da0p1: FILE SYSTEM KIPPING /dev/da0n, 16010(118 fra18 blockfragmentMou= nting local file syste. > ELF ldconfig path: /lib /usr/li /usr/lo/usr/loccc48 /uslib/grapr/local//= usr/locpencollalocal/li5.20/macusr/loca4 /usr/lm37/lib al/llvm3Setting host= name: www.ze. > Feeding entropy:. >=20 > There are a few dropped characters in the output from fsck, for example. >=20 > Finally, the login prompt looks like this: >=20 > n: eBSD/arm (www.zefottyu0) >=20 > Any attempt to type causes the line above to repeat without echo of the > typed characters at each keystroke. >=20 > If anybody has a hint what's wrong I'd be grateful. One thing I haven't > done is reboot the host driving the FTDI usb-serial adapter. It's been > perfectly stable for more than a month running r311959, so it seems an > unlikely culprit.=20 >=20 > Thanks for reading, >=20 > bob prohaska Hey Bob, I've got the same issue on the RPI3. Using HDMI instead of serial works for me, except that doing so is not typical of how I use the RPI3. I'll soon test on the OverDrive 1000. --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --z7oxin37jixdcfqx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAli3KIUACgkQaoRlj1JF bu4PVg//Q+Vii0tkifQP8OYVX88/52VlETzhiJNjD00jiXzVg6GYApL88UKk9mxQ QEuDaqtX7iN9OFu1r/wjPAqbnrT5HP8ezhMrhBk95sC5nVN9fFZanFgY0TMIJl/T +k1OthM71ZQVfa9nSkxQPracyLefnbzMln15+rqElYI9njZH1Ff1pm8GpYppxaiH ROpSs99cwwWGfnfuJOcWfHGoloq2MveE2Yxzq2WiuCscegRDfP6UuN8ypyq23jjF eR6M/CP12GXMf6WSEwI5zfTDoG1mzWjsbwElntomAuB6iCYEU5eKDyP+tlA1QF73 kjGU3GUbWvtfNzrbQdREsmLLJgBx8zFSGg0v3pXaydtesr/XicENxQQCy3G+WhO8 izm71gaZEC419h5AxRpVbwWHWs8j5dIHYgRzIeRSJdsRCoEPLKNjlkR32MuRRt/S GOV0XPaKSOs4u6PINQrXxjStREdwIOcP8oHz5S8mQV7LY5WZVbsn/usBQ64DLRcT 1hiFaM8hsoviRkql+BRFVIWvdAvlfsshMYYOZHgF89i1eM9oHS06uLLpeC6a7E73 XquvEzX7tWv0cQGy1rQZxUpZxHrgH3bqWOrsd/g8QnasIKzKClRuqX0JbQzchXHv RBZpzzxLikRIE22EZfmfNqNLPh6riRytis0nbONtaA2ynmqdbZk= =rDQh -----END PGP SIGNATURE----- --z7oxin37jixdcfqx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170301200112.ymwkfd64tzz5f3b2>