MySQL Bugs: #26840: mysqld crashes and dumps core when repairing tables at startup

Bug #26840	mysqld crashes and dumps core when repairing tables at startup
Submitted:	5 Mar 2007 14:32	Modified:	13 Apr 2007 14:04
Reporter:	PETER GRIGOR	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.0.33	OS:	FreeBSD (FreeBSD 6.2-RC2)
Assigned to:		CPU Architecture:	Any

Description:
mysqld crashes when repairing myisam tables at startup. message in error log is:

Fatal error 'Exceeded maximum lock level' at line 519 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 67108864)
Fatal error 'Thread is not system scope.
' at line 319 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 0)

The machine is a Dell Poweredge 2950 running FreeBSD 6.2-RC2 (amd) w/ 16G RAM and a perc/5i controller.

Mysqld was built from the ports collection with no special switches save inclusion of non-standard table types.

Last night I also had a mysqld freeze. It simply became completely unresponsive and logged no messages at all. I'm assuming this may have something to do with the error reported above.

How to repeat:
Start up mysqld and have an improperly closed table.

Thank you for a problem report. Please, send exact ./configure command line used. Is it 32-bit or 64-bit system (send the results of uname -a)?

According to http://www.dell.com/content/products/productdetails.aspx/pedge_2950?c=us&cs=555&l=en&s=biz... your server is Xeon-based, not AMD...

I'll keep this new crash in the current bug report, as I'm sure it is related:

When I do a "check table [tablename]" from within mysql on a fairly large table I get the following error in the error log and mysqld freezes:

Assertion failed: (lu->lu_myreq->lr_watcher == ((void *)0)), function _lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 170.

Please, try to repeat with a newer version, 5.0.37 (MySQL's binaries for x86_64), and inform about the results.

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".