Date: Sun, 19 May 2002 13:18:28 +0200 From: Axel Scheepers <axel@axel.truedestiny.net> To: Daniel Barron <nettle@jadeb.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: After 170 days uptime, now reboots every few hours Message-ID: <20020519131828.E64761@mars.thuis> In-Reply-To: <0302ca384b.nettle@jadeb.com>; from nettle@jadeb.com on Sat, May 18, 2002 at 11:25:00PM %2B0000 References: <20020518202133.74BBE5D88@server3.safepages.com> <a422bf384b.nettle@jadeb.com> <3CE6CFCA.889BEAF6@mrincubator.org> <0302ca384b.nettle@jadeb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 18, 2002 at 11:25:00PM +0000, Daniel Barron wrote: > Back to the original question; what tools exist on FBSD to diagnose where > the fault may lie (mb, hd, ram, cpu, etc)? > > -- > Daniel Barron > (Visit http://dansguardian.org/ - True web content filtering for all) Hi Daniel, Although it will take some trouble the best way to debug it will be to recompile the kernel with -g and enable the kernel debuuger. Most of these small boards will have a serial interface so you can hook up a debug terminal. Problem might be the hdd, since a debug kernel is a bit bigger then normal, you might consider setting up a tfpt server to make testing with it easy. Then, whenever it hangs, you'll probably be able to do a backtrace to see where things go wrong. Gr, -- Axel Scheepers UNIX System Administrator email: axel@axel.truedestiny.net a.scheepers@iae.nl http://axel.truedestiny.net/~axel ------------------------------------------ "I drink to make other people interesting." -- George Jean Nathan ------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020519131828.E64761>