From: Mike Rapoport <rppt@kernel.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Paul Burton <paul.burton@mips.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM
Date: Tue, 10 Sep 2019 12:32:44 +0100 [thread overview]
Message-ID: <20190910113243.GA19207@rapoport-lnx> (raw)
In-Reply-To: <20190909182242.c1ef9717d14b20212ef75954@suse.de>
On Mon, Sep 09, 2019 at 06:22:42PM +0200, Thomas Bogendoerfer wrote:
> On Fri, 6 Sep 2019 16:02:24 +0300
> Mike Rapoport <rppt@kernel.org> wrote:
>
> > I suspect that unaligned access comes from __page_to_pfn, can you please
> > check what scripts/fadd2line reports for kernel_init_free_pages+0xcc/0x138?
>
> kernel_init_free_pages+0xcc/0x138:
> pagefault_disabled_dec at include/linux/uaccess.h:173
> (inlined by) pagefault_enable at include/linux/uaccess.h:200
> (inlined by) __kunmap_atomic at include/linux/highmem.h:101
> (inlined by) clear_highpage at include/linux/highmem.h:215
> (inlined by) kernel_init_free_pages at mm/page_alloc.c:1124
>
> While making some sense out of this I booted the system a few times
> with the same kernel and I get different crashes (it even booted once
> to userspace).
>
> Here a list (decoded with fadd2line)
...
> I couldn't make real sense out of this yet, but maybe it gives
> a hint for you.
Unfortunately, no :(
Before we start adding printks, can you please run with
CONFIG_DEBUG_MEMORY_INIT=y and with
mminit_loglevel=4 ignore_loglevel
in the command line?
> Thomas.
>
> --
> SUSE Software Solutions Germany GmbH
> HRB 247165 (AG München)
> Geschäftsführer: Felix Imendörffer
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-09-10 11:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 5:47 [PATCH] mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM Mike Rapoport
2019-09-05 13:21 ` Thomas Bogendoerfer
2019-09-05 13:32 ` Mike Rapoport
2019-09-05 13:48 ` Thomas Bogendoerfer
2019-09-05 15:47 ` Mike Rapoport
2019-09-05 21:38 ` Thomas Bogendoerfer
2019-09-06 13:02 ` Mike Rapoport
2019-09-09 16:22 ` Thomas Bogendoerfer
2019-09-10 11:32 ` Mike Rapoport [this message]
2019-09-10 12:44 ` Thomas Bogendoerfer
2019-09-11 14:09 ` Thomas Bogendoerfer
2019-09-11 14:57 ` Mike Rapoport
2019-09-12 10:58 ` Mike Rapoport
2019-09-12 13:55 ` Thomas Bogendoerfer
2019-09-12 14:09 ` Thomas Bogendoerfer
2019-09-12 15:58 ` Mike Rapoport
2019-09-14 10:41 ` Mike Rapoport
2019-09-16 9:07 ` Thomas Bogendoerfer
2019-09-16 9:52 ` Mike Rapoport
2019-09-16 10:07 ` Thomas Bogendoerfer
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=20190910113243.GA19207@rapoport-lnx \
--to=rppt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=rppt@linux.ibm.com \
--cc=tbogendoerfer@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).