mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: x86@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_DEBUG_VIRTUAL instant reboot.
Date: Sat, 11 Jul 2015 10:13:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1507111009530.17353@nanos> (raw)
In-Reply-To: <20150710145047.GA16804@codemonkey.org.uk>

On Fri, 10 Jul 2015, Dave Jones wrote:
> I bought a Haswell Xeon E3-1225 v3 box, and found that
> my self-built kernel would instantly reboot the machine once
> grub had loaded it.
> 
> Through trial and error I found the following options matter..
> 
> if I _enable_ DEBUG_PAGEALLOC, it boots fine.
> disabling it again, instant death.
> 
> further narrowing down revealed that if I have DEBUG_PAGEALLOC off,
> I also _must_ also have CONFIG_DEBUG_VIRTUAL turned off.
> With both disabled, it also boots fine.
> 
> I tried earlyprintk, but this happens so soon I don't think
> we're even at the point of initializing that code.
> 
> Any ideas how I can further narrow this down ?

I assume that VIRTUAL_BUG_ON() triggers very early. Changing it to
WARN_ON() should keep the machine alive and give you a hint which of
those checks explodes.

Thanks,

	tglx
---
diff --git a/arch/x86/mm/physaddr.c b/arch/x86/mm/physaddr.c
index e666cbbb9261..e41c1227337f 100644
--- a/arch/x86/mm/physaddr.c
+++ b/arch/x86/mm/physaddr.c
@@ -76,7 +76,7 @@ unsigned long __phys_addr(unsigned long x)
 	/* max_low_pfn is set early, but not _that_ early */
 	if (max_low_pfn) {
 		VIRTUAL_BUG_ON((phys_addr >> PAGE_SHIFT) > max_low_pfn);
-		BUG_ON(slow_virt_to_phys((void *)x) != phys_addr);
+		VIRTUAL_BUG_ON(slow_virt_to_phys((void *)x) != phys_addr);
 	}
 	return phys_addr;
 }
diff --git a/include/linux/mmdebug.h b/include/linux/mmdebug.h
index 877ef226f90f..d7ff4c2ffd69 100644
--- a/include/linux/mmdebug.h
+++ b/include/linux/mmdebug.h
@@ -50,7 +50,7 @@ void dump_mm(const struct mm_struct *mm);
 #endif
 
 #ifdef CONFIG_DEBUG_VIRTUAL
-#define VIRTUAL_BUG_ON(cond) BUG_ON(cond)
+#define VIRTUAL_BUG_ON(cond) WARN_ON(cond)
 #else
 #define VIRTUAL_BUG_ON(cond) do { } while (0)
 #endif

  reply	other threads:[~2015-07-11  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 14:50 Dave Jones
2015-07-11  8:13 ` Thomas Gleixner [this message]
2015-07-11  9:37   ` Ingo Molnar

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=alpine.DEB.2.11.1507111009530.17353@nanos \
    --to=tglx@linutronix.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®