Question about mtrr test
Colin Ian King
colin.king at canonical.com
Thu Jul 14 10:26:42 UTC 2016
On 14/07/16 11:08, Dong, Eric wrote:
> I use LUV v2.1-rc1 image to do the test, not sure the Fwts version. I think it is Fwts V16.06.00.
>
>
>> -----Original Message-----
>> From: Colin Ian King [mailto:colin.king at canonical.com]
>> Sent: Thursday, July 14, 2016 6:00 PM
>> To: Dong, Eric; fwts-devel at lists.ubuntu.com
>> Subject: Re: Question about mtrr test
>>
>> On 14/07/16 10:58, Dong, Eric wrote:
>>> Hi,
>>>
>>>
>>>
>>> I use Fwts to test the uefi bios, it reported below errors:
>>>
>>>
>>>
>>> mtrr ;HED mtrr: MTRR tests.
>>>
>>> mtrr ;SEP
>>> ------------------------------------------------------------
>>>
>>> mtrr ;INF MTRR overview
>>>
>>> mtrr ;INF -------------
>>>
>>> mtrr ;INF Reg 0: 0x00000000c0000000 - 0x0000000100000000 (
>>> 1024 MB) Uncached
>>>
>>> mtrr ;INF Reg 1: 0x00000000bf800000 - 0x00000000c0000000 (
>>> 8 MB) Uncached
>>>
>>> mtrr ;NLN
>>>
>>> mtrr ;INF Test 1 of 3: Validate the kernel MTRR IOMEM setup.
>>>
>>> mtrr ;FAL FAILED [MEDIUM] MTRRIncorrectAttr: Test 1, Memory range
>>>
>>> mtrr ;FAL 0x1000 to 0x5efff (System RAM) has incorrect attribute
>>>
>>> mtrr ;FAL Default (Most probably Uncached).
>>>
>>> mtrr ;FAL FAILED [MEDIUM] MTRRLackingAttr: Test 1, Memory
>>> range 0x1000
>>>
>>> mtrr ;FAL to 0x5efff (System RAM) is lacking attribute Write-Back.
>>>
>>>
>>>
>>> But we already update the IA32_MTRR_DEF_TYPE (0x2FF) to set the default
>>> type to Write-Back. If update the IA32_MTRR_DEF_TYPE to set the default
>>> type to Uncached. These errors will not occur. I think this is Fwts
>>> tools issue. It should check the default type from IA32_MTRR_DEF_TYPE
>>> before run this test. Any feedback about it?
OK, I think thats a bug, thanks for reporting that. I've filed it under:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1603026
Any ideas Ivan/Alex?
Colin
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>>
>>>
>>> This body part will be downloaded on demand.
>>>
>>
>> Eric, which version of fwts are you using?
>>
>
More information about the fwts-devel
mailing list