From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] DMI: Always call dmi_present with DMI structure
Date: Thu, 21 Feb 2013 10:58:37 +0800 [thread overview]
Message-ID: <51258D5D.2070404@oracle.com> (raw)
In-Reply-To: <CAMe9rOrE4okBffqCE0mAK_ogc76Ty12OvBJGy69kLebGGXmM=Q@mail.gmail.com>
Hi
Ben had sent a patch fixing this issue. Would you like to test his patch?
https://lkml.org/lkml/2013/2/16/102
zduan
On 2013-02-21 02:12, H.J. Lu wrote:
> Hi,
>
> This patch:
>
> commit 9f9c9cbb60576a1518d0bf93fb8e499cffccf377
> Author: Zhenzhong Duan <zhenzhong.duan@oracle.com>
> Date: Thu Dec 20 15:05:14 2012 -0800
>
> drivers/firmware/dmi_scan.c: fetch dmi version from SMBIOS if it exists
>
> The right dmi version is in SMBIOS if it's zero in DMI region
>
> This issue was originally found from an oracle bug.
> One customer noticed system UUID doesn't match between dmidecode & uek2.
>
> - HP ProLiant BL460c G6 :
> # cat /sys/devices/virtual/dmi/id/product_uuid
> 00000000-0000-4C48-3031-4D5030333531
> # dmidecode | grep -i uuid drivers/firmware/dmi_scan.c:
> fetch dmi version from SMBIOS if it exists
>
> The right dmi version is in SMBIOS if it's zero in DMI region
>
> This issue was originally found from an oracle bug.
> One customer noticed system UUID doesn't match between dmidecode & uek2.
>
> - HP ProLiant BL460c G6 :
> # cat /sys/devices/virtual/dmi/id/product_uuid
> 00000000-0000-4C48-3031-4D5030333531
> # dmidecode | grep -i uuid
> UUID: 00000000-0000-484C-3031-4D5030333531
>
> From SMBIOS 2.6 on, spec use little-endian encoding for UUID other than
> network byte order.
>
> So we need to get dmi version to distinguish. If version is 0.0, the
> real version is taken from the SMBIOS version. This is part of original
> kernel comment in code.
>
> UUID: 00000000-0000-484C-3031-4D5030333531
>
> From SMBIOS 2.6 on, spec use little-endian encoding for UUID other than
> network byte order.
>
> So we need to get dmi version to distinguish. If version is 0.0, the
> real version is taken from the SMBIOS version. This is part of original
> kernel comment in code.
>
> causes a regression in 3.7, 3.8 and 3.9 kernels. Before the change,
> we only scan DMI structure. Now smbios_present scans SMBIOS
> entry point. I have a machine which has invalid checksum in
> SMBIOS entry point. We wind up calling dmi_present with SMBIOS
> entry point instead of DMI structure. This patch changes smbios_present
> to always call dmi_present with DMI structure.
>
>
next prev parent reply other threads:[~2013-02-21 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 18:12 H.J. Lu
2013-02-21 2:58 ` Zhenzhong Duan [this message]
2013-02-21 19:06 ` H.J. Lu
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=51258D5D.2070404@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome