From owner-freebsd-questions@FreeBSD.ORG Wed Oct 12 13:19:04 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 F323A16A41F for ; Wed, 12 Oct 2005 13:19:03 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9715043D45 for ; Wed, 12 Oct 2005 13:19:03 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1EPgVO-0008Fk-00; Wed, 12 Oct 2005 15:18:50 +0200 Message-ID: <434D0D34.3020101@axis.nl> Date: Wed, 12 Oct 2005 15:18:44 +0200 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stefan Cars References: <434CBAD5.10306@snowfall.se> In-Reply-To: <434CBAD5.10306@snowfall.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: questions@freebsd.org Subject: Re: Moving down from amd64 to i386 ?? 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 13:19:04 -0000 Hi, > We are having troubles with MySQL 4.1 on a amd64 (it's crashing randomly > with Seg fault, signal 11. gdb bt says: Cannot access memory at address > 0x800000000000). We have got information saying this is a 64bit related > issue and should be fixed by using the i386 version instead of amd64 > (this is an Intel Xeon). Just an observation, but that address translates to 2^47 = 140,737,488,355,328 which sounds to me like a very high address... Now, I'm not certain if FBSD uses memory mapped I/O with numbers this high (granted, 64 bits allows for 2^64 addressable memory positions...), but if that is indeed the case, if push really comes to shove you could try figuring out just what is being accessed at that position (RAM? HD?). Once you know that, you could check if perhaps that part is broken. Errors like these do sound to me somewhat like a memory error when accessing that particular address (does it also mention other addresses?), but then, I'm no expert, so maybe somethig entirely different is going on. Cheers! Olafo