Re: [tboot-devel] DMAR not found

[Alexander Nilsson]

Hi again!

Yes it seams it was some kind of firmware fault, however I did not have to
update it, it was apparently enough to disable the VT-d feature in BIOS,
doing a cold boot cycle and re-enable the feature again.

I think it's working now but on every boot I get the following
TXT.ERRORCODE: 0xC001 which I can't figure out what it means, is this
normal?

The complete log is available on: http://paste.ubuntu.com/7094797/

Anyway, thank you for your help, I would not have gotten this far without
your response!

//Alexander Nilsson


2014-03-14 18:58 GMT+01:00 Ross Philipson :

> On 03/14/2014 11:19 AM, Alexander Nilsson wrote:
>
>> Thank you for quick answer!
>>
>> VT-d is enabled in the BIOS.
>>
>> $ ls /sys/firmware/acpi/tables
>> APIC  ASF!  DBG2  DSDT  dynamic  ECDT  FACP  FACS  FPDT  HPET  MCFG
>> MSDM  SSDT1  SSDT2  SSDT3  SSDT4  SSDT5  SSDT6  TCPA  UEFI1  UEFI2
>> UEFI3
>>
>
> Right so it looks like you have firmware issues on this system. You should
> have a DMAR table - it is what describes the VT-d hardware and its
> capabilities. I guess the first step is to see if Lenovo has a firmware
> update.
>
>
>>
>> There is nothing that look like DMAR in there. I did also a "sudo
>> acpidump | grep -i DMA" but nothing intresting showed up.
>>
>> Once again, thank you for your quick reply!
>>
>> //Alexander
>>
>>
>> 2014-03-14 15:34 GMT+01:00 Ross Philipson > >:
>>
>>
>> On 03/14/2014 09:52 AM, Alexander Nilsson wrote:
>>
>> Hi!
>>
>> I'm trying to get tboot to work, but I'm getting nowhere fast.
>>
>> I've installed tboot (1.7.4-0ubuntu1 via apt-get) on xubuntu
>> 32-bit
>> (kernel 3.11.0-18-generic) on my machine (Lenovo Thinkpad Helix
>> 3701).
>>
>> Then I put the 3rd_gen_i5_i7_SINIT_67.BIN file in /boot/
>> directory (got
>> it form intel web page).
>>
>> I edited relevant lines in /boot/grub/grub.cfg to look like this:
>>
>>  submenu "tboot 1.7.4" {
>>  menuentry 'Ubuntu GNU/Linux, with tboot 1.7.4 and Linux
>>  3.11.0-18-generic' --class ubuntu --class gnu-linux --class
>> gnu
>>  --class os --class tboot {
>>   insmod part_msdos
>>   insmod ext2
>>   set root='hd1,msdos1'
>>   if [ x$feature_platform_search_hint = xy ]; then
>> search --no-floppy --fs-uuid --set=root
>>  --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1
>>  --hint-baremetal=ahci1,msdos1
>>   1ffcf898-aa43-4729-873a-__f17bd4342ca0
>>
>>   else
>> search --no-floppy --fs-uuid --set=root
>>  1ffcf898-aa43-4729-873a-__f17bd4342ca0
>>
>>   fi
>>   echo'Loading tboot 1.7.4 ...'
>>   multiboot   /tboot.gz /tboot.gz
>>  logging=serial,vga,memory vga_delay=5
>>   echo'Loading Linux 3.11.0-18-generic ...'
>>   module  /vmlinuz-3.11.0-18-generic
>>  /vmlinuz-3.11.0-18-generic
>>  root=UUID=abda87ef-d7e7-4411-__a3cc-49817ad7b692 ro  quiet
>>
>> splash
>>  intel_iommu=on
>>   echo'Loading initial ramdisk ...'
>>   module  /initrd.img-3.11.0-18-generic
>>  /initrd.img-3.11.0-18-generic
>>   echo'Loading ACM module ...'
>>   module  /3rd_gen_i5_i7_SINIT_67.BIN
>>  }
>>
>>
>> After this i reboot and select "tboot ..." in grub menu.
>>
>> After displaying "Executing GETSEC[SENTER]..." the machine
>> reboots and
>> on the next attempt I get the following error:
>>
>>  TXT.ERRORCODE: 0xC00010c1
>>  AC module error: acm_type=0x1, progress=0x0c, error=0x4
>>
>>
>> I've decoded the error code as per SINIT_Errors.pdf from the
>> intel web page:
>>
>>  1 - Valid
>>  1 - External software
>>  00 - Reserved
>>   - Minor Error code
>>  0 - Sotware source
>>  00100 - Major error code
>>  001100 - Class code
>>  0001 - Module type
>>
>>
>> Acording to the pdf this indcates: Class ACPI Check, DMAR not
>> found.
>>
>> I have really no idea where to go from here, what do you guys
>> suggest?
>>
>> I would have included more logs in this message, but I only have
>> them in
>> JPEGs since I had to take pictures of the screen to save the
>> output. If
>> you think it will help I will attempt to transcribe them to text
>> and
>> post a link to pastebin ?
>>
>>
>> Do you have VT-d enabled on the system? You will need to turn that
>> on. If that is not the issue, you could try usi

Re: [tboot-devel] DMAR not found

[Ross Philipson]

On 03/15/2014 06:59 AM, Alexander Nilsson wrote:
> Hi again!
>
> Yes it seams it was some kind of firmware fault, however I did not have
> to update it, it was apparently enough to disable the VT-d feature in
> BIOS, doing a cold boot cycle and re-enable the feature again.
>
> I think it's working now but on every boot I get the following
> TXT.ERRORCODE: 0xC001 which I can't figure out what it means, is
> this normal?

Yes it looks like you entered SMX mode successfully. I think that 
0xc001 code is not really an error - I have ran across it before. 
Also Jimmy (Gang Wei) from Intel in this thread says the same thing:

http://comments.gmane.org/gmane.comp.boot-loaders.tboot.devel/465

"> TBOOT: TXT.ERRORCODE: 0xc001
 > TBOOT: AC module error : acm_type=0x1, progress=0x00, error=0x0

This just mean everything is ok, sinit executed successfully."

I think you are in good shape :)

