From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754747AbbEMVu4 (ORCPT ); Wed, 13 May 2015 17:50:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45278 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752555AbbEMVuw (ORCPT ); Wed, 13 May 2015 17:50:52 -0400 Message-ID: <5553C733.5040000@redhat.com> Date: Wed, 13 May 2015 14:50:43 -0700 From: Laura Abbott User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Bjorn Helgaas , Stephane Eranian CC: "Rafael J. Wysocki" , Linux Kernel Mailing List , x86@kernel.org Subject: Mapping multiple BARs with PNP (again) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, We have some reports of warnings from ioremap about multiple BARs: [ 2.021722] resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than reserved [mem 0xfed10000-0xfed13fff] [ 2.021723] ------------[ cut here ]------------ [ 2.021727] WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:183 __ioremap_caller+0x258/0x2d0() [ 2.021728] Info: mapping multiple BARs. Your kernel is fine. [ 2.021729] Modules linked in: [ 2.021733] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.17.8-300.fc21.x86_64 #1 [ 2.021734] Hardware name: Hewlett-Packard HP ProBook 450 G0/1949, BIOS 68IRF Ver. F.04 06/24/2013 [ 2.021735] 0000000000000000 00000000066e29d6 ffff880149a57b08 ffffffff81741aea [ 2.021737] ffff880149a57b50 ffff880149a57b40 ffffffff810970bd ffffc90000038000 [ 2.021739] 0000000000006000 00000000fed10000 8000000000000573 ffffc90000038000 [ 2.021741] Call Trace: [ 2.021746] [] dump_stack+0x45/0x56 [ 2.021749] [] warn_slowpath_common+0x7d/0xa0 [ 2.021751] [] warn_slowpath_fmt+0x5c/0x80 [ 2.021753] [] ? iomem_map_sanity_check+0xc7/0xd0 [ 2.021755] [] __ioremap_caller+0x258/0x2d0 [ 2.021758] [] ioremap_nocache+0x17/0x20 [ 2.021761] [] snb_uncore_imc_init_box+0x7c/0xc0 [ 2.021763] [] uncore_pci_probe+0xcc/0x1a0 [ 2.021766] [] local_pci_probe+0x45/0xa0 [ 2.021769] [] pci_device_probe+0xf9/0x150 [ 2.021772] [] driver_probe_device+0xa3/0x400 [ 2.021774] [] __driver_attach+0x8b/0x90 [ 2.021775] [] ? __device_attach+0x40/0x40 [ 2.021777] [] bus_for_each_dev+0x73/0xc0 [ 2.021779] [] driver_attach+0x1e/0x20 [ 2.021781] [] bus_add_driver+0x180/0x250 [ 2.021783] [] ? uncore_types_init+0x1a1/0x1a1 [ 2.021785] [] driver_register+0x64/0xf0 [ 2.021787] [] __pci_register_driver+0x4c/0x50 [ 2.021789] [] intel_uncore_init+0x174/0x410 [ 2.021791] [] ? uncore_types_init+0x1a1/0x1a1 [ 2.021794] [] do_one_initcall+0xd8/0x210 [ 2.021796] [] ? parse_args+0x21d/0x4e0 [ 2.021799] [] kernel_init_freeable+0x1b8/0x254 [ 2.021802] [] ? rest_init+0x80/0x80 [ 2.021803] [] kernel_init+0xe/0xf0 [ 2.021807] [] ret_from_fork+0x7c/0xb0 [ 2.021808] [] ? rest_init+0x80/0x80 [ 2.021813] ---[ end trace e33d153422839ba3 ]--- This looks like the issue fixed by http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cb171f7abb9a and I believe this might have been specifically referenced by https://lkml.org/lkml/2014/9/30/614 although that never got any follow up. Does whatever BIOS this is need a workaround? Full dmesg is at https://bugzilla.redhat.com/attachment.cgi?id=979268 Thanks, Laura