From MAILER-DAEMON Fri Apr 01 04:25:40 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1aluOi-0007IN-6k
	for mharc-dmidecode-devel@gnu.org; Fri, 01 Apr 2016 04:25:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51764)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aluOg-0007Gx-8x
	for dmidecode-devel@nongnu.org; Fri, 01 Apr 2016 04:25:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aluOa-000437-Pn
	for dmidecode-devel@nongnu.org; Fri, 01 Apr 2016 04:25:38 -0400
Received: from userp1040.oracle.com ([156.151.31.81]:38083)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aluOa-00041B-HS
	for dmidecode-devel@nongnu.org; Fri, 01 Apr 2016 04:25:32 -0400
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234])
	by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with
	ESMTP id u318PTBX031822
	(version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dmidecode-devel@nongnu.org>; Fri, 1 Apr 2016 08:25:30 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72])
	by aserv0022.oracle.com (8.13.8/8.13.8) with ESMTP id u318PSGg012143
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dmidecode-devel@nongnu.org>; Fri, 1 Apr 2016 08:25:29 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11])
	by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u318PSIl015667
	for <dmidecode-devel@nongnu.org>; Fri, 1 Apr 2016 08:25:28 GMT
Received: from [10.167.102.69] (/10.167.102.69)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Fri, 01 Apr 2016 01:25:28 -0700
To: dmidecode-devel@nongnu.org
From: Eric Saint-Etienne <eric.saint.etienne@oracle.com>
Message-ID: <56FE3077.6020800@oracle.com>
Date: Fri, 1 Apr 2016 09:25:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
X-Received-From: 156.151.31.81
Subject: [dmidecode] non-dmi compliant systems
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dmidecode-devel@nongnu.org
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 08:25:39 -0000

Hi,

It appears that dmidecode can be called on systems that do not contain 
DMI tables. For instance the python-dmidecode module, often used to get 
system information, includes dmidecode sources, verbatim.
Programs that collect system information using python-dmidecode work 
fine on x86 compatible systems, but on machines such as SPARC, it simply 
makes cPython seg-fault when accessing non-existent DMI tables via mmap().

I'm only concerned with the SPARC case (no other arch has shout as of 
yet) and I've got a patch for an older version of dmidecode that 
prevents from accessing DMI tables on the SPARC architecture. It's 
basically a bunch of conditional compilation around accessing DMI tables.

If you find that using #if...#else at the right places an acceptable 
guard-rail, I'll then submit to this list a patch for the master branch.

When the patch will be in, other architectures/systems that don't 
support DMI tables (ARM?, MIPS?...) could be easily added.

Thanks
Eric


From MAILER-DAEMON Mon Apr 04 05:26:21 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1an0m5-0006gT-4U
	for mharc-dmidecode-devel@gnu.org; Mon, 04 Apr 2016 05:26:21 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43421)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1an0m2-0006gK-QO
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 05:26:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1an0lz-00073Q-K4
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 05:26:18 -0400
Received: from mx2.suse.de ([195.135.220.15]:38253)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1an0lz-00073K-DM
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 05:26:15 -0400
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254])
	by mx2.suse.de (Postfix) with ESMTP id 3A279AC64;
	Mon,  4 Apr 2016 09:26:13 +0000 (UTC)
Message-ID: <1459761973.14109.14.camel@chaos.suse>
From: Jean Delvare <jdelvare@suse.de>
To: dmidecode-devel@nongnu.org
Date: Mon, 04 Apr 2016 11:26:13 +0200
In-Reply-To: <56FE3077.6020800@oracle.com>
References: <56FE3077.6020800@oracle.com>
Organization: Suse Linux
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no
	timestamps) [generic]
X-Received-From: 195.135.220.15
Subject: Re: [dmidecode] non-dmi compliant systems
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dmidecode-devel@nongnu.org
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Apr 2016 09:26:19 -0000

Hello Eric,

Le Friday 01 April 2016 =C3=A0 09:25 +0100, Eric Saint-Etienne a =C3=A9cr=
it :
> Hi,
>=20
> It appears that dmidecode can be called on systems that do not contain=20
> DMI tables. For instance the python-dmidecode module, often used to get=
=20
> system information, includes dmidecode sources, verbatim.
> Programs that collect system information using python-dmidecode work=20
> fine on x86 compatible systems, but on machines such as SPARC, it simpl=
y=20
> makes cPython seg-fault when accessing non-existent DMI tables via mmap=
().
>=20
> I'm only concerned with the SPARC case (no other arch has shout as of=20
> yet) and I've got a patch for an older version of dmidecode that=20
> prevents from accessing DMI tables on the SPARC architecture. It's=20
> basically a bunch of conditional compilation around accessing DMI table=
s.
>=20
> If you find that using #if...#else at the right places an acceptable=20
> guard-rail, I'll then submit to this list a patch for the master branch=
.
>=20
> When the patch will be in, other architectures/systems that don't=20
> support DMI tables (ARM?, MIPS?...) could be easily added.