Ross

>
> The complete log is available on: http://paste.ubuntu.com/7094797/
>
> Anyway, thank you for your help, I would not have gotten this far
> without your response!
>
> //Alexander Nilsson
>
>
> 2014-03-14 18:58 GMT+01:00 Ross Philipson  >:
>
> On 03/14/2014 11:19 AM, Alexander Nilsson wrote:
>
> Thank you for quick answer!
>
> VT-d is enabled in the BIOS.
>
>  $ ls /sys/firmware/acpi/tables
>  APIC  ASF!  DBG2  DSDT  dynamic  ECDT  FACP  FACS  FPDT
>   HPET  MCFG
>  MSDM  SSDT1  SSDT2  SSDT3  SSDT4  SSDT5  SSDT6  TCPA  UEFI1
>   UEFI2
>  UEFI3
>
>
> Right so it looks like you have firmware issues on this system. You
> should have a DMAR table - it is what describes the VT-d hardware
> and its capabilities. I guess the first step is to see if Lenovo has
> a firmware update.
>
>
>
> There is nothing that look like DMAR in there. I did also a "sudo
> acpidump | grep -i DMA" but nothing intresting showed up.
>
> Once again, thank you for your quick reply!
>
> //Alexander
>
>
> 2014-03-14 15:34 GMT+01:00 Ross Philipson
> mailto:ross.philip...@citrix.com>
>  >>:
>
>
>  On 03/14/2014 09:52 AM, Alexander Nilsson wrote:
>
>  Hi!
>
>  I'm trying to get tboot to work, but I'm getting
> nowhere fast.
>
>  I've installed tboot (1.7.4-0ubuntu1 via apt-get) on
> xubuntu 32-bit
>  (kernel 3.11.0-18-generic) on my machine (Lenovo
> Thinkpad Helix
>  3701).
>
>  Then I put the 3rd_gen_i5_i7_SINIT_67.BIN file in /boot/
>  directory (got
>  it form intel web page).
>
>  I edited relevant lines in /boot/grub/grub.cfg to look
> like this:
>
>   submenu "tboot 1.7.4" {
>   menuentry 'Ubuntu GNU/Linux, with tboot 1.7.4 and
> Linux
>   3.11.0-18-generic' --class ubuntu --class
> gnu-linux --class gnu
>   --class os --class tboot {
>insmod part_msdos
>insmod ext2
>set root='hd1,msdos1'
>if [ x$feature_platform_search_hint = xy
> ]; then
>  search --no-floppy --fs-uuid --set=root
>   --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1
>   --hint-baremetal=ahci1,msdos1
>1ffcf898-aa43-4729-873a-f17bd4342ca0
>
>else
>  search --no-floppy --fs-uuid --set=root
>   1ffcf898-aa43-4729-873a-f17bd4342ca0
>
>fi
>echo'Loading tboot 1.7.4 ...'
>multiboot   /tboot.gz /tboot.gz
>   logging=serial,vga,memory vga_delay=5
>echo'Loading Linux 3.11.0-18-generic ...'
>module  /vmlinuz-3.11.0-18-generic
>   /vmlinuz-3.11.0-18-generic
>   root=UUID=abda87ef-d7e7-4411-a3cc-49817ad7b692
> ro  quiet
>
>  splash
>   intel_iommu=on
>echo'Loading initial ramdisk ...'
>module  /initrd.img-3.11.0-18-generic
>   /initrd.img-3.11.0-18-generic
>echo'Loading ACM module ...'
>module  /3rd_gen_i5_i7_SINIT_67.BIN
>   }
>
>
>  After this i reboot and select "tboot ..." in grub menu.
>
>  After displaying "Executing GETSEC[SENTER]..." the machine
>

Re: [tboot-devel] DMAR not found

[Alexander Nilsson]

Thanks for taking the time to answer my questions, on a weekend no less!

You should get a medal!

//Alexander Nilsson


2014-03-15 17:00 GMT+01:00 Ross Philipson :

> On 03/15/2014 06:59 AM, Alexander Nilsson wrote:
>
>> Hi again!
>>
>> Yes it seams it was some kind of firmware fault, however I did not have
>> to update it, it was apparently enough to disable the VT-d feature in
>> BIOS, doing a cold boot cycle and re-enable the feature again.
>>
>> I think it's working now but on every boot I get the following
>> TXT.ERRORCODE: 0xC001 which I can't figure out what it means, is
>> this normal?
>>
>
> Yes it looks like you entered SMX mode successfully. I think that
> 0xc001 code is not really an error - I have ran across it before. Also
> Jimmy (Gang Wei) from Intel in this thread says the same thing:
>
> http://comments.gmane.org/gmane.comp.boot-loaders.tboot.devel/465
>
> "> TBOOT: TXT.ERRORCODE: 0xc001
> > TBOOT: AC module error : acm_type=0x1, progress=0x00, error=0x0
>
> This just mean everything is ok, sinit executed successfully."
>
> I think you are in good shape :)
>
> Ross
>
>
>> The complete log is available on: http://paste.ubuntu.com/7094797/
>>
>> Anyway, thank you for your help, I would not have gotten this far
>> without your response!
>>
>> //Alexander Nilsson
>>
>>
>> 2014-03-14 18:58 GMT+01:00 Ross Philipson > >:
>>
>>
>> On 03/14/2014 11:19 AM, Alexander Nilsson wrote:
>>
>> Thank you for quick answer!
>>
>> VT-d is enabled in the BIOS.
>>
>>  $ ls /sys/firmware/acpi/tables
>>  APIC  ASF!  DBG2  DSDT  dynamic  ECDT  FACP  FACS  FPDT
>>   HPET  MCFG
>>  MSDM  SSDT1  SSDT2  SSDT3  SSDT4  SSDT5  SSDT6  TCPA  UEFI1
>>   UEFI2
>>  UEFI3
>>
>>
>> Right so it looks like you have firmware issues on this system. You
>> should have a DMAR table - it is what describes the VT-d hardware
>> and its capabilities. I guess the first step is to see if Lenovo has
>> a firmware update.
>>
>>
>>
>> There is nothing that look like DMAR in there. I did also a "sudo
>> acpidump | grep -i DMA" but nothing intresting showed up.
>>
>> Once again, thank you for your quick reply!
>>
>> //Alexander
>>
>>
>> 2014-03-14 15:34 GMT+01:00 Ross Philipson
>> mailto:ross.philip...@citrix.com>
>> >
>> >>:
>>
>>
>>  On 03/14/2014 09:52 AM, Alexander Nilsson wrote:
>>
>>  Hi!
>>
>>  I'm trying to get tboot to work, but I'm getting
>> nowhere fast.
>>
>>  I've installed tboot (1.7.4-0ubuntu1 via apt-get) on
>> xubuntu 32-bit
>>  (kernel 3.11.0-18-generic) on my machine (Lenovo
>> Thinkpad Helix
>>  3701).
>>
>>  Then I put the 3rd_gen_i5_i7_SINIT_67.BIN file in /boot/
>>  directory (got
>>  it form intel web page).
>>
>>  I edited relevant lines in /boot/grub/grub.cfg to look
>> like this:
>>
>>   submenu "tboot 1.7.4" {
>>   menuentry 'Ubuntu GNU/Linux, with tboot 1.7.4 and
>> Linux
>>   3.11.0-18-generic' --class ubuntu --class
>> gnu-linux --class gnu
>>   --class os --class tboot {
>>insmod part_msdos
>>insmod ext2
>>set root='hd1,msdos1'
>>if [ x$feature_platform_search_hint = xy
>> ]; then
>>  search --no-floppy --fs-uuid --set=root
>>   --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1
>>   --hint-baremetal=ahci1,msdos1
>>1ffcf898-aa43-4729-873a-f17bd4342ca0
>>
>>
>>else
>>  search --no-floppy --fs-uuid --set=root
>>   1ffcf898-aa43-4729-873a-f17bd4342ca0
>>
>>
>>fi
>>echo'Loading tboot 1.7.4 ...'
>>multiboot   /tboot.gz /tboot.gz
>>   logging=serial,vga,memory vga_delay=5
>>echo'Loading Linux 3.11.0-18-generic
>> ...'
>>module  /vmlinuz-3.11.0-18-generic
>>   /vmlinuz-3.11.0-18-generic
>>   root=UUID=abda87ef-d7e7-4411-a3cc-49817ad7b692
>>
>> ro  quiet
>>
>>  splash
>>   intel_iommu=on
>>echo'Loading initial ramdisk ...'
>>module  /initrd.img-3.11.0-18-generic
>>   /initrd.img-3.11.0-18-generic