Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp5497557pxb; Mon, 7 Feb 2022 03:28:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJztYBNg0ebgKIr6kELi56f2qngMuIof4TddxKLNWRYBIrL5XIy1OyEOdEDIZKyyYWeFERD4 X-Received: by 2002:aa7:dc44:: with SMTP id g4mr5734449edu.438.1644233320980; Mon, 07 Feb 2022 03:28:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644233320; cv=none; d=google.com; s=arc-20160816; b=arWiKbBwwUsk3Cx7Ar82SlVdJHD4UWaGQujNtDdBAJ4bNP/f2zH0ho0qL+d3Yv9/H3 5KiYRc+HAjMLsNOmKmoHzbL85NEljp4VoQjGa42TXOtvw0AXlVT4RhmjFmTi6PIYGSED /WWRdWLRs8j29/002vEKiupMPh1zcNv/tmBo/LE56gElSjG99iXNDh76/5ibi9OlycBe gLxQ0Hc20Wke9N8js37zHmv1+pwiH2EcKgqocDM89l9XtgNFeWISTmvc1YRMqRbmN+v3 vf/6r7FF2EZBY8smJgpKTOKH/BuDhFgz4/rjKMjOQ0VoQT0KhbuRH9XvKL6uHjY6aDGu 0r4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=nz2Z4bFotqetThuLUskNVZCWGhwv1YrdlfnjDQe5gQs=; b=rBlAfxnZiEfImAsEJ9b8eFj/5dO+8AiV5y8FnfxzGyNtHfrfISFtSVFD6yvUvSftLO pugGw6ZijOjxuRoiUadPEixjPzm9hoz7soDN6zdOmtmJ86AonA8yPX0PI1Jo2ZBCJ2OX 2ypzB+vmjLLaXB9BvAk5lkxWfcIKEXXusSRfUtv0TlhrHoGOWC7VqzN5jAkeh+gI8BUP 8e2JYzCsfNl5XL9VobPjUqin3ymaVg6hfVuRW0bRqz8aO8+m9Sfsj4lzkvB9LLIrlnnG B21DbCiZ0CY73L/2Y6iaCh9KCoe/iGETIdW/ZDWwVyKOJ1bMLOh0uep5w8vOhgpir6O1 x8pA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=K0puRBpp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gt42si370455ejc.468.2022.02.07.03.28.15; Mon, 07 Feb 2022 03:28:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=K0puRBpp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1381433AbiBEVNN (ORCPT + 99 others); Sat, 5 Feb 2022 16:13:13 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:59758 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233073AbiBEVNM (ORCPT ); Sat, 5 Feb 2022 16:13:12 -0500 Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id E54C23FE4B for ; Sat, 5 Feb 2022 21:13:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1644095590; bh=nz2Z4bFotqetThuLUskNVZCWGhwv1YrdlfnjDQe5gQs=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=K0puRBppIpE4rnEKVNnKGfOPwH0dhCZq5XLEdIgCOBGZByOikF33flBu2vbchkgEJ 74GKJBsu7xZoKu7/wzGJ7dxbzIsjbturV6JFTk8SlCLw3jZbSNmHwGEJp/SiMxTxH1 E/tl2PinE41s5nJH+FFUhmoL8/K0fTenK8d8irWz7Kc9pa26KlN3EciJwQlxWzm818 yoUFnz/zOyBUFv33vWOtK/vTMKaClWwyHRUFL+blv47CDPU1YgEsUOoloQcJ0xQVQ2 TbmmnU7W5BAPyiSysO4LM3DW38fqbe8E62+hzmuejUMp3IJyMBsLLQ/IiOpvVU644O K9pfcTyAi2YxA== Received: by mail-wm1-f69.google.com with SMTP id s187-20020a1ca9c4000000b0037bb8547d64so584896wme.0 for ; Sat, 05 Feb 2022 13:13:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=nz2Z4bFotqetThuLUskNVZCWGhwv1YrdlfnjDQe5gQs=; b=prwdYqjsSYv43bADxLLLBbOVtHvI2i9FAR2y251V5Q/jxkYWq88EELOP8QPAhqzngd uEBwqute1FKXHbj3D9KrP5UknBUARVVyquy4T1JE8F0y/o6UKSp7YI0xnaCkQksfldBS SCvqQJyZHulwJ4x3zDv1to8Sl8/op1q4iIo6zUZ1mPW/o8A+OjlRF8VYjVNXVDVuJ2/V zBQOmm8/Ii1gt02K/tLE+8zM4n8oBAKUsDhIvmVOqCHdzgVhvKVo+qgtZIpFmjpWTGvA 2Ot03i++zsLp7bNB8UvnGMhtFhV6TjXVcMr00kQq8vfajlydYvAyAFqVDOAHLTg+8em8 h6Yg== X-Gm-Message-State: AOAM533Ba4+yMNHKwBmD81UF6DwZ+H6MWPg9kMoYD31+ncY9LnHnZ7xt TG+6nw6HFxsjuFf2Xdp1OCQoYhC6JdCOLFZ3DA1DW9ScqevAHxxXJhZB5dEq991bIIQQ6IQopV5 FnxeS/eduYXlC90zRMiw9l6vh8kXOr3P76C9TloE6GXKghCq1897C3ydIEw== X-Received: by 2002:a05:6000:1707:: with SMTP id n7mr4286322wrc.234.1644095590469; Sat, 05 Feb 2022 13:13:10 -0800 (PST) X-Received: by 2002:a05:6000:1707:: with SMTP id n7mr4286310wrc.234.1644095590242; Sat, 05 Feb 2022 13:13:10 -0800 (PST) MIME-Version: 1.0 References: <20211129173637.303201-1-robh@kernel.org> In-Reply-To: From: dann frazier Date: Sat, 5 Feb 2022 14:12:57 -0700 Message-ID: Subject: Re: [PATCH] PCI: xgene: Fix IB window setup To: Rob Herring Cc: Toan Le , Lorenzo Pieralisi , =?UTF-8?Q?Krzysztof_Wilczy=C5=84ski?= , Bjorn Helgaas , Andrew Murray , =?UTF-8?Q?St=C3=A9phane_Graber?= , stable , PCI , linux-arm-kernel , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 5, 2022 at 9:05 AM Rob Herring wrote: > > On Fri, Feb 4, 2022 at 5:01 PM dann frazier = wrote: > > > > On Mon, Nov 29, 2021 at 11:36:37AM -0600, Rob Herring wrote: > > > Commit 6dce5aa59e0b ("PCI: xgene: Use inbound resources for setup") > > > broke PCI support on XGene. The cause is the IB resources are now sor= ted > > > in address order instead of being in DT dma-ranges order. The result = is > > > which inbound registers are used for each region are swapped. I don't > > > know the details about this h/w, but it appears that IB region 0 > > > registers can't handle a size greater than 4GB. In any case, limiting > > > the size for region 0 is enough to get back to the original assignmen= t > > > of dma-ranges to regions. > > > > hey Rob! > > > > I've been seeing a panic on HP Moonshoot m400 cartridges (X-Gene1) - > > only during network installs - that I also bisected down to commit > > 6dce5aa59e0b ("PCI: xgene: Use inbound resources for setup"). I was > > hoping that this patch that fixed the issue on St=C3=A9phane's X-Gene2 > > system would also fix my issue, but no luck. In fact, it seems to just > > makes it fail differently. Reverting both patches is required to get a > > v5.17-rc kernel to boot. > > > > I've collected the following logs - let me know if anything else would > > be useful. > > > > 1) v5.17-rc2+ (unmodified): > > http://dannf.org/bugs/m400-no-reverts.log > > Note that the mlx4 driver fails initialization. > > > > 2) v5.17-rc2+, w/o the commit that fixed St=C3=A9phane's system: > > http://dannf.org/bugs/m400-xgene2-fix-reverted.log > > Note the mlx4 MSI-X timeout, and later panic. > > > > 3) v5.17-rc2+, w/ both commits reverted (works) > > http://dannf.org/bugs/m400-both-reverted.log > > The ranges and dma-ranges addresses don't appear to match up with any > upstream dts files. Can you send me the DT? Sure: http://dannf.org/bugs/fdt -dann > Otherwise, we're going to need some debugging added to > xgene_pcie_setup_ib_reg() to see if the register setup changed. I can > come up with something next week. > > Rob