From owner-freebsd-hackers Fri Nov 23 20:59:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 42ADF37B405 for ; Fri, 23 Nov 2001 20:59:09 -0800 (PST) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fAO4x9M60953 for ; Fri, 23 Nov 2001 20:59:09 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id F2966380D; Fri, 23 Nov 2001 20:59:08 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Tim Wiess Cc: hackers@FreeBSD.ORG Subject: Re: Problems with Dual Athlons In-Reply-To: <20011123144529.A5628@ahaza.com> Date: Fri, 23 Nov 2001 20:59:08 -0800 From: Peter Wemm Message-Id: <20011124045909.F2966380D@overcee.netplex.com.au> 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 You have neglected to include some critical information, such as what OS you are running. I am wondering if you are running into the 4.4-RELEASE kernel stack overflow problems. 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 > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message