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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A2E62C4363C for ; Thu, 8 Oct 2020 14:47:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2D91821941 for ; Thu, 8 Oct 2020 14:47:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="VHGJaG8l" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730577AbgJHOrK (ORCPT ); Thu, 8 Oct 2020 10:47:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729828AbgJHOrJ (ORCPT ); Thu, 8 Oct 2020 10:47:09 -0400 Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B541AC061755 for ; Thu, 8 Oct 2020 07:47:09 -0700 (PDT) Received: by mail-io1-xd43.google.com with SMTP id u19so6459743ion.3 for ; Thu, 08 Oct 2020 07:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JfyqMEd778QyNbtI/v0Y/4c53t1ox1t/PqY3/TlES/c=; b=VHGJaG8lcYxKBr8ZUrviwB3LO58EAwFpRxS1d9tiNKSGj948O4EBvxsaGIQcUx64nx +S7pTXP0QX0N6YG62tvhobyWwwlmhihK+6FbGKpigc+dc2NqfrLf2ZnBV1Ltk1NZZxKh 4Wen+xjOlaT3UX+pN4YbuyNpkLCAZQ784Bgmmj7brvPnewQIukU4ZuPfdFIpAn4J0u6u GHqgBRYb4zyZlK9ZgEvhIkTHF/ZMZ8smSwQ8iXsrM3qadJZJgPB21yqd6jiNAP+dGWD4 9xwaGBaQKsFH8mZfZtxwtAnR6/ZbQ/230WOZzLV7N7WWRoZ4JWcjm8ppl5Yb2Yp2CH0N Ghlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JfyqMEd778QyNbtI/v0Y/4c53t1ox1t/PqY3/TlES/c=; b=XQSIGlIHaGROuPx3tqUR/t4LLnWE0Exwaf61InMnwdeiPq+qT6FQ/ifMHjDcJ1ZGhZ ELQW8jnBvCAOOIyktIKYcdbtyxtgOU53s/QBH2nL2uHQl5bf2GnVIi2dBf9Zwr7Taqtu EQydDPgbaXisaY7rxtykBpSXPwI+qrlIL6e/RtZIWAaoZpj41XpON2rt9J/KVXFDHH1x AuLSJUZhau8Wacej4mXK8cevq7inACQw0pMxWyDVzsSISgkn9fSlOYoFDC+RFTpvQc2s zfhhu0hkgYXOc2P2Y5xKro2QWXeuUN2P909bMg/fo7rwWsJegkOeCkvPWjAk/QqBN0iA 8N8Q== X-Gm-Message-State: AOAM531CPVvt+SHlBfUcPNqLVJBF73saF+9g4jqEixfdhF82M6HxEAiZ k64HShe1V6ByOtRi2glWwYrfY6NfRQjxfGXpsl0cQA== X-Google-Smtp-Source: ABdhPJw75ddyXkeM7k24xVz+a/obQzBxen8AUggFQ4shVf63vktSWKeHv9wbpC3JuJkin1zy+5RAk4ua6HAXEL2CHiY= X-Received: by 2002:a5e:9b11:: with SMTP id j17mr6086128iok.176.1602168428872; Thu, 08 Oct 2020 07:47:08 -0700 (PDT) MIME-Version: 1.0 References: <20200916054130.8685-1-Zhiqiang.Hou@nxp.com> <20200928093911.GB12010@e121166-lin.cambridge.arm.com> <9ac53f04-f2e8-c5f9-e1f7-e54270ec55a0@ti.com> <67ac959f-561e-d1a0-2d89-9a85d5f92c72@ti.com> <99d24fe08ecb5a6f5bba7dc6b1e2b42b@walle.cc> In-Reply-To: From: Naresh Kamboju Date: Thu, 8 Oct 2020 20:16:57 +0530 Message-ID: Subject: Re: [PATCH] PCI: dwc: Added link up check in map_bus of dw_child_pcie_ops To: Zhiqiang.Hou@nxp.com, Rob Herring , Stephen Rothwell Cc: Kishon Vijay Abraham I , Michael Walle , Gustavo Pimentel , Lorenzo Pieralisi , Bjorn Helgaas , Ard Biesheuvel , PCI , open list , lkft-triage@lists.linaro.org, Linux-Next Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Fri, 2 Oct 2020 at 14:59, Naresh Kamboju wrote: > > On Thu, 1 Oct 2020 at 22:16, Michael Walle wrote: > > > > Am 2020-10-01 15:32, schrieb Kishon Vijay Abraham I: > > > > > Meanwhile would it be okay to add linkup check atleast for DRA7X so > > > that > > > we could have it booting in linux-next? > > > > Layerscape SoCs (at least the LS1028A) are also still broken in > > linux-next, > > did I miss something here? > > I have been monitoring linux next boot and functional testing on nxp devices > for more than two week and still the problem exists on nxp-ls2088. > > Do you mind checking the possibilities to revert bad patches on linux next tree > and continue to work on fixes please ? > > suspected bad commit: [ I have not bisected this problem ] > c2b0c098fbd1 ("PCI: dwc: Use generic config accessors") > > crash log snippet: > [ 1.563008] SError Interrupt on CPU5, code 0xbf000002 -- SError > [ 1.563010] CPU: 5 PID: 1 Comm: swapper/0 Not tainted > 5.9.0-rc7-next-20201001 #1 > [ 1.563011] Hardware name: Freescale Layerscape 2088A RDB Board (DT) > [ 1.563013] pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--) > [ 1.563014] pc : pci_generic_config_read+0x44/0xe8 > [ 1.563015] lr : pci_generic_config_read+0x2c/0xe8 This reported issue is gone now on Linux next master branch. I am not sure which is a fix commit. - Naresh