Yes, kernel works fine without tboot, but hangs up there when tboot loads
the kernel, even if TPM is usable ...

With tboot, the previous email has all the logs, you can tell it's from
kernel when there is no tboot prefix in the line.

For non-tboot boot, do you need the full log?

Best wishes,
--
Ning Qu


On Tue, Feb 28, 2012 at 4:10 PM, Cihula, Joseph <joseph.cih...@intel.com>wrote:

>  Can you also capture the output from the Linux kernel (on both a tboot
> and non-toot boot)?  (I presume the kernel works fine if you don’t use
> tboot?)****
>
> ** **
>
> Joe****
>
> ** **
>
> *From:* Ning Qu [mailto:qun...@gmail.com]
> *Sent:* Tuesday, February 28, 2012 3:44 PM
> *To:* Wei, Gang
> *Cc:* tboot-devel@lists.sourceforge.net
> *Subject:* Re: [tboot-devel] any version combination worked for xeon 5620?
> ****
>
> ** **
>
> Sorry about the delay, got caught up by something else. The information is
> inline below. Thanks for any inputs!****
>
>
> Best wishes,
> --
> Ning Qu
>
> ****
>
> On Sun, Feb 26, 2012 at 12:11 PM, Wei, Gang <gang....@intel.com> wrote:***
> *
>
> Before I can help, I need to know:****
>
> 1.       Which tboot version are you using? Upstream changeset
> 299/v1.7.0, rpms released with distro, or some else?****
>
>  tboot-1.7.0.tar.gz from tboot official website, built from source code.**
> **
>
>  2.       Are you using grub or grub2?****
>
>  grub2 ****
>
>  3.       Have you configure the kernel with TXT options enabled before
> build it?****
>
>  Yes, with TXT enabled.****
>
>  ****
>
>  4.       Can you attach the whole serial log while you come back again?**
> **
>
>  Here is the output when TPM is disabled in BIOS:****
>
> ** **
>
>  TBOOT: ******************* TBOOT ***********************
>
> TBOOT:    2012-01-15 23:30 +0800 1.7.0****
>
> TBOOT: *************************************************
>
> TBOOT: command line: /boot/tboot.gz logging=vga,memory,serial vga_delay=5*
> ***
>
> TBOOT: BSP is cpu 32****
>
> TBOOT: no e820 map, mem_lower=27a, mem_upper=33d5e4****
>
> TBOOT: TPM is disabled.****
>
> TBOOT: TPM: write nv 20000002, offset 00000000, 00000004 bytes, return =
> 00000002****
>
> TBOOT: Error: write TPM error: 0x2.****
>
> TBOOT: TPM not ready.****
>
> TBOOT: no LCP module found****
>
> TBOOT: Error: ELF magic number is not matched.****
>
> TBOOT: assuming kernel is Linux format****
>
> TBOOT: Initrd from 0x7fc25000 to 0x7ffff4a0****
>
> TBOOT: Kernel (protected mode) from 0x1000000 to 0x13d68a0****
>
> TBOOT: Kernel (real mode) from 0x90000 to 0x93c00****
>
> TBOOT: transfering control to kernel @0x1000000...****
>
>  ** **
>
> Here is the log when TPM is enabled.****
>
> ** **
>
>   TBOOT: ******************* TBOOT ***********************
>
> TBOOT:    2012-01-15 23:30 +0800 1.7.0****
>
> TBOOT: *************************************************
>
> TBOOT: command line: /boot/tboot.gz logging=vga,memory,serial vga_delay=5*
> ***
>
> TBOOT: BSP is cpu 32****
>
> TBOOT: no e820 map, mem_lower=27a, mem_upper=33d5e4****
>
> TBOOT: TPM is ready****
>
> TBOOT: TPM nv_locked: TRUE****
>
> TBOOT: TPM timeout values: A: 750, B: 750, C: 750, D: 750****
>
> TBOOT: Wrong timeout B, fallback to 2000****
>
> TBOOT: reading Verified Launch Policy from TPM NV...****
>
> TBOOT: TPM: get capability, return value = 00000002****
>
> TBOOT: TPM: fail to get public data of 0x20000001 in TPM NV****
>
> TBOOT:  :reading failed****
>
> TBOOT: reading Launch Control Policy from TPM NV...****
>
> TBOOT: TPM: get capability, return value = 00000002****
>
> TBOOT: TPM: fail to get public data of 0x40000001 in TPM NV****
>
> TBOOT:  :reading failed****
>
> TBOOT: failed to read policy from TPM NV, using default****
>
> 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: 2****
>
> TBOOT:   policy entry[0]:****
>
> TBOOT:           mod_num: 0****
>
> TBOOT:           pcr: none****
>
> TBOOT:           hash_type: TB_HTYPE_ANY****
>
> TBOOT:           num_hashes: 0****
>
> TBOOT:   policy entry[1]:****
>
> TBOOT:           mod_num: any****
>
> TBOOT:           pcr: 19****
>
> TBOOT:           hash_type: TB_HTYPE_ANY****
>
> TBOOT:           num_hashes: 0****
>
> TBOOT: TPM: write nv 20000002, offset 00000000, 00000004 bytes, return =
> 00000002****
>
> TBOOT: Error: write TPM error: 0x2.****
>
> TBOOT: no policy in TPM NV.****
>
> TBOOT: IA32_FEATURE_CONTROL_MSR: 00000005****
>
> TBOOT: CPU is SMX-capable****
>
> TBOOT: ERR: SENTER disabled by feature control MSR (5)****
>
> TBOOT: SMX not supported.****
>
> TBOOT: no LCP module found****
>
> TBOOT: Error: ELF magic number is not matched.****
>
> TBOOT: assuming kernel is Linux format****
>
> TBOOT: Initrd from 0x7fc25000 to 0x7ffff4a0****
>
> TBOOT: Kernel (protected mode) from 0x1000000 to 0x13d68a0****
>
> TBOOT: Kernel (real mode) from 0x90000 to 0x93c00****
>
> TBOOT: transfering control to kernel @0x1000000...****
>
>            ****
>
>           Decompressing Linux... Parsing ELF... done.****
>
>           Booting the kernel.****
>
> ** **
>
> Then just hangs up there forever ..****
>
> ** **
>
>  ****
>
>   ****
>
> Jimmy****
>
>  ****
>
> *From:* Ning Qu [mailto:qun...@gmail.com]
> *Sent:* Saturday, February 25, 2012 2:48 AM
> *To:* tboot-devel@lists.sourceforge.net
> *Subject:* [tboot-devel] any version combination worked for xeon 5620?****
>
>  ****
>
> I have tried tboot with both kernel 2.6.35.13 and 2.6.38.8, none of them
> work for me.****
>
>  ****
>
> My machine is with Xeon 5620, and without TXT enabled. I was hoping this
> will be easier since tboot will just switch back to regular mode and load
> kernel and boot up with it.****
>
>  ****
>
> However, I even can't get that working. The kernel hangs up there after
> uncompressing itslef ...****
>
>  ****
>
> Any idea about this? Or any suggestion with a combination of tboot and
> kernel that works for your case? Thanks!****
>
>  ****
>
>  ** **
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel

Reply via email to