vtiger mysql crash

gistfile1.txt

InnoDB: Unable to lock ./vtigercrm521/vtiger_users2group.ibd, error: 37
110105  8:58:52InnoDB: Assertion failure in thread 2890320752 in file fil/fil0fil.c line 630
InnoDB: Failing assertion: ret
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/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
110105  8:58:52 - 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=16777216
read_buffer_size=262144
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 93184 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x9d158e8
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=0xac4687b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817f434
0xb76e14d4
0xb76e15fe
0xb76eb0b6
0xb76c48ce
0xb76ba1af
0xb76992a9
0xb7699434
0xb76cde08
0xb76ce1d5
0xb76d4df0
0x8246dd3
0x823b8ff
0x81c8f1c
0x81bffe6
0x81c1841
0x81c1d0a
0x81c1ff7
0x82611a1
0x8259379
0x81e6fa0
0x81e3d85
0x81e87a9
0x8197bfd
0x819e0f3
0x819fa05
0x81a0b7c
0xb765e6de
0xb715b88e
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9d825b8 = SHOW TABLE STATUS FROM `vtigercrm521`
thd->thread_id=2
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.