From: "Naik, Avadhut" <avadnaik@amd.com>
To: mailinglist@reox.at, "Žilvinas Žaltiena" <zilvinas@natrix.lt>
Cc: yazen.ghannam@amd.com, linux-edac@vger.kernel.org,
Borislav Petkov <bp@alien8.de>
Subject: Memory controller not showing half of the memory?
Date: Tue, 1 Apr 2025 13:00:52 -0500 [thread overview]
Message-ID: <3d9b82ed-a5ce-4d15-afb7-bce1dd40649b@amd.com> (raw)
In-Reply-To: <a1ed1aa7-96df-4c95-b818-4dd8f9da7c56@reox.at>
On 4/1/2025 06:44, mailinglist@reox.at wrote:
>
>
> Am 28.03.2025 um 16:24 schrieb Borislav Petkov:
>> On Thu, Mar 20, 2025 at 11:38:58AM +0200, Žilvinas Žaltiena wrote:
>>> Hello,
>>>
>>> I am also having this "half" memory problem - EDAC is showing 48GB instead
>>> of 96GB, however otherwise whole 96GB are usable by OS.
>>
>> Both of y'all folks encountering this issue, care to run the below patch?
>>
>> https://lore.kernel.org/all/20250327210718.1640762-1-avadhut.naik@amd.com/
>>
>> Thx.
>>
>
> I tried to apply it on the current Bookworm Backports kernel (6.12.12) - which seemed to work but I still get the same output, i.e., 32GB out of 64GB of RAM.
>
Think we are mixing up issues here. So, to clarify, there are two issues currently being worked on in the
amd64_edac module.
1. For Family 19h Models 70h-7Fh all UMCs are not enumerated by the module. 4 are present but only 2 are
enumerated. Currently, required approvals are being sought to upstream the fix. I think this is the issue
being encountered by Sebastian from the dmesg logs and lshw output provided in this thread.
2. For calculating DIMM sizes, the module does not consider both Address Mask and Address Mask Secondary
registers. Consequently, for non-power-of-2 DIMMs, the memory size logged by the module is inaccurate. I
think this is the issue being encountered by Žilvinas.
The patch that Boris asked you folks to try out fixes the second issue. Fix for the first issue has not
yet been submitted.
> I may not have built the kernel correct though... I did not had an environment to do that and just set one up. Or do I need a newer kernel version to apply the patch to? Sorry for the noob questions...
>
> Best,
> Sebastian
--
Thanks,
Avadhut Naik
next prev parent reply other threads:[~2025-04-01 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 17:21 Memory controller not showing half of the memory? reox
2025-03-13 17:31 ` Borislav Petkov
2025-03-13 17:48 ` reox
2025-03-17 12:07 ` Yazen Ghannam
2025-03-17 12:37 ` reox
2025-03-20 9:38 ` Žilvinas Žaltiena
2025-03-28 15:24 ` Borislav Petkov
2025-03-30 8:25 ` Žilvinas
2025-03-30 10:39 ` Borislav Petkov
2025-03-30 11:00 ` Žilvinas Žaltiena
2025-04-01 11:44 ` mailinglist
2025-04-01 18:00 ` Naik, Avadhut [this message]
2025-07-24 17:47 ` mailinglist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d9b82ed-a5ce-4d15-afb7-bce1dd40649b@amd.com \
--to=avadnaik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=mailinglist@reox.at \
--cc=yazen.ghannam@amd.com \
--cc=zilvinas@natrix.lt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.