FW: FWTS- DMA Remapping (VT-d) test
Huang, Bryan
bryanhuang at hpe.com
Mon Feb 21 08:21:47 UTC 2022
Hi Alex,
Thanks for your information.
I’m not fully understand the DMAR section, as shown below.
Would you please share how to check the DMAR section and the test purpose of DMAR with us?
== DMAR ==
[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
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]"?).
Sorry, I don't know how to reply to your question.
The multi-segment is our new support feature.
I cannot find 0001h:E7h:01h.00h in the lspci.log.
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?
Thanks.
Best regards,
Bryan
From: Alex Hung [mailto:alex.hung at canonical.com]
Sent: Saturday, February 19, 2022 8:52 AM
To: Huang, Rachel <rachel.huang at hpe.com>
Cc: Huang, Bryan <bryanhuang at hpe.com>; fwts-devel at lists.ubuntu.com; Chang, Alvin (HPE DVT UEFI) <achang at hpe.com>
Subject: Re: FW: FWTS- DMA Remapping (VT-d) test
This likely the be the results of the below mismatch in DMAR and PCI device lists
== DMAR ==
[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
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]"?).
This doesn't look like the only mismatched one. You can modify your ACPI BIOS and run the same test to verify.
On Thu, Feb 17, 2022 at 3:02 AM Huang, Rachel <rachel.huang at hpe.com<mailto:rachel.huang at hpe.com>> wrote:
Hi Alex and Bryan,
Capture all of the result log including acpi/cpuinfo/dmesg/dmidcode/Ispci as attachment.
BRs,
Rachel
From: Alex Hung <alex.hung at canonical.com<mailto:alex.hung at canonical.com>>
Sent: 17 February 2022 03:57
To: Huang, Bryan <bryanhuang at hpe.com<mailto:bryanhuang at hpe.com>>
Cc: fwts-devel at lists.ubuntu.com<mailto:fwts-devel at lists.ubuntu.com>; Chang, Alvin (HPE DVT UEFI) <achang at hpe.com<mailto:achang at hpe.com>>; Huang, Rachel <rachel.huang at hpe.com<mailto:rachel.huang at hpe.com>>
Subject: Re: FW: FWTS- DMA Remapping (VT-d) test
Hi Bryan,
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.
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.
On Wed, Feb 16, 2022 at 6:13 AM Huang, Bryan <bryanhuang at hpe.com<mailto:bryanhuang at hpe.com>> wrote:
Hi Alex and FWTS team members,
Here is TPE HPE Bryan Huang.
We ran DMA Remapping (VT-d) test and encountered the following FWTS issue as shown below. (The FWTS log is as attachment.)
According to this result, we have no further information.
Would you please help us to confirm it?
[cid:image002.jpg at 01D8272B.F6B8E8E0]
Thanks.
Best regards,
Bryan
From: Huang, Rachel
Sent: Wednesday, February 16, 2022 5:44 PM
To: Huang, Bryan <bryanhuang at hpe.com<mailto:bryanhuang at hpe.com>>
Cc: Chang, Alvin (HPE DVT UEFI) <achang at hpe.com<mailto:achang at hpe.com>>
Subject: RE: FWTS- DMA Remapping (VT-d) test
Hi Bryan,
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:
[cid:image003.png at 01D8272B.F6B8E8E0]
BRs,
Rachel
--
Cheers,
Alex Hung
--
Cheers,
Alex Hung
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20220221/aef50664/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 23888 bytes
Desc: image002.jpg
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20220221/aef50664/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 66774 bytes
Desc: image003.png
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20220221/aef50664/attachment-0001.png>
More information about the fwts-devel
mailing list