Date: Sun, 1 Jan 2006 01:19:20 -0500 From: Martin Cracauer <cracauer@cons.org> To: Armin Pirkovitsch <a.pirko@inode.at> Cc: freebsd-hackers@freebsd.org, Martin Cracauer <cracauer@cons.org> Subject: Re: Deadlock FreeBSD 6 / 7 Message-ID: <20060101011920.A76058@cons.org> In-Reply-To: <43B72A00.2010503@inode.at>; from a.pirko@inode.at on Sun, Jan 01, 2006 at 02:01:52AM %2B0100 References: <43B6C134.6060802@inode.at> <20051231135851.A65762@cons.org> <43B72A00.2010503@inode.at>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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). > > I guess I should have mentioned that other systems work fine and run > stable (and memtest returns no errors) > (Linux was up several days compiling stuff like OO etc) Still, we have seen that several times before, machine stable in Linux, not in FreeBSD and vice versa. Using prime95/mprime ist the best way to ensure this. Run it for 36 hours in the torture test mode. 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?20060101011920.A76058>