Info: mapping multiple BARs. Your kernel is fine. (original) (raw)

Stephane Eranian eranian at google.com
Thu Feb 27 02:12:32 PST 2014

On Wed, Feb 26, 2014 at 10:59 AM, Borislav Petkov <bp at alien8.de> wrote:

Can you please, pretty please, not top-post...

On Wed, Feb 26, 2014 at 10:47:05AM +0100, Stephane Eranian wrote: Hi,

Ok, so I am getting the same error message as you. I checked my syslog now. I have my uncoreimc addr=0xfed10000 (after masking) And I also have pnp 00:01 overlapping the imc range completely. What pnp device does it really represent? the DRAM controller? So I think my laptop behaves like yours. grep -Er . /sys/devices/pnp0/00:01/* 2>/dev/null /sys/devices/pnp0/00:01/firmwarenode/hid:PNP0C02 ... so this PNP0C02 is [ 0.363943] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) My Lenovo IVB is like yours. But I tried on my SandyBridge desktop and there to BAR is at a completely different address. Same thing on my Haswell desktop system.

As a asides, my SNB and HSW desktops with 3.14-rc4 are totally unstable. They hang if I type make in my kernel tree. Whereas 3.14-rc3 is stable. I am not so sure this is all related to the uncore IMC support, though.

@Rafael, can you please make sense of this whole ACPI gunk?

We have a resource conflict with pnp 00:01, analysis here: http://lkml.kernel.org/r/20140226092903.GA22639@pd.tnic This is the rest of the 00:01 info from sysfs: /sys/devices/pnp0/00:01/firmwarenode/uid:0 /sys/devices/pnp0/00:01/firmwarenode/path:_SB.PCI0.LPC.SIO /sys/devices/pnp0/00:01/firmwarenode/power/control:auto /sys/devices/pnp0/00:01/firmwarenode/power/runtimeactivetime:0 /sys/devices/pnp0/00:01/firmwarenode/power/runtimestatus:unsupported /sys/devices/pnp0/00:01/firmwarenode/power/runtimesuspendedtime:0 /sys/devices/pnp0/00:01/firmwarenode/modalias:acpi:PNP0C02: /sys/devices/pnp0/00:01/firmwarenode/uevent:MODALIAS=acpi:PNP0C02: /sys/devices/pnp0/00:01/id:PNP0c02 /sys/devices/pnp0/00:01/power/control:auto /sys/devices/pnp0/00:01/power/runtimeactivetime:0 /sys/devices/pnp0/00:01/power/runtimestatus:unsupported /sys/devices/pnp0/00:01/power/runtimesuspendedtime:0 /sys/devices/pnp0/00:01/resources:state = active /sys/devices/pnp0/00:01/resources:io 0x10-0x1f /sys/devices/pnp0/00:01/resources:io 0x90-0x9f /sys/devices/pnp0/00:01/resources:io 0x24-0x25 /sys/devices/pnp0/00:01/resources:io 0x28-0x29 /sys/devices/pnp0/00:01/resources:io 0x2c-0x2d /sys/devices/pnp0/00:01/resources:io 0x30-0x31 /sys/devices/pnp0/00:01/resources:io 0x34-0x35 /sys/devices/pnp0/00:01/resources:io 0x38-0x39 /sys/devices/pnp0/00:01/resources:io 0x3c-0x3d /sys/devices/pnp0/00:01/resources:io 0xa4-0xa5 /sys/devices/pnp0/00:01/resources:io 0xa8-0xa9 /sys/devices/pnp0/00:01/resources:io 0xac-0xad /sys/devices/pnp0/00:01/resources:io 0xb0-0xb5 /sys/devices/pnp0/00:01/resources:io 0xb8-0xb9 /sys/devices/pnp0/00:01/resources:io 0xbc-0xbd /sys/devices/pnp0/00:01/resources:io 0x50-0x53 /sys/devices/pnp0/00:01/resources:io 0x72-0x77 /sys/devices/pnp0/00:01/resources:io 0x400-0x47f /sys/devices/pnp0/00:01/resources:io 0x500-0x57f /sys/devices/pnp0/00:01/resources:io 0x800-0x80f /sys/devices/pnp0/00:01/resources:io 0x15e0-0x15ef /sys/devices/pnp0/00:01/resources:io 0x1600-0x167f /sys/devices/pnp0/00:01/resources:mem 0xf8000000-0xfbffffff /sys/devices/pnp0/00:01/resources:mem 0xfffff000-0xffffffff /sys/devices/pnp0/00:01/resources:mem 0xfed1c000-0xfed1ffff /sys/devices/pnp0/00:01/resources:mem 0xfed10000-0xfed13fff /sys/devices/pnp0/00:01/resources:mem 0xfed18000-0xfed18fff /sys/devices/pnp0/00:01/resources:mem 0xfed19000-0xfed19fff /sys/devices/pnp0/00:01/resources:mem 0xfed45000-0xfed4bfff /sys/devices/pnp0/00:01/resources:mem 0xfed40000-0xfed44fff /sys/devices/pnp0/00:01/subsystem/driversautoprobe:1 /sys/devices/pnp0/00:01/uevent:DRIVER=system -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --

More information about the dri-devel mailing list