[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dmidecode] A "physical memory array" issue
From: |
Jean Delvare |
Subject: |
Re: [dmidecode] A "physical memory array" issue |
Date: |
Fri, 19 Jun 2009 14:02:23 +0200 |
Hi LiLin,
On Thu, 18 Jun 2009 07:19:46 +0000, Li, Lin (address@hidden) wrote:
> There is "physical memory array" issue on hp integrity ia64 server.
>
> Pls look that there is only seven trailing zeros in the following code, which
> has disorder the output of "Maximum Capacity".
I presume you meant "only six trailing zeroes". Seven is how many there
should be.
>
> [dmidecode.c]
>
> 2008 static void dmi_memory_array_capacity(u32 code)
> 2009 {
> 2010 if (code == 0x8000000)
> 2011 printf(" Unknown");
> 2012 else
> 2013 {
> 2014 if ((code & 0x000FFFFF) == 0)
> 2015 printf(" %u GB", code >> 20);
> 2016 else if ((code & 0x000003FF) == 0)
> 2017 printf(" %u MB", code >> 10);
> 2018 else
> 2019 printf(" %u kB", code);
> 2020 }
> 2021 }
>
>
> address@hidden dmidecode]# ./dmidecode -t 16
> # dmidecode 2.10
> # SMBIOS entry point at 0x3e52a000
> SMBIOS 2.4 present.
>
> Handle 0x0012, DMI type 16, 15 bytes
> Physical Memory Array
> Location: System Board Or Motherboard
> Use: System Memory
> Error Correction Type: Multi-bit ECC
> Maximum Capacity: 2048 GB
> Error Information Handle: Not Provided
> Number Of Devices: 12
You're right, this is a bug. Good catch... it's been there since the
very beginning of dmidecode 2.x.
Bug fixed in CVS:
http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&r1=1.141&r2=1.142
Thanks for reporting.
--
Jean Delvare