From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752406AbbJMHac (ORCPT ); Tue, 13 Oct 2015 03:30:32 -0400 Received: from smtp1.it.da.ut.ee ([193.40.5.66]:41497 "EHLO smtp1.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbbJMHaa (ORCPT ); Tue, 13 Oct 2015 03:30:30 -0400 Date: Tue, 13 Oct 2015 10:32:04 +0300 (EEST) From: Meelis Roos To: Yinghai Lu cc: Linux Kernel list , "linux-pci@vger.kernel.org" Subject: Re: 4.3-rc3 BAR allocation problems on multiple machines In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Updated on V210 - the others were more recent. Now I get more BAR > > warning there too: > > > > http://kodu.ut.ee/~mroos/dm/dm.v210+patches > > > > interesting, mem and mem64 is overlapping. > > [ 38.824625] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0] > [ 38.824654] /pci@1f,700000: PCI IO [io > 0x7f601000000-0x7f601ffffff] offset 7f601000000 > [ 38.824680] /pci@1f,700000: PCI MEM [mem > 0x7f700000000-0x7f7ffffffff] offset 7f700000000 > [ 38.824704] /pci@1f,700000: PCI MEM64 [mem > 0x7f700000000-0x7f7ffffffff] offset 7f700000000 > [ 38.826310] PCI: Scanning PBM /pci@1f,700000 > [ 38.826479] schizo f0069c00: PCI host bridge to bus 0000:00 > [ 38.826506] pci_bus 0000:00: root bus resource [io > 0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff]) > [ 38.826536] pci_bus 0000:00: root bus resource [mem > 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff]) > [ 38.826565] pci_bus 0000:00: root bus resource [mem > 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff]) > > We need to add more sanitary checking. > > Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ? http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug Applied the fix_mem_mem64_overlapping.patch and retested. The BAR allocation problems are still there: http://kodu.ut.ee/~mroos/dm/dm.v210+patch+mem64patch+debug -- Meelis Roos (mroos@linux.ee)