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=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED,USER_AGENT_SANE_1 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 2439BC4363D for ; Thu, 24 Sep 2020 14:19:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CD4C822208 for ; Thu, 24 Sep 2020 14:19:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728224AbgIXOTv (ORCPT ); Thu, 24 Sep 2020 10:19:51 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:59776 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728024AbgIXOTv (ORCPT ); Thu, 24 Sep 2020 10:19:51 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: gtucker) with ESMTPSA id C2C8929D17C Subject: Re: [PATCH v3 16/16] ARM: Remove custom IRQ stat accounting To: Fabio Estevam Cc: Marc Zyngier , Valentin Schneider , Sumit Garg , Florian Fainelli , Russell King , Jason Cooper , Saravana Kannan , Andrew Lunn , Catalin Marinas , Gregory Clement , linux-kernel , kernelci-results@groups.io, Will Deacon , Thomas Gleixner , kernel-team@android.com, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" References: <20200901144324.1071694-1-maz@kernel.org> <20200901144324.1071694-17-maz@kernel.org> From: Guillaume Tucker Message-ID: <2a985dd2-9e56-605a-8ab7-a6ae35aba506@collabora.com> Date: Thu, 24 Sep 2020 15:19:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24/09/2020 14:34, Fabio Estevam wrote: > Hi Guillaume, > > On Thu, Sep 24, 2020 at 6:01 AM Guillaume Tucker > wrote: > >> This appears to be causing a NULL pointer dereference on >> beaglebone-black, it got bisected automatically several times. >> None of the other platforms in the KernelCI labs appears to be >> affected. > > Actually imx53-qsb is also affected: > https://storage.kernelci.org/next/master/next-20200924/arm/imx_v6_v7_defconfig/gcc-8/lab-pengutronix/baseline-imx53-qsrb.html > > kernelci marks it Boot result: PASS though. > > Shouldn't kernelci flag a warning or error instead? Thanks for bringing this up. The status in the HTML log file is a very coarse one, in this case the board booted "fine" since it reached a login prompt. The issue was detected later when checking for errors in the kernel log. But yes you're right, the issue is also impacting imx53-qsrb indeed. I didn't spot that because it was only reported as a regression on staging.kernelci.org, whereas imx53-qsrb is in the Pengutronix lab which is not sending results there at the moment. The failures can be found on the production web dashboard though, but not as regressions: beaglebone-black: https://kernelci.org/test/case/id/5f6c7f1ab7c8c5472cbf9de9/ imx53-qsrb: https://kernelci.org/test/case/id/5f6c7ea6f89a9d0f4dbf9ddf/ I need to investigate why that is the case, knowing that the regression was detected correctly on staging which is the development KernelCI instance: https://staging.kernelci.org/test/plan/id/5f6bea67f724eb1b34dce581/ Thanks, Guillaume 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=-6.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED, USER_AGENT_SANE_1 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 C944CC4363D for ; Thu, 24 Sep 2020 14:21:24 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 79FC922208 for ; Thu, 24 Sep 2020 14:21:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GphCTpjk" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 79FC922208 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=collabora.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=UWSb5M/AelVnPgBRcNkY4oRrcEA6JjlMQtTt7sC7QAY=; b=GphCTpjkZ+2/ZyDeMPeZ45sVq mMjjklBNCgXjuAAh+WVPqG24gAdszPY/RT2K6JV7VQKNTkdtxotlS4SXywQPjx7JVSzqh+XjXdOo7 IbEEmNotGmtP9mSlvKR/4ExUlbe8XjhoGimDqKX4tRJ8EetDPzenl26uA4XhYubl3Eg/S9RyVj/O8 u0l3GaDGIT1jMMevM8o7jJQPZCsUulpXuAEJJfCOHIAV7K4uXLsO96eWXw3EA7FB99xvPLcsEzAO2 Sn7sndkTl2MepDI+KYax3Lq5mbxtMRYxVXZW2qwa7JFLpJSGTLPrS3NhEnZ04e9VU5kiNOvR0qY46 B7+/bNC/A==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kLS6E-0003zN-Az; Thu, 24 Sep 2020 14:19:54 +0000 Received: from bhuna.collabora.co.uk ([46.235.227.227]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kLS6B-0003yl-QP for linux-arm-kernel@lists.infradead.org; Thu, 24 Sep 2020 14:19:52 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: gtucker) with ESMTPSA id C2C8929D17C Subject: Re: [PATCH v3 16/16] ARM: Remove custom IRQ stat accounting To: Fabio Estevam References: <20200901144324.1071694-1-maz@kernel.org> <20200901144324.1071694-17-maz@kernel.org> From: Guillaume Tucker Message-ID: <2a985dd2-9e56-605a-8ab7-a6ae35aba506@collabora.com> Date: Thu, 24 Sep 2020 15:19:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200924_101951_953184_05F43202 X-CRM114-Status: GOOD ( 19.98 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Sumit Garg , kernel-team@android.com, Florian Fainelli , Russell King , Jason Cooper , Saravana Kannan , Andrew Lunn , Marc Zyngier , Gregory Clement , linux-kernel , kernelci-results@groups.io, Catalin Marinas , Thomas Gleixner , Will Deacon , Valentin Schneider , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 24/09/2020 14:34, Fabio Estevam wrote: > Hi Guillaume, > > On Thu, Sep 24, 2020 at 6:01 AM Guillaume Tucker > wrote: > >> This appears to be causing a NULL pointer dereference on >> beaglebone-black, it got bisected automatically several times. >> None of the other platforms in the KernelCI labs appears to be >> affected. > > Actually imx53-qsb is also affected: > https://storage.kernelci.org/next/master/next-20200924/arm/imx_v6_v7_defconfig/gcc-8/lab-pengutronix/baseline-imx53-qsrb.html > > kernelci marks it Boot result: PASS though. > > Shouldn't kernelci flag a warning or error instead? Thanks for bringing this up. The status in the HTML log file is a very coarse one, in this case the board booted "fine" since it reached a login prompt. The issue was detected later when checking for errors in the kernel log. But yes you're right, the issue is also impacting imx53-qsrb indeed. I didn't spot that because it was only reported as a regression on staging.kernelci.org, whereas imx53-qsrb is in the Pengutronix lab which is not sending results there at the moment. The failures can be found on the production web dashboard though, but not as regressions: beaglebone-black: https://kernelci.org/test/case/id/5f6c7f1ab7c8c5472cbf9de9/ imx53-qsrb: https://kernelci.org/test/case/id/5f6c7ea6f89a9d0f4dbf9ddf/ I need to investigate why that is the case, knowing that the regression was detected correctly on staging which is the development KernelCI instance: https://staging.kernelci.org/test/plan/id/5f6bea67f724eb1b34dce581/ Thanks, Guillaume _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel