From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
linux-next <linux-next@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-mm <linux-mm@kvack.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: next: armv7: kernel BUG at mm/slub.c:4240! - PC is at __kmem_cache_create+0x580/0x588
Date: Tue, 18 Apr 2023 09:13:50 +0200 [thread overview]
Message-ID: <ae159daf-28cb-4d48-9ae8-2f2d1dd5970b@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYv70wipaANT2Yau4xjfVHx1muyV-Eae8F8atoAV4cJHxw@mail.gmail.com>
On Tue, Apr 18, 2023, at 08:51, Naresh Kamboju wrote:
> <0>[ 0.000000] __kmem_cache_create from create_boot_cache+0x9c/0xc4
> <0>[ 0.000000] create_boot_cache from kmem_cache_init+0x8c/0x150
> <0>[ 0.000000] kmem_cache_init from mm_core_init+0x34/0x44
> <0>[ 0.000000] mm_core_init from start_kernel+0x18c/0x3b4
> <0>[ 0.000000] start_kernel from 0x0
> <0>[ 0.000000] Code: e3100801 1affff5b eaffff62 e7f001f2 (e7f001f2)
> <4>[ 0.000000] ---[ end trace 0000000000000000 ]---
> <0>[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
> <0>[ 0.000000] ---[ end Kernel panic - not syncing: Attempted to
> kill the idle task! ]---
>
Sorry about this regression. Andrew picked up my follow-up fix today,
should work again tomorrow:
https://lore.kernel.org/all/20230417185525.1420-1-sj@kernel.org/T/#u
https://lore.kernel.org/all/20230418013829.5957EC433D2@smtp.kernel.org/
Arnd
prev parent reply other threads:[~2023-04-18 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 6:51 Naresh Kamboju
2023-04-18 7:13 ` Arnd Bergmann [this message]
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=ae159daf-28cb-4d48-9ae8-2f2d1dd5970b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
/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