Thank you so much  for the details you provided.  We are working with our BIOS 
vendors to resolve the problem.

-Rajesh

-----Original Message-----
From: Dan Williams [mailto:dan.j.willi...@intel.com] 
Sent: Friday, June 19, 2020 8:20 PM
To: Ananth, Rajesh
Cc: linux-nvdimm
Subject: Re: Question on PMEM regions (Linux 4.9 Kernel & above)

SMART Modular Security Checkpoint: External email. Please make sure you trust 
this source before clicking links or opening attachments.

On Fri, Jun 19, 2020 at 7:02 PM Ananth, Rajesh <rajesh.ana...@smartm.com> wrote:
>
> We used the Ubuntu 18.04 to get the "acpdump" outputs (This is the only 
> complete package distribution we have. Otherwise, we use mainly the built 
> Kernels).  The NFIT data is all valid, but somehow it is printing the "@ 
> addresss" at the beginning as zeros.
>
> =============================  acpdump -n NFIT  
> ========================================
>
> NFIT @ 0x0000000000000000              <<<<  DON'T KNOW WHY.

That's fine, acpixtract was still able to convert it... I see this
from disassembling it:

acpixtract -s NFIT nfit.txt
iasl -d nft.dat
cat nfit.dsl


[000h 0000   4]                    Signature : "NFIT"    [NVDIMM
Firmware Interface Table]
[004h 0004   4]                 Table Length : 000001A4
[008h 0008   1]                     Revision : 01
[009h 0009   1]                     Checksum : 83
[00Ah 0010   6]                       Oem ID : "ALASKA"
[010h 0016   8]                 Oem Table ID : "A M I "
[018h 0024   4]                 Oem Revision : 00000002
[01Ch 0028   4]              Asl Compiler ID : "INTL"
[020h 0032   4]        Asl Compiler Revision : 20091013

[024h 0036   4]                     Reserved : 00000000

[028h 0040   2]                Subtable Type : 0000 [System Physical
Address Range]
[02Ah 0042   2]                       Length : 0038

[02Ch 0044   2]                  Range Index : 0001
[02Eh 0046   2]        Flags (decoded below) : 0002
                   Add/Online Operation Only : 0
                      Proximity Domain Valid : 1
[030h 0048   4]                     Reserved : 00000000
[034h 0052   4]             Proximity Domain : 00000000
[038h 0056  16]             Region Type GUID :
66F0D379-B4F3-4074-AC43-0D3318B78CDB
[048h 0072   8]           Address Range Base : 0000004080000000
[050h 0080   8]         Address Range Length : 0000000400000000
[058h 0088   8]         Memory Map Attribute : 0000000000008008
[..]
[0E0h 0224   2]                Subtable Type : 0000 [System Physical
Address Range]
[0E2h 0226   2]                       Length : 0038

[0E4h 0228   2]                  Range Index : 0002
[0E6h 0230   2]        Flags (decoded below) : 0002
                   Add/Online Operation Only : 0
                      Proximity Domain Valid : 1
[0E8h 0232   4]                     Reserved : 00000000
[0ECh 0236   4]             Proximity Domain : 00000000
[0F0h 0240  16]             Region Type GUID :
66F0D379-B4F3-4074-AC43-0D3318B78CDB
[100h 0256   8]           Address Range Base : 0000004480000000
[108h 0264   8]         Address Range Length : 0000000400000000
[110h 0272   8]         Memory Map Attribute : 0000000000008008


...so Linux is being handed an NFIT with 2 regions. So the 4.16
interpretation looks correct to me. Are you sure you only changed
kernel versions and did not also do a BIOS update? If not the 4.7
result looks like a bug for this NFIT.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-le...@lists.01.org

Reply via email to