<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Hi Alex,<o:p></o:p> <o:p> </o:p> Thanks for your information.<o:p></o:p> I’m not fully understand the DMAR section, as shown below.<o:p></o:p> Would you please share how to check the DMAR section and the test purpose of DMAR with us?<o:p></o:p> <o:p> </o:p> <table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none"> <tbody> <tr> <td width="471" valign="top" style="width:467.5pt;border:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt"> <o:p> </o:p> == DMAR ==<o:p></o:p> <o:p> </o:p> [0D6h 0214 2] PCI Segment Number : 0001 [0D8h 0216 8] Register Base Address : 00000000E3FFC000 [0E0h 0224 1] Device Scope Type : 01 [PCI Endpoint Device] [0E1h 0225 1] Entry Length : 08 [0E2h 0226 2] Reserved : 0000 [0E4h 0228 1] Enumeration ID : 00 [0E5h 0229 1] PCI Bus Number : E7 [0E6h 0230 2] PCI Path : 01,00<o:p></o:p> <o:p> </o:p> </td> </tr> </tbody> </table> <o:p> </o:p> This points to PCI device 0001h:E7h:01h.00h (note the PCI seg number is 1). However, there is no such a device in the lspci.log (do you mean "0000:e7:00.1 System peripheral [0880]: Intel Corporation Device [8086:09a4]"?).<o:p></o:p> <o:p> </o:p> Sorry, I don't know how to reply to your question.<o:p></o:p> The multi-segment is our new support feature.<o:p></o:p> I cannot find 0001h:E7h:01h.00h in the lspci.log. <o:p></o:p> In this case, If we cannot find 0001h:E7h:01h.00h in the lspci.log, Is it a BIOS bug and needs to be fixed?<o:p></o:p> <o:p> </o:p> Thanks.<o:p></o:p> Best regards,<o:p></o:p> Bryan<o:p></o:p> From: Alex Hung [mailto:alex.hung@canonical.com] Sent: Saturday, February 19, 2022 8:52 AM To: Huang, Rachel <rachel.huang@hpe.com> Cc: Huang, Bryan <bryanhuang@hpe.com>; fwts-devel@lists.ubuntu.com; Chang, Alvin (HPE DVT UEFI) <achang@hpe.com> Subject: Re: FW: FWTS- DMA Remapping (VT-d) test<o:p></o:p> <o:p> </o:p> <div> <div> This likely the be the results of the below mismatch in DMAR and PCI device lists<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> == DMAR ==<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> [0D6h 0214 2] PCI Segment Number : 0001 [0D8h 0216 8] Register Base Address : 00000000E3FFC000 [0E0h 0224 1] Device Scope Type : 01 [PCI Endpoint Device] [0E1h 0225 1] Entry Length : 08 [0E2h 0226 2] Reserved : 0000 [0E4h 0228 1] Enumeration ID : 00 [0E5h 0229 1] PCI Bus Number : E7 [0E6h 0230 2] PCI Path : 01,00<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> This points to PCI device 0001h:E7h:01h.00h (note the PCI seg number is 1). However, there is no such a device in the lspci.log (do you mean "0000:e7:00.1 System peripheral [0880]: Intel Corporation Device [8086:09a4]"?).<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> This doesn't look like the only mismatched one. You can modify your ACPI BIOS and run the same test to verify.<o:p></o:p> </div> <div> <o:p> </o:p> </div> </div> <o:p> </o:p> <div> <div> On Thu, Feb 17, 2022 at 3:02 AM Huang, Rachel <<a href="mailto:rachel.huang@hpe.com">rachel.huang@hpe.com</a>> wrote:<o:p></o:p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> Hi Alex and Bryan,<o:p></o:p> <o:p></o:p> Capture all of the result log including acpi/cpuinfo/dmesg/dmidcode/Ispci as attachment.<o:p></o:p> <o:p></o:p> <o:p></o:p> BRs,<o:p></o:p> Rachel<o:p></o:p> <div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:currentcolor currentcolor"> From: Alex Hung <<a href="mailto:alex.hung@canonical.com" target="_blank">alex.hung@canonical.com</a>> Sent: 17 February 2022 03:57 To: Huang, Bryan <<a href="mailto:bryanhuang@hpe.com" target="_blank">bryanhuang@hpe.com</a>> Cc: <a href="mailto:fwts-devel@lists.ubuntu.com" target="_blank">fwts-devel@lists.ubuntu.com</a>; Chang, Alvin (HPE DVT UEFI) <<a href="mailto:achang@hpe.com" target="_blank">achang@hpe.com</a>>; Huang, Rachel <<a href="mailto:rachel.huang@hpe.com" target="_blank">rachel.huang@hpe.com</a>> Subject: Re: FW: FWTS- DMA Remapping (VT-d) test<o:p></o:p> </div> <o:p></o:p> <div> <div> Hi Bryan,<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> This requires more log files, including acpidump.log, lspci.log and dmesg.log, for more analysis. These files can be generated by "sudo fwts --dump". If fwts-live is used, they should be available in the same directory of the results.log.<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Having said that, I would guess the target DMAR has declared a PCI device, 0001h:E7h:01h.00h, but it is not present in the system under test. Please have a look at your DMAR table and PCI list.<o:p></o:p> </div> </div> <o:p></o:p> <div> <div> On Wed, Feb 16, 2022 at 6:13 AM Huang, Bryan <<a href="mailto:bryanhuang@hpe.com" target="_blank">bryanhuang@hpe.com</a>> wrote:<o:p></o:p> </div> <blockquote style="border:none;border-left:solid windowtext 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)"> <div> <div> Hi Alex and FWTS team members,<o:p></o:p> <o:p></o:p> Here is TPE HPE Bryan Huang.<o:p></o:p> We ran DMA Remapping (VT-d) test and encountered the following FWTS issue as shown below. (The FWTS log is as attachment.)<o:p></o:p> According to this result, we have no further information.<o:p></o:p> Would you please help us to confirm it?<o:p></o:p> <o:p></o:p> <img border="0" width="750" height="115" id="gmail-m_2034438784030935513gmail-m_-8337795240993553289_x005f_x0000_i1026" src="cid:image002.jpg@01D8272B.F6B8E8E0"><o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> Thanks.<o:p></o:p> Best regards, <o:p></o:p> Bryan<o:p></o:p> <div> <div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:currentcolor"> From: Huang, Rachel Sent: Wednesday, February 16, 2022 5:44 PM To: Huang, Bryan <<a href="mailto:bryanhuang@hpe.com" target="_blank">bryanhuang@hpe.com</a>> Cc: Chang, Alvin (HPE DVT UEFI) <<a href="mailto:achang@hpe.com" target="_blank">achang@hpe.com</a>> Subject: RE: FWTS- DMA Remapping (VT-d) test<o:p></o:p> </div> </div> <o:p></o:p> <o:p></o:p> Hi Bryan,<o:p></o:p> I’m going to start to test with DMA Remapping(VT-D) under FWTS test plan. Currently , check with the test result log and found one test fail while VT-D was enabled. Please review more detail as below:<o:p></o:p> <o:p></o:p> <img border="0" width="570" height="212" id="gmail-m_2034438784030935513gmail-m_-8337795240993553289Picture_x0020_1" src="cid:image003.png@01D8272B.F6B8E8E0"><o:p></o:p> <o:p></o:p> BRs,<o:p></o:p> Rachel<o:p></o:p> </div> </div> </blockquote> </div> -- <o:p></o:p> <div> <div> Cheers, Alex Hung<o:p></o:p> </div> </div> </div> </div> </blockquote> </div> -- <o:p></o:p> <div> <div> Cheers, Alex Hung<o:p></o:p> </div> </div> </div> </body> </html>