From: Jeroen Roovers <jer@gentoo.org>
To: linux-parisc@vger.kernel.org
Cc: Meelis Roos <mroos@linux.ee>
Subject: Re: new panic in 5.5-rc1 (parisc, kmem_cache_open)
Date: Mon, 9 Dec 2019 20:26:26 +0100 [thread overview]
Message-ID: <20191209202626.0f2c2112@wim.jer> (raw)
In-Reply-To: <de6b77cc-9c32-23fa-5caf-b6d370792e85@linux.ee>
On Mon, 9 Dec 2019 20:22:17 +0200
Meelis Roos <mroos@linux.ee> wrote:
> I tried 5.5-rc1 on RP3440 and got a surprise panic on boot (5.4
> worked):
Ah, I was going to reported this, too.
> mem auto-init: stack:off, heap alloc:off, heap free:off
> Memory: 12348004K/12580864K available (6438K kernel code, 2148K
> rwdata, 954K rodata, 1193K init, 500K bss, 232860K reserved, 0K
> cma-reserved)
I see an additional message after this:
random: get_random_u64 called from __kmem_cache_create+0x70/0x660 with
crng_init=0
And then the same or similar enough backtrace.
Regards,
jer
next prev parent reply other threads:[~2019-12-09 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 18:22 new panic in 5.5-rc1 (parisc, kmem_cache_open) Meelis Roos
2019-12-09 19:26 ` Jeroen Roovers [this message]
2020-01-07 14:52 ` Mikulas Patocka
2020-01-08 8:02 ` Mike Rapoport
2020-01-08 10:05 ` Mikulas Patocka
2020-01-08 11:24 ` Jeroen Roovers
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=20191209202626.0f2c2112@wim.jer \
--to=jer@gentoo.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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