Bug #38830 Assertion failure in thread 1147169120 in file srv0srv.c line 2095. Then
Submitted: 15 Aug 2008 23:16 Modified: 15 Sep 2008 23:27
Reporter: Gary Barrueto Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.51a OS:Linux (RHEL4 2.6.9-55.0.2.ELsmp)
Assigned to: CPU Architecture:Any
Tags: semaphore hung signal 11 segmentation fault Assertion failure

[15 Aug 2008 23:16] Gary Barrueto
The server crashed with the following error:
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
080815 11:39:47InnoDB: Assertion failure in thread 1147169120 in file srv0srv.c line 2095
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.
080815 11:39:47 - 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3481822 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
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.

How to repeat:
This is the first occurrence we have seen this happen.
[15 Aug 2008 23:27] MySQL Verification Team
Thank you for the bug report. Looks like duplicate of bug: http://bugs.mysql.com/bug.php?id=34459.
[16 Sep 2008 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".