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 DE5E1C77B7F for ; Wed, 3 May 2023 10:54:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229745AbjECKyb (ORCPT ); Wed, 3 May 2023 06:54:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56512 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229569AbjECKy3 (ORCPT ); Wed, 3 May 2023 06:54:29 -0400 Received: from pandora.armlinux.org.uk (pandora.armlinux.org.uk [IPv6:2001:4d48:ad52:32c8:5054:ff:fe00:142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 659593C01 for ; Wed, 3 May 2023 03:54:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KUYY2bE5shqnm/FG8O/MklH06r5Nhh3u60SjyKiTrnA=; b=LFq3X47lk7axBmHPKPuygFqeYT 39fQM/1IgaA+ulDyDWPAgEsUFYZ4H+BwelTAMz6FpC8cPK8bF6PG/fMPPB8LN2LN3ZbwuMeHUxTez Wzs1dFBXSLZyF+YjnBxtixoUShs4ZszFeoEQNUg0KpGs6/qXBoYni/pTTBTJD43O4A5m61g2wJjlB JVt7YEvf1nh0tfeigikeDCf1UkZq7CNXkj53SC1yVmDG6PRh4Vdu6pIQrmP78qn4+uBMKRtOfiXme vptGHz0yyNkDoxJYw3gPK66KVF0zZAcjj3NihdqYJLLOmM9F/LGSGw2E5BPGu8AmjTL+vDTymDpay DcM+HRAQ==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:47624) by pandora.armlinux.org.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1puA7r-0003FO-Dz; Wed, 03 May 2023 11:54:23 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.94.2) (envelope-from ) id 1puA7o-0001iz-Vw; Wed, 03 May 2023 11:54:20 +0100 Date: Wed, 3 May 2023 11:54:20 +0100 From: "Russell King (Oracle)" To: Dmitry Vyukov Cc: syzbot , bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com, hannes@cmpxchg.org, juri.lelli@redhat.com, linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org, surenb@google.com, syzkaller-bugs@googlegroups.com, vincent.guittot@linaro.org, vschneid@redhat.com, Linux ARM Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in psi_task_switch Message-ID: References: <000000000000281ae805faa4844e@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Russell King (Oracle) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 03, 2023 at 12:38:19PM +0200, Dmitry Vyukov wrote: > On Wed, 3 May 2023 at 12:34, Russell King (Oracle) > wrote: > > > > On Tue, May 02, 2023 at 08:37:15AM +0200, Dmitry Vyukov wrote: > > > On Mon, 1 May 2023 at 18:43, syzbot > > > wrote: > > > > > > > > Hello, > > > > > > > > syzbot found the following issue on: > > > > > > > > HEAD commit: 89d77f71f493 Merge tag 'riscv-for-linus-6.4-mw1' of git://.. > > > > git tree: upstream > > > > console output: https://syzkaller.appspot.com/x/log.txt?x=1113550c280000 > > > > kernel config: https://syzkaller.appspot.com/x/.config?x=4cc65ccad523b604 > > > > dashboard link: https://syzkaller.appspot.com/bug?extid=0827f43974813b74e6db > > > > compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > > > userspace arch: arm > > > > > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > > > Reported-by: syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com > > > > > > +arm mailing list > > > > > > Kernel started falling apart on arm during boot in various strange ways. > > > > Are these all the same hardware platform? If so, please check the > > hardware with a known working kernel. These look like spurious failts > > caused possibly the hardware platform failing. > > It happens in the same qemu that used to work before. So "hardware" is > presumably working. I have no other ideas based on the incomplete information provided (due to the initial oops triggering a subsequent oops while trying to print the register "information".) And I have no suggestions how to debug it further. Sorry. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last! 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0D42AC77B78 for ; Wed, 3 May 2023 10:55:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=x4ovj4mERFjrbDKERPaWfkdGgCYZrXD7O8500lxgayM=; b=tBNCy9e5TtL0aj Crn2KA0xjiYj6TKn5HaVCe1hAWwxitlzmgCtMcduA7cJmQsw1fj6d+5f8KzC9RZ+CD+emIA2+1AAd XE6tafjO6QKbOD7Vg4eWJ+HK0MZIU2lshUDjuQNadEN7n3Qn0jQAfyzAVnX9ieov+pxeWfVJ1+VUF vLA+5EpyhfFJsLqTLUX/OY/LJntNXvsdtOwcPo5KHwPLmdmGb3+XOifiL/zKcCpQU5HkpzsQu1Fxy C7XKkw2kT50aRM5og7CqGw+TMVJICkMELeA/Bj6gvEQIjxAU0gAJxM/UiIQeVu5x71IIFb5bEeLOJ KruiVspL/KSbZgjYN8WA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1puA84-004JpI-07; Wed, 03 May 2023 10:54:36 +0000 Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:32c8:5054:ff:fe00:142]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1puA81-004JoZ-0h for linux-arm-kernel@lists.infradead.org; Wed, 03 May 2023 10:54:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KUYY2bE5shqnm/FG8O/MklH06r5Nhh3u60SjyKiTrnA=; b=LFq3X47lk7axBmHPKPuygFqeYT 39fQM/1IgaA+ulDyDWPAgEsUFYZ4H+BwelTAMz6FpC8cPK8bF6PG/fMPPB8LN2LN3ZbwuMeHUxTez Wzs1dFBXSLZyF+YjnBxtixoUShs4ZszFeoEQNUg0KpGs6/qXBoYni/pTTBTJD43O4A5m61g2wJjlB JVt7YEvf1nh0tfeigikeDCf1UkZq7CNXkj53SC1yVmDG6PRh4Vdu6pIQrmP78qn4+uBMKRtOfiXme vptGHz0yyNkDoxJYw3gPK66KVF0zZAcjj3NihdqYJLLOmM9F/LGSGw2E5BPGu8AmjTL+vDTymDpay DcM+HRAQ==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:47624) by pandora.armlinux.org.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1puA7r-0003FO-Dz; Wed, 03 May 2023 11:54:23 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.94.2) (envelope-from ) id 1puA7o-0001iz-Vw; Wed, 03 May 2023 11:54:20 +0100 Date: Wed, 3 May 2023 11:54:20 +0100 From: "Russell King (Oracle)" To: Dmitry Vyukov Cc: syzbot , bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com, hannes@cmpxchg.org, juri.lelli@redhat.com, linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org, surenb@google.com, syzkaller-bugs@googlegroups.com, vincent.guittot@linaro.org, vschneid@redhat.com, Linux ARM Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in psi_task_switch Message-ID: References: <000000000000281ae805faa4844e@google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230503_035433_256494_51E5E0AF X-CRM114-Status: GOOD ( 18.81 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Wed, May 03, 2023 at 12:38:19PM +0200, Dmitry Vyukov wrote: > On Wed, 3 May 2023 at 12:34, Russell King (Oracle) > wrote: > > > > On Tue, May 02, 2023 at 08:37:15AM +0200, Dmitry Vyukov wrote: > > > On Mon, 1 May 2023 at 18:43, syzbot > > > wrote: > > > > > > > > Hello, > > > > > > > > syzbot found the following issue on: > > > > > > > > HEAD commit: 89d77f71f493 Merge tag 'riscv-for-linus-6.4-mw1' of git://.. > > > > git tree: upstream > > > > console output: https://syzkaller.appspot.com/x/log.txt?x=1113550c280000 > > > > kernel config: https://syzkaller.appspot.com/x/.config?x=4cc65ccad523b604 > > > > dashboard link: https://syzkaller.appspot.com/bug?extid=0827f43974813b74e6db > > > > compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > > > userspace arch: arm > > > > > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > > > Reported-by: syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com > > > > > > +arm mailing list > > > > > > Kernel started falling apart on arm during boot in various strange ways. > > > > Are these all the same hardware platform? If so, please check the > > hardware with a known working kernel. These look like spurious failts > > caused possibly the hardware platform failing. > > It happens in the same qemu that used to work before. So "hardware" is > presumably working. I have no other ideas based on the incomplete information provided (due to the initial oops triggering a subsequent oops while trying to print the register "information".) And I have no suggestions how to debug it further. Sorry. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel