From: Will Deacon <will@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Nathan Chancellor <nathan@kernel.org>,
Mark Brown <broonie@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
Date: Mon, 21 Nov 2022 18:03:22 +0000 [thread overview]
Message-ID: <20221121180321.GA7645@willie-the-truck> (raw)
In-Reply-To: <CA+G9fYuYashEQsCfScoVbVqAxeXC4w6VnenO-5dHDH8OEfFBTQ@mail.gmail.com>
On Mon, Nov 21, 2022 at 09:17:18PM +0530, Naresh Kamboju wrote:
> LKFT detected arm64 boot regression on today's Linux next-20221121 tag.
> The Kernel boot log did not show anything on the serial console.
>
> Anders bisected this problem and found the subject commit is the
> first bad commit.
>
> # first bad commit: [9ed2b4616d4e846ece2a04cb5007ce1d1bd9e3f3]
> arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
>
> Later it was found this lore link which was already reported [1].
>
> ref:
> [1] https://lore.kernel.org/all/Y3pS5fdZ3MdLZ00t@dev-arch.thelio-3990X/
Yup, I've queued a revert locally and will push it out this evening.
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2022-11-21 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+G9fYuYashEQsCfScoVbVqAxeXC4w6VnenO-5dHDH8OEfFBTQ@mail.gmail.com>
2022-11-21 18:03 ` Will Deacon [this message]
2022-11-18 5:31 [PATCH] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc) Anshuman Khandual
2022-11-18 11:10 ` Mark Rutland
2022-11-18 19:40 ` Will Deacon
2022-11-20 16:16 ` Nathan Chancellor
2022-11-21 5:30 ` Anshuman Khandual
2022-11-21 12:27 ` Mark Rutland
2022-11-21 12:51 ` Will Deacon
2022-11-21 13:56 ` Robin Murphy
2022-11-22 3:13 ` Anshuman Khandual
2022-11-22 14:12 ` Biju Das
2022-11-22 19:08 ` Robin Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221121180321.GA7645@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox