linux-kernel - Re: [bug] mapping multiple BARs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160324101505.GA23754@pd.tnic>
Date:	Thu, 24 Mar 2016 11:15:06 +0100
From:	Borislav Petkov <bp@...e.de>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Stephane Eranian <eranian@...gle.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andi Kleen <ak@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	"mingo@...e.hu" <mingo@...e.hu>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Zhang Rui <rui.zhang@...el.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [bug] mapping multiple BARs

On Thu, Mar 24, 2016 at 10:44:41AM +0100, Jiri Olsa wrote:
> hi,
> I'm hitting following lines in dmesg:
>   resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than reserved [mem 0xfed10000-0xfed13fff]
>   caller snb_uncore_imc_init_box+0x7c/0xa0 mapping multiple BARs
> 
> I'm on IvyBridge model 58
>   vendor_id       : GenuineIntel
>   cpu family      : 6
>   model           : 58
>   model name      : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
>   stepping        : 9
>   microcode       : 0x1c
> 
> I've read following threads:
>   http://marc.info/?w=2&r=1&s=mapping+multiple+BARs&q=t
> 
> and it seems this is supposed to be already fixed by:
>   cb171f7abb9a PNP: Work around BIOS defects in Intel MCH area reporting

And as we talked on IRC, it looked like the quirk gets applied on my
machine and not on yours. I.e., I see:

[    0.669351] pnp 00:01: [Firmware Bug]: PNP resource [mem 0xfed10000-0xfed13fff] covers only part of 0000:00:00.0 Intel MCH; extending to [mem 0xfed10000-0xfed17fff]

and you don't.

Can you add some debug printks to quirk_intel_mch() to find out why?

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--