I'm confused. What is the point of building dmidecode (or
python-dmidecode for that matter) for systems which do not support DMI
in the first place?

--=20
Jean Delvare
SUSE L3 Support



From MAILER-DAEMON Mon Apr 04 08:33:32 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1an3hE-0002O7-8a
	for mharc-dmidecode-devel@gnu.org; Mon, 04 Apr 2016 08:33:32 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42990)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1an3h9-0002NI-46
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 08:33:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1an3h5-0001SS-UH
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 08:33:27 -0400
Received: from userp1040.oracle.com ([156.151.31.81]:35721)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1an3h5-0001SH-MA
	for dmidecode-devel@nongnu.org; Mon, 04 Apr 2016 08:33:23 -0400
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71])
	by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with
	ESMTP id u34CXLNY024468
	(version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 4 Apr 2016 12:33:21 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236])
	by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u34CXK7b027948
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 4 Apr 2016 12:33:20 GMT
Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12])
	by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id u34CXHhe025687;
	Mon, 4 Apr 2016 12:33:19 GMT
Received: from [10.167.102.69] (/10.167.102.69)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Mon, 04 Apr 2016 05:33:17 -0700
To: Jean Delvare <jdelvare@suse.de>, dmidecode-devel@nongnu.org
References: <56FE3077.6020800@oracle.com>
	<1459761973.14109.14.camel@chaos.suse>
From: Eric Saint-Etienne <eric.saint.etienne@oracle.com>
Message-ID: <57025F0B.3070702@oracle.com>
Date: Mon, 4 Apr 2016 13:33:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <1459761973.14109.14.camel@chaos.suse>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: userv0021.oracle.com [156.151.31.71]
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
X-Received-From: 156.151.31.81
Subject: Re: [dmidecode] non-dmi compliant systems
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dmidecode-devel@nongnu.org
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Apr 2016 12:33:31 -0000

Hi Jean,

On 04/04/16 10:26, Jean Delvare wrote:
> Hello Eric,
>
> I'm confused. What is the point of building dmidecode (or
> python-dmidecode for that matter) for systems which do not support DMI
> in the first place?
I see what you mean, but keep in mind that dmidecode ends up being 
called by softwares that are architecture agnostic, to gather 
information about the system.
In the occurence I'm concerned with, this high level architecture 
agnostic software is written in Python, which is a "portable" 
language/platform, so it's fair for this software to make use of 
python-dmidecode irrespectively of the architecture: if the DMI tables 
are present, then meaningful data will be extracted and returned by 
python-dmidecode. Otherwise python-dmidecode should not return anything.

At the moment, python-dmidecode acts as a mere wrapper around dmidecode 
C functions. The maintainer regularly rebases upon earlier versions of 
dmidecode sources that gets included verbatim into github 
python-dmidecode repo.

The integration flow {dmidecode -> python-dmidecode -> arch-agnostic 
diagnostic software} is not always controllable and I can see two options:
     - a guard rail in the midlleware python-dmidecode
     - or directly in dmidecode.

To me it makes sense to make dmidecode safer for the following reasons:
     - the middleware may not be the only one to include dmidecode 
sources, so that making dmidecode safer benefits to a larger scope of 
middlewares and diagnostic programs.
     - dmidecode-python would have to patch every rebase.

Kind Regards,
Eric


From MAILER-DAEMON Mon Apr 11 15:54:45 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1aphv3-0005CQ-RZ
	for mharc-dmidecode-devel@gnu.org; Mon, 11 Apr 2016 15:54:45 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42190)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1aphv1-00058E-Av
	for dmidecode-devel@nongnu.org; Mon, 11 Apr 2016 15:54:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1aphuy-0001Or-4X
	for dmidecode-devel@nongnu.org; Mon, 11 Apr 2016 15:54:43 -0400
Received: from mx2.suse.de ([195.135.220.15]:42887)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1aphux-0001Oi-RN
	for dmidecode-devel@nongnu.org; Mon, 11 Apr 2016 15:54:40 -0400
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254])
	by mx2.suse.de (Postfix) with ESMTP id C4096AC89;
	Mon, 11 Apr 2016 19:54:36 +0000 (UTC)
Message-ID: <1460404476.4247.21.camel@chaos.suse>
From: Jean Delvare <jdelvare@suse.de>
To: Eric Saint-Etienne <eric.saint.etienne@oracle.com>
Cc: dmidecode-devel@nongnu.org
Date: Mon, 11 Apr 2016 21:54:36 +0200
In-Reply-To: <57025F0B.3070702@oracle.com>
References: <56FE3077.6020800@oracle.com>
	<1459761973.14109.14.camel@chaos.suse> <57025F0B.3070702@oracle.com>
Organization: Suse Linux
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no
	timestamps) [generic]
X-Received-From: 195.135.220.15
Subject: Re: [dmidecode] non-dmi compliant systems
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 19:54:44 -0000

On lun., 2016-04-04 at 13:33 +0100, Eric Saint-Etienne wrote:
> Hi Jean,
> 
> On 04/04/16 10:26, Jean Delvare wrote:
> > Hello Eric,
> >
> > I'm confused. What is the point of building dmidecode (or
> > python-dmidecode for that matter) for systems which do not support DMI
> > in the first place?
> I see what you mean, but keep in mind that dmidecode ends up being 
> called by softwares that are architecture agnostic, to gather 
> information about the system.
> In the occurence I'm concerned with, this high level architecture 
> agnostic software is written in Python, which is a "portable" 
> language/platform, so it's fair for this software to make use of 
> python-dmidecode irrespectively of the architecture: if the DMI tables 

You are mixing two completely different things here. Portability of a
language has nothing to do with portability - desired or effective - of
programs written in said language.

> are present, then meaningful data will be extracted and returned by 
> python-dmidecode. Otherwise python-dmidecode should not return anything.

This is one possible way to implement it. But that's not the smartest
one IMVHO, see below.

> At the moment, python-dmidecode acts as a mere wrapper around dmidecode 
> C functions. The maintainer regularly rebases upon earlier versions of 
> dmidecode sources that gets included verbatim into github 
> python-dmidecode repo.

This is a mess I don't want to be involved in. dmidecode isn't a library
and shouldn't be used as one. There is libsmbios for that.

> The integration flow {dmidecode -> python-dmidecode -> arch-agnostic 
> diagnostic software} is not always controllable and I can see two options:

You are again mixing different things. You first "->" is source code
copy and wrapping up, while the second "->" is one piece of software
calling another, unrelated and independent piece of software.

>      - a guard rail in the midlleware python-dmidecode
>      - or directly in dmidecode.
> 
> To me it makes sense to make dmidecode safer for the following reasons:
>      - the middleware may not be the only one to include dmidecode 
> sources,

I very much hope it is the only one. One is one too much already as far
as I am concerned.

>  so that making dmidecode safer benefits to a larger scope of 
> middlewares and diagnostic programs.
>      - dmidecode-python would have to patch every rebase.

They already do exactly that. A little more, I can't see how that would
bother them.

Anyway I don't think the "fix" belongs to either dmidecode or
python-dmidecode. It belongs to whoever calls python-dmidecode. That
piece of software (you still did not tell us what it was?) should simply
be able to cope with python-dmidecode being absent on architectures
where it is not relevant. This is by far the most simple and optimal way
to solve your problem.

Once again, building dmidecode or python-dmidecode on architectures that
do not implement SMBIOS, for the sole purpose of them doing nothing
successfully, is a waste of time and energy. If you really want to do
that, just do:

# ln -s /usr/bin/false /usr/sbin/dmidecode
# ln -s /usr/bin/false /usr/sbin/python-dmidecode

(or /usr/bin/true, you decide.) Here, problem solved.

-- 
Jean Delvare
SUSE L3 Support



From MAILER-DAEMON Wed Apr 13 02:43:36 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1aqEWW-00043Z-Dk
	for mharc-dmidecode-devel@gnu.org; Wed, 13 Apr 2016 02:43:36 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45359)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aqEWU-00041J-8f
	for dmidecode-devel@nongnu.org; Wed, 13 Apr 2016 02:43:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aqEWR-0006lh-39
	for dmidecode-devel@nongnu.org; Wed, 13 Apr 2016 02:43:34 -0400
Received: from aserp1040.oracle.com ([141.146.126.69]:46077)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.saint.etienne@oracle.com>) id 1aqEWQ-0006PG-Sg
	for dmidecode-devel@nongnu.org; Wed, 13 Apr 2016 02:43:31 -0400
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234])
	by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with
	ESMTP id u3D6gSob023615
	(version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 13 Apr 2016 06:42:28 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235])
	by aserv0022.oracle.com (8.13.8/8.13.8) with ESMTP id u3D6gR9J023714
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 13 Apr 2016 06:42:28 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15])
	by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u3D6gR9C023793;
	Wed, 13 Apr 2016 06:42:27 GMT
Received: from [10.167.102.69] (/10.167.102.69)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Tue, 12 Apr 2016 23:42:27 -0700
To: Jean Delvare <jdelvare@suse.de>
References: <56FE3077.6020800@oracle.com>
	<1459761973.14109.14.camel@chaos.suse> <57025F0B.3070702@oracle.com>
	<1460404476.4247.21.camel@chaos.suse>
Cc: dmidecode-devel@nongnu.org
From: Eric Saint-Etienne <eric.saint.etienne@oracle.com>
Message-ID: <570DEA4C.2070209@oracle.com>
Date: Wed, 13 Apr 2016 07:42:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <1460404476.4247.21.camel@chaos.suse>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
X-Received-From: 141.146.126.69
Subject: Re: [dmidecode] non-dmi compliant systems
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 06:43:35 -0000

