060712 10:24:18  mysqld started
060712 10:24:18 [Note] Starting MySQL Cluster Binlog Thread
060712 10:24:18 [Note] /opt/local/test/mysql5.1/bin/mysqld: ready for connections.
Version: '5.1.11-beta-log'  socket: '/opt/local/test/mysql5.1/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
060712 10:24:18 [Note] SCHEDULER: Manager thread booting
060712 10:24:18 [Note] SCHEDULER: Loaded 0 events
060712 10:24:18 [Note] SCHEDULER: Suspending operations
060712 11:25:29 [ERROR] Got error 121 when reading table './tpcw/ITEM'
060712 11:25:29 [ERROR] Got error 121 when reading table './tpcw/ADDRESS'
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=1048576
read_buffer_size=258048
max_used_connections=45
max_connections=200
threads_connected=45
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 153822 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xb538e228
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=0xb, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0xb, stack_bottom=0xb68c0000, thread_stack=262144, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9e505e0 = commit
thd->thread_id=29
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.