Date: Fri, 9 Mar 2018 13:05:27 -0800 From: "Michael Mitchell (megabyte)" <mmitchel@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org Subject: Re: Garbled console output on Pi3 Message-ID: <1F29E846-6EFE-4966-85BC-742F0B59B774@gmail.com> In-Reply-To: <1520628270.84937.56.camel@freebsd.org> References: <20180307182117.GA55819@www.zefox.net> <1520628270.84937.56.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This happens to me when the cable FTDI USB/232TTL isn't seated very = well. Pin header connectors do have a limited cycle count, and become loose over time. The first thing I = always blame is the cable... Michael Mitchell > On Mar 9, 2018, at 12:44 PM, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Wed, 2018-03-07 at 10:21 -0800, bob prohaska wrote: >> =46rom time to time I observe garbled console output on a Pi3 running = -current. >> The present revision is=20 >> FreeBSD 12.0-CURRENT (ZEFOX) #1 r330571: Wed Mar 7 00:58:23 PST 2018 >> but I don't think that's special; the same thing has shown up = sporadically >> for the past month or so. >>=20 >> The output looks like this: >>=20 >> Mar 7 09:53:53 www kernel: pid 44970 (llvm-tblgen), uid 0, was = killed: out of swap space >> sswawpa_spp_apgaegr:er iw:ndsaewap fii_ppnand_ieptge fiweaanrig:eti = r:teb u wfiifannidt deefebr:i fnbuiiuffontife tberwajit:e : bu0f, = bufeblfokb nj:r:o: 0,w2 b b22u3fo94aibj,tl: k b0nosui:,z fe = b1siz87erlk6:n, o:sbi 4zue: : 202f901o669b604,=20 >> ej0sw: : >> r:ag le4,0paap9 g6_epb >> inrkd: inendefifnioini:te t w1eai35t bu w2fai6t0f b,er:uf = fbufoerbj: :bufo bjs0:i , z0bl, blkeknno: 2: o16: 4260191,52 >> 9393s7ize:, 1siz63e:84 4 >> 096 >> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 210573, size: = 4096 >>=20 >> The first and last lines look normal, which seems to rule out errors = in >> the serial link.=20 >=20 > I can't come up with a reason for this. This was normal in the old > days, but console output is buffered these days, and the buffer size = is > 128 bytes on arm[64], so if things are going to interleave it should = be > in chunks of 128, not a few chars at a time like that. >=20 > Oh... unless it's a case of userland and the kernel writing to the > terminal at the same time, independently of each other. Were you > running the commands that are failing from the console? >=20 > -- Ian >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1F29E846-6EFE-4966-85BC-742F0B59B774>