In data mercoledì 9 luglio 2014 11:54:21, Greg Kroah-Hartman ha scritto: > Try cc:ing everyone on that patch, with the original information you > provided, and the linux-kernel mailing list. Those developers should be > able to help you out properly.
Ok, here you can find the description of a problem that I'm experiencing on latest kernels, since 3.15.0. (this report comes from 3.15.4) lug 07 22:08:00 calvin kernel: resource map sanity check conflict: 0xfed10000 0xfed15fff 0xfed10000 0xfed13fff reserved lug 07 22:08:00 calvin kernel: ------------[ cut here ]------------ lug 07 22:08:00 calvin kernel: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa() lug 07 22:08:00 calvin kernel: Info: mapping multiple BARs. Your kernel is fine. lug 07 22:08:00 calvin kernel: Modules linked in: lug 07 22:08:00 calvin kernel: lug 07 22:08:00 calvin kernel: CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.15.4 #1 lug 07 22:08:00 calvin kernel: Hardware name: Hewlett-Packard HP EliteBook Folio 9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013 lug 07 22:08:00 calvin kernel: 00009f90000000f7 ffffffff8175d44b ffff8802334fbc78 ffffffff810af219 lug 07 22:08:00 calvin kernel: ffffffff81028e43 ffffc90000070000 ffff8802334fbcc8 00000000fed10000 lug 07 22:08:00 calvin kernel: 00000000fed16000 ffffffff810af275 ffffffff81991de2 0000000000000018 lug 07 22:08:00 calvin kernel: Call Trace: lug 07 22:08:00 calvin kernel: [<ffffffff8175d44b>] ? dump_stack+0x49/0x6a lug 07 22:08:00 calvin kernel: [<ffffffff810af219>] ? warn_slowpath_common+0x6f/0x84 lug 07 22:08:00 calvin kernel: [<ffffffff81028e43>] ? __ioremap_caller+0x290/0x2fa lug 07 22:08:00 calvin kernel: [<ffffffff810af275>] ? warn_slowpath_fmt+0x47/0x49 lug 07 22:08:00 calvin kernel: [<ffffffff810b3932>] ? iomem_map_sanity_check+0xa5/0xb1 lug 07 22:08:00 calvin kernel: [<ffffffff81028e43>] ? __ioremap_caller+0x290/0x2fa lug 07 22:08:00 calvin kernel: [<ffffffff81016316>] ? snb_uncore_imc_init_box+0x5c/0x7a lug 07 22:08:00 calvin kernel: [<ffffffff81017e8e>] ? uncore_pci_probe+0x100/0x168 lug 07 22:08:00 calvin kernel: [<ffffffff813c8da9>] ? pci_device_probe+0x6c/0xcb lug 07 22:08:00 calvin kernel: [<ffffffff814e8f46>] ? driver_probe_device+0x9b/0x1ce lug 07 22:08:00 calvin kernel: [<ffffffff814e90fd>] ? __driver_attach+0x53/0x73 lug 07 22:08:00 calvin kernel: [<ffffffff814e90aa>] ? __device_attach+0x31/0x31 lug 07 22:08:00 calvin kernel: [<ffffffff814e7814>] ? bus_for_each_dev+0x6e/0x78 lug 07 22:08:00 calvin kernel: [<ffffffff814e87f9>] ? bus_add_driver+0xfb/0x1c4 lug 07 22:08:00 calvin kernel: [<ffffffff814e95f9>] ? driver_register+0x83/0xbb lug 07 22:08:00 calvin kernel: [<ffffffff81cb0fb6>] ? uncore_pmu_register+0xd1/0xd1 lug 07 22:08:00 calvin kernel: [<ffffffff81cb1128>] ? intel_uncore_init+0x172/0x41e lug 07 22:08:00 calvin kernel: [<ffffffff81cb0fb6>] ? uncore_pmu_register+0xd1/0xd1 lug 07 22:08:00 calvin kernel: [<ffffffff8100029f>] ? do_one_initcall+0x88/0x11c lug 07 22:08:00 calvin kernel: [<ffffffff810c41ac>] ? parse_args+0x17f/0x23b lug 07 22:08:00 calvin kernel: [<ffffffff81ca8e1f>] ? kernel_init_freeable+0x14f/0x1d1 lug 07 22:08:00 calvin kernel: [<ffffffff81ca86b2>] ? do_early_param+0x81/0x81 lug 07 22:08:00 calvin kernel: [<ffffffff81756463>] ? rest_init+0x77/0x77 lug 07 22:08:00 calvin kernel: [<ffffffff81756468>] ? kernel_init+0x5/0xd0 lug 07 22:08:00 calvin kernel: [<ffffffff8176493c>] ? ret_from_fork+0x7c/0xb0 lug 07 22:08:00 calvin kernel: [<ffffffff81756463>] ? rest_init+0x77/0x77 lug 07 22:08:00 calvin kernel: ---[ end trace 076d7a33d4c45496 ]--- lug 07 22:08:00 calvin kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer Bisecting I got here: b9e1ab6d4c0582cad97699285a6b3cf992251b00 is the first bad commit commit b9e1ab6d4c0582cad97699285a6b3cf992251b00 Author: Stephane Eranian <[email protected]> Date: Tue Feb 11 16:20:12 2014 +0100 perf/x86/uncore: add SNB/IVB/HSW client uncore memory controller support This patch adds a new uncore PMU for Intel SNB/IVB/HSW client CPUs. It adds the Integrated Memory Controller (IMC) PMU. This new PMU provides a set of events to measure memory bandwidth utilization. The IMC on those processor is PCI-space based. This patch exposes a new uncore PMU on those processor: uncore_imc Two new events are defined: - name: data_reads - code: 0x1 - unit: 64 bytes - number of full cacheline read requests to the IMC - name: data_writes - code: 0x2 - unit: 64 bytes - number of full cacheline write requests to the IMC Documentation available at: http://software.intel.com/en-us/articles/monitoring-integrated-memory-controller-requests-in-the-2nd-3rd-and-4th-generation-intel Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Signed-off-by: Stephane Eranian <[email protected]> Signed-off-by: Peter Zijlstra <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Thomas Gleixner <[email protected]> :040000 040000 2d628022cbc4b8969a2ec311082053510cf6eed5 79b2a1cc3ed29e4820a5ae4221b4cf603c138887 M arch Please note that while bisecting I got a kernel with compilation error, so I'm not 100% sure of the correctness of the result. I can retry the whole process with differen starting point, however I send here the results hoping that they can be of some help. Attached you can find my config.gz gcc (Gentoo 4.8.3 p1.1, pie-0.5.9) 4.8.3 Linux calvin 3.15.4 #1 SMP PREEMPT Mon Jul 7 11:18:48 CEST 2014 x86_64 Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz GenuineIntel GNU/Linux Of course I'm available for any additional information, please cc: me as I'm not subscribed to lkml atm. many thanks. -- Fabio
config.gz
Description: application/gzip
