Version: '5.0.22-max-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
060725  3:11:44  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 2808882! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
060725  3:11:57InnoDB: Assertion failure in thread 133213104 in file ../include/buf0buf.ic line 188
InnoDB: Failing assertion: block->state == BUF_BLOCK_FILE_PAGE
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
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=65536
read_buffer_size=126976
max_used_connections=1
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 = 38063 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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=0x7f0964c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81bae30
0xc3f888
0x794f4000
0x83cf9a2
0x8396d86
0x8396f7b
0x837e747
0x837e4db
0x83cff82
0x8365a78
0xc39371
0xb929be
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_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
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.

Number of processes running now: 0
060725 03:11:57  mysqld restarted
060725  3:11: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...
060725  3:11:57  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 9 789808595.
InnoDB: Doing recovery: scanned up to log sequence number 9 790633800
060725  3:11:58  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
060725  3:11:59  InnoDB: Started; log sequence number 9 790633800
060725  3:11:59 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: '5.0.22-max-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
060725  3:12:00  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 2808883! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
q