From: Lil Evil <Lil_E<vil@gm...> - 2009-01-28 12:41:41
I ve been fiddling around with TXT lately and been receiving SINIT errorcodes, which are not listed in the sinit_error.txt
For instance 0x80000005 and 0x80000006 which are marked for future use.
Any chance to get a description for those errorcodes or an updated errorcode list?
NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
From: Cihula, Joseph <joseph.cihula@in...> - 2009-01-28 18:12:14
> From: Lil Evil [mailto:Lil_Evil@...]
> Sent: Wednesday, January 28, 2009 3:41 AM
> Hi there,
> I ve been fiddling around with TXT lately and been receiving SINIT errorcodes, which are not
> listed in the sinit_error.txt
> For instance 0x80000005 and 0x80000006 which are marked for future use.
> Any chance to get a description for those errorcodes or an updated errorcode list?
These error codes are processor-generated. Tables 14 and 15 (in Appendix B) describe the overall format of the ERRORCODE register, where if bit 30 is clear then it is a processor-generated error.
Error 0x80000005 is #BadACMMType, which indicates that the MTRRs are not programmed correctly. If you are seeing this with the latest tboot code, then it may be an issue with BIOS--we have seen at least one BIOS whose SMI handler mis-set one of the MTRRs that was being used by SMM. If this seems to be the condition, you can see if your BIOS provides a configuration option to disable the BIOS's/SMM's use of the MTRR; otherwise contact your system vendor.
Error 0x80000006 is #UnsupportedACM, which indicates some type of corruption of the SINIT ACM in memory. I have not seen this before on any of my systems, so you should check that no code has accidentally trampled over it.