From owner-freebsd-hackers Sat Nov 24 2:48:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21109.mail.yahoo.com (web21109.mail.yahoo.com [216.136.227.111]) by hub.freebsd.org (Postfix) with SMTP id A491637B416 for ; Sat, 24 Nov 2001 02:48:12 -0800 (PST) Message-ID: <20011124104812.11118.qmail@web21109.mail.yahoo.com> Received: from [62.254.0.4] by web21109.mail.yahoo.com via HTTP; Sat, 24 Nov 2001 02:48:12 PST Date: Sat, 24 Nov 2001 02:48:12 -0800 (PST) From: Hiten Pandya Subject: Re: Problems with Dual Athlons To: Tim Wiess Cc: hackers@freebsd.org In-Reply-To: <20011123144529.A5628@ahaza.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi.. no offense... but Tyan motherboards are the one which cause the whole problem... did u try to use the kernel option which works around an SMP Bug... try that one... it solved an issue on my friend's system and also someone on the archive... for reference.. the option is: options I4B_SMP_WORKAROUND this should solve your problem... thanks.. regards... Hiten Pandya... .. --- Tim Wiess wrote: > Hello all, > I've recently put together a dual Athlon system, and > unfortunately so far I > have had nothing but problems running FreeBSD on it. > I have gone through many > of the archives in the hackers, bugs, and smp lists, > and while most indicate > that they have had much success running FreeBSD on > dual Athlons, there have > been a few cases which were similar to mine. > Basically, I am unable to run > the system for more than 30 minutes without getting > a panic. > > Fatal trap 12: page fault while in kernel mode > mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 > fault virtual address = 0xa0a > fault code = supervisor read, page not > present > instruction pointer = 0x8:0xc02218e8 > stack pointer = 0x10:0xff80fbc0 > frame pointer = 0x10:0xff80fbc0 > code segment = base 0x0, limit 0xfffff, > type 0x1b > = DPL 0, pres 1, def32 1, > gran 1 > processor eflags = interrupt enabled, resume, > IOPL = 0 > current process = Idle > interrupt mask = bio <- SMP: XXX > > The instruction pointer points to the > worklist_insert routine in the > soft updates code. Although I don't think that it's > the file system that's > really the source of the problem, since I believe > I've seen different > instruction pointers listed for the same type of > panic. > > In the other cases I was reading about, their panics > were also caused by a > page fault. Unfortunately it didn't seem like the > source of the problem was > ever really located. So I thought I would run this > by you all and see if > anyone had any additional thoughts or suggestions. > > For the record, I'm running the 1.2Ghz Athlons on a > Tyan S2460 board with > 256MB of 266Mhz DDR-SDRAM. > > thanks > > tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of > the message ===== regards, Hiten Pandya ---------------------------------------------------- Guys!... stay away from Einstein Junior! ---------------------------------------------------- __________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message