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:yhwa...@kaist.ac.kr] Sent: Wednesday, August 18, 2010 10:15 PM To: tboot-devel@lists.sourceforge.net 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.
------------------------------------------------------------------------------ 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 tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
