Menu
▾
▴
tboot-devel — Developer support
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(13) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(19) |
Feb
(24) |
Mar
(8) |
Apr
(14) |
May
(8) |
Jun
(10) |
Jul
(14) |
Aug
(3) |
Sep
(13) |
Oct
(27) |
Nov
(39) |
Dec
(24) |
| 2009 |
Jan
(19) |
Feb
(4) |
Mar
(2) |
Apr
(15) |
May
|
Jun
(2) |
Jul
(44) |
Aug
(21) |
Sep
(20) |
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2010 |
Jan
(7) |
Feb
(10) |
Mar
(2) |
Apr
(12) |
May
(7) |
Jun
(2) |
Jul
(18) |
Aug
(11) |
Sep
(4) |
Oct
(25) |
Nov
(8) |
Dec
(1) |
| 2011 |
Jan
(27) |
Feb
(2) |
Mar
(19) |
Apr
(8) |
May
(16) |
Jun
(11) |
Jul
(9) |
Aug
(9) |
Sep
(35) |
Oct
(9) |
Nov
(8) |
Dec
(32) |
| 2012 |
Jan
(37) |
Feb
(20) |
Mar
(2) |
Apr
(24) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(21) |
Sep
(8) |
Oct
(15) |
Nov
(1) |
Dec
(7) |
| 2013 |
Jan
(4) |
Feb
(8) |
Mar
(38) |
Apr
(9) |
May
(42) |
Jun
(4) |
Jul
(21) |
Aug
(4) |
Sep
|
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2014 |
Jan
(8) |
Feb
(8) |
Mar
(5) |
Apr
(9) |
May
(19) |
Jun
(1) |
Jul
(10) |
Aug
(25) |
Sep
(6) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2015 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(12) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(11) |
Oct
(5) |
Nov
(3) |
Dec
(1) |
| 2016 |
Jan
(2) |
Feb
(24) |
Mar
|
Apr
(6) |
May
(26) |
Jun
(20) |
Jul
(8) |
Aug
(15) |
Sep
(21) |
Oct
(1) |
Nov
(7) |
Dec
(24) |
| 2017 |
Jan
(12) |
Feb
(2) |
Mar
(6) |
Apr
(8) |
May
(18) |
Jun
(13) |
Jul
(12) |
Aug
(8) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
(12) |
Mar
(8) |
Apr
(5) |
May
(7) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(2) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
| 2019 |
Jan
(8) |
Feb
|
Mar
(2) |
Apr
|
May
(3) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(8) |
Oct
(6) |
Nov
(20) |
Dec
(14) |
| 2020 |
Jan
(25) |
Feb
(12) |
Mar
(2) |
Apr
(13) |
May
(44) |
Jun
(9) |
Jul
|
Aug
(3) |
Sep
(5) |
Oct
(4) |
Nov
(2) |
Dec
|
| 2021 |
Jan
(6) |
Feb
|
Mar
(7) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
(16) |
Sep
(4) |
Oct
(6) |
Nov
(1) |
Dec
(6) |
| 2022 |
Jan
(5) |
Feb
(4) |
Mar
(22) |
Apr
(6) |
May
(4) |
Jun
(17) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(2) |
| 2023 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(3) |
|
From: 魏成龙 <che...@16...> - 2010-10-08 08:32:26
|
Hello: I am installing Tboot now, but I have several problems. My PC is IBM T400 with Fedora 10. I have downloaded SINIT(GM45_GS45_PM45_SINIT_21.BIN) and tboot-20100427-1.fc12.src.rpm. But I failed to install tboot. Error message is that "no LCP module found" and it stopped at executing GETSEC[SENTER]... I think the grub I haved modified may be fault. Can you give me an example about how to modify grub.conf to support tboot? Following is my grub.conf I have modified. Thank you. title Fedora (2.6.27.53) kernel /boot/tboot.gz logging=serial,vga,memory module /boot/vmlinuz-2.6.27.53 ro root=UUID=2d052b74-4adf-45b3-95fe-326239a5ac56 rhgb quiet module /boot/initrd-2.6.27.53.img module /boot/GM45_GS45_PM45_SINIT_21.BIN |
|
From: 黄文超 <hua...@gm...> - 2010-10-08 08:24:44
|
Hi, I saw the previous mail showing that tboot will work on feroda 13. However, I'm wondering if it will work on Ubuntu 10.04, for I was suffering from installing the tboot for several days. I've changed the default grub2 to grub, and made the same grub configuration as in the previous mail, and change the kernel to 2.6.35-19 . It succeeded in launching the tboot.gz (including the begin_launch() and post_launch() ), and transferring the control to linux kernel, however, it fails, and stops while launching the kernel, showing the message like this: "ALERT! /dev/disk/by-uuid/.... does not exist. Dropping a shell!" I tried to boot pc with several configurations, in order to dig more information: 1. remove the sinit module in menu.lst the kernel was launched successfully, which shows begin_launch() and launch_kernel(false) works. But it didn't enter into post_launch(), which means it was not a measured launch. 2. edit the source code in post_launch() where launch_kernel(true) turns to launch_kernel(false) It also failed and showed the message:"ALERT!......Dropping a shell!!" I thought launch_kernel(false) worked fine in begin_launch() where the policy was TB_POLACT_UNMEASURED_LAUNCH, and it would work as well in post_launch. However, it turned out that I was wrong. So, until now, I still cannot figure out what's wrong with the configuration, and expect if someone would help me with this. Thanks very much -- Colahuang |
|
From: Cihula, J. <jos...@in...> - 2010-10-08 03:16:54
|
(You should send questions to tboot-devel; tboot-changelog is intended for automated messages from the mercurial source repository.) The 2.6.27 kernel does not have tboot/TXT support; you need at least 2.6.33, and preferably 2.6.35+. If you want to use the distro kernel, you will need Fedora 13 x86_64. Otherwise, this is the correct modification to grub.conf. joe From: 魏成龙 [mailto:che...@16...] Sent: Thursday, October 07, 2010 8:04 PM To: tboot-changelog Subject: [Tboot-changelog] How to modify grub.conf to support Tboot Hello: I am installing Tboot now, but I have several problems. My PC is IBM T400 with Fedora 10. I have downloaded SINIT(GM45_GS45_PM45_SINIT_21.BIN) and tboot-20100427-1.fc12.src.rpm. But I failed to install tboot. I think the grub I haved modified may be fault. Can you give me an example about how to modify grub.conf to support tboot? Following is my grub.conf I have modified. Thank you. title Fedora (2.6.27.53) kernel /boot/tboot.gz logging=serial,vga,memory module /boot/vmlinuz-2.6.27.53 ro root=UUID=2d052b74-4adf-45b3-95fe-326239a5ac56 rhgb quiet module /boot/initrd-2.6.27.53.img module /boot/GM45_GS45_PM45_SINIT_21.BIN 2010-10-08 ________________________________ Chenglong Wei Best wishes |
|
From: Martin P. <Mar...@ia...> - 2010-10-06 10:04:17
|
Today, the Trusted Computing for the Java Platform project[1] released an update of jTSS, a Trusted Software Stack (TSS) implemented in 100% Java, and jTpmTools, a command-line tool to exercise various TPM features. This update adds commands to manipulate Launch Control Policies v2 as used by newest Intel chipsets with their TXT technology and Tboot. This extends the v1 support already published in a previous release. This release is experimental - use at your own risk! We want to thank everyone who contributed to this release, especially Michael, Josef, Brian and Jonathan. Have fun, Martin & Ronald [1] http://trustedjava.sourceforge.net/ [2] http://sourceforge.net/projects/tboot/ |
|
From: Michael G. <m.g...@tu...> - 2010-09-28 13:31:40
|
Michael Gissing wrote: > *) What is the desired storage of VLPs in the long run? An own TPM NV RAM index or > as a custom element in LCP_POLICY_DATA? > *) As TBoot now supports this feature it would be good to define an UUID which identifies > an LCP_CUSTOM_ELEMENT as a TBoot VLP. (I haven't found an UUID in Shane's code, maybe i missed it) > *) Shane could you please announce your contributions to the tboot source code repository as > Joseph does via tboot-changelog@sf? Any comments? Michael |
|
From: Cihula, J. <jos...@in...> - 2010-09-20 08:00:48
|
This would indicate that you are trying to launch when DMA remapping is already enabled. If you have rebooted the system, that should reset VT-d and you shouldn’t get this error. When are you trying to launch TXT?
Joe
From: Younghwan Go [mailto:yh...@ka...]
Sent: Friday, September 17, 2010 4:27 AM
To: tbo...@li...
Subject: [tboot-devel] LT.ERRORCODE = c00004f1
Hi.
I was working and got an error.
The LT.ERRORCODE is c00004f1.
According to this, progress value is 0fh and errorcode is 1.
This means that it's VT-d remap engine enabled.
I have iommu=on on the boot menu.
Can you tell me how I should do this? Should I delete iommu=on from the boot menu?
Thanks.
Younghwan Go
2010-08-17 오후 2:38, Cihula, Joseph 쓴 글:
You need to specify ‘iommu=on’ on the kernel command line—tboot is DMA protecting memory and the kernel needs to enable VT-d to open the DMA buffers. You should also be using a kernel built with CONFIG_INTEL_TXT.
Joe
From: Younghwan Go [mailto:yh...@ka...]
Sent: Monday, August 16, 2010 10:19 PM
To: Cihula, Joseph
Subject: Re: Hi Shane. I have question on tboot.
Hi Joe. Thank you for your email.
I did tpmnv_relindex and it fixed the reboot problem :D
But I encountered another problem after tboot :(
All things that start with [TBOOT] are done and then it starts to load ubuntu kernel.
However, it dies after giving out errors such as irq_stat 0x20000000 host bus error and can't find the boot block.
The same kernel can be booted without problem if it's booted without tboot.
Right now, I set it so that it goes straight from tboot to linux. I didn't put Xen.gz.
Is there a way to solve the problem?
If I need to show you the boot log, where can I get it because it doesn't seem to be stored anywhere.
Thanks.
Younghwan Go.
2010-08-17 오전 8:25, Cihula, Joseph 쓴 글:
Can you delete your owner index (0x40000001) and try again? You can do this with the tpmnv_relindex command in lcptools/ (load the driver and tcsd first).
Joe
________________________________
From: Younghwan Go [mailto:yh...@ka...]
Sent: 2010年8月13日 13:24
To: Wang, Shane
Subject: Re: Hi Shane. I have question on tboot.
Sorry. I forgot to include the last line.
0x10000001 0x50000001 0x40000001 0x1000f000 0x50000002 0x20000002 0x30000001 0x20000001
Thanks.
Younghwan Go.
2010-08-13 오후 2:04, Younghwan Go 쓴 글:
Hi.
I got this from tpmnv_getcap:
________________________________
The response data is:
10 00 00 01 50 00 00 01 40 00 00 01 10 00 f0 00
50 00 00 02 20 00 00 02 30 00 00 01 20 00 00 01
8 indices have been defined
list of indices for defined NV storage areas:
________________________________
What I meant was can tboot work without Xen?
I was using fedora before and that worked fine with just Xen, without tboot.
Now I'm trying with ubunt but Xen seems to now work for some reason.
Since in your README file, Xen is added in grub menu. That's why I was asking.
The problem with tboot is same for both fedora and ubuntu.
Thanks.
Younghwan Go.
2010-08-13 오후 1:56, Wang, Shane 쓴 글:
Thanks.
Can you run "tpmnv_getcap"(you can find it in lcptools/) on your system? before doing that, you need to run "modprobe tpm_tis interrupts=0 force=1" and "tcsd". What do you see?
Strange! The log says SINIT gets a TPM error. (The error code = 0). But in TPM, error code 0 means "success".
Do you mean you can boot Xen with tboot now but can't boot ubuntu with tboot? Is that correct?
Thanks.
Shane
________________________________
From: Younghwan Go [mailto:yh...@ka...]
Sent: 2010年8月13日 11:59
To: Wang, Shane
Subject: Re: Hi Shane. I have question on tboot.
Hi.
I got the whole TBOOT log. :)
Regarding the TPM, I checked with tpmmanager and confirmed that TPM is enabled and owner is set.
I used tpm_takeownership -z command.
I didn't fully understand the "define owner/aux indexes" part.
Do you mean have I followed the steps of the policy text file in the tboot folder?
There were some errors but eventually they were all successful.
Also I'm wondering if not using Xen causes a problem because I've been using ubuntu and Xen seems to now work on it.
Thank you for your help.
Younghwan Go.
________________________________
TBOOT: command line: logging=serial,vga,memory vga_delay = 5
TBOOT: TPM is ready
TBOOT: TPM nv_locked: TRUE
TBOOT: read verified launch policy (256 bytes) from TPM NV
TBOOT: policy:
TBOOT: version: 2
TBOOT: policy_type: TB_POLTYPE_CONT_NON_FATAL
TBOOT: hash_alg: TB_HALG_SHA1
TBOOT: policy_control: 00000001 (EXTEND_PCR17)
TBOOT: num_entries: 3
TBOOT: policy entry[0]:
TBOOT: mod_num: 0
TBOOT: pcr: none
TBOOT: hash_type: TB_HTYPE_IMAGE
TBOOT: num_hashes: 2
TBOOT: hashes[0]: cb f6 2a ab c6 c9 27 eb e4 1c 2b 8e d7 05 1d b5 28 b2 0b f8
TBOOT: hashes[1]: cb f6 2a ab c6 c9 27 eb e4 1c 2b 8e d7 05 1d b5 28 b2 0b f8
TBOOT: policy entry[1]:
TBOOT: mod_num: 1
TBOOT: pcr: 19
TBOOT: hash_type: TB_HTYPE_IMAGE
TBOOT: num_hashes: 2
TBOOT: hashes[0]: ec 28 2d a7 e7 86 46 8a 7e a0 c1 bd fa 9e e2 78 7b 10 e9 6c
TBOOT: hashes[1]: ec 28 2d a7 e7 86 46 8a 7e a0 c1 bd fa 9e e2 78 7b 10 e9 6c
TBOOT: policy entry[2]:
TBOOT: mod_num: 2
TBOOT: pcr: 19
TBOOT: hash_type: TB_HTYPE_IMAGE
TBOOT: num_hashes: 3
TBOOT: hashes[0]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea ae 10 9c
TBOOT: hashes[1]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea ae 10 9c
TBOOT: hashes[2]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea ae 10 9c
TBOOT: IA32_FEATURE_CONTROL_MSR: 0000ff07
TBOOT: CPU is SMX-capable
TBOOT: CPU is VMX-capable
TBOOT: SMX is enabled
TBOOT: TXT chipset and all needed capabilities present
TBOOT: LT.ERRORCODE=c00028d1
TBOOT: AC module error : acm_type=1, progress=0d, error=a
TBOOT: TPM error code = 0
TBOOT: LT.ESTS=0
TBOOT: bios_data (@7f720008, 2c):
TBOOT: version: 3
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: CR0.NE not set
TBOOT: CR0 and EFLAGS OK
TBOOT: no machine check errors
TBOOT: CPU is ready for SENTER
TBOOT: checking previous errors on the last boot.
Last boot has error.
TBOOT: user-provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN
TBOOT: chipset ids: vendor=8086, device=c002, revision=1
TBOOT: 1 ACM chipset id entries:
TBOOT: vendor=8086, device=c002, flags=1, revision=7, extended=0
TBOOT: copied SINIT (size=aa80) to 7f700000
TBOOT: AC mod base alignment OK
TBOOT: AC mod size OK
TBOOT: AC module header dump for SINIT:
TBOOT: type: 0x2 (ACM_TYPE_CHIPSET)
TBOOT: length: 0xa1 (161)
TBOOT: version: 0
TBOOT: chipset_ide: 0xd130
TBOOT: flags: 0x0
TBOOT: pre_production: 0
TBOOT: debug_signed: 0
TBOOT: vendor: 0x8086
TBOOT: date: 0x20100512
TBOOT: size*4: 0xaa80 (43648)
TBOOT: code_control: 0x0
TBOOT: entry point: 0x00000008:00008788
TBOOT: scratch_size: 0x8f (143)
TBOOT: info_table:
TBOOT: uuid: {0x7fc03aaa, 0x46a7, 0x18유, 0xac2e, {0x69, 0x8f, 0x8d, 0x41, 0x7f, 0x5a}}
TBOOT: ACM_UUID_V3
TBOOT: chipset_acm_type: 0x1 (SINIT)
TBOOT: version: 3
TBOOT: length: 0x28 (40)
TBOOT: chipset_id_list: 0x4e8
TBOOT: os_sinit_data_ver: 0x5
TBOOT: min_mle_hdr_ver: 0x00020000
TBOOT: capabilities: 0x0000000e
TBOOT: rlp_wake_getsec: 0
TBOOT: rlp_wake_monitor: 1
TBOOT: acm_vers: 20
TBOOT: chipset list:
TBOOT: count: 1
TBOOT: entry 0:
TBOOT: flags: 0x1
TBOOT: vendor_id: 0x8086
TBOOT: device_id: 0xc002
TBOOT: revision_id: 0x7
TBOOT: extended_id: 0x0
TBOOT: SINIT’s os_sinit_data version unsupported (5)
TBOOT: file addresses:
TBOOT: &_start=00803000
TBOOT: &_end=0084ec6c
TBOOT: &_mle_start=00803000
TBOOT: &_mle_end=00821000
TBOOT: &_post_launch_entry=00803020
TBOOT: &_txt_wakeup=008031f0
TBOOT: &g_mle_hdr=00818aa0
TBOOT: MLE header:
TBOOT: uuid={0x9082ac5a, 0x476f, 0x74a7, 0x5c0f, {0x55, 0xa2, 0xcb, 0x51, 0xb6, 0x42}}
TBOOT: length=34
TBOOT: version=00020001
TBOOT: entry_point=00000020
TBOOT: first_valid_page=00000000
TBOOT: mle_start_off=0
TBOOT: mle_end_off=1e000
TBOOT: capabilities: 0x00000003
TBOOT: rlp_wake_getsec: 1
TBOOT: rlp_wake_monitor: 1
TBOOT: MLE start=803000, end=821000, size=1e000
TBOOT: ptab_size=3000, ptab_base=00800000
TBOOT: bios_data (@7f720008, 2c):
TBOOT: version: 3
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440
TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0
TBOOT: no LCP manifest found
TBOOT: os_sinit_data (@7f720154, 5c):
TBOOT: version: 4TBOOT: mle_ptab: 0x800000TBOOT: mle_size: 0x1e000 (122880)
TBOOT: mle_hdr_base: 0x15920
TBOOT: vtd_pmr_los_base: 0x0
TBOOT: vtd_pmr_lo_size: 0x7bc00000
TBOOT: vtd_pmr_hi_base: 0x0
TBOOT: vtd_pmr_hi_size: 0x0
TBOOT: lcp_po_base: 0x0
TBOOT: lcp_po_size: 0x0 (0)
TBOOT: capabilities: 0x00000002
TBOOT: rlp_wake_getsec: 0
TBOOT: rlp_wake_monitor: 1
TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11
TBOOT: executing GETSEC[SENTER]...
________________________________
2010-08-12 오후 11:13, Wang, Shane 쓴 글:
PS: when I am saying TPM, I mean to check BIOS options.
________________________________
From: Wang, Shane
Sent: 2010年8月12日 22:12
To: 'Younghwan Go'
Subject: RE: Re: Hi Shane. I have question on tboot.
No. tboot is 32bit. Kernel can be 32b and 64b.
Hi, Get tboot hg repo from http://www.bughost.org/repos.hg/tboot.hg
And set vga_delay=5 (which means 5 seconds delay) in the grub command line to get the whole log.
Or, tell me whether or not you enable your TPM, take ownership, and define owner/aux indexes in it?
Shane
________________________________
From: Younghwan Go [mailto:yh...@ka...]
Sent: 2010年8月12日 14:57
To: Wang, Shane
Subject: Fwd: Re: Hi Shane. I have question on tboot.
Hi.
I sent you an email of the tboot log yesteryda.
I'm sending it just in case you missed it.
I have one more question. I was reading the README file and it said that Tboot is always build 32bit. Does that mean linux also has to be in 32bit? because mine is in 64bit.
Thanks.
Younghwan Go.
-------- 원본 메시지 --------
제목:
Re: Hi Shane. I have question on tboot.
날짜:
Wed, 11 Aug 2010 22:11:51 +0900
보낸 사람:
Younghwan Go <yh...@ka...><mailto:yh...@ka...>
받는 사람:
Wang, Shane <sha...@in...><mailto:sha...@in...>
Hi.
I've been trying to get the log from tboot.
Sinced I don't have serial port I was trying to find another way to get the log, but was not successful.
I partly got the tboot by just looking at the screen. this is the end part.
________________________________
TBOOT: o version: 3
TBOOT: o bios_sinit_size: 0x0 (0)
TBOOT: o lcp_pd_base: 0x0
TBOOT: o lcp_pd_size: 0x0 (0)
TBOOT: o num_logical_procs: 8
TBOOT: o flags: 0x0000000000
TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440
TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0
TBOOT: no LCP manifest found
TBOOT: os_sinit_data (@7f720154, 5c):
TBOOT: o version: 4
TBOOT: o mle_ptab: 0x800000
TBOOT: o mle_size: 0x1e000 (122880)
TBOOT: o mle_hdr_base: 0x15920
TBOOT: o vtd_pmr_los_base: 0x0
TBOOT: o vtd_pmr_lo_size: 0x7bc00000
TBOOT: o vtd_pmr_hi_base: 0x0
TBOOT: o vtd_pmr_hi_size: 0x0
TBOOT: o lcp_po_base: 0x0
TBOOT: o lcp_po_size: 0x0 (0)
TBOOT: o capabilities: 0x00000002
TBOOT: o rlp_wake_getsec: 0
TBOOT: o rlp_wake_monitor: 1
TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11
TBOOT: executing GETSEC[SENTER]...
________________________________
I also saw parts such as
no machine check erros
user provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN
SINIT' .... sinit_data version unsupported (5)
TPM error code 0
policy_type: TP_POLTYPE_CONT_NON_FATAL
policy_control: 00000001 (EXTEND_PCR17)
num_entries: 2
policy entry[0]:
mod_num: 0
pcr: none
hash_type: TB_HTYPE_ANY
num_hashes: 0
policy entry[1]:
mod_num: any
pcr: 19
hash_type: TB_HTYPE_ANY
num_hashes: 0
no policy in TPM NV
IA32_FEATURE_CONTROL_MSR: 0000ff07
CPU is SMX-capable
CPU is VMX-capable
SMX is enabled
________________________________
I couldn't find any TXT.ERRORCODE during boot.
I hope this is enough for you to see what the problem is.
I'm still trying to find another way to get the log.
Sincerely,
Younghwan Go
2010-08-11 오후 2:29, Wang, Shane 쓴 글:
Hi
Do you have serial port? If you have, can you send me the serial log. (here the log what you send is not what I want). I want something like "TBOOT.......". If you don't have, you must see on the screen. Can you show me "TXT.ERRORCODE=???" after you boot your system at the second time, and show me as more as possible on the screen?
Thanks.
Shane
________________________________
From: Younghwan Go [mailto:yh...@ka...]
Sent: 2010年8月11日 12:35
To: Wang, Shane
Subject: Hi Shane. I have question on tboot.
Hi Shane. My name is Younghwan Go.
I'm a student in Korean University called KAIST.
I've been studying on trusted computing and came upon your tboot project.
I tried to run it on my computer after following the steps you posted.
But when I did, I faced some problems I couldn't solve.
________________________________
My machine spec is as follows:
CPU : Intel Core i7-860 (2.8GHz)
M/B : Intel Q57 PCM
RAM : 6GB DDR3 SDRAM PC3-10600/1333Mhz
Graphics Card : Geforce GTX460 DDR5 1GB
My OS is running on:
Fedora 13, kernel 2.6.32.16.
menu.lst:
title Xen w/ Intel(R) Trusted Execution Technology - Fedora (2.6.32.16)
root (hd0,0)
kernel /tboot.gz logging=serial,vga,memory
module /xen.gz iommu=1 dom0_mem=524288 com1=115200,8n1
module /vmlinuz-2.6.32.16 ro root=/dev/mapper/vg_ndslpc2-lv_root rd_LVM_LV=vg_ndslpc2/lv_root rd_LVM_LV=vg_ndslpc2/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet intel_iommu=on 3
module /initramfs-2.6.32.16.img
module /i7_QUAD_SINIT_20.BIN
log message:
Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty2) main process (1674) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 init: system-setup-keyboard main process (1078) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty3) main process (1677) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty4) main process (1680) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty5) main process (1683) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty6) main process (1686) killed by TERM signal
Aug 10 15:40:05 ndsl-pc2 console-kit-daemon[1756]: WARNING: Couldn't read /proc/2144/environ: Failed to open file '/proc/2144/environ': No such file or directory
Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Got SIGTERM, quitting.
Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Leaving mDNS multicast group on interface eth0.IPv4 with address 143.248.151.113.
Aug 10 15:40:05 ndsl-pc2 libvirtd: 15:40:05.637: warning : qemudDispatchSignalEvent:396 : Shutting down on signal 15
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin Bugzilla
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin CCpp
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin Kerneloops
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin KerneloopsReporter
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Action plugin KerneloopsScanner
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin Logger
Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin Python
Aug 10 15:40:06 ndsl-pc2 abrtd: Got signal 15, exiting
Aug 10 15:40:10 ndsl-pc2 acpid: exiting
Aug 10 15:40:11 ndsl-pc2 ntpd[1498]: ntpd exiting on signal 15
Aug 10 15:40:11 ndsl-pc2 rpc.statd[1329]: Caught signal 15, un-registering and exiting
Aug 10 15:40:11 ndsl-pc2 NetworkManager[1302]: <info> caught signal 15, shutting down normally.
Aug 10 15:40:11 ndsl-pc2 NetworkManager[1302]: <info> exiting (success)
Aug 10 15:40:11 ndsl-pc2 rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Aug 10 15:40:11 ndsl-pc2 rtkit-daemon[1950]: Demoting known real-time threads.
Aug 10 15:40:11 ndsl-pc2 rtkit-daemon[1950]: Demoted 0 threads.
Aug 10 15:40:11 ndsl-pc2 console-kit-daemon[1756]: WARNING: no sender#012
Aug 10 15:40:11 ndsl-pc2 init: Disconnected from system bus
Aug 10 15:40:12 ndsl-pc2 auditd[1193]: The audit daemon is exiting.
Aug 10 15:40:12 ndsl-pc2 kernel: type=1305 audit(1281422412.008:35): audit_pid=0 old=1193 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
Aug 10 15:40:12 ndsl-pc2 cpuspeed: Disabling ondemand cpu frequency scaling governor
Aug 10 15:40:12 ndsl-pc2 kernel: Kernel logging (proc) stopped.
Aug 10 15:40:12 ndsl-pc2 rsyslogd: [origin software="rsyslogd" swVersion="4.4.2" x-pid="1220" x-info="http://www.rsyslog.com"] exiting on signal 15.
________________________________
The problem is when I add the SINIT module in menu.lst, whenever it is booting, it restarts after printing out
"Executing GETSEC[SENTER]..."
I tried tboot without SINIT module and it worked fine by just skipping tboot.
Can you help me solve this problem?
Thanks.
Sincerely,
Younghwan Go.
|
|
From: Younghwan Go <yh...@ka...> - 2010-09-18 00:29:50
|
Hi. I was working with TXT and got a SINIT error. The LT.ERRORCODE is c00004f1. According to this, progress value is 0fh and errorcode is 1. This means that it's VT-d remap engine enabled. I have iommu=on on the boot menu. Can you tell me how I should do this? Should I delete iommu=on from the boot menu? Thanks. Younghwan Go 2010-08-17 오후 2:38, Cihula, Joseph 쓴 글: > > You need to specify ‘iommu=on’ on the kernel command line---tboot is > DMA protecting memory and the kernel needs to enable VT-d to open the > DMA buffers. You should also be using a kernel built with > CONFIG_INTEL_TXT. > > Joe > |
|
From: Younghwan Go <yh...@ka...> - 2010-09-17 11:27:30
|
Hi.
I was working and got an error.
The LT.ERRORCODE is c00004f1.
According to this, progress value is 0fh and errorcode is 1.
This means that it's VT-d remap engine enabled.
I have iommu=on on the boot menu.
Can you tell me how I should do this? Should I delete iommu=on from the
boot menu?
Thanks.
Younghwan Go
2010-08-17 오후 2:38, Cihula, Joseph 쓴 글:
>
> You need to specify ‘iommu=on’ on the kernel command line---tboot is
> DMA protecting memory and the kernel needs to enable VT-d to open the
> DMA buffers. You should also be using a kernel built with
> CONFIG_INTEL_TXT.
>
> Joe
>
> *From:* Younghwan Go [mailto:yh...@ka...]
> *Sent:* Monday, August 16, 2010 10:19 PM
> *To:* Cihula, Joseph
> *Subject:* Re: Hi Shane. I have question on tboot.
>
> Hi Joe. Thank you for your email.
> I did tpmnv_relindex and it fixed the reboot problem :D
> But I encountered another problem after tboot :(
> All things that start with [TBOOT] are done and then it starts to load
> ubuntu kernel.
> However, it dies after giving out errors such as irq_stat 0x20000000
> host bus error and can't find the boot block.
> The same kernel can be booted without problem if it's booted without
> tboot.
> Right now, I set it so that it goes straight from tboot to linux. I
> didn't put Xen.gz.
> Is there a way to solve the problem?
> If I need to show you the boot log, where can I get it because it
> doesn't seem to be stored anywhere.
> Thanks.
>
> Younghwan Go.
>
> 2010-08-17 오전 8:25, Cihula, Joseph 쓴 글:
>
> Can you delete your owner index (0x40000001) and try again? You can do
> this with the tpmnv_relindex command in lcptools/ (load the driver and
> tcsd first).
>
> Joe
>
> ------------------------------------------------------------------------
>
> *From:* Younghwan Go [mailto:yh...@ka...]
> *Sent:* 2010年8月13日 13:24
> *To:* Wang, Shane
> *Subject:* Re: Hi Shane. I have question on tboot.
>
> Sorry. I forgot to include the last line.
> 0x10000001 0x50000001 0x40000001 0x1000f000 0x50000002 0x20000002
> 0x30000001 0x20000001
> Thanks.
>
> Younghwan Go.
>
> 2010-08-13 오후 2:04, Younghwan Go 쓴 글:
>
> Hi.
> I got this from tpmnv_getcap:
>
> ------------------------------------------------------------------------
>
> The response data is:
> 10 00 00 01 50 00 00 01 40 00 00 01 10 00 f0 00
> 50 00 00 02 20 00 00 02 30 00 00 01 20 00 00 01
>
>
> 8 indices have been defined
> list of indices for defined NV storage areas:
>
> ------------------------------------------------------------------------
>
> What I meant was can tboot work without Xen?
> I was using fedora before and that worked fine with just Xen, without
> tboot.
> Now I'm trying with ubunt but Xen seems to now work for some reason.
> Since in your README file, Xen is added in grub menu. That's why I was
> asking.
> The problem with tboot is same for both fedora and ubuntu.
> Thanks.
>
> Younghwan Go.
>
> 2010-08-13 오후 1:56, Wang, Shane 쓴 글:
>
> Thanks.
>
> Can you run "tpmnv_getcap"(you can find it in lcptools/) on your
> system? before doing that, you need to run "modprobe tpm_tis
> interrupts=0 force=1" and "tcsd". What do you see?
>
> Strange! The log says SINIT gets a TPM error. (The error code = 0).
> But in TPM, error code 0 means "success".
>
> Do you mean you can boot Xen with tboot now but can't boot ubuntu with
> tboot? Is that correct?
>
> Thanks.
>
> Shane
>
> ------------------------------------------------------------------------
>
> *From:* Younghwan Go [mailto:yh...@ka...]
> *Sent:* 2010年8月13日 11:59
> *To:* Wang, Shane
> *Subject:* Re: Hi Shane. I have question on tboot.
>
> Hi.
> I got the whole TBOOT log. :)
> Regarding the TPM, I checked with tpmmanager and confirmed that TPM is
> enabled and owner is set.
> I used tpm_takeownership -z command.
> I didn't fully understand the "define owner/aux indexes" part.
> Do you mean have I followed the steps of the policy text file in the
> tboot folder?
> There were some errors but eventually they were all successful.
> Also I'm wondering if not using Xen causes a problem because I've been
> using ubuntu and Xen seems to now work on it.
> Thank you for your help.
>
> Younghwan Go.
>
> ------------------------------------------------------------------------
>
> TBOOT: command line: logging=serial,vga,memory vga_delay = 5
> TBOOT: TPM is ready
> TBOOT: TPM nv_locked: TRUE
> TBOOT: read verified launch policy (256 bytes) from TPM NV
> TBOOT: policy:
> TBOOT: version: 2
> TBOOT: policy_type: TB_POLTYPE_CONT_NON_FATAL
> TBOOT: hash_alg: TB_HALG_SHA1
> TBOOT: policy_control: 00000001 (EXTEND_PCR17)
> TBOOT: num_entries: 3
> TBOOT: policy entry[0]:
> TBOOT: mod_num: 0
> TBOOT: pcr: none
> TBOOT: hash_type: TB_HTYPE_IMAGE
> TBOOT: num_hashes: 2
> TBOOT: hashes[0]: cb f6 2a ab c6 c9 27 eb e4 1c 2b 8e d7 05 1d b5 28
> b2 0b f8
> TBOOT: hashes[1]: cb f6 2a ab c6 c9 27 eb e4 1c 2b 8e d7 05 1d b5 28
> b2 0b f8
> TBOOT: policy entry[1]:
> TBOOT: mod_num: 1
> TBOOT: pcr: 19
> TBOOT: hash_type: TB_HTYPE_IMAGE
> TBOOT: num_hashes: 2
> TBOOT: hashes[0]: ec 28 2d a7 e7 86 46 8a 7e a0 c1 bd fa 9e e2 78 7b
> 10 e9 6c
> TBOOT: hashes[1]: ec 28 2d a7 e7 86 46 8a 7e a0 c1 bd fa 9e e2 78 7b
> 10 e9 6c
> TBOOT: policy entry[2]:
> TBOOT: mod_num: 2
> TBOOT: pcr: 19
> TBOOT: hash_type: TB_HTYPE_IMAGE
> TBOOT: num_hashes: 3
> TBOOT: hashes[0]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea
> ae 10 9c
> TBOOT: hashes[1]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea
> ae 10 9c
> TBOOT: hashes[2]: d3 51 45 c8 1a 52 50 2d 0e df 7b 30 86 01 f2 02 ea
> ae 10 9c
> TBOOT: IA32_FEATURE_CONTROL_MSR: 0000ff07
> TBOOT: CPU is SMX-capable
> TBOOT: CPU is VMX-capable
> TBOOT: SMX is enabled
> TBOOT: TXT chipset and all needed capabilities present
> TBOOT: LT.ERRORCODE=c00028d1
> TBOOT: AC module error : acm_type=1, progress=0d, error=a
> TBOOT: TPM error code = 0
> TBOOT: LT.ESTS=0
> TBOOT: bios_data (@7f720008, 2c):
> TBOOT: version: 3
> TBOOT: bios_sinit_size: 0x0 (0)
> TBOOT: lcp_pd_base: 0x0
> TBOOT: lcp_pd_size: 0x0 (0)
> TBOOT: num_logical_procs: 8
> TBOOT: flags: 0x00000000
> TBOOT: CR0.NE not set
> TBOOT: CR0 and EFLAGS OK
> TBOOT: no machine check errors
> TBOOT: CPU is ready for SENTER
> TBOOT: checking previous errors on the last boot.
> Last boot has error.
> TBOOT: user-provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN
> TBOOT: chipset ids: vendor=8086, device=c002, revision=1
> TBOOT: 1 ACM chipset id entries:
> TBOOT: vendor=8086, device=c002, flags=1, revision=7, extended=0
> TBOOT: copied SINIT (size=aa80) to 7f700000
> TBOOT: AC mod base alignment OK
> TBOOT: AC mod size OK
> TBOOT: AC module header dump for SINIT:
> TBOOT: type: 0x2 (ACM_TYPE_CHIPSET)
> TBOOT: length: 0xa1 (161)
> TBOOT: version: 0
> TBOOT: chipset_ide: 0xd130
> TBOOT: flags: 0x0
> TBOOT: pre_production: 0
> TBOOT: debug_signed: 0
> TBOOT: vendor: 0x8086
> TBOOT: date: 0x20100512
> TBOOT: size*4: 0xaa80 (43648)
> TBOOT: code_control: 0x0
> TBOOT: entry point: 0x00000008:00008788
> TBOOT: scratch_size: 0x8f (143)
> TBOOT: info_table:
> TBOOT: uuid: {0x7fc03aaa, 0x46a7, 0x18유, 0xac2e, {0x69, 0x8f, 0x8d,
> 0x41, 0x7f, 0x5a}}
> TBOOT: ACM_UUID_V3
> TBOOT: chipset_acm_type: 0x1 (SINIT)
> TBOOT: version: 3
> TBOOT: length: 0x28 (40)
> TBOOT: chipset_id_list: 0x4e8
> TBOOT: os_sinit_data_ver: 0x5
> TBOOT: min_mle_hdr_ver: 0x00020000
> TBOOT: capabilities: 0x0000000e
> TBOOT: rlp_wake_getsec: 0
> TBOOT: rlp_wake_monitor: 1
> TBOOT: acm_vers: 20
> TBOOT: chipset list:
> TBOOT: count: 1
> TBOOT: entry 0:
> TBOOT: flags: 0x1
> TBOOT: vendor_id: 0x8086
> TBOOT: device_id: 0xc002
> TBOOT: revision_id: 0x7
> TBOOT: extended_id: 0x0
> TBOOT: SINIT’s os_sinit_data version unsupported (5)
> TBOOT: file addresses:
> TBOOT: &_start=00803000
> TBOOT: &_end=0084ec6c
> TBOOT: &_mle_start=00803000
> TBOOT: &_mle_end=00821000
> TBOOT: &_post_launch_entry=00803020
> TBOOT: &_txt_wakeup=008031f0
> TBOOT: &g_mle_hdr=00818aa0
> TBOOT: MLE header:
> TBOOT: uuid={0x9082ac5a, 0x476f, 0x74a7, 0x5c0f, {0x55, 0xa2, 0xcb,
> 0x51, 0xb6, 0x42}}
> TBOOT: length=34
> TBOOT: version=00020001
> TBOOT: entry_point=00000020
> TBOOT: first_valid_page=00000000
> TBOOT: mle_start_off=0
> TBOOT: mle_end_off=1e000
> TBOOT: capabilities: 0x00000003
> TBOOT: rlp_wake_getsec: 1
> TBOOT: rlp_wake_monitor: 1
> TBOOT: MLE start=803000, end=821000, size=1e000
> TBOOT: ptab_size=3000, ptab_base=00800000
> TBOOT: bios_data (@7f720008, 2c):
> TBOOT: version: 3
> TBOOT: bios_sinit_size: 0x0 (0)
> TBOOT: lcp_pd_base: 0x0
> TBOOT: lcp_pd_size: 0x0 (0)
> TBOOT: num_logical_procs: 8
> TBOOT: flags: 0x00000000
> TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440
> TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0
> TBOOT: no LCP manifest found
> TBOOT: os_sinit_data (@7f720154, 5c):
> TBOOT: version: 4TBOOT: mle_ptab: 0x800000TBOOT: mle_size: 0x1e000
> (122880)
> TBOOT: mle_hdr_base: 0x15920
> TBOOT: vtd_pmr_los_base: 0x0
> TBOOT: vtd_pmr_lo_size: 0x7bc00000
> TBOOT: vtd_pmr_hi_base: 0x0
> TBOOT: vtd_pmr_hi_size: 0x0
> TBOOT: lcp_po_base: 0x0
> TBOOT: lcp_po_size: 0x0 (0)
> TBOOT: capabilities: 0x00000002
> TBOOT: rlp_wake_getsec: 0
> TBOOT: rlp_wake_monitor: 1
> TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11
> TBOOT: executing GETSEC[SENTER]...
>
> ------------------------------------------------------------------------
>
>
> 2010-08-12 오후 11:13, Wang, Shane 쓴 글:
>
> PS: when I am saying TPM, I mean to check BIOS options.
>
> ------------------------------------------------------------------------
>
> *From:* Wang, Shane
> *Sent:* 2010年8月12日 22:12
> *To:* 'Younghwan Go'
> *Subject:* RE: Re: Hi Shane. I have question on tboot.
>
> No. tboot is 32bit. Kernel can be 32b and 64b.
>
> Hi, Get tboot hg repo from http://www.bughost.org/repos.hg/tboot.hg
>
> And set vga_delay=5 (which means 5 seconds delay) in the grub command
> line to get the whole log.
>
> Or, tell me whether or not you enable your TPM, take ownership, and
> define owner/aux indexes in it?
>
> Shane
>
> ------------------------------------------------------------------------
>
> *From:* Younghwan Go [mailto:yh...@ka...]
> *Sent:* 2010年8月12日 14:57
> *To:* Wang, Shane
> *Subject:* Fwd: Re: Hi Shane. I have question on tboot.
>
> Hi.
> I sent you an email of the tboot log yesteryda.
> I'm sending it just in case you missed it.
> I have one more question. I was reading the README file and it said
> that Tboot is always build 32bit. Does that mean linux also has to be
> in 32bit? because mine is in 64bit.
> Thanks.
>
> Younghwan Go.
>
> -------- 원본 메시지 --------
>
> *제목**: *
>
>
>
> Re: Hi Shane. I have question on tboot.
>
> *날짜**: *
>
>
>
> Wed, 11 Aug 2010 22:11:51 +0900
>
> *보낸 사람**: *
>
>
>
> Younghwan Go <yh...@ka...> <mailto:yh...@ka...>
>
> *받는 사람**: *
>
>
>
> Wang, Shane <sha...@in...> <mailto:sha...@in...>
>
>
>
> Hi.
> I've been trying to get the log from tboot.
> Sinced I don't have serial port I was trying to find another way to
> get the log, but was not successful.
> I partly got the tboot by just looking at the screen. this is the end
> part.
>
> ------------------------------------------------------------------------
>
> TBOOT: o version: 3
> TBOOT: o bios_sinit_size: 0x0 (0)
> TBOOT: o lcp_pd_base: 0x0
> TBOOT: o lcp_pd_size: 0x0 (0)
> TBOOT: o num_logical_procs: 8
> TBOOT: o flags: 0x0000000000
> TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440
> TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0
> TBOOT: no LCP manifest found
> TBOOT: os_sinit_data (@7f720154, 5c):
> TBOOT: o version: 4
> TBOOT: o mle_ptab: 0x800000
> TBOOT: o mle_size: 0x1e000 (122880)
> TBOOT: o mle_hdr_base: 0x15920
> TBOOT: o vtd_pmr_los_base: 0x0
> TBOOT: o vtd_pmr_lo_size: 0x7bc00000
> TBOOT: o vtd_pmr_hi_base: 0x0
> TBOOT: o vtd_pmr_hi_size: 0x0
> TBOOT: o lcp_po_base: 0x0
> TBOOT: o lcp_po_size: 0x0 (0)
> TBOOT: o capabilities: 0x00000002
> TBOOT: o rlp_wake_getsec: 0
> TBOOT: o rlp_wake_monitor: 1
> TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11
> TBOOT: executing GETSEC[SENTER]...
>
> ------------------------------------------------------------------------
>
> I also saw parts such as
>
> no machine check erros
> user provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN
> SINIT' .... sinit_data version unsupported (5)
> TPM error code 0
> policy_type: TP_POLTYPE_CONT_NON_FATAL
> policy_control: 00000001 (EXTEND_PCR17)
> num_entries: 2
> policy entry[0]:
> mod_num: 0
> pcr: none
> hash_type: TB_HTYPE_ANY
> num_hashes: 0
> policy entry[1]:
> mod_num: any
> pcr: 19
> hash_type: TB_HTYPE_ANY
> num_hashes: 0
> no policy in TPM NV
> IA32_FEATURE_CONTROL_MSR: 0000ff07
> CPU is SMX-capable
> CPU is VMX-capable
> SMX is enabled
>
> ------------------------------------------------------------------------
>
> I couldn't find any TXT.ERRORCODE during boot.
> I hope this is enough for you to see what the problem is.
> I'm still trying to find another way to get the log.
>
> Sincerely,
> Younghwan Go
>
> 2010-08-11 오후 2:29, Wang, Shane 쓴 글:
>
> Hi
>
> Do you have serial port? If you have, can you send me the serial log.
> (here the log what you send is not what I want). I want something like
> "TBOOT.......". If you don't have, you must see on the screen. Can you
> show me "TXT.ERRORCODE=???" after you boot your system at the second
> time, and show me as more as possible on the screen?
>
> Thanks.
>
> Shane
>
> ------------------------------------------------------------------------
>
> *From:* Younghwan Go [mailto:yh...@ka...]
> *Sent:* 2010年8月11日 12:35
> *To:* Wang, Shane
> *Subject:* Hi Shane. I have question on tboot.
>
> Hi Shane. My name is Younghwan Go.
> I'm a student in Korean University called KAIST.
> I've been studying on trusted computing and came upon your tboot project.
> I tried to run it on my computer after following the steps you posted.
> But when I did, I faced some problems I couldn't solve.
>
> ------------------------------------------------------------------------
>
> My machine spec is as follows:
> CPU : Intel Core i7-860 (2.8GHz)
> M/B : Intel Q57 PCM
> RAM : 6GB DDR3 SDRAM PC3-10600/1333Mhz
> Graphics Card : Geforce GTX460 DDR5 1GB
>
> My OS is running on:
> Fedora 13, kernel 2.6.32.16.
>
> menu.lst:
> title Xen w/ Intel(R) Trusted Execution Technology - Fedora (2.6.32.16)
> root (hd0,0)
> kernel /tboot.gz logging=serial,vga,memory
> module /xen.gz iommu=1 dom0_mem=524288 com1=115200,8n1
> module /vmlinuz-2.6.32.16 ro root=/dev/mapper/vg_ndslpc2-lv_root
> rd_LVM_LV=vg_ndslpc2/lv_root rd_LVM_LV=vg_ndslpc2/lv_swap rd_NO_LUKS
> rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
> KEYTABLE=us nomodeset rhgb quiet intel_iommu=on 3
> module /initramfs-2.6.32.16.img
> module /i7_QUAD_SINIT_20.BIN
>
> log message:
>
> Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty2) main process (1674)
> killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 init: system-setup-keyboard main process
> (1078) killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty3) main process (1677)
> killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty4) main process (1680)
> killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty5) main process (1683)
> killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 init: tty (/dev/tty6) main process (1686)
> killed by TERM signal
> Aug 10 15:40:05 ndsl-pc2 console-kit-daemon[1756]: WARNING: Couldn't
> read /proc/2144/environ: Failed to open file '/proc/2144/environ': No
> such file or directory
> Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Got SIGTERM, quitting.
> Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Leaving mDNS multicast
> group on interface virbr0.IPv4 with address 192.168.122.1.
> Aug 10 15:40:05 ndsl-pc2 avahi-daemon[1313]: Leaving mDNS multicast
> group on interface eth0.IPv4 with address 143.248.151.113.
> Aug 10 15:40:05 ndsl-pc2 libvirtd: 15:40:05.637: warning :
> qemudDispatchSignalEvent:396 : Shutting down on signal 15
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin Bugzilla
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin CCpp
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin Kerneloops
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin
> KerneloopsReporter
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Action plugin
> KerneloopsScanner
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Reporter plugin Logger
> Aug 10 15:40:06 ndsl-pc2 abrtd: UnRegistered Analyzer plugin Python
> Aug 10 15:40:06 ndsl-pc2 abrtd: Got signal 15, exiting
> Aug 10 15:40:10 ndsl-pc2 acpid: exiting
> Aug 10 15:40:11 ndsl-pc2 ntpd[1498]: ntpd exiting on signal 15
> Aug 10 15:40:11 ndsl-pc2 rpc.statd[1329]: Caught signal 15,
> un-registering and exiting
> Aug 10 15:40:11 ndsl-pc2 NetworkManager[1302]: <info> caught signal
> 15, shutting down normally.
> Aug 10 15:40:11 ndsl-pc2 NetworkManager[1302]: <info> exiting (success)
> Aug 10 15:40:11 ndsl-pc2 rpcbind: rpcbind terminating on signal.
> Restart with "rpcbind -w"
> Aug 10 15:40:11 ndsl-pc2 rtkit-daemon[1950]: Demoting known real-time
> threads.
> Aug 10 15:40:11 ndsl-pc2 rtkit-daemon[1950]: Demoted 0 threads.
> Aug 10 15:40:11 ndsl-pc2 console-kit-daemon[1756]: WARNING: no sender#012
> Aug 10 15:40:11 ndsl-pc2 init: Disconnected from system bus
> Aug 10 15:40:12 ndsl-pc2 auditd[1193]: The audit daemon is exiting.
> Aug 10 15:40:12 ndsl-pc2 kernel: type=1305 audit(1281422412.008:35):
> audit_pid=0 old=1193 auid=4294967295 ses=4294967295
> subj=system_u:system_r:auditd_t:s0 res=1
> Aug 10 15:40:12 ndsl-pc2 cpuspeed: Disabling ondemand cpu frequency
> scaling governor
> Aug 10 15:40:12 ndsl-pc2 kernel: Kernel logging (proc) stopped.
> Aug 10 15:40:12 ndsl-pc2 rsyslogd: [origin software="rsyslogd"
> swVersion="4.4.2" x-pid="1220" x-info="http://www.rsyslog.com"]
> exiting on signal 15.
>
> ------------------------------------------------------------------------
>
>
> The problem is when I add the SINIT module in menu.lst, whenever it is
> booting, it restarts after printing out
> "Executing GETSEC[SENTER]..."
> I tried tboot without SINIT module and it worked fine by just skipping
> tboot.
> Can you help me solve this problem?
> Thanks.
>
> Sincerely,
> Younghwan Go.
>
|
|
From: Cihula, J. <jos...@in...> - 2010-08-23 16:51:08
|
> From: Martin Pirker [mailto:Mar...@ia...] > Sent: Monday, August 23, 2010 6:24 AM > > Hi... > > Tboot-ing a machine based on Arrandale platform works in text console. > X requires KMS for graphics. > As soon as Intel KMS framebuffer is activated screen looks like this: > http://i.imgur.com/4kW5y.jpg > > HD led is flashing and one can blindly type to reboot the machine, > however this is clearly unusable. > This problem does not happen without Tboot, graphics work normally. > > What am I missing (iommu is on)? Anybody succeeded with TXT on newest > iCore platforms with integrated Intel graphics yet? We're looking into issues with these systems. In the meantime, if you specify 'vga=normal nomodeset 3' to the Linux kernel that should get you a text console. Joe > > Thanks, > Martin > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > tboot-devel mailing list > tbo...@li... > https://lists.sourceforge.net/lists/listinfo/tboot-devel |
|
From: Martin P. <Mar...@ia...> - 2010-08-23 13:23:11
|
Hi... Tboot-ing a machine based on Arrandale platform works in text console. X requires KMS for graphics. As soon as Intel KMS framebuffer is activated screen looks like this: http://i.imgur.com/4kW5y.jpg HD led is flashing and one can blindly type to reboot the machine, however this is clearly unusable. This problem does not happen without Tboot, graphics work normally. What am I missing (iommu is on)? Anybody succeeded with TXT on newest iCore platforms with integrated Intel graphics yet? Thanks, Martin |
|
From: Michael G. <m.g...@tu...> - 2010-08-23 10:36:37
|
Hi list! On August 12th Shane committed a changeset which introduces storing TBoot's VLP as an LCP_CUSTOM_ELEMENT. What is the desired storage of VLPs in the long run? An own TPM NV RAM index or as a custom element in LCP_POLICY_DATA? Either way: as TBoot now supports this feature it would be good to define an UUID which identifies an LCP_CUSTOM_ELEMENT as a TBoot VLP. (I haven't found an UUID in Shane's code, maybe i missed it) btw: Shane could you please announce your contributions to the tboot source code repository as Joseph does via tboot-changelog@sf? Michael |
|
From: Cihula, J. <jos...@in...> - 2010-08-19 05:27:01
|
This is most likely due to the kernel not supporting VT-d. You really need to move to a 2.6.33+ kernel-is there some reason that you must use this version? I should also note that our original patch submission is not compatible with the latest versions of tboot, so if you must use a 2.6.30 kernel then you will need to backport from the latest kernel and not from the old patches. Joe From: Younghwan Go [mailto:yh...@ka...] Sent: Wednesday, August 18, 2010 10:15 PM To: tbo...@li... Subject: Re: [tboot-devel] How to build old kernel with CONFIG_INTEL_TXT Hi. I could compile the patch on kernel 2.6.30 successfully without any conflicts. So I ran tboot with this grub menu list: kernel /boot/tboot.gz logging=serial,vga,memory module /boot/vmlinuz-2.6.30-custom root=UUID=..... iommu=on ro quiet rhgb splash text module /boot/initrd.img-2.6.30-custom module /boot/i7_QUAD_SINIT_20.BIN quiet Tboot ran successfuly and transferred control back to kernel. Then error showed up. This is the error message. ________________________________ ehci_hcd 0000:00:1a.0: fatal error ehci_hcd 0000:00:1a.0: HC died; cleaning up hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) ehci_hcd 0000:00:1d.0: fatal error ehci_hcd 0000:00:1d.0: HC died; cleaning up hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) ata2: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x1 t4 ata2: irq_stat 0x20000000, host bus error ata1: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x1 t4 ata1: irq_stat 0x20000000, host bus error Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/1099bffc-45c7-4733-aafc-2abaac6b507 does not exist. Dropping to a shell! ________________________________ Can someone help me what the problem is? Thanks Younghwan Go. 2010-08-18 오후 6:00, Wang, Shane 쓴 글: Younghwan Go wrote: Hi. I was successful in booting without tboot.gz and the sinit. As I was searching, I came upon a site "http://lkml.org/lkml/2009/3/31/24"<http://lkml.org/lkml/2009/3/31/24> It said that with the patch given on the page, kernel 2.6.29 was successful in running tboot. So I changed my linux kernel 2.6.30 with the patch given. But it seems to not work still. Does this patch work with old kernels? If you can apply the patch without any conflicts, then the kernel can work with the patch. But I need to tell you, all TXT support doesn't include the only one patch. We pushed some later. Also, according to the README, I must write: module /vmlinuz.... intel_iommu=on ro root=LABEL=/ rhgb console=ttyS0,115200 3 I have question on whether intel_iommu is right or just iommu is right. Thanks. Younghwan Go It is iommu=on. |
|
From: Younghwan Go <yh...@ka...> - 2010-08-19 05:15:40
|
Hi. I could compile the patch on kernel 2.6.30 successfully without any conflicts. So I ran tboot with this grub menu list: kernel /boot/tboot.gz logging=serial,vga,memory module /boot/vmlinuz-2.6.30-custom root=UUID=..... iommu=on ro quiet rhgb splash text module /boot/initrd.img-2.6.30-custom module /boot/i7_QUAD_SINIT_20.BIN quiet Tboot ran successfuly and transferred control back to kernel. Then error showed up. This is the error message. ------------------------------------------------------------------------ ehci_hcd 0000:00:1a.0: fatal error ehci_hcd 0000:00:1a.0: HC died; cleaning up hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot reset port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) hub 1-0:1.0: cannot disable port 1 (err = -19) ehci_hcd 0000:00:1d.0: fatal error ehci_hcd 0000:00:1d.0: HC died; cleaning up hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot reset port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) hub 2-0:1.0: cannot disable port 1 (err = -19) ata2: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x1 t4 ata2: irq_stat 0x20000000, host bus error ata1: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x1 t4 ata1: irq_stat 0x20000000, host bus error Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/1099bffc-45c7-4733-aafc-2abaac6b507 does not exist. Dropping to a shell! ------------------------------------------------------------------------ Can someone help me what the problem is? Thanks Younghwan Go. 2010-08-18 ?? 6:00, Wang, Shane ? ?: > Younghwan Go wrote: >> Hi. I was successful in booting without tboot.gz and the sinit. >> As I was searching, I came upon a site >> "http://lkml.org/lkml/2009/3/31/24" It said that with the patch given >> on the page, kernel 2.6.29 was successful in running tboot. >> So I changed my linux kernel 2.6.30 with the patch given. >> But it seems to not work still. >> Does this patch work with old kernels? > If you can apply the patch without any conflicts, then the kernel can work with the patch. > But I need to tell you, all TXT support doesn't include the only one patch. We pushed some later. > >> Also, according to the README, I must write: >> module /vmlinuz.... intel_iommu=on ro root=LABEL=/ rhgb >> console=ttyS0,115200 3 >> I have question on whether intel_iommu is right or just iommu is >> right. Thanks. >> >> Younghwan Go >> > It is iommu=on. |
|
From: Wang, S. <sha...@in...> - 2010-08-18 09:01:43
|
Younghwan Go wrote: > Hi. I was successful in booting without tboot.gz and the sinit. > As I was searching, I came upon a site > "http://lkml.org/lkml/2009/3/31/24" It said that with the patch given > on the page, kernel 2.6.29 was successful in running tboot. > So I changed my linux kernel 2.6.30 with the patch given. > But it seems to not work still. > Does this patch work with old kernels? If you can apply the patch without any conflicts, then the kernel can work with the patch. But I need to tell you, all TXT support doesn't include the only one patch. We pushed some later. > > Also, according to the README, I must write: > module /vmlinuz.... intel_iommu=on ro root=LABEL=/ rhgb > console=ttyS0,115200 3 > I have question on whether intel_iommu is right or just iommu is > right. Thanks. > > Younghwan Go > It is iommu=on. |
|
From: Younghwan Go <yh...@ka...> - 2010-08-18 06:29:08
|
Hi. I was successful in booting without tboot.gz and the sinit. As I was searching, I came upon a site "http://lkml.org/lkml/2009/3/31/24" It said that with the patch given on the page, kernel 2.6.29 was successful in running tboot. So I changed my linux kernel 2.6.30 with the patch given. But it seems to not work still. Does this patch work with old kernels? Also, according to the README, I must write: module /vmlinuz.... intel_iommu=on ro root=LABEL=/ rhgb console=ttyS0,115200 3 I have question on whether intel_iommu is right or just iommu is right. Thanks. Younghwan Go 2010-08-18 오후 12:22, Wang, Shane 쓴 글: > Younghwan Go, > > If you want to build kernel with tboot/TXT support, you should use>= 2.6.33 and set 'CONFIG_INTEL_TXT=y' by "make menuconfig". > > Can you check your "root=XXX" in your grub? > I assume you have the following grub menu. > > root (hd0,0) > kernel /tboot.gz logging=serial,vga,memory > module /vmlinuz > module /initrd > module /i7_QUAD_SINIT_20.BIN > > Try to remove tboot.gz and the sinit to be > kernel /vmlinuz > module /initrd > > To see whether you can find the root device? > > Thanks. > Shane > > Younghwan Go wrote: >> Hi. I've been working on tboot. >> I was successful in running tboot but I encountered a problem when it >> was trying to boot my kernel. >> It says that it cannot find the root device. >> I asked around and was told that I need to build kernel with >> CONFIG_INTEL_TXT. >> I thought it was done after enabling vt-d by adding iommu=on in grub >> command list. >> But there was something more :( >> I'm trying to work on old kernel versions such as 2.6.30. >> Can someone help me solve this problem? >> Thanks. >> >> Younghwan Go. >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> tboot-devel mailing list >> tbo...@li... >> https://lists.sourceforge.net/lists/listinfo/tboot-devel |
|
From: Wang, S. <sha...@in...> - 2010-08-18 03:23:38
|
Younghwan Go,
If you want to build kernel with tboot/TXT support, you should use >= 2.6.33 and set 'CONFIG_INTEL_TXT=y' by "make menuconfig".
Can you check your "root=XXX" in your grub?
I assume you have the following grub menu.
root (hd0,0)
kernel /tboot.gz logging=serial,vga,memory
module /vmlinuz
module /initrd
module /i7_QUAD_SINIT_20.BIN
Try to remove tboot.gz and the sinit to be
kernel /vmlinuz
module /initrd
To see whether you can find the root device?
Thanks.
Shane
Younghwan Go wrote:
> Hi. I've been working on tboot.
> I was successful in running tboot but I encountered a problem when it
> was trying to boot my kernel.
> It says that it cannot find the root device.
> I asked around and was told that I need to build kernel with
> CONFIG_INTEL_TXT.
> I thought it was done after enabling vt-d by adding iommu=on in grub
> command list.
> But there was something more :(
> I'm trying to work on old kernel versions such as 2.6.30.
> Can someone help me solve this problem?
> Thanks.
>
> Younghwan Go.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> tboot-devel mailing list
> tbo...@li...
> https://lists.sourceforge.net/lists/listinfo/tboot-devel
|
|
From: Younghwan Go <yh...@ka...> - 2010-08-18 02:23:05
|
Hi. I've been working on tboot. I was successful in running tboot but I encountered a problem when it was trying to boot my kernel. It says that it cannot find the root device. I asked around and was told that I need to build kernel with CONFIG_INTEL_TXT. I thought it was done after enabling vt-d by adding iommu=on in grub command list. But there was something more :( I'm trying to work on old kernel versions such as 2.6.30. Can someone help me solve this problem? Thanks. Younghwan Go. |
|
From: Wang, S. <sha...@in...> - 2010-08-12 14:13:36
|
Per error code in sinit_errors.txt, your TXT.ERRORCODE=0xc00028d1.
It seems your TPM returns an error. Please check your TPM.
Can you use the latest tboot code and set "vga_delay=5" in the grub command line to get the whole log?
Thanks.
Shane
________________________________
From: Younghwan Go [mailto:yh...@ka...]
Sent: 2010年8月12日 16:54
To: tbo...@li...
Subject: [tboot-devel] It reboots after showing Executing GETSEC[SENTER]...
Hi. I've just started using tboot for few days now.
I've got compiled the tboot (tboot-20090330) successfully and did all the policy.
________________________________
title Xen w/ Intel(R) Trusted Execution Technology - Fedora (2.6.32.16)
root (hd0,0)
kernel /tboot.gz logging=serial,vga,memory
module /vmlinuz-2.6.32.16 ro root=/dev/mapper/vg_ndslpc2-lv_root rd_LVM_LV=vg_ndslpc2/lv_root rd_LVM_LV=vg_ndslpc2/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet intel_iommu=on 3
module /initramfs-2.6.32.16.img
module /i7_QUAD_SINIT_20.BIN
________________________________
This is my grub.conf.
When I booted with tboot, it showed tboot log such as this. (I had to manually type it by looking)
________________________________
...
no machine check erros
user provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN
SINIT' .... sinit_data version unsupported (5)
TPM error code 0
policy_type: TP_POLTYPE_CONT_NON_FATAL
policy_control: 00000001 (EXTEND_PCR17)
num_entries: 2
policy entry[0]:
mod_num: 0
pcr: none
hash_type: TB_HTYPE_ANY
num_hashes: 0
policy entry[1]:
mod_num: any
pcr: 19
hash_type: TB_HTYPE_ANY
num_hashes: 0
no policy in TPM NV
IA32_FEATURE_CONTROL_MSR: 0000ff07
CPU is SMX-capable
CPU is VMX-capable
SMX is enabled
...
TBOOT: o version: 3
TBOOT: o bios_sinit_size: 0x0 (0)
TBOOT: o lcp_pd_base: 0x0
TBOOT: o lcp_pd_size: 0x0 (0)
TBOOT: o num_logical_procs: 8
TBOOT: o flags: 0x0000000000
TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440
TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0
TBOOT: no LCP manifest found
TBOOT: os_sinit_data (@7f720154, 5c):
TBOOT: o version: 4
TBOOT: o mle_ptab: 0x800000
TBOOT: o mle_size: 0x1e000 (122880)
TBOOT: o mle_hdr_base: 0x15920
TBOOT: o vtd_pmr_los_base: 0x0
TBOOT: o vtd_pmr_lo_size: 0x7bc00000
TBOOT: o vtd_pmr_hi_base: 0x0
TBOOT: o vtd_pmr_hi_size: 0x0
TBOOT: o lcp_po_base: 0x0
TBOOT: o lcp_po_size: 0x0 (0)
TBOOT: o capabilities: 0x00000002
TBOOT: o rlp_wake_getsec: 0
TBOOT: o rlp_wake_monitor: 1
TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11
TBOOT: executing GETSEC[SENTER]...
________________________________
I used txt-stat to get additional information
________________________________
Intel(r) TXT Configuration Registers:
STS: 0x00000002
senter_done: FALSE
sexit_done: TRUE
mem_unlock: FALSE
mem_config_lock: FALSE
private_open: FALSE
mem_config_ok: FALSE
ESTS: 0x00
txt_reset: FALSE
txt_wake_error: FALSE
E2STS: 0x000000000000000c
slp_entry_error: FALSE
secrets: FALSE
block_mem: TRUE
reset: TRUE
ERRORCODE: 0xc00028d1
DIDVID: 0x00000001c0028086
vendor_id: 0x8086
device_id: 0xc002
revision_id: 0x1
SINIT.BASE: 0x7f700000
SINIT.SIZE: 131072B (0x20000)
HEAP.BASE: 0x7f720000
HEAP.SIZE: 917504B (0xe0000)
DPR: 0x000000007f800031
lock: TRUE
top: 0x7f800000
size: 3MB (3145728B)
***********************************************************
TXT measured launch: FALSE
secrets flag set: FALSE
***********************************************************
bios_data (@0x7fecac539008, 2c):
version: 3
bios_sinit_size: 0x0 (0)
lcp_pd_base: 0x0
lcp_pd_size: 0x0 (0)
num_logical_procs: 8
flags: 0x12000000000
unable to find TBOOT log
________________________________
Can you help me find why the tboot restarts after Executing GETSEC[SENTER]...?
Thanks.
|
|
From: Younghwan Go <yh...@ka...> - 2010-08-12 09:21:48
|
Hi. I've just started using tboot for few days now. I've got compiled the tboot (tboot-20090330) successfully and did all the policy. ------------------------------------------------------------------------ title Xen w/ Intel(R) Trusted Execution Technology - Fedora (2.6.32.16) root (hd0,0) kernel /tboot.gz logging=serial,vga,memory module /vmlinuz-2.6.32.16 ro root=/dev/mapper/vg_ndslpc2-lv_root rd_LVM_LV=vg_ndslpc2/lv_root rd_LVM_LV=vg_ndslpc2/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet intel_iommu=on 3 module /initramfs-2.6.32.16.img module /i7_QUAD_SINIT_20.BIN ------------------------------------------------------------------------ This is my grub.conf. When I booted with tboot, it showed tboot log such as this. (I had to manually type it by looking) ------------------------------------------------------------------------ ... no machine check erros user provided SINIT found: /boot/i7_QUAD_SINIT_20.BIN SINIT' .... sinit_data version unsupported (5) TPM error code 0 policy_type: TP_POLTYPE_CONT_NON_FATAL policy_control: 00000001 (EXTEND_PCR17) num_entries: 2 policy entry[0]: mod_num: 0 pcr: none hash_type: TB_HTYPE_ANY num_hashes: 0 policy entry[1]: mod_num: any pcr: 19 hash_type: TB_HTYPE_ANY num_hashes: 0 no policy in TPM NV IA32_FEATURE_CONTROL_MSR: 0000ff07 CPU is SMX-capable CPU is VMX-capable SMX is enabled ... TBOOT: o version: 3 TBOOT: o bios_sinit_size: 0x0 (0) TBOOT: o lcp_pd_base: 0x0 TBOOT: o lcp_pd_size: 0x0 (0) TBOOT: o num_logical_procs: 8 TBOOT: o flags: 0x0000000000 TBOOT: min_lo_ram: 0x0, max_lo_ram: 0x7bcad440 TBOOT: min_hi_ram: 0x0, max_hi_ram: 0x0 TBOOT: no LCP manifest found TBOOT: os_sinit_data (@7f720154, 5c): TBOOT: o version: 4 TBOOT: o mle_ptab: 0x800000 TBOOT: o mle_size: 0x1e000 (122880) TBOOT: o mle_hdr_base: 0x15920 TBOOT: o vtd_pmr_los_base: 0x0 TBOOT: o vtd_pmr_lo_size: 0x7bc00000 TBOOT: o vtd_pmr_hi_base: 0x0 TBOOT: o vtd_pmr_hi_size: 0x0 TBOOT: o lcp_po_base: 0x0 TBOOT: o lcp_po_size: 0x0 (0) TBOOT: o capabilities: 0x00000002 TBOOT: o rlp_wake_getsec: 0 TBOOT: o rlp_wake_monitor: 1 TBOOT: setting MTRRs for acmod: base=7f700000, size_aa80, num_pages=11 TBOOT: executing GETSEC[SENTER]... ------------------------------------------------------------------------ I used txt-stat to get additional information ------------------------------------------------------------------------ Intel(r) TXT Configuration Registers: STS: 0x00000002 senter_done: FALSE sexit_done: TRUE mem_unlock: FALSE mem_config_lock: FALSE private_open: FALSE mem_config_ok: FALSE ESTS: 0x00 txt_reset: FALSE txt_wake_error: FALSE E2STS: 0x000000000000000c slp_entry_error: FALSE secrets: FALSE block_mem: TRUE reset: TRUE ERRORCODE: 0xc00028d1 DIDVID: 0x00000001c0028086 vendor_id: 0x8086 device_id: 0xc002 revision_id: 0x1 SINIT.BASE: 0x7f700000 SINIT.SIZE: 131072B (0x20000) HEAP.BASE: 0x7f720000 HEAP.SIZE: 917504B (0xe0000) DPR: 0x000000007f800031 lock: TRUE top: 0x7f800000 size: 3MB (3145728B) *********************************************************** TXT measured launch: FALSE secrets flag set: FALSE *********************************************************** bios_data (@0x7fecac539008, 2c): version: 3 bios_sinit_size: 0x0 (0) lcp_pd_base: 0x0 lcp_pd_size: 0x0 (0) num_logical_procs: 8 flags: 0x12000000000 unable to find TBOOT log ------------------------------------------------------------------------ Can you help me find why the tboot restarts after Executing GETSEC[SENTER]...? Thanks. |
|
From: Cihula, J. <jos...@in...> - 2010-07-28 18:17:37
|
I like to keep the defaults together, i.e. in cmdline.c. There are inconsistencies with the logging defaults there and the ones assigned to g_log_targets, so I will correct that (eventually). Joe > -----Original Message----- > From: Michael Gissing [mailto:m.g...@tu...] > Sent: Thursday, July 22, 2010 8:01 AM > To: tbo...@li... > Subject: Re: [tboot-devel] Incorrect command line handling with GRUB 1.97 and above > > Hi! > > I forgot to mention that the initialization of g_log_targets in printk.c is pointless. > g_log_targets is always overwritten by get_tboot_log_targets() because get_option_val() will > return "serial" if logging isn't specified via command line. > > I suggest to remove "serial" from g_tboot_cmdline_options[] in cmdline.c (see attached diff) > > Michael |
|
From: Frédéric G. <sy...@ca...> - 2010-07-27 11:57:37
|
Ok, I found the problem with the Makefile. On Ubuntu, /bin/sh is linked
to /bin/dash. So when you run a command in the Makefile, it is
interpreted by Dash. However, Dash does not support "echo -e". I guess a
portable workaround would be to use "printf" instead (patch attached).
Fred
Signed-off-by: Frederic Guihery<sy...@ca...>
diff -r a5db79cb4fb8 lcptools/Makefile
--- a/lcptools/Makefile Tue Jul 27 01:54:29 2010 -0700
+++ b/lcptools/Makefile Tue Jul 27 13:55:26 2010 +0200
@@ -75,7 +75,7 @@
#
trousers_dep:
- @echo -e "#include <trousers/tss.h>" | $(CC) -x c $(CFLAGS)
$(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@ >/dev/null 2>&1 || (echo
trousers-devel package is not installed && false)
+ @printf "#include <trousers/tss.h>\n" | $(CC) -x c $(CFLAGS)
$(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@ >/dev/null 2>&1 || (echo
trousers-devel package is not installed && false)
#
# dependencies
On Mon, 26 Jul 2010 19:31:11 -0700, "Cihula, Joseph"
<jos...@in...> wrote:
> I applied the fix for lcptools.c (with a small change to cast to size_t).
>
> The change for lcptools/Makefile, however cause my system to fail to
> detect that trousers is not installed and thus causes a bunch of
> compilation errors. Please give more information as to how/why the
> current version of the Makefile is failing for you.
>
> Joe
>
>> -----Original Message-----
>> From: Frédéric Guihéry [mailto:sy...@ca...]
>> Sent: Monday, July 26, 2010 2:02 PM
>> To: tbo...@li...
>> Subject: Re: [tboot-devel] [PATCH] fix build errors
>>
>> With the attached file, it should be better.
>>
>> Le 26/07/2010 22:54, Frédéric Guihéry a écrit :
>> > Hi,
>> >
>> > Here is a tiny patch that fixes some issues I met building tboot.
>> >
>> > Kind regards,
>> > Frederic Guihery
>> >
>> > Signed-off-by: Frederic Guihery<sy...@ca...>
>> >
>> >
>> > diff -r 57ea1beb3bc8 lcptools/Makefile
>> > --- a/lcptools/Makefile Thu Jul 22 22:19:08 2010 -0700
>> > +++ b/lcptools/Makefile Mon Jul 26 22:33:28 2010 +0200
>> > @@ -75,7 +75,7 @@
>> > #
>> >
>> > trousers_dep:
>> > - @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
>> > $(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
>> > trousers-devel package is not installed&& false)
>> > + @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
>> > $(LDFLAGS) $(LIBS) -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
>> > trousers-devel package is not installed&& false)
>> >
>> > #
>> > # dependencies
>> > diff -r 57ea1beb3bc8 lcptools/lcptools.c
>> > --- a/lcptools/lcptools.c Thu Jul 22 22:19:08 2010 -0700
>> > +++ b/lcptools/lcptools.c Mon Jul 26 22:33:28 2010 +0200
>> > @@ -736,7 +736,7 @@
>> > pcr_length = select + sizeof(select)
>> > + sizeof(TPM_LOCALITY_SELECTION) +
>> > SHA1_HASH_LEN;
>> > /* check whether the data input is long enough */
>> > - if ( (pcr_length + (pread_data - src.listdata) -2)
>> > + if ( (pcr_length + (uint32_t)(pread_data -
>> > src.listdata) - 2)
>> > > src.listdata_length ) {
>> > log_error("the policy list data is not correct\n");
>> > result = LCP_E_COMD_INTERNAL_ERR;
>> >
|
|
From: Cihula, J. <jos...@in...> - 2010-07-27 02:31:22
|
I applied the fix for lcptools.c (with a small change to cast to size_t).
The change for lcptools/Makefile, however cause my system to fail to detect that trousers is not installed and thus causes a bunch of compilation errors. Please give more information as to how/why the current version of the Makefile is failing for you.
Joe
> -----Original Message-----
> From: Frédéric Guihéry [mailto:sy...@ca...]
> Sent: Monday, July 26, 2010 2:02 PM
> To: tbo...@li...
> Subject: Re: [tboot-devel] [PATCH] fix build errors
>
> With the attached file, it should be better.
>
> Le 26/07/2010 22:54, Frédéric Guihéry a écrit :
> > Hi,
> >
> > Here is a tiny patch that fixes some issues I met building tboot.
> >
> > Kind regards,
> > Frederic Guihery
> >
> > Signed-off-by: Frederic Guihery<sy...@ca...>
> >
> >
> > diff -r 57ea1beb3bc8 lcptools/Makefile
> > --- a/lcptools/Makefile Thu Jul 22 22:19:08 2010 -0700
> > +++ b/lcptools/Makefile Mon Jul 26 22:33:28 2010 +0200
> > @@ -75,7 +75,7 @@
> > #
> >
> > trousers_dep:
> > - @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
> > $(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
> > trousers-devel package is not installed&& false)
> > + @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
> > $(LDFLAGS) $(LIBS) -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
> > trousers-devel package is not installed&& false)
> >
> > #
> > # dependencies
> > diff -r 57ea1beb3bc8 lcptools/lcptools.c
> > --- a/lcptools/lcptools.c Thu Jul 22 22:19:08 2010 -0700
> > +++ b/lcptools/lcptools.c Mon Jul 26 22:33:28 2010 +0200
> > @@ -736,7 +736,7 @@
> > pcr_length = select + sizeof(select)
> > + sizeof(TPM_LOCALITY_SELECTION) +
> > SHA1_HASH_LEN;
> > /* check whether the data input is long enough */
> > - if ( (pcr_length + (pread_data - src.listdata) -2)
> > + if ( (pcr_length + (uint32_t)(pread_data -
> > src.listdata) - 2)
> > > src.listdata_length ) {
> > log_error("the policy list data is not correct\n");
> > result = LCP_E_COMD_INTERNAL_ERR;
> >
|
|
From: Frédéric G. <sy...@ca...> - 2010-07-26 20:56:42
|
With the attached file, it should be better.
Le 26/07/2010 22:54, Frédéric Guihéry a écrit :
> Hi,
>
> Here is a tiny patch that fixes some issues I met building tboot.
>
> Kind regards,
> Frederic Guihery
>
> Signed-off-by: Frederic Guihery<sy...@ca...>
>
>
> diff -r 57ea1beb3bc8 lcptools/Makefile
> --- a/lcptools/Makefile Thu Jul 22 22:19:08 2010 -0700
> +++ b/lcptools/Makefile Mon Jul 26 22:33:28 2010 +0200
> @@ -75,7 +75,7 @@
> #
>
> trousers_dep:
> - @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
> $(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
> trousers-devel package is not installed&& false)
> + @echo -e "#include<trousers/tss.h>" | $(CC) -x c $(CFLAGS)
> $(LDFLAGS) $(LIBS) -Wl,--defsym=main=0 -o $@>/dev/null 2>&1 || (echo
> trousers-devel package is not installed&& false)
>
> #
> # dependencies
> diff -r 57ea1beb3bc8 lcptools/lcptools.c
> --- a/lcptools/lcptools.c Thu Jul 22 22:19:08 2010 -0700
> +++ b/lcptools/lcptools.c Mon Jul 26 22:33:28 2010 +0200
> @@ -736,7 +736,7 @@
> pcr_length = select + sizeof(select)
> + sizeof(TPM_LOCALITY_SELECTION) +
> SHA1_HASH_LEN;
> /* check whether the data input is long enough */
> - if ( (pcr_length + (pread_data - src.listdata) -2)
> + if ( (pcr_length + (uint32_t)(pread_data -
> src.listdata) - 2)
> > src.listdata_length ) {
> log_error("the policy list data is not correct\n");
> result = LCP_E_COMD_INTERNAL_ERR;
>
|
|
From: Frédéric G. <sy...@ca...> - 2010-07-26 20:49:01
|
Hi,
Here is a tiny patch that fixes some issues I met building tboot.
Kind regards,
Frederic Guihery
Signed-off-by: Frederic Guihery <sy...@ca...>
diff -r 57ea1beb3bc8 lcptools/Makefile
--- a/lcptools/Makefile Thu Jul 22 22:19:08 2010 -0700
+++ b/lcptools/Makefile Mon Jul 26 22:33:28 2010 +0200
@@ -75,7 +75,7 @@
#
trousers_dep:
- @echo -e "#include <trousers/tss.h>" | $(CC) -x c $(CFLAGS)
$(LDFLAGS) $(LIBS) - -Wl,--defsym=main=0 -o $@ >/dev/null 2>&1 || (echo
trousers-devel package is not installed && false)
+ @echo -e "#include <trousers/tss.h>" | $(CC) -x c $(CFLAGS)
$(LDFLAGS) $(LIBS) -Wl,--defsym=main=0 -o $@ >/dev/null 2>&1 || (echo
trousers-devel package is not installed && false)
#
# dependencies
diff -r 57ea1beb3bc8 lcptools/lcptools.c
--- a/lcptools/lcptools.c Thu Jul 22 22:19:08 2010 -0700
+++ b/lcptools/lcptools.c Mon Jul 26 22:33:28 2010 +0200
@@ -736,7 +736,7 @@
pcr_length = select + sizeof(select)
+ sizeof(TPM_LOCALITY_SELECTION) +
SHA1_HASH_LEN;
/* check whether the data input is long enough */
- if ( (pcr_length + (pread_data - src.listdata) -2)
+ if ( (pcr_length + (uint32_t)(pread_data -
src.listdata) - 2)
> src.listdata_length ) {
log_error("the policy list data is not correct\n");
result = LCP_E_COMD_INTERNAL_ERR;
|
|
From: Michael G. <m.g...@tu...> - 2010-07-26 14:20:54
|
It's me again Joseph Cihula wrote: > changeset ccc9e78f30fa in /var/www/tboot.hg > details: tboot.hg?cmd=changeset;node=ccc9e78f30fa > description: > Added additional compiler warnings and cleaned up code to build cleanly This causes build errors on ubuntu systems: lcptools.c: In function ‘lcp_create_policy_list’: lcptools.c:740: error: comparison between signed and unsigned integer expressions gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1 and gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3 Michael |
15 messages has been excluded from this view by a project administrator.
