This means that the first processor plays a role in our ESXi host crashing as well, but it was pretty well hidden until a custom stress test was made – only the 2nd CPU has seemed to cause trouble when the stress test was spanning both NUMA nodes. Now, we see that we have unfortunately run into an Internal unclassified error – looking at the note a condition must be satisfied that at least one X must equal to one, and that is true. That way you can better see the bits we need (61 and 57-55) to further debug.Ĭhecking the Simple Error Code Encoding table to gain further insight. Step 1: Convert the Hexadecimal String to Binary (I like ’s converter) and space it appropriately according to Figure 15-6 in the Manual. I’ll again be using the indispensable Intel® 64 and IA-32 Architectures Software Developer’s Manual (further referenced as “the Manual”) – the pictures below are courtesy of Intel Corporation and are taken from that manual. I will try to be more detailed than in my previous article. Now let’s take a quick look at Processor 1’s MCE. In my previous article about stress testing the host’s memory the Processor 2’s MCE was debugged there and was shown to be indeed a Generic TransBus Error. Processor 2: 0xFA001A4000020E0F – this has been reported when the whole NUMA node was tested.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |