Date: Sat, 31 Dec 2005 13:58:51 -0500 From: Martin Cracauer <cracauer@cons.org> To: Armin Pirkovitsch <a.pirko@inode.at> Cc: freebsd-hackers@freebsd.org Subject: Re: Deadlock FreeBSD 6 / 7 Message-ID: <20051231135851.A65762@cons.org> In-Reply-To: <43B6C134.6060802@inode.at>; from a.pirko@inode.at on Sat, Dec 31, 2005 at 06:34:44PM %2B0100 References: <43B6C134.6060802@inode.at>
next in thread | previous in thread | raw e-mail | index | archive | help
Armin Pirkovitsch wrote on Sat, Dec 31, 2005 at 06:34:44PM +0100: > Hi! > > I have some troubles with my notebook and any version of FreeBSD > (starting with 6 since my sata controller wasn't supported earlier). > It looks like as it would end up in a deadlock which means i have no > access to the debugger nor to any other kind of tracing methods. > Even with KTR, WITTNESS and DIAGNOSTIC enabled in the kerenl I get no > message what went wrong or what might have caused the trouble. > These fullstops always turn up when i compile and install programs (or > sometimes during the installation of FreeBSD itself) > Hardware: > Intel Pentium-M 760 (Centrino, 2GHz) > VIA VT 6421 SATA Controller > 80GB Samsung SATA HD > > I guess one of those parts creates the trouble, but I have no idea how > to trace it... > Is there a way to run the whole thing in some kind of debugger? > Or is there a diffrent way to locate the problem? It's more likely to be a general instability from broken hardware. Use prime95 (ports/math/mprime) to test your processor and thermal stability (36 hours or so), and memtest86 (seperately). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051231135851.A65762>