Thanks for the reply. I broadly agree with you, except on the following: 
you've got a opinionated view on how dmideode sources should be used, 
but considering dmidecode sources aren't always used the way you intend 
to, being practical and making them more safe looks like a good thing to me.

-eric


From MAILER-DAEMON Sun Apr 17 15:31:53 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1arsQD-0002yp-GW
	for mharc-dmidecode-devel@gnu.org; Sun, 17 Apr 2016 15:31:53 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34722)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1arsQA-0002uL-4W
	for dmidecode-devel@nongnu.org; Sun, 17 Apr 2016 15:31:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1arsQ9-0002Gg-Ab
	for dmidecode-devel@nongnu.org; Sun, 17 Apr 2016 15:31:50 -0400
Received: from mail-yw0-x22d.google.com ([2607:f8b0:4002:c05::22d]:35901)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1arsQ9-0002Gb-62
	for dmidecode-devel@nongnu.org; Sun, 17 Apr 2016 15:31:49 -0400
Received: by mail-yw0-x22d.google.com with SMTP id o66so183455418ywc.3
	for <dmidecode-devel@nongnu.org>; Sun, 17 Apr 2016 12:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to;
	bh=hJnyPJaaNG59V/Yn7dCzVYcJxhFt432bfVGU3z+wo9k=;
	b=yoZw0bLTDufZx7c0xLY0XnAYTodSJy9q3o+MzD2hR0ksuYwg9qjb2yWTuOn5r/tBjY
	jhtZ+Nb5JXGrARUAA1TwsYAWBVSK0vp33Qlk5FzxjAhW6AMEXcyTOPBSk0PsUB5kjcEM
	SOVBDgzTiozd42qwfu2msO45GCcGOcbiv5K1CuxHGapGftpLseyO3Xp4wl2C7OkvTehT
	9c1wqU6uibDZ6u1pvRqMaCwDbmCAMJINodryggSJUw3zQbJfPYFWe4Ks6z+SSDyGwgAi
	ONAlyG4zD8Dj83UnkdQHIBXQoth551LX9MRQ3wzMp/lQl16iaQ5CTuM0JPTxthNER6k/
	4b+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:date:message-id:subject:from
	:to; bh=hJnyPJaaNG59V/Yn7dCzVYcJxhFt432bfVGU3z+wo9k=;
	b=V8YaN9KLfri+XIWOw1JgP5jBpzRhswxkgw1yjywnUBSVl3L6BEHAx5Wna6v6B00Fjj
	iB1VXlXLU2Vsr+FxiAG5JJ9dpJgaF6zhtmISaBaUWa9vqCnPIx10FhLhKCswKNn9va6F
	PQKTPZyxauyxOS1atTVwqjDBAdHC9KUmwx2/OLJCcjo8rZioDW1tBLrdQb+Ugu6sUiSR
	C4VM19nnlebGEN8bjywzCrbJ8um0B+4x0uvZiYsdyeB260g1IMuRLjXkrBfI07BE0xVs
	dwYTMp7GBg8IIO/+gPVfUMHBgNDooLXbAp87eea6NaCS3UZ8ApAGxR+U/HdEpd4UM5Lk
	38OA==
X-Gm-Message-State: AOPr4FUh6ZOI2xziU/nm2myLbumBdIl+2ImOr8DmJ6BNdHkqu+e8n/zIRrqa7PkvegIilyIMN6kQkIFNz4BA8Q==
MIME-Version: 1.0
X-Received: by 10.13.204.144 with SMTP id o138mr19847311ywd.192.1460921508481; 
	Sun, 17 Apr 2016 12:31:48 -0700 (PDT)
Sender: xlmpkrst@gmail.com
Received: by 10.37.195.132 with HTTP; Sun, 17 Apr 2016 12:31:48 -0700 (PDT)
Date: Sun, 17 Apr 2016 19:31:48 +0000
X-Google-Sender-Auth: PYayFmhGfuLklQZ5Q3xgu4g1Ol0
Message-ID: <CADm8ZdWCUHzTtJCKT415Yx2Mk8q0wbik55ZabR6v2fGcVqK=-Q@mail.gmail.com>
From: shen long <wdlkmpx@gmail.com>
To: dmidecode-devel@nongnu.org
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2607:f8b0:4002:c05::22d
Subject: [dmidecode] dmidecode does not show DDR SDRAM size, speed..
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2016 19:31:52 -0000

I wonder if it can be solved, this is the mainboard:

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer: KOB
	Product Name: KOBP4M266A
	Version: 1.0
	Serial Number: 00000000
	UUID: Not Settable
	Wake-up Type: Modem Ring

This is the real info:
bank 1 DDR SDRAM 333 MHz (PC2700) 256 MB
bank 2 DDR SDRAM 333 MHz (PC2700) 256 MB

