public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/mm] x86: make e820_update_range() handle small range update
Date: Sun, 15 Mar 2009 07:04:56 +0100	[thread overview]
Message-ID: <20090315060456.GF20949@elte.hu> (raw)
In-Reply-To: <49BC2279.2030101@kernel.org>


* Yinghai Lu <yinghai@kernel.org> wrote:

> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> > 
> >> Ingo Molnar wrote:
> >>> * Yinghai Lu <yinghai@kernel.org> wrote:
> >>>
> >>>> Commit-ID:  78a8b35bc7abf8b8333d6f625e08c0f7cc1c3742
> >>>> Gitweb:     http://git.kernel.org/tip/78a8b35bc7abf8b8333d6f625e08c0f7cc1c3742
> >>>> Author:     Yinghai Lu <yinghai@kernel.org>
> >>>> AuthorDate: Thu, 12 Mar 2009 22:36:01 -0700
> >>>> Commit:     Ingo Molnar <mingo@elte.hu>
> >>>> CommitDate: Sat, 14 Mar 2009 12:20:07 +0100
> >>>>
> >>>> x86: make e820_update_range() handle small range update
> >>>>
> >>>> Impact: enhance e820 code to handle more cases
> >>>>
> >>>> Try to handle new range which could be covered by one entry.
> >>>>
> >>>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> >>>> Cc: jbeulich@novell.com
> >>>> LKML-Reference: <49B9F0C1.10402@kernel.org>
> >>>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> >>> -tip testing found a bootup crash + reboot due to this patch.
> >>>
> >>> config attached. The bootup crashes here:
> >>>
> >>> [    0.000000] MTRR variable ranges enabled:
> >>> [    0.000000]   0 base 0000000000 mask FFC0000000 write-back
> >>> [    0.000000]   1 disabled
> >>> [    0.000000]   2 disabled
> >>> [    0.000000]   3 disabled
> >>> [    0.000000]   4 disabled
> >>> [    0.000000]   5 disabled
> >>> [    0.000000]   6 disabled
> >>> [    0.000000]   7 disabled
> >>> [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> >>> [    0.000000]   get_mtrr: cpu0 reg00 base=0000000000 size=0000040000 write-back
> >>> [    reboot  ]
> >>>
> >> what does the e820 map look like?
> > 
> > [    0.000000] BIOS-provided physical RAM map:
> > [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> > [    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> > [    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
> > [    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
> > [    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
> > [    0.000000]  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > 
> 
> it seems that patch revealed the bug in 
> setup_bios_corruption_check

Cool. I'm wondering, could this explain:

   http://bugzilla.kernel.org/show_bug.cgi?id=12645

?

	Ingo

  reply	other threads:[~2009-03-15  6:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 12:57 [PATCH] x86: clean up output resulting from update_mptable option Jan Beulich
2009-03-13  2:34 ` [tip:x86/mm] " Jan Beulich
2009-03-13  4:35   ` [PATCH] x86: fix e820_update_range() Yinghai Lu
2009-03-13  4:39     ` [tip:x86/mm] " Yinghai Lu
2009-03-13  5:36       ` [PATCH] x86: make e820_update_range to handle small range update Yinghai Lu
2009-03-14 11:39         ` [tip:x86/mm] x86: make e820_update_range() " Yinghai Lu
2009-03-14 12:17           ` Ingo Molnar
2009-03-14 18:21             ` Yinghai Lu
2009-03-14 18:40               ` Ingo Molnar
2009-03-14 21:32                 ` Yinghai Lu
2009-03-15  6:04                   ` Ingo Molnar [this message]
2009-03-15  6:20                     ` Yinghai Lu
2009-03-15  6:25                       ` Ingo Molnar
2009-03-15  6:12                   ` [tip:x86/mm] x86: fix 64k corruption-check Yinghai Lu
2009-03-13  7:57     ` [PATCH] x86: fix e820_update_range() Jan Beulich
2009-03-13 11:13       ` Ingo Molnar
2009-03-13 18:22         ` Yinghai Lu

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=20090315060456.GF20949@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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