Serious MySQL Error

when i start mysql i get this written to the log constantly and mysql doesn't start

the log grows to over 1MB in a few mins.....

here is what is constantly written to the log over and over:

Code: 
Number of processes running now: 0
050122 13:58:57  mysqld restarted
050122 13:58:57  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050122 13:58:57  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43634.
InnoDB: Doing recovery: scanned up to log sequence number 0 43634
050122 13:58:57  InnoDB: Flushing modified pages from the buffer pool...
050122 13:58:57  InnoDB: Started; log sequence number 0 43634
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=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x88f8a30
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbffff228, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81506ea
0x4004ce65
0x4021df23
0x8150dc2
0x401cc549
0x80d7101
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Us...ack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=0
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
This happened after a server reboot and the server had been running mysql fine for months and months

i have tried the latest mysql 4 and mysql 4.1 and both do the same

any ideas?

 

 

 

 

Top