This is the output of dmidecode --type memory


# dmidecode 3.0
Scanning /dev/mem for entry point.
SMBIOS 2.3 present.

Handle 0x0007, DMI type 5, 24 bytes
Memory Controller Information
	Error Detecting Method: 32-bit ECC
	Error Correcting Capabilities:
		Single-bit Error Correcting
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 1024 MB
	Maximum Total Memory Size: 4096 MB
	Supported Speeds:
		70 ns
		60 ns
	Supported Memory Types:
		Standard
		FPM
		EDO
		Parity
		ECC
		SIMM
	Memory Module Voltage: 3.3 V
	Associated Memory Slots: 4
		0x0008
		0x0009
		0x000A
		0x000B
	Enabled Error Correcting Capabilities:
		Single-bit Error Correcting

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM1
	Bank Connections: 1 0
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 256 MB (Single-bank Connection)
	Enabled Size: 256 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM2
	Bank Connections: 3 2
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 256 MB (Single-bank Connection)
	Enabled Size: 256 MB (Single-bank Connection)
	Error Status: OK

Handle 0x000A, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM3
	Bank Connections: 5 4
	Current Speed: Unknown
	Type: Unknown
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK

Handle 0x000B, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM4
	Bank Connections: 7 6
	Current Speed: Unknown
	Type: Unknown
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK


From MAILER-DAEMON Mon Apr 18 05:48:42 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1as5nN-0007F8-UT
	for mharc-dmidecode-devel@gnu.org; Mon, 18 Apr 2016 05:48:41 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46725)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1as5nL-0007BJ-NK
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 05:48:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1as5nI-000465-HO
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 05:48:39 -0400
Received: from mx2.suse.de ([195.135.220.15]:48859)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1as5nI-00045k-BC
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 05:48:36 -0400
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254])
	by mx2.suse.de (Postfix) with ESMTP id 40CD8ABB4;
	Mon, 18 Apr 2016 09:48:33 +0000 (UTC)
Message-ID: <1460972913.18333.4.camel@chaos.suse>
From: Jean Delvare <jdelvare@suse.de>
To: dmidecode-devel@nongnu.org
Cc: shen long <wdlkmpx@gmail.com>
Date: Mon, 18 Apr 2016 11:48:33 +0200
In-Reply-To: <CADm8ZdWCUHzTtJCKT415Yx2Mk8q0wbik55ZabR6v2fGcVqK=-Q@mail.gmail.com>
References: <CADm8ZdWCUHzTtJCKT415Yx2Mk8q0wbik55ZabR6v2fGcVqK=-Q@mail.gmail.com>
Organization: Suse Linux
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no
	timestamps) [generic]
X-Received-From: 195.135.220.15
Subject: Re: [dmidecode] dmidecode does not show DDR SDRAM size, speed..
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 09:48:40 -0000

Hi Shen,

On dim., 2016-04-17 at 19:31 +0000, shen long wrote:
> I wonder if it can be solved, this is the mainboard:
> 
> Handle 0x0001, DMI type 1, 25 bytes
> System Information
> 	Manufacturer: KOB
> 	Product Name: KOBP4M266A
> 	Version: 1.0
> 	Serial Number: 00000000
> 	UUID: Not Settable
> 	Wake-up Type: Modem Ring
> 
> This is the real info:
> bank 1 DDR SDRAM 333 MHz (PC2700) 256 MB
> bank 2 DDR SDRAM 333 MHz (PC2700) 256 MB
> 
> This is the output of dmidecode --type memory
> 
> 
> # dmidecode 3.0
> Scanning /dev/mem for entry point.
> SMBIOS 2.3 present.
> 
> Handle 0x0007, DMI type 5, 24 bytes
> Memory Controller Information
> 	Error Detecting Method: 32-bit ECC
> 	Error Correcting Capabilities:
> 		Single-bit Error Correcting
> 	Supported Interleave: One-way Interleave
> 	Current Interleave: One-way Interleave
> 	Maximum Memory Module Size: 1024 MB
> 	Maximum Total Memory Size: 4096 MB
> 	Supported Speeds:
> 		70 ns
> 		60 ns
> 	Supported Memory Types:
> 		Standard
> 		FPM
> 		EDO
> 		Parity
> 		ECC
> 		SIMM
> 	Memory Module Voltage: 3.3 V
> 	Associated Memory Slots: 4
> 		0x0008
> 		0x0009
> 		0x000A
> 		0x000B
> 	Enabled Error Correcting Capabilities:
> 		Single-bit Error Correcting
> 
> Handle 0x0008, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM1
> 	Bank Connections: 1 0
> 	Current Speed: Unknown
> 	Type: DIMM SDRAM
> 	Installed Size: 256 MB (Single-bank Connection)
> 	Enabled Size: 256 MB (Single-bank Connection)

Module size is actually shown properly.

