Thanks for the reply Mike.
Yes, I am able to boot 32 bit 2.6.38 kernel without tboot using the following 
grub.cfg entry:
menuentry "Ubuntu, with Linux 2.6.38-020638-generic (on /dev/sda1)" {   insmod 
part_msdos       insmod ext2     set root='(hd0,msdos1)' search --no-floppy 
--fs-uuid --set 154e4bc5-aa94-4e1d-9f1c-e6c5cda3ed38 linux 
/boot/vmlinuz-2.6.38-020638-generic 
root=UUID=154e4bc5-aa94-4e1d-9f1c-e6c5cda3ed38 ro quiet splash        initrd 
/boot/initrd.img-2.6.38-020638-generic}
I don't believe that the ERRORCODE got assigned any value at all during the 
tboot booting on 32 bit configuration. That's just being the log from last 
successful tboot boot on 64 bit configuration.
The whole thing is strange because, I am able to boot with tboot on exact same 
hardware configuration but using 64 bit Ubuntu dist and 64 bit kernel.
Anyway thanks again,CheersSansar
--- On Wed, 5/11/11, Mike Detwiler <j.michael.detwi...@gmail.com> wrote:
From: Mike Detwiler <j.michael.detwi...@gmail.com>Subject: Re: [tboot-devel] 
tboot on Ubuntu 10.10/ Linux kernel 2.6.38 32 bitTo: "Sansar Choinyambuu" 
<sunny_a42...@yahoo.com>Cc: "tboot mailing list" 
<tboot-devel@lists.sourceforge.net>Date: Wednesday, May 11, 2011, 4:53 AM
Hi Sansar,
On Wed, May 11, 2011 at 7:11 AM, Sansar Choinyambuu <sunny_a42...@yahoo.com> 
wrote:Hello everybody
I have a problem with booting with tboot on Ubuntu 10.10 (32 bit)/ Linux kernel 
2.6.38 (32 bit). I succeeded booting on same hardware but on 64 bit Ubuntu 
10.10 and 64 bit 2.6.38 kernel.
Now the problem is, TBOOT hangs on the screen on which I could see the 
following, then I've to power down to boot again....     TBOOT: VMXOFF done for 
cpu 1    TBOOT: cpu 1 is waking up, SIPI vector=9b000    TBOOT: VMXOFF done for 
cpu 4    TBOOT: cpu 4 is waking up, SIPI vector=9b000    TBOOT: VMXOFF done for 
cpu 5    TBOOT: cpu 5 is waking up, SIPI vector=9b000[ xxx ] ehci_hcd 
0000:00:1d.0: fatal error[ xxx] ehci_hcd 0000:00:1d.0: HC died; cleaning up[ 
xxx] hub 2-0:1.0 : cannot reset port 1 (err = - 19)...
Could somebody help me further on?
Thanks in advanceSansar Choinyambuu
------------------------------------------------- Attachment 
-----------------------------------------------
I've the following set of hardware:Intel DQ57TM board (with q57 Chipset) and 
Core i5 660 processor.I've updated my BIOS to the latest available version of 
22.03.2011.I've enabled TPM, VT-d, TXT enabled in BIOS and taken ownership of 
my TPM with well known passwords.
The following is the output I was able to get using tboot/utils/txt-stat after 
power down and boot without tboot:
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: 0x0000000000000000   
        slp_entry_error: FALSE          secrets: FALSE          block_mem: 
FALSE        reset: FALSE        ERRORCODE: 0x00000000
It looks like the measured/verified lanuch succeeded based on this ERRORCODE. 
The problem is further down the line.     DIDVID: 0x0000001fa0008086          
vendor_id: 0x8086       device_id: 0xa000       revision_id: 0x1f   SINIT.BASE: 
0xcb700000  SINIT.SIZE: 131072B (0x20000)   HEAP.BASE: 0xcb720000   HEAP.SIZE: 
917504B (0xe0000)    DPR: 0x00000000cb800031     lock: TRUE      top: 
0xcb800000         size: 3MB 
(3145728B)***********************************************************      TXT 
measured launch: FALSE      secrets flag set: 
FALSE***********************************************************ERROR: reading 
TXT heap failed by read()unable to find TBOOT log

Following is the entry in my grub.cfg :
menuentry "Ubuntu, with Linux 2.6.38-020638-generic with tboot (on /dev/sda1)"  
{       insmod part_msdos       insmod ext2     set root='(hd0,msdos1)'
This line looks strange to me (I'm not saying it's wrong). My root device is 
always ext2 not msdos and is set like this:
insmod ext2set root='(hd0,1)'
Are you able to boot your 32-bit kernel without tboot? What does that grub 
menuentry look like?
Good luck,
-Mike
        search --no-floppy --fs-uuid --set 154e4bc5-aa94-4e1d-9f1c-e6c5cda3ed38 
multiboot       /boot/tboot.gz tboot.gz logging=serial,vga,memory       module  
/boot/vmlinuz-2.6.38-020638-generic vmlinuz-2.6.38-020638-generic 
root=UUID=154e4bc5-aa94-4e1d-9f1c-e6c5cda3ed38 ro   quiet splash      module  
/boot/initrd.img-2.6.38-020638-generic initrd.img-2.6.38-020638-generic module  
/boot/i5_i7_DUAL_SINIT_18.BIN i5_i7_DUAL_SINIT_18.BIN   module 
/home/sansar/Project/tarballs/tboot-20101005/lcptools/list.data list.data}
------------------------------------------------------------------------------Achieve
 unprecedented app performance and reliabilityWhat every C/C++ and Fortran 
developer should know.Learn how Intel has extended the reach of its 
next-generation toolsto help boost performance applications - inlcuding 
clusters.http://p.sf.net/sfu/intel-dev2devmay_______________________________________________tboot-devel
 mailing 
listtboot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/tboot-devel
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel

Reply via email to