Date: Tue, 15 Oct 2013 17:28:55 +0400 From: Sevan / Venture37 <venture37@gmail.com> To: Ian Lepore <ian@FreeBSD.org> Cc: "arm@freebsd.org" <arm@FreeBSD.org> Subject: Re: Instability on Raspberry Pi Message-ID: <FF2CE7AB-A1E9-45D4-83B5-702E7EA68198@gmail.com> In-Reply-To: <1381843499.42859.103.camel@revolution.hippie.lan> References: <525AF318.3000900@gmail.com> <20131013194040.GA21904@night.db.net> <CAHNYxxOBvmota4BYoH0Tr8au_LX3_QEx8nDdX8Eh4%2BEeuDq2Lw@mail.gmail.com> <CA%2BU3Mf5=Ejt94SzNDQJTM85%2BVb3dRw%2BcJ=CseLa9L-tTS7pTuw@mail.gmail.com> <1381843499.42859.103.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 Oct 2013, at 17:24, Ian Lepore <ian@FreeBSD.org> wrote: > When this happens, can you hit ^T on the console or any locked up > terminal sessions and get any output? Not a sausage > Can you get into the debugger on a serial console with an alt-break > sequence (CR ~ ^B)? Will retry & see, I wasn't aware of this sequence so didn't try it previousl= y. Sevan / Venture37=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF2CE7AB-A1E9-45D4-83B5-702E7EA68198>