The dmi_remap() is arch dependent function and for mainline used as ioremap_cache for
And only for ia64 as ioremap (where it's same as ioremap_cache). I'm talking
It's rather bug of dmi_remap than the patch which
just use it.
The only reason why the bug wasn't found earlier it was unmapped back at init, but
doesn't mean it cannot be used after init, which can lead to strange behavior in
If it should be ioremap_cache(), it's better to change dmi_remap() for your arch.
Oh, yes, k4.2 is using the ioremap instead of ioremap_cache().
But seems it's currently solved with:
"x86/dmi: Switch dmi_remap() from ioremap() [uncached] to ioremap_cache()"
So, probably, it should be back ported.
On 28.03.16 11:44, Paul Menzel wrote:
> 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  does not work anymore
> on a lot of systems as reported in coreboot’s issue tracker as ticket
> #33 .
> Failed to mmap /dev/mem: Resource temporarily unavailable
> Aaron Durbin analyzed on the coreboot mailing list :
>>> 3) Why is that range set as uncached-minus? Would write-back work?
>> Please see this thread:
>> The actual issue stems from
>> 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.
>  https://www.coreboot.org
>  https://ticket.coreboot.org/issues/33
>  https://www.coreboot.org/pipermail/coreboot/2015-October/080568.html