From owner-freebsd-questions@FreeBSD.ORG Wed Oct 12 14:13:39 2005 Return-Path: X-Original-To: questions@freebsd.org 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 7218B16A41F for ; Wed, 12 Oct 2005 14:13:39 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E9643D7C for ; Wed, 12 Oct 2005 14:13:38 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id j9CEDaUo025365 for ; Wed, 12 Oct 2005 10:13:37 -0400 (EDT) (envelope-from nvidican@wmptl.com) Message-ID: <434D1A10.1000701@wmptl.com> Date: Wed, 12 Oct 2005 10:13:36 -0400 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: Subject: AMD64 vs i386 on a Dual Opteron Box X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2005 14:13:39 -0000 We've been encountering some difficulty between OpenLDAP/nss/pam/FreeBSD/samba over the past few months and really since inception. After countless recompiles of samba, working with samba and openldap code, we've traced it to being an issue somwhere between freebsd and openldap using threads, a clean compile of openldap without using threads runs fine, but still seem to have inconsistency with nss portions of it. The conscencus accross a few different threads on various mailing lists seems to be to try running FreeBSD/i386 instead, therefore assuming perhaps that there are some issues with threading/openldap/nss_ldap on the AMD64/64-bit platform. We're currently running 5.3-RELEASE, I'm going to attempt 5.4-RELEASE/amd64 first, if the issues still arises, the next step would be to try 5.4-RELEASE/i386, and if the problem still exists... then back to trying to debug the whole situation. So, given the above information, my question is this: Knowing FreeBSD i386 can be run on AMD64 hardware, is there any disadvantage other than the obvious 64-bit support? We're using dual AMD Opteron based machines with 2GB ECC registered memory, so memory capacity shouldn't be an issue running 32bit, but how about smp support? Also, if anyone might have another idea or option to go with towards fixing the openldap/freebsd issue, that'd be even better still - but to be honest I lack the skills, time, and hardware neccessary to accomplish this on my own. I'm hoping that something between 5.3-RELEASE and 5.4-RELEASE can resolv the issue, or at least to isolate it to FreeBSD/OpenLDAP/Samba/nss_ldap/? as the cause. In short, i386 on AMD64 good, bad, why? -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/