public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
	linux-parisc@vger.kernel.org, Meelis Roos <mroos@linux.ee>,
	Helge Deller <deller@gmx.de>,
	Anatoly Pugachev <matorola@gmail.com>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"David S. Miller" <davem@davemloft.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greentime Hu <green.hu@gmail.com>,
	Greg Ungerer <gerg@linux-m68k.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Jeff Dike <jdike@addtoit.com>,
	John David Anglin <dave.anglin@bell.net>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Mark Salter <msalter@redhat.com>,
	Matt Turner <mattst88@gmail.com>, Michal Simek <monstr@monstr.eu>,
	Peter Rosin <peda@axentia.se>,
	Richard Weinberger <richard@nod.at>,
	Rolf Eike Beer <eike-kernel@sf-tec.de>,
	Russell King <linux@armlinux.org.uk>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Sam Creasey <sammy@sammy.net>, Vincent Chen <deanbo422@gmail.com>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: new panic in 5.5-rc1 (parisc, kmem_cache_open)
Date: Wed, 8 Jan 2020 12:24:21 +0100	[thread overview]
Message-ID: <20200108122421.37e3d709@wim.jer> (raw)
In-Reply-To: <alpine.LRH.2.02.2001080504340.1997@file01.intranet.prod.int.rdu2.redhat.com>

On Wed, 8 Jan 2020 05:05:24 -0500 (EST)
Mikulas Patocka <mpatocka@redhat.com> wrote:

> On Wed, 8 Jan 2020, Mike Rapoport wrote:
> 
> > On Tue, Jan 07, 2020 at 09:52:20AM -0500, Mikulas Patocka wrote:  
> > > 
> > > On Mon, 9 Dec 2019, Jeroen Roovers wrote:
> > >   
> > > > 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  
> > > 
> > > Hi
> > > 
> > > I also have this panic. I bisected it and it is caused by the
> > > patch d96885e277b5edcd1e474e8b1579005163f23dbe.  
> > 
> > My guess would be that pgd is not populated after the change.
> > Can you please check if the below hack fixes the crash?
> > 
> > 
> > diff --git a/arch/parisc/mm/init.c b/arch/parisc/mm/init.c
> > index ddca8287d43b..354cf060b67f 100644
> > --- a/arch/parisc/mm/init.c
> > +++ b/arch/parisc/mm/init.c
> > @@ -401,7 +401,7 @@ static void __init map_pages(unsigned long
> > start_vaddr, pmd = (pmd_t *) __pa(pmd);
> >  		}
> >  
> > -		pgd_populate(NULL, pg_dir, __va(pmd));
> > +		pud_populate(NULL, (pud_t *)pg_dir, __va(pmd));
> >  #endif
> >  		pg_dir++;
> >  
> >    
> 
> Test-by: Mikulas Patocka <mpatocka@redhat.com>
> 
> This patch fixes it.
> 
> Mikulas
> 

Fixes the issue on a C8000.

Tested-by: Jeroen Roovers <jer@gentoo.org>


Thanks,
     jer

      reply	other threads:[~2020-01-08 11:24 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
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 [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=20200108122421.37e3d709@wim.jer \
    --to=jer@gentoo.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=arnd@arndb.de \
    --cc=dave.anglin@bell.net \
    --cc=davem@davemloft.net \
    --cc=deanbo422@gmail.com \
    --cc=deller@gmx.de \
    --cc=eike-kernel@sf-tec.de \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=green.hu@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=kirill@shutemov.name \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=matorola@gmail.com \
    --cc=mattst88@gmail.com \
    --cc=monstr@monstr.eu \
    --cc=mpatocka@redhat.com \
    --cc=mroos@linux.ee \
    --cc=msalter@redhat.com \
    --cc=peda@axentia.se \
    --cc=richard@nod.at \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rppt@linux.ibm.com \
    --cc=sammy@sammy.net \
    /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