Date: Fri, 10 Oct 2003 21:24:32 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: des@des.no Cc: current@FreeBSD.org Subject: Re: Seeing system-lockups on recent current Message-ID: <200310110424.h9B4OWN1063722@gw.catspoiler.org> In-Reply-To: <xzpoewon4jo.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Oct, Dag-Erling Smørgrav wrote: > 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...) My Athlon XP 1900+/AMD 761 UP box is happily running a late October 6th version of -current.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310110424.h9B4OWN1063722>