MySQL Bugs: #34470: Server stops during MySql restoring

Bug #34470	Server stops during MySql restoring
Submitted:	11 Feb 2008 19:38	Modified:	9 Jun 2010 19:42
Reporter:	Jonatas Cruz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.0.51a	OS:	Windows (2003)
Assigned to:		CPU Architecture:	Any
Tags:	8110, e5335, freeze, server, stops

Description:
Hi everybody

During the restore operation my server stops (screen freezes, keyboard/mouse doesn't works). After system reboot the bios shows the following error:

###
Error code: 8110
Severity: major
Instance: 1

Description: Processor 01 Internal error (IERR). The error code value identifies the error. Major severity requires user intervention but does not stop system boot. The instance value identifies the conponent in error.
###

After restarting, the Eventviewer doesn't give details about the stop.

According to the message, the error probably is the processor, but I tested the    restore in another machine, with the same specification to the first (RAM, processor, Hd, motherboard). The same error is raised. 

The restore were tested in the following platforms with the same error:
-Windows 2003 64 bits edition x MySql 64 bits
-Windows 2003 64 bits edition x MySql 32 bits
-Windows 2003 Enterprise (32 bits) x MySql 32 bits

In other different servers the backup files is restored successfuly.
 
I suspect there is a relation to the 64 bits quadcore CPU and the MySql process.

Maybe its an CPU error. I've already contacted Intel about this, but no valid answer yet.

My servers specifications:
BIOS VERSION: S5000.86B.07.00.0079.060520071732, 5/6/2007
Motherboard: S5000VSA
Processor: 2x XEON E5335 
Ram: 8 GB

Any help is welcome.

Thanks in advance,
Jonatas Pereira da Cruz

How to repeat:
Doing any MySql stress test (like restore) under a E5335 Intel Xeon CPU.

Thank you for the report.

Most likely it is just because all resources were taken during stress test.

But if you still think this is MySQL bug please provide MySQL error log, configuration file and describe hardware which you use (CPU, RAM etc.)

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

Just updating...
The problem was the software RAID-0.
Using hardware RAID, the problem was gone.