Speed is indeed missing. Please provide the output of
# dmidecode -t 6 -u
for confirmation, but most likely the information was not set by the
BIOS so there's nothing dmidecode can do about it.

Also check if you have type 17 records later on, as type 6 was
deprecated long ago. You may get more information from type 17 if
present.

> 	Error Status: OK
> 
> Handle 0x0009, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM2
> 	Bank Connections: 3 2
> 	Current Speed: Unknown
> 	Type: DIMM SDRAM
> 	Installed Size: 256 MB (Single-bank Connection)
> 	Enabled Size: 256 MB (Single-bank Connection)
> 	Error Status: OK
> 
> Handle 0x000A, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM3
> 	Bank Connections: 5 4
> 	Current Speed: Unknown
> 	Type: Unknown
> 	Installed Size: Not Installed
> 	Enabled Size: Not Installed
> 	Error Status: OK
> 
> Handle 0x000B, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM4
> 	Bank Connections: 7 6
> 	Current Speed: Unknown
> 	Type: Unknown
> 	Installed Size: Not Installed
> 	Enabled Size: Not Installed
> 	Error Status: OK

-- 
Jean Delvare



From MAILER-DAEMON Mon Apr 18 10:43:49 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1asAOz-0001RO-BI
	for mharc-dmidecode-devel@gnu.org; Mon, 18 Apr 2016 10:43:49 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60655)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1asAOv-0001J9-1Z
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 10:43:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1asAOr-0003NC-8t
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 10:43:44 -0400
Received: from mail-yw0-x243.google.com ([2607:f8b0:4002:c05::243]:36401)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <xlmpkrst@gmail.com>) id 1asAOr-0003Mx-4D
	for dmidecode-devel@nongnu.org; Mon, 18 Apr 2016 10:43:41 -0400
Received: by mail-yw0-x243.google.com with SMTP id u62so4846659ywe.3
	for <dmidecode-devel@nongnu.org>; Mon, 18 Apr 2016 07:43:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:cc; bh=GITeur0Vqh7pH0+412lrhScAgHhfYP2wPHrhmbBl01E=;
	b=gqacPJerSQGgOJkkTtgyTKb/VECDZZfoHnCx84TqWQkMSlQDOW7ZZaiRacwguDBoRz
	XMdRvVka43O0nEeLuSL82WdLu8ql13GT6poSC3JJkOyun7fjjQVgFV9SGkqz9tpRS3+o
	hi5mZjv94EbIIgI33g9Ttx1FAyHpFhNm8LqtFvwmmVch9k3jRzk4tndmh1lHbL7em7MF
	stxhJCPngBizTB0elpzr6iTyq/LNTSXecn2Slbf8GB5OBcU9sSQHOCTE23lf8L6oObl6
	m3vdCp5jCzWdV82lS4sLkzM5S30l6Huw3uVaL1o1xwyxJQHJWQWu2O7Tcmc6YqYr+l4Q
	XzeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
	:message-id:subject:from:to:cc;
	bh=GITeur0Vqh7pH0+412lrhScAgHhfYP2wPHrhmbBl01E=;
	b=lMN4U9f9knFp6RDby1avkIFFaB5NzpMB2WgsSnX0CK+JZQBipLzjggGDsbyMjC1Wnk
	CX7pBa/gsh7tJn1LE/djUGP/8Ij74IgsKYZ6BpstyCoKwyVJnYv/kd76FWzEzjEo3xTj
	glYQVj/ymzuXwFzGTjhkB5BPiBlq/DiYWYE1oVDMB+aL2kIZ05eY6WpzPjCMjF4VSG+w
	NliKFFlpRTuc0PIFq/1sk5SRodIQ02xIpqnJFa+iqM7KQyy32UxVwBgtUBlAePRLp0J3
	bJpgWmwV4gSk0AxUR4cJqu3Tik4KIOusnuHZVH7G+sr5isjAZKx83SBItXCppCLOes7e
	t3Cg==
X-Gm-Message-State: AOPr4FVvYKlFr5Ygu8RDCZWSh03ZPi6Gi1LQODvKNYlQ4SSPskIurOwt+9Sl+oF/GvM4Ra9WYXtQcneTfHWzTg==
MIME-Version: 1.0
X-Received: by 10.37.74.202 with SMTP id x193mr19680426yba.24.1460990620491;
	Mon, 18 Apr 2016 07:43:40 -0700 (PDT)
Sender: xlmpkrst@gmail.com
Received: by 10.37.195.132 with HTTP; Mon, 18 Apr 2016 07:43:40 -0700 (PDT)
In-Reply-To: <1460972913.18333.4.camel@chaos.suse>
References: <CADm8ZdWCUHzTtJCKT415Yx2Mk8q0wbik55ZabR6v2fGcVqK=-Q@mail.gmail.com>
	<1460972913.18333.4.camel@chaos.suse>
