From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>,
Jean Delvare <jdelvare@suse.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
coreboot@coreboot.org
Subject: [REGRESSION] firmware: dmi_scan: add SBMIOS entry and DMI tables
Date: Mon, 28 Mar 2016 10:44:09 +0200 [thread overview]
Message-ID: <1459154648.2351.19.camel@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
Dear Ivan, dear Jeann,
There is an unwanted regression due to commit d7f96f97 (firmware:
dmi_scan: add SBMIOS entry and DMI tables).
Since Linux kernel 4.2 the utility `cbmem`, used to access information
stored in memory, from the coreboot project [1] does not work anymore
on a lot of systems as reported in coreboot’s issue tracker as ticket
#33 [2].
```
Failed to mmap /dev/mem: Resource temporarily unavailable
```
Aaron Durbin analyzed on the coreboot mailing list [3]:
> > 3) Why is that range set as uncached-minus? Would write-back work?
>
> Please see this thread:
> http://www.coreboot.org/pipermail/coreboot/2015-September/080381.html
>
> The actual issue stems from
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=d7f96f97c4031fa4ffdb7801f9aae23e96170a6f
> which maintains a persistent mapping of smbios tables. It uses
> dmi_remap() which is '#define dmi_remap ioremap' which is where the
> uncached-minus PAT entry comes from. It should be using the same
> mechanism as the ACPI table mappings which uses ioremap_cache().
It’d be great, if the commit could be reverted, or the code be changed
in a way that `cbmem` still works.
If I should report this issue somewhere else, please tell me too, and
I’ll do my best to follow up there.
Thanks,
Paul
[1] https://www.coreboot.org
[2] https://ticket.coreboot.org/issues/33
[3] https://www.coreboot.org/pipermail/coreboot/2015-October/080568.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2016-03-28 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 8:44 Paul Menzel [this message]
2016-03-28 12:44 ` [REGRESSION] firmware: dmi_scan: add SBMIOS entry and DMI tables ivan.khoronzhuk
2016-03-28 13:11 ` Ivan Khoronzhuk
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=1459154648.2351.19.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=coreboot@coreboot.org \
--cc=ivan.khoronzhuk@globallogic.com \
--cc=jdelvare@suse.de \
--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