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=-7.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,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 B2F8EC48BE8 for ; Tue, 15 Jun 2021 11:50:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9705B6145D for ; Tue, 15 Jun 2021 11:50:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230186AbhFOLwz (ORCPT ); Tue, 15 Jun 2021 07:52:55 -0400 Received: from mail.kernel.org ([198.145.29.99]:60396 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229979AbhFOLwy (ORCPT ); Tue, 15 Jun 2021 07:52:54 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4A165613BF; Tue, 15 Jun 2021 11:50:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623757850; bh=q1+9+561eC7jmhlBQGchmKhaf063MtAVBSjBfa/pKvs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UmCtA2/eef34H13ygfdC+6kV9vk8kNdh7SXa2j2d1Er5i1KNTi1XV2p7lq+6vvJla 0sEhqYO2gme/hoNYL/Wdy+e5hugm8tRABjisZS7YLLe7EP7HxlQaYLQaS/3uR+3EvL wDsLz9ynF2E16oncM83gvzreSf6fHhcBWMJcvBqLR9ZgopIkQn5P7dJ6hWCKaadd6q drMR97ncGKnkcsxXZFpy41lEHSWWBpMH0Qox2m4qzGwv4vVADrU3aO/1aX96yL1Bc3 ne1aFU1RQ8BMSewv5ol/rGDN2AX05so/aM2UlYUX7q4PUi3M43DZo7RBxpWjkh9Kj5 K+Gh5Du/lvzGw== Date: Tue, 15 Jun 2021 12:50:45 +0100 From: Will Deacon To: Naresh Kamboju Cc: Linux-Next Mailing List , linux-mm , Linux ARM , open list , lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Andrew Morton , Stephen Rothwell , Arnd Bergmann , Ard Biesheuvel , Catalin Marinas , Mike Rapoport , Christophe Leroy Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Message-ID: <20210615115044.GC20598@willie-the-truck> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Naresh, On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote: > Following kernel crash reported while boot linux next 20210615 tag on qemu_arm64 > with allmodconfig build. > > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] > [ 0.000000] Linux version 5.13.0-rc6-next-20210615 > (tuxmake@ac7978cddede) (aarch64-linux-gnu-gcc (Debian 11.1.0-1) > 11.1.0, GNU ld (GNU Binutils for Debian) 2.36.50.20210601) #1 SMP > PREEMPT Tue Jun 15 10:20:51 UTC 2021 > [ 0.000000] Machine model: linux,dummy-virt > [ 0.000000] earlycon: pl11 at MMIO 0x0000000009000000 (options '') > [ 0.000000] printk: bootconsole [pl11] enabled > [ 0.000000] efi: UEFI not found. > [ 0.000000] NUMA: No NUMA configuration found > [ 0.000000] NUMA: Faking a node at [mem > 0x0000000040000000-0x00000000bfffffff] > [ 0.000000] NUMA: NODE_DATA [mem 0xbfc00d40-0xbfc03fff] > [ 0.000000] ------------[ cut here ]------------ > [ 0.000000] kernel BUG at arch/arm64/mm/physaddr.c:27! > [ 0.000000] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP > [ 0.000000] Modules linked in: > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Tainted: G T > 5.13.0-rc6-next-20210615 #1 c150a8161d8ff395c5ae7ee0c3c8f22c3689fae4 > [ 0.000000] Hardware name: linux,dummy-virt (DT) > [ 0.000000] pstate: 404000c5 (nZcv daIF +PAN -UAO -TCO BTYPE=--) > [ 0.000000] pc : __phys_addr_symbol+0x44/0xc0 > [ 0.000000] lr : __phys_addr_symbol+0x44/0xc0 > [ 0.000000] sp : ffff800014287b00 > [ 0.000000] x29: ffff800014287b00 x28: fc49a9b89db36f0a x27: ffffffffffffffff > [ 0.000000] x26: 0000000000000280 x25: 0000000000000010 x24: ffff8000145a8000 > [ 0.000000] x23: 0000000008000000 x22: 0000000000000010 x21: 0000000000000000 > [ 0.000000] x20: ffff800010000000 x19: ffff00007fc00d40 x18: 0000000000000000 > [ 0.000000] x17: 00000000003ee000 x16: 00000000bfc12000 x15: 0000001000000000 > [ 0.000000] x14: 000000000000de8c x13: 0000001000000000 x12: 00000000f1f1f1f1 > [ 0.000000] x11: dfff800000000000 x10: ffff700002850eea x9 : 0000000000000000 > [ 0.000000] x8 : ffff00007fbe0d40 x7 : 0000000000000000 x6 : 000000000000003f > [ 0.000000] x5 : 0000000000000040 x4 : 0000000000000005 x3 : ffff8000142bb0c0 > [ 0.000000] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 > [ 0.000000] Call trace: > [ 0.000000] __phys_addr_symbol+0x44/0xc0 > [ 0.000000] sparse_init_nid+0x98/0x6d0 > [ 0.000000] sparse_init+0x460/0x4d4 > [ 0.000000] bootmem_init+0x110/0x340 > [ 0.000000] setup_arch+0x1b8/0x2e0 > [ 0.000000] start_kernel+0x110/0x870 > [ 0.000000] __primary_switched+0xa8/0xb0 > [ 0.000000] Code: 940ccf23 eb13029f 54000069 940cce60 (d4210000) > [ 0.000000] random: get_random_bytes called from > oops_exit+0x54/0xc0 with crng_init=0 > [ 0.000000] ---[ end trace 0000000000000000 ]--- > [ 0.000000] Kernel panic - not syncing: Oops - BUG: Fatal exception > [ 0.000000] ---[ end Kernel panic - not syncing: Oops - BUG: Fatal > exception ]--- > > Reported-by: Naresh Kamboju Thanks for the report, although since this appears to be part of a broader testing effort, here are some things that I think would make the reports even more useful: 1. An indication as to whether or not this is a regression (i.e. do you have a known good build, perhaps even a bisection?) 2. Either a link to the vmlinux, or faddr2line run on the backtrace. Looking at the above, I can't tell what sparse_init_nid+0x98/0x6d0 actually is. 3. The exact QEMU command-line you are using, so I can try to reproduce this locally. I think the 0-day bot wraps the repro up in a shell script for you. 4. Whether or not the issue is reproducible. 5. Information about the toolchain you used to build the kernel (it happens to be present here because it's in the kernel log, but generally I think it would be handy to specify that in the report). Please can you provide that information for this crash? It would really help in debugging it. Thanks! Will 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.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, 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 AA34FC48BE5 for ; Tue, 15 Jun 2021 13:49:37 +0000 (UTC) Received: from bombadil.infradead.org (unknown [198.137.202.133]) (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 7CF3B60234 for ; Tue, 15 Jun 2021 13:49:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7CF3B60234 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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=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=g9GBNWNzFOfg+OD4p8trHovWfS/YKZrWKIBiHW471As=; b=erSTHCjHGff+vj ELYSGWDy94VkuHianrlup4a2AjvE4Cxcz699nq4jSfWBBLma3SWD1v/v0Mga27GqUdlZNlI1fKwxl bxZgm53pMaiRG1ig5XaP9k6ic0ipbTKLO8WuXuQDESuRhf7YB/jNgudo16IDXdRvURVkkTWsKKEtW JbFSAGSkhpBRhzhbyh7q6mS9e3CAdPmwJL+Z7/bl93JOrSFpKuw6znSImUc/FrNpFrBamsRXf06NA dNg2fxXDLyI+7LOalpnP1jRd0Sn6/6DsLPzrkqWesUimE7UJ0lJ48WTeFc17fjLMQ2QRWy1NodFLc R8ZOnxtNE7mVEPaRQuFA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1lt9LE-000GSx-Jo; Tue, 15 Jun 2021 13:42:56 +0000 Received: from desiato.infradead.org ([2001:8b0:10b:1:d65d:64ff:fe57:4e05]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1lt9FI-000DDm-8h for linux-arm-kernel@bombadil.infradead.org; Tue, 15 Jun 2021 13:36:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=desiato.20200630; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Qzext9+ZHttO9Gcj5jhSbGtn239GxPYRXBpgSRBww58=; b=fxRsSEXiQe+C/weMuTDF7AAbRw KmTj3fHekhENddraXqWLfw5R+7pIQisBtCGXhY+mncBgZgRMYUZlnkphKXZbo51MpK8b289HvEfSX OZ5cm384sbzkY+AusjUvubNPnhaqVZ9OQvk891y7+Pf0v30yQpY8t3oU4pILjmWPvjOukQtkGcxDc Uh2192u2EABDEas03bDXLhLAVcG070bnXpSj551nGRiqMTkeI8Uu6HbVC7joipzDvh/1SxpFhD8VA 0NGgJ1gXMdfPU3/agDL2f9Q0JeW+n/DJO0cl1RnvpJGizme8Z1A1VavQFgDpOPztmrND6vAk3xJkV W80H1e+w==; Received: from mail.kernel.org ([198.145.29.99]) by desiato.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1lt7af-007opa-4r for linux-arm-kernel@lists.infradead.org; Tue, 15 Jun 2021 11:50:53 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4A165613BF; Tue, 15 Jun 2021 11:50:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623757850; bh=q1+9+561eC7jmhlBQGchmKhaf063MtAVBSjBfa/pKvs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UmCtA2/eef34H13ygfdC+6kV9vk8kNdh7SXa2j2d1Er5i1KNTi1XV2p7lq+6vvJla 0sEhqYO2gme/hoNYL/Wdy+e5hugm8tRABjisZS7YLLe7EP7HxlQaYLQaS/3uR+3EvL wDsLz9ynF2E16oncM83gvzreSf6fHhcBWMJcvBqLR9ZgopIkQn5P7dJ6hWCKaadd6q drMR97ncGKnkcsxXZFpy41lEHSWWBpMH0Qox2m4qzGwv4vVADrU3aO/1aX96yL1Bc3 ne1aFU1RQ8BMSewv5ol/rGDN2AX05so/aM2UlYUX7q4PUi3M43DZo7RBxpWjkh9Kj5 K+Gh5Du/lvzGw== Date: Tue, 15 Jun 2021 12:50:45 +0100 From: Will Deacon To: Naresh Kamboju Cc: Linux-Next Mailing List , linux-mm , Linux ARM , open list , lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Andrew Morton , Stephen Rothwell , Arnd Bergmann , Ard Biesheuvel , Catalin Marinas , Mike Rapoport , Christophe Leroy Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Message-ID: <20210615115044.GC20598@willie-the-truck> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210615_125052_292952_20E15BE9 X-CRM114-Status: GOOD ( 18.10 ) 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 Hi Naresh, On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote: > Following kernel crash reported while boot linux next 20210615 tag on qemu_arm64 > with allmodconfig build. > > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] > [ 0.000000] Linux version 5.13.0-rc6-next-20210615 > (tuxmake@ac7978cddede) (aarch64-linux-gnu-gcc (Debian 11.1.0-1) > 11.1.0, GNU ld (GNU Binutils for Debian) 2.36.50.20210601) #1 SMP > PREEMPT Tue Jun 15 10:20:51 UTC 2021 > [ 0.000000] Machine model: linux,dummy-virt > [ 0.000000] earlycon: pl11 at MMIO 0x0000000009000000 (options '') > [ 0.000000] printk: bootconsole [pl11] enabled > [ 0.000000] efi: UEFI not found. > [ 0.000000] NUMA: No NUMA configuration found > [ 0.000000] NUMA: Faking a node at [mem > 0x0000000040000000-0x00000000bfffffff] > [ 0.000000] NUMA: NODE_DATA [mem 0xbfc00d40-0xbfc03fff] > [ 0.000000] ------------[ cut here ]------------ > [ 0.000000] kernel BUG at arch/arm64/mm/physaddr.c:27! > [ 0.000000] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP > [ 0.000000] Modules linked in: > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Tainted: G T > 5.13.0-rc6-next-20210615 #1 c150a8161d8ff395c5ae7ee0c3c8f22c3689fae4 > [ 0.000000] Hardware name: linux,dummy-virt (DT) > [ 0.000000] pstate: 404000c5 (nZcv daIF +PAN -UAO -TCO BTYPE=--) > [ 0.000000] pc : __phys_addr_symbol+0x44/0xc0 > [ 0.000000] lr : __phys_addr_symbol+0x44/0xc0 > [ 0.000000] sp : ffff800014287b00 > [ 0.000000] x29: ffff800014287b00 x28: fc49a9b89db36f0a x27: ffffffffffffffff > [ 0.000000] x26: 0000000000000280 x25: 0000000000000010 x24: ffff8000145a8000 > [ 0.000000] x23: 0000000008000000 x22: 0000000000000010 x21: 0000000000000000 > [ 0.000000] x20: ffff800010000000 x19: ffff00007fc00d40 x18: 0000000000000000 > [ 0.000000] x17: 00000000003ee000 x16: 00000000bfc12000 x15: 0000001000000000 > [ 0.000000] x14: 000000000000de8c x13: 0000001000000000 x12: 00000000f1f1f1f1 > [ 0.000000] x11: dfff800000000000 x10: ffff700002850eea x9 : 0000000000000000 > [ 0.000000] x8 : ffff00007fbe0d40 x7 : 0000000000000000 x6 : 000000000000003f > [ 0.000000] x5 : 0000000000000040 x4 : 0000000000000005 x3 : ffff8000142bb0c0 > [ 0.000000] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 > [ 0.000000] Call trace: > [ 0.000000] __phys_addr_symbol+0x44/0xc0 > [ 0.000000] sparse_init_nid+0x98/0x6d0 > [ 0.000000] sparse_init+0x460/0x4d4 > [ 0.000000] bootmem_init+0x110/0x340 > [ 0.000000] setup_arch+0x1b8/0x2e0 > [ 0.000000] start_kernel+0x110/0x870 > [ 0.000000] __primary_switched+0xa8/0xb0 > [ 0.000000] Code: 940ccf23 eb13029f 54000069 940cce60 (d4210000) > [ 0.000000] random: get_random_bytes called from > oops_exit+0x54/0xc0 with crng_init=0 > [ 0.000000] ---[ end trace 0000000000000000 ]--- > [ 0.000000] Kernel panic - not syncing: Oops - BUG: Fatal exception > [ 0.000000] ---[ end Kernel panic - not syncing: Oops - BUG: Fatal > exception ]--- > > Reported-by: Naresh Kamboju Thanks for the report, although since this appears to be part of a broader testing effort, here are some things that I think would make the reports even more useful: 1. An indication as to whether or not this is a regression (i.e. do you have a known good build, perhaps even a bisection?) 2. Either a link to the vmlinux, or faddr2line run on the backtrace. Looking at the above, I can't tell what sparse_init_nid+0x98/0x6d0 actually is. 3. The exact QEMU command-line you are using, so I can try to reproduce this locally. I think the 0-day bot wraps the repro up in a shell script for you. 4. Whether or not the issue is reproducible. 5. Information about the toolchain you used to build the kernel (it happens to be present here because it's in the kernel log, but generally I think it would be handy to specify that in the report). Please can you provide that information for this crash? It would really help in debugging it. Thanks! Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel