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 180F0C43334 for ; Tue, 7 Jun 2022 06:37:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231145AbiFGGhI (ORCPT ); Tue, 7 Jun 2022 02:37:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230258AbiFGGhE (ORCPT ); Tue, 7 Jun 2022 02:37:04 -0400 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9531CD8090 for ; Mon, 6 Jun 2022 23:37:02 -0700 (PDT) Received: by mail-pl1-x634.google.com with SMTP id t2so14024021pld.4 for ; Mon, 06 Jun 2022 23:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RPy1vRYX875/GqkTt8ngXPSVHhf5IBO6TQDfdYyr/ik=; b=qTTWQagnTxOownb+q9+ji78HVjHIiaZkav+VM4+0IUqgsdOPKCDsDMNxMqH4/uCLJT 6ebXsJWPDEA9TfeatTvk6PYLnnhIAaqeKppqhggZeOoTnzNLYakX8+Une88JzLh5k388 OOPyZUTN7K7cedesqAD1o1Q5EANs13I+dlITktlzgJqWbm3pb+CyDD35fn8F57k0OMsX OhLx6ajixuaEhk6aiCtAvDrMihX2z0BhOFYfYta4dfeOh+TA/9Hi0SXU24eSoklpIXbN Npu+hkh5um+gu4ELjdsR/qkOcHJW1AS+qYrY9snf3qh9bQL3djh2W3e7EjWwPwSPNzpc DbEA== 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; bh=RPy1vRYX875/GqkTt8ngXPSVHhf5IBO6TQDfdYyr/ik=; b=G/8+0VjMkfxdZ6Ad2l/HUpPua2EqR5JIsBLccurn5WF33+taf/tRKRXh2UVRFx4OhT 3AWEfXBvWHN7fgLhm6Wmj4slyZ/eNTajY6Zb6mlNLXFMJ7V7qLx8NlBTOZvTzuFC5y6o Bnegw2RTvZQd+PxoF/AhAyFY4poYcTpm6owpS0nsfNAUvY4/JPcit/xMsreBP8duB8Yx CIR4V3eqwr1MnH7rpji38G4aq4K75CpMsuKcYrtx9819+dO6OjCuSZB8TmsexQ6oW5JT 88+cNYJT3iIAfG6DsnXHfHJMc+egucCQJm56Z/wUJvN2J2y4LotOmnnAmwCMNlmLSNDP gY8A== X-Gm-Message-State: AOAM530zw2bNmkFLTVfE1w6SjhuNoZv/L/9cFcB0CulKOm0QQiLfNDuE Jjy9Qq083v0Q+EJ9IIwatHOTtsFv8088Sao8xlleFA== X-Google-Smtp-Source: ABdhPJxVvgt2hIXvmLPGVFVhfbxEgZL0vuvlRmPPHO4jvH8UPfAtY7DZVGdOhaRYFs3imdKenmDuePTQJQSVLGnznSs= X-Received: by 2002:a17:903:2cb:b0:14f:4fb6:2fb0 with SMTP id s11-20020a17090302cb00b0014f4fb62fb0mr27311276plk.172.1654583821901; Mon, 06 Jun 2022 23:37:01 -0700 (PDT) MIME-Version: 1.0 References: <20220607162504.7fd5a92a@canb.auug.org.au> In-Reply-To: <20220607162504.7fd5a92a@canb.auug.org.au> From: Shakeel Butt Date: Mon, 6 Jun 2022 23:36:50 -0700 Message-ID: Subject: Re: [next] arm64: boot failed - next-20220606 To: Stephen Rothwell Cc: Naresh Kamboju , Linux-Next Mailing List , open list , regressions@lists.linux.dev, lkft-triage@lists.linaro.org, Linux ARM , linux-mm , Andrew Morton , Ard Biesheuvel , Arnd Bergmann , Catalin Marinas , Raghuram Thammiraju , Mark Brown , Will Deacon , Roman Gushchin , Vasily Averin , Qian Cai Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 6, 2022 at 11:25 PM Stephen Rothwell wrote: > > Hi Naresh, > > On Tue, 7 Jun 2022 11:00:39 +0530 Naresh Kamboju wrote: > > > > On Mon, 6 Jun 2022 at 17:16, Naresh Kamboju wrote: > > > > > > Linux next-20220606 arm64 boot failed. The kernel boot log is empty. > > > I am bisecting this problem. > > > > > > Reported-by: Linux Kernel Functional Testing > > > > > > The initial investigation show that, > > > > > > GOOD: next-20220603 > > > BAD: next-20220606 > > > > > > Boot log: > > > Starting kernel ... > > > > Linux next-20220606 and next-20220607 arm64 boot failed. > > The kernel panic log showing after earlycon. > > > > Reported-by: Linux Kernel Functional Testing > > Can you test v5.19-rc1, please? If that does not fail, then you could > bisect between that and next-20220606 ... > This is already reported at https://lore.kernel.org/all/Yp4F6n2Ie32re7Ed@qian/ and I think we know the underlying issue (which is calling virt_to_page() on a vmalloc address).