From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: akataria@vmware.com, "Thomas Gleixner" <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Daniel Hecht" <dhecht@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
"Jeremy Fitzhardinge" <jeremy@goop.org>
Subject: Re: [PATCH 05/05] x86: Rename paravirtualized TSC functions
Date: Thu, 10 Jul 2008 01:04:24 -0700 [thread overview]
Message-ID: <86802c440807100104s1e1f1cdeg421be2dbeffdcb75@mail.gmail.com> (raw)
In-Reply-To: <20080710075030.GA27361@elte.hu>
On Thu, Jul 10, 2008 at 12:50 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>
>> > that would be the tip/xen64 stuff, right? Does this revert:
>> >
>> > | Revert "x86_64: there's no need to preallocate level1_fixmap_pgt"
>> > |
>> > | This reverts commit 033786969d1d1b5af12a32a19d3a760314d05329.
>> > |
>> > | Suresh Siddha reported that this broke booting on his 2GB testbox.
>> >
>> > solve your problems, or are there other problems still?
>>
>> still is bisecting it now...
>
> ok. I have no mystery crash on my test-systems.
>
> by the looks of it, your crashes seem to be pagetable related. If it's
> in the tip/xen-64bit branch, my candidates would be:
>
> 0f38c08: x86: use __page_aligned_data/bss
> 0337869: x86_64: there's no need to preallocate level1_fixmap_pgt
> 89d7bb5: x86_64: add workaround for no %gs-based percpu
>
> 0337869 is reverted already.
>
> Or if it's an older commit, two candidates would be:
>
> b50efd2: x86: introduce page_size_mask for 64bit
> 3a9e189: x86: map UV chipset space - pagetable
>
> do you know the sha1 of the first broken tree? We know that
> tip-history-2008-07-08_16.08_Tue is known-good.
first round bisect all works..
it seems make oldconfig change setting between different setting...
diff .config config.full.good
4c4
< # Thu Jul 10 00:52:52 2008
---
> # Thu Jul 10 00:40:03 2008
295,296c295
< CONFIG_CC_STACKPROTECTOR_ALL=y
< CONFIG_CC_STACKPROTECTOR=y
---
> # CONFIG_CC_STACKPROTECTOR is not set
it seems some recent change doesn't like stackprotector.
YH
next prev parent reply other threads:[~2008-07-10 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 18:43 Alok Kataria
2008-07-09 6:13 ` Ingo Molnar
2008-07-09 7:20 ` Yinghai Lu
2008-07-09 17:30 ` Alok Kataria
2008-07-09 17:38 ` Yinghai Lu
2008-07-10 7:22 ` Ingo Molnar
2008-07-10 7:34 ` Yinghai Lu
2008-07-10 7:50 ` Ingo Molnar
2008-07-10 8:04 ` Yinghai Lu [this message]
2008-07-10 8:11 ` Yinghai Lu
2008-07-10 10:22 ` Yinghai Lu
2008-07-10 8:12 ` Ingo Molnar
2008-07-10 18:59 ` Jeremy Fitzhardinge
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=86802c440807100104s1e1f1cdeg421be2dbeffdcb75@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akataria@vmware.com \
--cc=dhecht@vmware.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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
Powered by JetHome