Moving down from amd64 to i386 ??

Stefan Cars stefan at
Thu Oct 13 08:56:21 PDT 2005


After doing some testing this is what I found out:

1) Exchanging memory on the machine did not work. Same error.
2) Trying it on another 64 bit machine with same FreeBSD (RC1) creates 
EXACT same problem
3) Installing the i386 version of RC1 instead of amd64 on the same 
machines and it works terrific. No crash.

The bt is always the same and it always crash the same, look here:

#784 0x0000000000000000 in ?? ()
#785 0x247c8d48002454ff in ?? ()
#786 0x01a1c0c748006a10 in ?? ()
#787 0x66fdebf4050f0000 in ?? ()
#788 0x9066669066669066 in ?? ()
#789 0x00007fffffffe778 in ?? ()
#790 0x0000000000000006 in ?? ()
#791 0x00007fffffffe7b0 in ?? ()
#792 0x0000000000000017 in ?? ()
Cannot access memory at address 0x800000000000

Greg 'groggy' Lehey wrote:
> On Wednesday, 12 October 2005 at  9:27:17 +0200, Stefan Cars wrote:
>>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).
> Where did you get that information from?
>>What is the way to go when moving from amd64 to i386 ?
> If you mean "how do I install an i386 kernel on this machine", I can't
> think of any way except to start from scratch.  It would be a good
> idea to install a separate disk, so you can access the configuration
> files and the database on the old disk.  But before doing this, I'd be
> very interested in knowing what the problem is.  Is the backtrace
> always the same?  Where does it crash?
> Greg
> --
> When replying to this message, please copy the original recipients.
> If you don't, I may ignore the reply or reply to the original recipients.
> For more information, see
> See complete headers for address and phone numbers.

More information about the freebsd-questions mailing list