MySQL Bugs: #8639: IA64 4GB RAM

Bug #8639	IA64 4GB RAM
Submitted:	21 Feb 2005 8:33	Modified:	21 Feb 2005 22:54
Reporter:	devklop devklop	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	4.0.23a	OS:	Linux (Linux Redhat AS 3.0)
Assigned to:		CPU Architecture:	Any

Description:
complie partment
CFLAGS="-O9 -mcpu=ia64 -fomit-frame-pointer -fomit-frame-pointer -fno-exceptions -fno-rtti" CXX=gcc CXXFLAGS="-O9 -mcpu=ia64 -felide-constructors -fomit-frame-pointer -fno-exceptions -fno-rtti"
./configure --prefix=/app/mysql-4.0.23  --enable-assembler --with-extra-charsets=none --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static --without-innodb --without-bench --without-isam  --without-readline  --without-docs  --without-debug --disable-largefile --enable-local-infile

/etc/my.cnf
# The MySQL server
[mysqld]
port            = 3306
socket          = /tmp/mysql.sock
datadir         = /data/mysql_data
skip-locking
key_buffer = 384M
max_allowed_packet = 16M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
myisam_sort_buffer_size = 64M
thread_cache = 16
query_cache_size= 16M
query_cache_limit= 4M
bind-address=192.168.0.143
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 4
max_connections = 1200
max_connect_errors = 1000
interactive_timeout = 300
wait_timeout = 300
skip-log-warnings
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

error log 
Version: '4.0.23a'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=402653184
read_buffer_size=2093056
max_used_connections=0
max_connections=1200
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 5303606 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

How to repeat:
e-mail ro me

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Using MySQL 4.1.14 on Win 2k 3 SP1, on a ML380p, 4GB RAM.
Cannot start MySQL with innodb_buffer_pool_size > 924M.
I get the error:
050921  4:35:11  InnoDB: Error: cannot allocate 947929088 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 84084420 bytes. Operating system errno: 8
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: We keep retrying the allocation for 60 seconds...
InnoDB: Fatal error: cannot allocate the memory for the buffer pool
050921  4:36:11 [ERROR] Can't init databases
050921  4:36:11 [ERROR] Aborting

How do I setup MySQL to use the full 4GB RAM on the dedicated server?
The "my-innodb-heavy-4G.ini did not work, whenever innodb_buffer_pool_size > 924M