From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 05:01:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0C4916A4CE for ; Sat, 27 Nov 2004 05:01:51 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9336443D1F for ; Sat, 27 Nov 2004 05:01:51 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id w41so139378cwb for ; Fri, 26 Nov 2004 21:01:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=DldtwfAmPTKueGMZN2JmuEsDW0mKw8w14lXzc2lXK+vnwRaS4OvUYzwTpUjS26USwkmlID5kbM9vW20+qV+sxajt031IuhmGEpxnnKF3npxDcHdXNYVb647SOf/vUayIBZOkxvi2/AErx4mI/ztplXK4K4nQ6/5hzHfX2Jj9V+o= Received: by 10.11.99.16 with SMTP id w16mr39385cwb; Fri, 26 Nov 2004 21:01:50 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id o9sm3953cwc; Fri, 26 Nov 2004 21:01:50 -0800 (PST) Message-ID: <41A80A0F.9030502@gmail.com> Date: Fri, 26 Nov 2004 21:01:03 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Bojara , freebsd-amd64@freebsd.org References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> In-Reply-To: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Page fault on Tyan K8S Pro (S2882) board X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 05:01:52 -0000 Mark Bojara wrote: >Hello All, > >For the last 3 weeks I have been trying to get this motherboard to run with 5.3-STABLE. Basically what happens is if I run the box at 100% utilization the server is stable but as soon as I let it idle and do basic Apache webserver tests and other small apps an hour after that the server will crash. I have tried enabling debug support in my kernel to supply the mailing list with a debug of the error but it seems that when it page faults the entire machine locks up. Please let me know if you require any additional information. > >Spec: >2 x AMD Opteron 242 CPU's >1 x 1GB Corsair PC2700 Memory Module >Bios Version 2.03E > > >Error: >Fatal trap 12: page fault while in kernel mode >cpu id =1; apic id=01 >fault virtual address = 0x18 >fault code = supervisor read,page not present >Instruction pointer = 0x8:0xffffffffa25bc800 >frame pointer = 0x10:0x0 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, olef32 0, gran 1 >trap number = 12 >panic: page fault >cpuid = 1 >boot() called on cpu#1 >uptime 10h3m45s > >I have also tried disabling ACPI to see if thats the problem but the server still crashes > >Thanks Alot >Mark Bojara >AboutIT Online - 012-460-1000 > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > Couple things. We use this setup pretty often, but there are a couple things to keep in mind. #1. on the 4 bank Tyan Tiger boards (K8W), you have one CPU acting as a memory controller for the other. The second CPU makes use of AMD's Hypertransport system for this access. #2. I'd put $50 on the problem going away with SMP disabled, but thats a whole new can of worms. #3. AMD Opteron processors expect, and for all intents and purposes, require ECC Registered Memory. Furthermore, they expect the memory to operate in a dual channel mode. Running 1 DIMM in this kind of setup is shooting yourself in the foot. If CPU #1 requests something through CPU #0, and we're using 1 bank of memory the whole setup..... performance is gonna be crap. Both CPUs will be blocked from processing instructions while the request is fulfilled. There are known performance issues with the 4+0 memory config... but they're still good if you use 2 or 4 DIMMs. It boils down to adding another DIMM, and seeing if that solves your problem. I would strongly suspect that it will quite easily. --- Harrison Grundy