Right, you can see my output from Ross's dmardump utility at http://docs.google.com/View?id=df2b4r7r_1hcbtgbnd
Or here is the binary output of acpidump -t DMAR. BTW you can see the BEARLAKE chipset ID right there: DMAR @ 0x3e2c225f 0000: 44 4d 41 52 98 01 00 00 01 ce 43 4f 4d 50 41 51 DMAR......COMPAQ 0010: 42 45 41 52 4c 41 4b 45 01 00 00 00 00 00 00 00 BEARLAKE........ 0020: 00 00 00 00 23 00 00 00 00 00 00 00 00 00 00 00 ....#........... 0030: 00 00 18 00 00 00 00 00 00 00 d9 fe 00 00 00 00 ................ 0040: 01 08 00 00 00 00 1b 00 00 00 18 00 00 00 00 00 ................ 0050: 00 10 d9 fe 00 00 00 00 01 08 00 00 00 00 02 00 ................ 0060: 00 00 28 00 00 00 00 00 00 20 d9 fe 00 00 00 00 ..(...... ...... 0070: 01 08 00 00 00 00 03 00 01 08 00 00 00 00 03 02 ................ 0080: 01 08 00 00 00 00 03 03 00 00 10 00 01 00 00 00 ................ 0090: 00 30 d9 fe 00 00 00 00 01 00 20 00 00 00 00 00 .0........ ..... 00a0: 00 00 60 3e 00 00 00 00 ff ff ff 3e 00 00 00 00 ..`>.......>.... 00b0: 01 08 00 00 00 00 02 00 01 00 20 00 00 00 00 00 .......... ..... 00c0: 00 00 2d 3e 00 00 00 00 ff 0f 2d 3e 00 00 00 00 ..->......->.... 00d0: 01 08 00 00 00 00 1d 07 01 00 20 00 00 00 00 00 .......... ..... 00e0: 00 10 2d 3e 00 00 00 00 ff 1f 2d 3e 00 00 00 00 ..->......->.... 00f0: 01 08 00 00 00 00 1a 07 01 00 20 00 00 00 00 00 .......... ..... 0100: 00 20 2d 3e 00 00 00 00 ff 2f 2d 3e 00 00 00 00 . ->...../->.... 0110: 01 08 00 00 00 00 1d 00 01 00 20 00 00 00 00 00 .......... ..... 0120: 00 30 2d 3e 00 00 00 00 ff 3f 2d 3e 00 00 00 00 .0->.....?->.... 0130: 01 08 00 00 00 00 1d 01 01 00 20 00 00 00 00 00 .......... ..... 0140: 00 40 2d 3e 00 00 00 00 ff 4f 2d 3e 00 00 00 00 ....@->.....O->.... 0150: 01 08 00 00 00 00 1d 02 01 00 20 00 00 00 00 00 .......... ..... 0160: 00 50 2d 3e 00 00 00 00 ff 5f 2d 3e 00 00 00 00 .P->....._->.... 0170: 01 08 00 00 00 00 1a 00 01 00 20 00 00 00 00 00 .......... ..... 0180: 00 60 2d 3e 00 00 00 00 ff 6f 2d 3e 00 00 00 00 .`->.....o->.... 0190: 01 08 00 00 00 00 1a 01 ........ Comparing with the VT-d spec, it looks pretty reasonable to me. But I may be missing some details. There must be something about it that SINIT doesn't like. Hal On Thu, Jul 30, 2009 at 2:14 PM, Ross Philipson<ross.philip...@citrix.com> wrote: > Martin, > > The dump utility I gave Hal earlier was reading the ACPI tables and > formatting/tracing out the DMAR table from his system. The DMAR is there and > on the surface it looked correct to me (at least nothing obviously wrong with > it). Hal attached the trace in an earlier reply. > > Thanks > Ross > > -----Original Message----- > From: Martin Thiim [mailto:mar...@thiim.net] > Sent: Thursday, July 30, 2009 4:07 PM > To: Hal Finney > Cc: tboot-devel@lists.sourceforge.net > Subject: Re: [tboot-devel] GETSEC[SENTER] fail on HP dc7800 > > Hello Hal > > I could be wrong, but I think what the "Enable VT-d" option in the > BIOS really refers to is whether the BIOS should set up the ACPI > tables related to VT-d. > > You could use acpidump to see if those tables contain anything VT-d > related (DMAR and the like) - the VT-d spec would be helpful for this. > > http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Direct_IO.pdf > > I currently don't have access to my VT-d system so I can't give you a > table of what it looks like on my machine but perhaps others could. > > Best regards, > > Martin Thiim > > On Thu, Jul 30, 2009 at 7:28 PM, Hal Finney<hal.fin...@gmail.com> wrote: >> Hi Shane - I'm not sure what it would do to add these switches, since >> tboot doesn't get as far as launching the kernel, since it hangs in >> SENTER. However I can try doing it and then just booting into the >> kernel, in case I get any error reports about VT-d. >> >> Are there any MSRs or other registers I can patch tboot to dump out, >> to indicate whether VT-d is turned on? >> >> My HP dc7800 was one of the very first commercially released systems >> to support TXT. I bought one as soon as they became available in order >> to experiment with this technology. It has an E6550 "Conroe" processor >> with a Q35 "Bearlake" chipset. >> >> Hal >> >> On Thu, Jul 30, 2009 at 12:24 AM, Shane Wang<shane.w...@intel.com> wrote: >>> Hal, >>> >>> If you work with Xen, please try to add "iommu=1 vtd=1" in Xen command line >>> (i.e. the end of "module /boot/xen.gz ...") >>> If you work with Linux, please try to add "iommu=on" in the command >>> line (i.e. the end of "module /boot/vmlinuz-2.6.30 ..." >>> >>> PS: do you know which platform HP dc7800 is? *Field or *Dale? >>> Can you see VTd lsoc (Azalia) WA in BIOS or somewhere? >>> >>> Thanks. >>> Shane >>> >>> Hal Finney wrote: >>>> >>>> Thanks for the reply, Shane. VT-d is enabled in the BIOS; in fact, the >>>> BIOS automatically enables VT-d when TXT is enabled. >>>> >>>> I don't know of anything I would do in any grub configuration file to >>>> enable VT-d for tboot and SINIT. Do you have any suggestions? >>>> >>>> Hal >>>> >>>> On Wed, Jul 29, 2009 at 10:04 PM, Shane Wang<shane.w...@intel.com> wrote: >>>>> >>>>> Hi Hal >>>>> >>>>> The error code means VTd is disabled. >>>>> Is your VT-d enabled in your new BIOS and grub.conf? >>>>> >>>>> Thanks. >>>>> Shane >>>>> >>>>> Hal Finney wrote: >>>>>> >>>>>> I haven't run tboot in a while, but I'm trying it on my HP dc7800 and >>>>>> finding it hangs in GETSEC[SENTER]. This is even true with old >>>>>> versions of tboot that used to work. My system has no USB ports >>>>>> plugged in, and no hardware changes. >>>>>> >>>>>> The one change is I recently updated my BIOS. I suspect this has to be >>>>>> the cause. One nice thing about the new BIOS is that the tboot hang >>>>>> actually reboots the machine with the ERRORCODE register intact. Its >>>>>> value is c00020a1. This is progress code 0ah, error code 1000, >>>>>> meaning: "device scope of VT-d DMAR ACPI table is invalid". Not clear >>>>>> what this means. >>>>>> >>>>>> My log is attached, including the hang and the relaunch of tboot. This >>>>>> is version 20090330 of tboot. Thanks very much - >>>>>> >>>>>> Hal Finney >>>>> >>> >>> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> tboot-devel mailing list >> tboot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/tboot-devel >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > tboot-devel mailing list > tboot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tboot-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
