Re: [tboot-devel] reset after GETSEC[SENTER] on redhat platforms

[Sun, N. <nin...@in...>]

Hi Brian,

Do you have other TXT capable server or vPro brand client machine, any commercial laptops or desktops are OK, I have HP EliteDesk SFF 800 to run tboot.
Maybe your 2600 server needs a BIOS update or so, I guess.

Regards,
-ning

-----Original Message-----
From: Brian Luckau [mailto:bri...@hp...] 
Sent: Tuesday, January 24, 2017 8:35 AM
To: gr...@en...; Sun, Ning <nin...@in...>; 'tbo...@li...' <tbo...@li...>
Subject: Re: [tboot-devel] reset after GETSEC[SENTER] on redhat platforms

The error code comes from the console output when we boot with UEFI enabled, and Intel TXT enabled. It happens sometime before the reset happens.

We are loading the AC module via the bios as far as I can tell. I went to try to download a new one so that I could try to specify it in the
grub2 modules but for our processor there did not seem to be a match listed. This was a few weeks ago, but I remember concluding that for this board and processor, it was expected for it to be loaded from the BIOS and no download was available.


On 01/22/2017 11:18 AM, Dr. Greg Wettstein wrote:
> On Jan 17,  3:24pm, Brian Luckau wrote:
> } Subject: Re: [tboot-devel] reset after GETSEC[SENTER] on redhat 
> platforms
>
> Good Brian, et.al., I hope the weekend has gone well for everyone.
>
>> Thanks for your responses. I did not forget, just had to juggle some 
>> priorities.
> No problem, everyone is swamped.
>
>> The board we have is Intel s2600KP. I believe the board is custom I'm 
>> told it is not a custom bios implementation.
>>
>> I can tell you the TPM version is currently 1.2.
>>
>> For the  TXT machine Model -- How do we find this out?) Is this a 
>> technical specification of the TPM chip or something more general 
>> like saying "what kind of machine is this? Sorry about the confusion.
>>
>> The micro-architercture is Haswell (Intel(R) Xeon(R) CPU E5-2660 v3).
> So it is an Intel 2600 series server board.
>
> The server class motherboards should have their Authenticated Code 
> Module (ACM) loaded from BIOS.  Is this correct or are you specifying 
> an ACM module in your boot configuration?
>
> If you are not specifying the ACM in the boot stack you may want to 
> try downloading the ACM for this platform class, presumably a 4th 
> generation module and trying that to see if there is any difference in 
> behavior.
>
> If the board is indeed 'custom' this may be the root of the problem as 
> the ACM carries out platform verification checks which may not succeed 
> in the presence of a 'custom' hardware configuration.
>
>> Here is the information that was near the beginning of boot.message:
>>
>> [    0.000000] ACPI: RSDP 000000007b7d6014 00024 (v02 INTEL )
> So this is the Root System Description Pointer (RSD) message from a 
> standard boot.  Where did the following message come from which you 
> previously quoted?
>
>>>>>> .000000] ACPI BIOS Error (bug): A valid RSDP was not found
>>>>>> (20150930/tbxfroot-243)
> As I noted previously the error code which you posted decodes as
> follows:
>
> Class-C/Major-8/Minor-0  - 'Invalid RSDP'
>
> This in combination with the above 'ACPI BIOS Error' message indicates 
> the ACM is probably resetting the board because it believes there is 
> something wrong with the ACPI implementation on the board.
>
> Ning, any reflections from Intel?
>
> Dr. Greg
>
> }-- End of excerpt from Brian Luckau
>
> As always,
> Dr. G.W. Wettstein, Ph.D.   Enjellic Systems Development, LLC.
> 4206 N. 19th Ave.           Specializing in information infra-structure
> Fargo, ND  58102            development.
> PH: 701-281-1686
> FAX: 701-281-3949           EMAIL: gr...@en...
> ----------------------------------------------------------------------
> -------- "We trained hard......but every time we were beginning to 
> form up into
>   teams, we would be reorganised. I was to learn later in life that we
>   tend to meet any new situations by reorganising.......  and a
>   wonderful process it can be for creating the illusion of progress,
>   while producing inefficiency and demoralisation."
>                                  -- Petronius (6 AD)