From: Ralph Campbell <rcampbell@nvidia.com>
To: William Kucharski <william.kucharski@oracle.com>,
Meelis Roos <mroos@linux.ee>
Cc: LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: CONFIG_DEBUG_VIRTUAL breaks boot on x86-32
Date: Tue, 26 Mar 2019 13:11:31 -0700 [thread overview]
Message-ID: <f39477da-a1ef-e31e-a72d-8ea1d5755234@nvidia.com> (raw)
In-Reply-To: <A1B7F481-4BF6-4441-8019-AE088F8A8939@oracle.com>
On 3/26/19 6:52 AM, William Kucharski wrote:
> Does this still happen on 5.1-rc2?
>
> Do you have idea as to what max_low_pfn() gets set to on your system at boot time?
>
> From the screen shot I'm guessing it MIGHT be 0x373fe, but it's hard to know for sure.
>
>
>> On Mar 21, 2019, at 2:22 PM, Meelis Roos <mroos@linux.ee> wrote:
>>
>> I tried to debug another problem and turned on most debug options for memory.
>> The resulting kernel failed to boot.
>>
>> Bisecting the configurations led to CONFIG_DEBUG_VIRTUAL - if I turned it on
>> in addition to some other debug options, the machine crashed with
>>
>> kernel BUG at arch/x86/mm/physaddr.c:79!
>>
>> Screenshot at http://kodu.ut.ee/~mroos/debug_virtual-boot-hang-1.jpg
>>
>> The machine was Athlon XP with VIA KT600 chipset and 2G RAM.
>>
>> --
>> Meelis Roos <mroos@linux.ee>
>>
>
You might be hitting a bug I found.
Try applying this patch:
https://marc.info/?l=linux-kernel&m=155355953012985&w=2
next prev parent reply other threads:[~2019-03-26 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 20:22 CONFIG_DEBUG_VIRTUAL breaks boot on x86-32 Meelis Roos
2019-03-26 13:52 ` William Kucharski
2019-03-26 17:50 ` Meelis Roos
2019-03-26 20:11 ` Ralph Campbell [this message]
2019-03-27 7:03 ` Meelis Roos
2019-03-27 10:26 ` William Kucharski
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=f39477da-a1ef-e31e-a72d-8ea1d5755234@nvidia.com \
--to=rcampbell@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mroos@linux.ee \
--cc=william.kucharski@oracle.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