Date: Sun, 04 Mar 2001 13:24:01 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: The Hermit Hacker <scrappy@hub.org> Cc: freebsd-current@FreeBSD.org Subject: RE: Using serial console to debug system hangs ... Message-ID: <XFMail.010304132401.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.33.0103041520140.33622-100000@mobile.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04-Mar-01 The Hermit Hacker wrote: > On Sat, 3 Mar 2001, John Baldwin wrote: > >> >> On 04-Mar-01 The Hermit Hacker wrote: >> > >> > Wow, that was painful ... after 2 hrs, I got as far as: >> >> Yeah, it spews out a lot of crap. :-/ You prolly want to use a 115200 >> serial >> console if at all possible. Should've mentioned that earlier.. > > Okay, I'm up to 115200, still a lot of crap ;) Any lower mask I can set > things at to get enough info, without so much flowing up the screen? I > can understand why she's so unresponsive, just wondering if there is a way > of reducing the amount of debugging without losing too much ... Well. Currnetly what 0x1200 logs is KTR_PROC and KTR_INTR, so it logs all incoming threaded interrupts as well as context switches, etc. If the machine hagns, it is very helpful to know if a) we are still getting interrupts at all (such as clock interrupts, which I can tell beecause the softclock swi thread get scheduled to execute.) and b) what processes were doing what when the machien hung. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010304132401.jhb>