[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140225221027.GB21559@pd.tnic>
Date: Tue, 25 Feb 2014 23:10:28 +0100
From: Borislav Petkov <bp@...en8.de>
To: Stephane Eranian <eranian@...gle.com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
x86 <x86@...nel.org>, Daniel Vetter <daniel.vetter@...ll.ch>,
Jani Nikula <jani.nikula@...ux.intel.com>,
David Airlie <airlied@...ux.ie>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
Jiri Kosina <jkosina@...e.cz>
Subject: Re: Info: mapping multiple BARs. Your kernel is fine.
On Tue, Feb 25, 2014 at 07:54:53PM +0100, Stephane Eranian wrote:
> I am on tip.git at cfbf8d4 Linux 3.14-rc4.
> and I don't see the problem (using Ubuntu Saucy).
Also IVB, model 58?
> Given what you commented out, it seems like you're saying
> something goes wrong with pci_get_device().
Probably. I'll add some debug printk's tomorrow to shed some more light
on the matter.
> Am I missing some pm callbacks?
Dunno. What do you mean by "pm callbacks" exactly? I don't know that
code so I have to ask.
> The uncore IMC is not used internally.
By IMC I'm assuming this PIC dev:
#define PCI_DEVICE_ID_INTEL_IVB_IMC 0x0154
?
And "internally" means by BIOS or something behind the curtains like
SMM...?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists