Date: Sun, 19 Nov 2017 08:19:17 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <markmi@dsl-only.net> Cc: Freebsd-arm <freebsd-arm@freebsd.org>, bob prohaska <fbsd@www.zefox.net> Subject: Re: ssh sessions close spontaneously on rpi2 [Also: I got a rpi2 'Translation Fault (L1)' crash that I also report here, -r325700 based context] Message-ID: <20171119161917.GA49502@www.zefox.net> In-Reply-To: <F62EE16E-7D21-4658-9E8F-6D947C29B4DC@dsl-only.net> References: <20171118165638.GA47956@www.zefox.net> <1A09ACF9-1A85-480D-90BD-9886FC54D116@dsl-only.net> <EC817B7A-29E4-4152-A817-6C60300BB23F@dsl-only.net> <F62EE16E-7D21-4658-9E8F-6D947C29B4DC@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 19, 2017 at 12:15:47AM -0800, Mark Millard wrote: > Do you get any messages like: > > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > . . . > smsc0: warning: Failed to write register 0x114 > . . . Nothing of that sort. The closest thing to a system-level error I saw was the appearance of what looked like a console message which appeared instead on an ssh session su-ed to root. There was no corresponding message on the serial console. Alas, the scrollback buffer on the root ssh session doesn't go back far enough to retrieve it. In some ways it looked almost as if the kernel was talking to wrong device files. However, the mischief was confined exclusively to make sessions run in /usr/ports. Make run in /usr/src has (so far) worked without any oddities. I don't think a make session run in /usr/ports has finished on anything, even make clean, without some sort of error event. Thanks for reading, and any insights... bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171119161917.GA49502>