Bug #15288 Deadlock / MyISAM Tables
Submitted: 28 Nov 2005 14:33 Modified: 28 Dec 2005 14:41
Reporter: Moritz Unbekannt Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.13 OS:Linux (Debian Sarge)
Assigned to: CPU Architecture:Any

[28 Nov 2005 14:33] Moritz Unbekannt 
Description:
Running MySQL 4.1.13 Max / Debian Sarge x86_64 / Dual Opteron 244 / 6 GB RAM.
Under high load, MyISAM-Tables seem to deadlock sometimes. mysqlctl stop doesn't work, kill -9 is needed. We cannot determine the definite cause, but it seems to happen only on our x86_64 machines and only under high load.
The load does not have to be MyISAM-specific, on one server all databases run completely using InnoDB, and it deadlocked on a GRANT command.

How to repeat:
---
[28 Nov 2005 14:41] Valeriy Kravchuk 
Thank you for a problem report. 

Weird behaviour (hangs and deadlocks) on Debian and x86_64 was reported many times. See, for example, http://bugs.mysql.com/bug.php?id=8555
and http://bugs.mysql.com/bug.php?id=7254. 

It was decided that the problem is  caused by a bug in glibc for x86_64. Please, check that reports. I believe, you hit exactly the same problem.
[28 Nov 2005 14:48] Jim Winstead 
This is probably this bug in Debian's glibc: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314408
[29 Dec 2005 0: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".