Date: Mon, 18 Apr 2016 14:43:40 +0000
X-Google-Sender-Auth: 65qAnDoXWUxI-XkV5Wwq_9Quat0
Message-ID: <CADm8ZdUDZppbqQ-kyP0N_CWTe_efHFq2gaOTwWCh-K-zTQhdXg@mail.gmail.com>
From: shen long <wdlkmpx@gmail.com>
To: dmidecode-devel@nongnu.org
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2607:f8b0:4002:c05::243
Subject: Re: [dmidecode] dmidecode does not show DDR SDRAM size, speed..
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 14:43:48 -0000

I have another ddr sdram module and I think it did not show the size.
No -t 17 records, I guess this thing is too old..

Output of # dmidecode -t 6 -u

# dmidecode 3.0
Scanning /dev/mem for entry point.
SMBIOS 2.3 present.

Handle 0x0008, DMI type 6, 12 bytes
	Header and Data:
		06 0C 08 00 01 10 00 00 05 08 08 00
	Strings:
		44 49 4D 4D 31 00
		"DIMM1"

Handle 0x0009, DMI type 6, 12 bytes
	Header and Data:
		06 0C 09 00 01 32 00 00 05 08 08 00
	Strings:
		44 49 4D 4D 32 00
		"DIMM2"

Handle 0x000A, DMI type 6, 12 bytes
	Header and Data:
		06 0C 0A 00 01 54 00 02 00 7F 7F 00
	Strings:
		44 49 4D 4D 33 00
		"DIMM3"

Handle 0x000B, DMI type 6, 12 bytes
	Header and Data:
		06 0C 0B 00 01 76 00 02 00 7F 7F 00
	Strings:
		44 49 4D 4D 34 00
		"DIMM4"


From MAILER-DAEMON Tue Apr 19 09:29:44 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1asViq-0005hz-SU
	for mharc-dmidecode-devel@gnu.org; Tue, 19 Apr 2016 09:29:44 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54979)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1asVik-0005TA-3e
	for dmidecode-devel@nongnu.org; Tue, 19 Apr 2016 09:29:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1asVig-0006oZ-T3
	for dmidecode-devel@nongnu.org; Tue, 19 Apr 2016 09:29:38 -0400
Received: from mx2.suse.de ([195.135.220.15]:33073)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdelvare@suse.de>) id 1asVig-0006oG-IF
	for dmidecode-devel@nongnu.org; Tue, 19 Apr 2016 09:29:34 -0400
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254])
	by mx2.suse.de (Postfix) with ESMTP id E93F3ABB2;
	Tue, 19 Apr 2016 13:29:29 +0000 (UTC)
Message-ID: <1461072568.3370.5.camel@chaos.suse>
From: Jean Delvare <jdelvare@suse.de>
To: shen long <wdlkmpx@gmail.com>
Cc: dmidecode-devel@nongnu.org
Date: Tue, 19 Apr 2016 15:29:28 +0200
In-Reply-To: <CADm8ZdUDZppbqQ-kyP0N_CWTe_efHFq2gaOTwWCh-K-zTQhdXg@mail.gmail.com>
References: <CADm8ZdWCUHzTtJCKT415Yx2Mk8q0wbik55ZabR6v2fGcVqK=-Q@mail.gmail.com>
	<1460972913.18333.4.camel@chaos.suse>
	<CADm8ZdUDZppbqQ-kyP0N_CWTe_efHFq2gaOTwWCh-K-zTQhdXg@mail.gmail.com>
Organization: Suse Linux
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no
	timestamps) [generic]
X-Received-From: 195.135.220.15
Subject: Re: [dmidecode] dmidecode does not show DDR SDRAM size, speed..
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 13:29:43 -0000

Hi Shen,

On lun., 2016-04-18 at 14:43 +0000, shen long wrote:
> I have another ddr sdram module and I think it did not show the size.

I can only comment on actual DMI data, not things you think you've
seen ;-)

> No -t 17 records, I guess this thing is too old..
> 
> Output of # dmidecode -t 6 -u
> 
> # dmidecode 3.0
> Scanning /dev/mem for entry point.
> SMBIOS 2.3 present.
> 
> Handle 0x0008, DMI type 6, 12 bytes
> 	Header and Data:
> 		06 0C 08 00 01 10 00 00 05 08 08 00
> 	Strings:
> 		44 49 4D 4D 31 00
> 		"DIMM1"
> 
> Handle 0x0009, DMI type 6, 12 bytes
> 	Header and Data:
> 		06 0C 09 00 01 32 00 00 05 08 08 00
> 	Strings:
> 		44 49 4D 4D 32 00
> 		"DIMM2"
> 
> Handle 0x000A, DMI type 6, 12 bytes
> 	Header and Data:
> 		06 0C 0A 00 01 54 00 02 00 7F 7F 00
> 	Strings:
> 		44 49 4D 4D 33 00
> 		"DIMM3"
> 
> Handle 0x000B, DMI type 6, 12 bytes
> 	Header and Data:
> 		06 0C 0B 00 01 76 00 02 00 7F 7F 00
> 	Strings:
> 		44 49 4D 4D 34 00
> 		"DIMM4"

