All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
	Jan Beulich <jbeulich@suse.com>,
	Matt Fleming <matt.fleming@intel.com>,
	David Howells <dhowells@redhat.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Arnd Bergmann <arnd@arndb.de>, Dave Jones <davej@redhat.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] x86/uapi for 3.8
Date: Sat, 15 Dec 2012 11:41:03 -0800	[thread overview]
Message-ID: <50CCD24F.9090603@zytor.com> (raw)
In-Reply-To: <CA+55aFz3iLPT3wzbU_Nhh4ft1eNQcd4WdQXsgXnKBs6vG9a_Uw@mail.gmail.com>

On 12/15/2012 10:35 AM, Linus Torvalds wrote:
> On Sat, Dec 15, 2012 at 8:33 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
>> On 2012.12.14 at 17:47 -0800, Linus Torvalds wrote:
>>>
>>> Ho humm. Anybody else see anything strange?
>>
>> Yes. I'm seeing a BUG early during boot on my machine (RIP=NULL):
>>
>>  BUG: unable to handle kernel NULL pointer dereference at           (null)
>>
>> This is caused by commit 53b87cf088e2 ("x86, mm: Include the
>> entire kernel memory map in trampoline_pgd")
> 
> Hmm. That reverts cleanly, and the result boots fine for me. And the
> commit looks like exactly the kind of thing that could result in
> problems with exactly the right memory layout, so it could explain why
> the bisect failed and some kernels randomly worked for me and others
> didn't.
> 
> So this at least looks like a very possible candidate.
> 
> Does anybody have an explanation for the problem?
> 
> Btw. the machine in question does not have EFI, and is a bog-standard
> PC (DMI string: "P7H57D-V EVO, BIOS 0999 01/19/2010")
> 
> Matt? Jan?
> 

Matt is on vacation, and I'm partly offline for the weekend, but that
definitely seems suspicious.  Do we have a memory map of the affected
machine(s)?

	-hpa



  reply	other threads:[~2012-12-15 19:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 22:11 [GIT PULL] x86/uapi for 3.8 H. Peter Anvin
2012-12-12 23:48 ` David Howells
2012-12-14 18:25   ` Linus Torvalds
2012-12-14 23:45     ` David Howells
2012-12-15  1:16       ` Linus Torvalds
2012-12-15  1:41         ` Linus Torvalds
2012-12-15  1:47           ` Linus Torvalds
2012-12-15 16:33             ` Markus Trippelsdorf
2012-12-15 16:35               ` Markus Trippelsdorf
2012-12-16 12:43                 ` Matt Fleming
2012-12-16 13:25                   ` Markus Trippelsdorf
2012-12-16 14:54                     ` Matt Fleming
2012-12-16 20:12                       ` Linus Torvalds
2012-12-16 22:07                         ` Linus Torvalds
2012-12-16 22:25                           ` H. Peter Anvin
2012-12-16 22:40                           ` Matt Fleming
2012-12-16 22:52                             ` Linus Torvalds
2012-12-16 23:49                           ` Markus Trippelsdorf
2012-12-15 18:35               ` Linus Torvalds
2012-12-15 19:41                 ` H. Peter Anvin [this message]
2012-12-15 19:58                   ` Linus Torvalds
2012-12-15 20:06                     ` Markus Trippelsdorf
2012-12-15 21:04                     ` Markus Trippelsdorf
2012-12-15 21:06                       ` Linus Torvalds
2012-12-15 21:36                         ` H. Peter Anvin
2012-12-15 22:05                         ` Yinghai Lu
2012-12-15 23:37                           ` Linus Torvalds
2012-12-15 23:46                             ` H. Peter Anvin
2012-12-16 12:46                             ` Matt Fleming
2012-12-15 21:37                     ` Dave Jones
2012-12-15 23:47                       ` H. Peter Anvin
2012-12-17  9:04                 ` Jan Beulich
2012-12-17 15:44                   ` Linus Torvalds
2012-12-17 16:00                     ` Jan Beulich
2012-12-17 16:39                       ` H. Peter Anvin
2012-12-17 17:03                         ` Jan Beulich
2012-12-17 17:15                           ` H. Peter Anvin
2012-12-18  8:02                             ` Jan Beulich
2012-12-15  4:25         ` H. Peter Anvin

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=50CCD24F.9090603@zytor.com \
    --to=hpa@zytor.com \
    --cc=arnd@arndb.de \
    --cc=davej@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=grant.likely@secretlab.ca \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=matt.fleming@intel.com \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.