linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Ralph Campbell <rcampbell@nvidia.com>,
	William Kucharski <william.kucharski@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: CONFIG_DEBUG_VIRTUAL breaks boot on x86-32
Date: Wed, 27 Mar 2019 09:03:37 +0200	[thread overview]
Message-ID: <dca61136-db66-a89e-e79d-679ee2281d8d@linux.ee> (raw)
In-Reply-To: <f39477da-a1ef-e31e-a72d-8ea1d5755234@nvidia.com>

> You might be hitting a bug I found.
> Try applying this patch:
> https://marc.info/?l=linux-kernel&m=155355953012985&w=2

Unfortunately it did not change anything.

-- 
Meelis Roos <mroos@linux.ee>


  reply	other threads:[~2019-03-27  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 20:22 Meelis Roos
2019-03-26 13:52 ` William Kucharski
2019-03-26 17:50   ` Meelis Roos
2019-03-26 20:11   ` Ralph Campbell
2019-03-27  7:03     ` Meelis Roos [this message]
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=dca61136-db66-a89e-e79d-679ee2281d8d@linux.ee \
    --to=mroos@linux.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rcampbell@nvidia.com \
    --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