For all 4 slots the speed byte is 0x00, which translates to "unknown"
according to the spec. So, BIOS did not fill it out, nothing dmidecode
can do, sorry.

-- 
Jean Delvare
SUSE L3 Support



From MAILER-DAEMON Thu Apr 28 21:56:31 2016
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1avxfT-0001t4-3G
	for mharc-dmidecode-devel@gnu.org; Thu, 28 Apr 2016 21:56:31 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41297)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kevin.bowling@kev009.com>) id 1avxfQ-0001o6-0T
	for dmidecode-devel@nongnu.org; Thu, 28 Apr 2016 21:56:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kevin.bowling@kev009.com>) id 1avxfP-0007vb-6P
	for dmidecode-devel@nongnu.org; Thu, 28 Apr 2016 21:56:27 -0400
Received: from mail-oi0-x230.google.com ([2607:f8b0:4003:c06::230]:36203)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kevin.bowling@kev009.com>) id 1avxfP-0007vW-26
	for dmidecode-devel@nongnu.org; Thu, 28 Apr 2016 21:56:27 -0400
Received: by mail-oi0-x230.google.com with SMTP id x201so104149840oif.3
	for <dmidecode-devel@nongnu.org>; Thu, 28 Apr 2016 18:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google;
	h=mime-version:date:message-id:subject:from:to;
	bh=K/nhb0Y/JMBd8Ig4wpjimmNEl0/rb5iFTibuUvqFdvY=;
	b=pAOqJ/+k/d/RkJ/xMZ6Li/sXoOSJ3WeENfn2QEbgPlBZ0GqYLQzScCok7wVApX6ymi
	b5DwsC5Tbg4a+5/ACihGXw+FTKUhsDe4ZbHaOFawz6BbdjX952r5XfIGlIRZny3WWomq
	ANyG+wBAhMAsCMCgnPBh6cLFyg3dCo1EOm5tw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:date:message-id:subject:from:to;
	bh=K/nhb0Y/JMBd8Ig4wpjimmNEl0/rb5iFTibuUvqFdvY=;
	b=fYtZWDEpRgjCY7RYyqoRaRnolLiGujDTzATL6v1cu1bseBnF/NZZyJhN+kA6fwhjJf
	F/y6pYoUtoa8Ns+ZqA0zVGTQIiJwpdBwNc2V6Rr8z+2Ztxm9W9U8CwwtGlBauOSYxOnd
	c4DaE5qZnqJlEGfrotahf4i773YtTRZLY3aidvlsLltyoYXvcPsQEtASdxLrt3FHAopz
	FUalR+Zb3gECRfOmkjX4ySUON920Vyyfvsp51JuCdlDDBBxmc7B5jc2jfRTCfCUXpIT3
	6sTH1zhj4/Vrr2v222R6nAoxGBJoJrGcNW4UF/cj5I/vdmjDLwCIyoWJi4gYA4gXF3jY
	qmSg==
X-Gm-Message-State: AOPr4FW1025JAXQ9P9F6tZGUpqWMNdrbs4pPaT392NIWNCdEo7NgZdyZKKNwiSYDRhDLHdG7zy6YLezGV97Ueg==
MIME-Version: 1.0
X-Received: by 10.157.17.107 with SMTP id p40mr7870988otp.144.1461894986515;
	Thu, 28 Apr 2016 18:56:26 -0700 (PDT)
Received: by 10.157.61.227 with HTTP; Thu, 28 Apr 2016 18:56:26 -0700 (PDT)
Date: Thu, 28 Apr 2016 18:56:26 -0700
Message-ID: <CAK7dMtBOZvFm4vDQJ2sv0VDAz9f=DGOfv=xnumqSyTv_M7yVAA@mail.gmail.com>
From: Kevin Bowling <kevin.bowling@kev009.com>
To: dmidecode-devel@nongnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2607:f8b0:4003:c06::230
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: [dmidecode] [patch #8989] Output "Invalid entry length.. Fixed up"
 warning to stderr
X-BeenThere: dmidecode-devel@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <dmidecode-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/dmidecode-devel>, 
	<mailto:dmidecode-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/dmidecode-devel/>
List-Post: <mailto:dmidecode-devel@nongnu.org>
List-Help: <mailto:dmidecode-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/dmidecode-devel>,
	<mailto:dmidecode-devel-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2016 01:56:28 -0000

Hi,

dmidecode 3.0 breaks DMI values of some tools like SaltStack that read
stdout for specific values to populate data structures about a host on some
hardware because of a warning like "Invalid entry length (16). Fixed up to
11."

My proposed fix is to simply move it to stderr
http://savannah.nongnu.org/patch/?8989

Regards,
Kevin

