From: John David Anglin <dave.anglin@bell.net>
To: Helge Deller <deller@gmx.de>, Mikulas Patocka <mpatocka@redhat.com>
Cc: linux-parisc@vger.kernel.org
Subject: Re: [PATCH][RFC] parisc: Use per-pagetable spinlock (v2)
Date: Fri, 3 May 2019 07:58:21 -0400 [thread overview]
Message-ID: <e8e6f1f8-3bb0-f0d0-4f0d-1389c01540de@bell.net> (raw)
In-Reply-To: <a98ef81b-cd8e-b81d-df24-8c508e8a01b0@gmx.de>
On 2019-05-02 12:14 p.m., Helge Deller wrote:
>>> CONFIG_SPARSEMEM_MANUAL=y, CONFIG_SPARSEMEM_VMEMMAP=n - works.
>>> CONFIG_SPARSEMEM_MANUAL=y, CONFIG_SPARSEMEM_VMEMMAP=y - hangs on boot.
>> I thought I selected CONFIG_SPARSEMEM_VMEMMAP but will check. Have multiple
>> builds with original SPARSEMEM patch that were okay.
> It sometimes hung for me too.
> I think my VMEMMAP patch overwrites other memory and thus only sometimes crashes the machine...
>
> By the way, I've rebased my for-next tree, fixed a few small issues and dropped the VMEMMAP patch for now.
> Please give it a new try:
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next
I had selected CONFIG_SPARSEMEM_VMEMMAP=y. My c8000 seemed to cold boot okay. But
I built the above rebased tree using the CONFIG_SPARSEMEM_VMEMMAP=y kernel. The new kernel
failed to boot when I tried to reboot. It did boot boot okay when I tried a cold reboot with console
connected.
I then rebuilt the above tree, installed it and it booted okay. So, I tend to think the memory corruption (?)
carries across a hot reboot.
Dave
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2019-05-03 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 17:34 [PATCH][RFC] parisc: Use per-pagetable spinlock (v2) Helge Deller
2019-05-01 14:22 ` Mikulas Patocka
2019-05-01 14:34 ` Helge Deller
2019-05-01 16:21 ` Mikulas Patocka
2019-05-02 1:27 ` John David Anglin
2019-05-02 13:43 ` Mikulas Patocka
2019-05-02 14:34 ` John David Anglin
2019-05-02 16:14 ` Helge Deller
2019-05-02 17:40 ` Mikulas Patocka
2019-05-03 11:58 ` John David Anglin [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=e8e6f1f8-3bb0-f0d0-4f0d-1389c01540de@bell.net \
--to=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=mpatocka@redhat.com \
/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).