From: Robin Holt <holt@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jean Delvare <jdelvare@suse.de>,
DuanZhenzhong <zhenzhong.duan@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"holt@sgi.com" <holt@sgi.com>
Subject: Re: memcpy_fromio in dmi_scan.c
Date: Wed, 24 Apr 2013 21:07:24 -0500 [thread overview]
Message-ID: <20130425020724.GR3658@sgi.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1EA53DAA@ORSMSX104.amr.corp.intel.com>
On Wed, Apr 24, 2013 at 08:16:50PM +0000, Luck, Tony wrote:
> > That being said, "my" SN2 machine was previously running kernel 3.0.34
> > which has the old dmi_scan code and it also said "DMI not present or
> > invalid." Plus dmidecode fails on this machine with:
> >
> > /sys/firmware/efi/systab: SMBIOS entry point missing
> >
> > So it might as well be that DMI support on SN2 was already broken.
> > Please let me know your findings on other SN2 machines.
>
> I don't have an sn2 to test. Added Robin Holt to Cc list
I will try and boot an sn2 machine first thing tomorrow morning.
I don't recall dmidecode being broken, but that was quite a while ago.
I thought the license validation code we used on sn2 used data from the
dmidecode output.
Robin
next prev parent reply other threads:[~2013-04-25 2:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:18 memcpy_fromio in dmi_scan.c Jean Delvare
2013-04-23 3:25 ` DuanZhenzhong
2013-04-23 7:28 ` Jean Delvare
2013-04-23 22:00 ` Luck, Tony
2013-04-24 19:22 ` Jean Delvare
2013-04-24 20:16 ` Luck, Tony
2013-04-25 2:07 ` Robin Holt [this message]
2013-04-25 9:52 ` Robin Holt
2013-04-25 20:37 ` Andrew Morton
2013-07-08 13:54 ` Jean Delvare
2013-04-25 1:51 ` Zhenzhong Duan
2013-04-25 10:02 ` Robin Holt
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=20130425020724.GR3658@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=zhenzhong.duan@oracle.com \
/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.