From owner-freebsd-questions@FreeBSD.ORG Wed Apr 13 16:17:43 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB8DE16A4CE for ; Wed, 13 Apr 2005 16:17:43 +0000 (GMT) Received: from mxc1.crockettint.com (chameleon1.crockettint.com [206.224.72.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25DF243D5E for ; Wed, 13 Apr 2005 16:17:43 +0000 (GMT) (envelope-from emartinez@crockettint.com) Received: from localhost (localhost.crockettint.com [127.0.0.1]) by mxc1.crockettint.com (Postfix) with ESMTP id 7105A379BB; Wed, 13 Apr 2005 11:17:42 -0500 (CDT) Received: from mxc1.crockettint.com ([127.0.0.1]) by localhost (mxc1.crockettint.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37517-06; Wed, 13 Apr 2005 11:17:38 -0500 (CDT) Received: from memnoch (ausc1.crockettint.com [24.153.230.82]) by mxc1.crockettint.com (Postfix) with ESMTP id B37A5379B8; Wed, 13 Apr 2005 11:17:38 -0500 (CDT) From: "Edgar Martinez" To: "'Alex Zbyslaw'" Date: Wed, 13 Apr 2005 11:17:40 -0500 Organization: Crockett International MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <425D2F2D.2090605@dial.pipex.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcVANqiKafHglBjeSRyU/+w/bHlc+QACHKUQ Message-Id: <20050413161738.B37A5379B8@mxc1.crockettint.com> X-Virus-Scanned: amavisd-new at crockettint.com cc: freebsd-questions@freebsd.org Subject: RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: emartinez@crockettint.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 16:17:44 -0000 I appreciate your help! There is NO stupid question or answer...as far as I am concerned ANY help is always WELCOME help...THANKS So, yeah being from the i386 world, I am also aware of the timing quirks in the intel world. The CPU is a 754 pin...specs below..hope this sheds some light on the situation...if anyone wants me to throw up some debug info let me know!! AMD Athlon 64 3000+, 1MB L2 Cache, 64-bit Processor for DTR Notebooks - OEM Model# AMA3000BEX5AP Item # N82E16819103444 Specifications: Model: AMD Athlon 64 3000+ Core: ClawHammer Operating Frequency: 1.8 GHz FSB: Integrated into Chip Cache: L1/64K+64K; L2/1MB Voltage: 1.5V Process: 0.13Micron Socket: Socket 754 Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+ Packaging: OEM(Processor Only) PATRIOT Extreme Performance 184-Pin 512MB DDR PC-3200 w/ XBL Technology, Model PEP5123200+XBL - Retail Model# PEP5123200+XBL Item # N82E16820220036 Specifications: Manufacturer: PDP Systems Speed: DDR400(PC3200) Type: 184-Pin DDR SDRAM Error Checking: Non-ECC Registered/Unbuffered: Unbuffered Cas Latency: 2-2-2-5 T1 Support Voltage: 2.8V Bandwidth: 3.2GB/s Organization: 64M x 64 -Bit Warranty: Lifetime -----Original Message----- From: Alex Zbyslaw [mailto:xfb52@dial.pipex.com] Sent: Wednesday, April 13, 2005 9:40 AM To: emartinez@crockettint.com Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: >OK, removed all misc cards, devices, recabled...attempting to reinstall with >5.3, and I continue to get a "kernel: priviledged instruction fault" >followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? > > I don't know this brand of RAM, and I may be completely wrong but... When looking at 939 pin AMD CPUs, and what memory to get, I noticed that for one major quality RAM maker, the timings they recommended for Intel CPUs were faster than those they recommended for AMD CPUs and your figures look eerily familiar. It was something like 2-2-2-5 for Intel and 2-2.5-2-5 for AMD. I'm no expert on RAM, but your error does sound very hardware related. Can you check the RAM manufacturer's web site to see if they say anything? Also, some motherboards can be very picky about RAM. Is it worth trying with just one RAM chip? Does the machine POST ok with full memory tests on? (It doesn't prove anything, but if a chip is really duff it should find it). A little heretical, I realise, but is there the possibility of trying another OS (Windows, Linux) just to see if you have the same kinds of problems? I'm not copying to the list because I'm no real expert on this kind of thing; just stuff picked up from background reading. If you try any of this and it works can you post back to the list what finally worked? Best, --Alex