[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48691E92.30809@goop.org>
Date: Mon, 30 Jun 2008 10:57:38 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Ingo Molnar <mingo@...e.hu>
CC: Nick Piggin <npiggin@...e.de>, Mark McLoughlin <markmc@...hat.com>,
xen-devel <xen-devel@...ts.xensource.com>,
Eduardo Habkost <ehabkost@...hat.com>,
Vegard Nossum <vegard.nossum@...il.com>,
Stephen Tweedie <sct@...hat.com>, x86@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for
64-bit Xen support
Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
>
>
>> * Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>>
>>
>>> Ingo Molnar wrote:
>>>
>>>> with this config:
>>>>
>>>> http://redhat.com/~mingo/misc/config-Sun_Jun_29_10_29_11_CEST_2008.bad
>>>>
>>>> i've saved the merged 2.6.26-rc8-tip-00241-gc6c8cb2-dirty tree into
>>>> tip/tmp.x86.xen-64bit.Sun_Jun_29_10 and pushed it out, so you can test
>>>> that exact version.
>>>>
>>> Looks like the setup.c unification missed the early_ioremap init from
>>> the early_ioremap unification. Unconditionally call
>>> early_ioremap_init().
>>>
>> applied to tip/x86/unify-setup - thanks Jeremy.
>>
>> I've reactived the x86/xen-64bit branch and i'm testing it currently.
>>
>
> -tip auto-testing found pagetable corruption (CPA self-test failure):
>
> [ 32.956015] CPA self-test:
> [ 32.958822] 4k 2048 large 508 gb 0 x 2556[ffff880000000000-ffff88003fe00000] miss 0
> [ 32.964000] CPA ffff88001d54e000: bad pte 1d4000e3
> [ 32.968000] CPA ffff88001d54e000: unexpected level 2
> [ 32.972000] CPA ffff880022c5d000: bad pte 22c000e3
> [ 32.976000] CPA ffff880022c5d000: unexpected level 2
> [ 32.980000] CPA ffff8800200ce000: bad pte 200000e3
> [ 32.984000] CPA ffff8800200ce000: unexpected level 2
> [ 32.988000] CPA ffff8800210f0000: bad pte 210000e3
>
> config and full log can be found at:
>
> http://redhat.com/~mingo/misc/config-Mon_Jun_30_11_11_51_CEST_2008.bad
>
This config doesn't have CONFIG_DEBUG_KERNEL enabled, let alone
CONFIG_CPA_DEBUG. I've noticed this seems to happen quite a lot:
there's a disconnect between the log file and the config which is
supposed to have built the kernel. Is there a bug in your test
infrastructure?
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists