MySQL Bugs: #38750: Server crashes due to long semaphore wait

Bug #38750	Server crashes due to long semaphore wait > 600 seconds
Submitted:	12 Aug 2008 14:21	Modified:	13 Sep 2008 11:40
Reporter:	Nicholas Goodwin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.0.51b	OS:	Windows (SP2)
Assigned to:		CPU Architecture:	Any
Tags:	crash, hang, long, Semaphore

Description:
I seem to be hitting a long semaphore wait somewhere in mysql.  I'm not 100% sure if this is hardware or software (pretty sure the hardware is OK will reply to this bug report after i test the ram which is the only conceivable place the hardware would be bad)  I am not even sure if a query could (or even should?) be able to solve this.  I'm post a bit of my .err file. Hope it helps and any help would definitely be appreciated.  I'm getting these crashes almost daily at this point so i really have no idea what is going on.  (My error log which will hopefully be attached contains multiple crashes)

Thanks again!

-Not sure of category.  I am guessing this is a bug in innodb storage engine but I'm not 100% sure where the issue lies

How to repeat:
Unknown

Suggested fix:
-

Error log

Attachment: w_acu_willwinn.zip (application/zip, text), 107.53 KiB.

Had to fix severity.  This is a total crash and mysql has to be restarted

Thank you for a problem report. It looks similar to bug #25645. What CPU(s) do you have? AMD? Can you, please, try to upgrade to a newer version, 5.0.67, and check if this problem is still repeatable.

I'm about to test the memory on the box.  i will let you know the exact specs of the machine once the memory test is complete and i will also upgrade the server when i'm bringing it back up.

Okay yesterday i finished testing the RAM in the machine and it is fine.  I also upgraded MySQL to version  5.0.67  It has been running since yesterday at 5pm with no problems i will post here again if it doesn't happen again (it seems to happen at least once a week if not more so i will wait a week if it doesn't happen again I'll just close the bug.)

Oops forgot to say that the system is NOT an AMD system, the processor in it is an Intel P4

Thank you for the feedback. Please comment here when your test is done. Thanks.

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

This could be a duplicate of Bug #59733. Without seeing the stack traces of all threads during the hang or crash, it is impossible to tell.