From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2140AC32771 for ; Mon, 26 Sep 2022 17:43:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231129AbiIZRnX (ORCPT ); Mon, 26 Sep 2022 13:43:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59068 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230503AbiIZRm4 (ORCPT ); Mon, 26 Sep 2022 13:42:56 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5317D20348; Mon, 26 Sep 2022 10:11:07 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D5F3361053; Mon, 26 Sep 2022 17:11:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 11C84C433D6; Mon, 26 Sep 2022 17:11:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664212266; bh=ciwd8dFrpPmD6qUMx+CV8r30wFdgfrze3F87Azbcrnw=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=pc4QfuUmYeW97UGWxcJpLG8z7S0CHvP01tpkkXE3ZNPT96L4y8H+Iix2E7LUhpKSG 4Sqg1CoaRZB2+s024/CyT2Q2ajdcQiw+6l7FgbXDdJx9UxCOKv7fBMmGcr5+2tgwX8 /Ilhw8TRJ/dL/vOQrMxgPQKs/rwEZtjjVeGq3QHlewGw/wuYjjnzZaNOgt2QECsytn 9gzWwUnKUo+3roQTWtYun8C9iY/bXzKpLnKlbNQb55BJYRRKqXp9u1pMwUHfcMjQ/t wIfZausc0eELLMHDWZ1Y9nZ1/d5uy5Eg0UgPLS6rJf5yssbXiEMFWvjU+xIap163F7 ziihy3gc1i/4g== Date: Mon, 26 Sep 2022 12:11:04 -0500 From: Bjorn Helgaas To: Richard Rogalski Cc: Linux Pci , Alex Deucher , "David S. Miller" , sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: SPARC64: getting "no compatible bridge window" errors :/ Message-ID: <20220926171104.GA1605932@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [+cc Alex, David, sparclinux, LKML] On Sun, Sep 25, 2022 at 06:59:23PM +0200, Richard Rogalski wrote: > I hope this is the right place for this. This is great, thanks a lot for your report! Is this a regression? If so, what's the most recent kernel that worked? > In my dmesg output, I get things like: > > pci 0000:04:00.0: can't claim VGA legacy [mem 0x000a0000-0x000bffff]: no compatible bridge window > pci 0000:06:00.0: can't claim VGA legacy [mem 0x000a0000-0x000bffff]: no compatible bridge window > pci 0000:06:00.1: can't claim BAR 0 [mem 0x84110200000-0x84110203fff 64bit]: no compatible bridge window > > I opened a bug for amdgpu [here](https://gitlab.freedesktop.org/drm/amd/-/issues/2169) but looking further into it I think it is caused by deeper PCIe problems :\ > > https://gitlab.freedesktop.org/drm/amd/uploads/cbf47807972c8a990bb2a8cdbb39ad9e/8C7CA9QNG dmesg log > https://gitlab.freedesktop.org/drm/amd/uploads/6a799425dea50febd82f8bc11e54433a/ll.txt lspci -vv > https://gitlab.freedesktop.org/drm/amd/uploads/7d4a794b1f7d67a1ffcdee5dfdec3ad6/config.txt kernel .config Your error output attachment [1] contains an address that looks like it's in 06:00.0 BAR 5: pci 0000:06:00.0: reg 0x24: [mem 0x84001200000-0x8400123ffff] NON-RESUMABLE ERROR: insn effective address [0x0000084001201410] This looks like an amdgpu issue. There have been recent changes like c1c39032a074 ("drm/amdgpu: make sure to init common IP before gmc") and dd6aeb4e5f59 ("drm/amdgpu: Don't enable LTR if not supported") that could be related. The PCI "no compatible bridge window" warnings are definitely an issue, but I don't think they're related to the amdgpu crash: pci@400: PCI MEM64 [mem 0x84100000000-0x84dffffffff] offset 80000000000 pci_bus 0000:00: root bus resource [mem 0x84100000000-0x84dffffffff] (bus address [0x4100000000-0x4dffffffff]) pci 0000:09:00.0: can't claim BAR 0 [mem 0x84120000000-0x8412007ffff 64bit]: no compatible bridge window Those and this from lspci: 0000:01:00.0 bridge to [bus 02-09] window [mem 0x4100000000-0x412fffffff pref] 0000:02:0c.0 bridge to [bus 09] window [mem 0x4120000000-0x412fffffff pref] 0000:09:00.0 Intel 82599ES NIC Region 0: Memory at 0x84120000000 are telling us there's something wrong with how the resource-to-bus offset is being applied. It looks like the offset was applied to the NIC BAR, but didn't get applied to the bridge windows. Could you start a new thread here (linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, and sparclinux@vger.kernel.org) for this issue and attach the dmesg log when booting with "ofpci_debug=1"? Do the devices we complain about (NICs and storage HBAs 09:00.0, 09:00.1, 0d:00.0, 0d:00.1, 0e:00.0, 0f:00.0, 0001:03:00.0, 0001:03:00.1, 0001:0:00.0, 0001:0a:00.1) work? Bjorn [1] https://gitlab.freedesktop.org/drm/amd/uploads/b51f4d6783eeebf90de9a400525d07d6/qq