Date: Fri, 10 Oct 2003 23:52:59 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Doug White <dwhite@gumbysoft.com> Cc: current@FreeBSD.org Subject: Re: Seeing system-lockups on recent current Message-ID: <xzpoewon4jo.fsf@dwp.des.no> In-Reply-To: <20031010124744.V66490@carver.gumbysoft.com> (Doug White's message of "Fri, 10 Oct 2003 12:48:52 -0700 (PDT)") References: <p06002013bbac9e8160de@[128.113.24.47]> <20031010124744.V66490@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White <dwhite@gumbysoft.com> writes: > On Fri, 10 Oct 2003, Garance A Drosihn wrote: > > For the past week or so, I have been having a frustrating time > > with my freebsd-current/i386 system. It is a dual Athlon > > system. [...] > It would be useful to isolate exactly what day the problem started > occuring. I experienced similar problems on a dual Athlon system (MSI K7D Master-L motherboard, AMD 760MPX chipset, dual Athlon MP 2200+) which is barely a couple of months old. I ended up reverting to RELENG_5_1. With -CURRENT, both UP and SMP kernels will crash with symptoms which suggest hardware trouble. With RELENG_5_1, UP is rock solid (knock on wood) while SMP crashes within minutes of booting. I've run out of patience with this system, so I'll keep running RELENG_5_1 on it until someone manages to convince me that -CURRENT will run properly on AMD hardware (maybe around 5.3 or so...) Now, my shiny new 2.4 GHz P4, on the other hand... *drool* DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpoewon4jo.fsf>