060817 11:19:04  InnoDB: Page checksum 2417263940, prior-to-4.0.14-form checksum 1307242357
InnoDB: stored checksum 3183501941, prior-to-4.0.14-form stored checksum 1307242357
InnoDB: Page lsn 59 578938385, low 4 bytes of lsn at page end 578938385
InnoDB: Page number (if stored to page already) 68784,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 985
InnoDB: Page may be an index page where index id is 0 3429
InnoDB: (index schedule_detail_idx1 of table ccms/schedule_detail)
060817 11:19:04  InnoDB: Page dump in ascii and hex (16384 bytes):

....
..

060817 11:19:04  InnoDB: Page checksum 2350537004, prior-to-4.0.14-form checksum 1307242357
InnoDB: stored checksum 3183501941, prior-to-4.0.14-form stored checksum 1307242357
InnoDB: Page lsn 59 578938385, low 4 bytes of lsn at page end 578938385
InnoDB: Page number (if stored to page already) 68784,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 985
InnoDB: Page may be an index page where index id is 0 3429
InnoDB: (index schedule_detail_idx1 of table ccms/schedule_detail)
060817 11:19:04InnoDB: rec offset 99, cur1 offset 13488, cur2 offset 15972
060817 11:19:04InnoDB: Assertion failure in thread 2065046448 in file page0page.c line 519
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=8388608
read_buffer_size=258048
max_used_connections=511
max_connections=510
threads_connected=422
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 658948 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=0x7b16029c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817b8f2
0x6d4888
0x386d
0x82e0dcf
0x82bb620
0x82bc8bb
0x8310a18
0x83164ad
0x8316e5a
0x82b9929
0x82b997e
0x829fc18
0x6ce371
0x4349be
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
nformation that should help you find out what is causing the crash.