|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support |
From: |
Ingo Molnar <mingo@xxxxxxx> |
Date: |
Tue, 1 Jul 2008 11:21:52 +0200 |
Cc: |
Nick Piggin <npiggin@xxxxxxx>, Mark McLoughlin <markmc@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Eduardo Habkost <ehabkost@xxxxxxxxxx>, Vegard Nossum <vegard.nossum@xxxxxxxxx>, Stephen Tweedie <sct@xxxxxxxxxx>, x86@xxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Yinghai Lu <yhlu.kernel@xxxxxxxxx> |
Delivery-date: |
Tue, 01 Jul 2008 02:22:30 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20080701085204.GA23289@xxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20080626105818.GA13805@xxxxxxx> <4863A8E6.1010807@xxxxxxxx> <20080627160333.GA27072@xxxxxxx> <486539A3.3030102@xxxxxxxx> <20080629084318.GA28815@xxxxxxx> <48684CD4.7040403@xxxxxxxx> <20080630082135.GA22844@xxxxxxx> <20080630092209.GA29815@xxxxxxx> <48696690.90907@xxxxxxxx> <20080701085204.GA23289@xxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Ingo Molnar <mingo@xxxxxxx> wrote:
> great - i've applied your fix and re-integrated x86/xen-64bit, it's
> under testing now. (no problems so far)
hm, -tip testing still triggers a 64-bit bootup crash:
[ 0.000000] init_memory_mapping
[ 0.000000] kernel direct mapping tables up to 3fff0000 @ 8000-a000
PANIC: early exception 0e rip 10:ffffffff80418f81 error 0 cr2 ffffffffff300000
[ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.26-rc8-tip #13363
[ 0.000000]
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff807f088b>] ? init_memory_mapping+0x341/0x56b
[ 0.000000] [<ffffffff80dba19f>] early_idt_handler+0x5f/0x73
[ 0.000000] [<ffffffff80418f81>] ? __memcpy_fromio+0xd/0x1e
[ 0.000000] [<ffffffff80de238a>] dmi_scan_machine+0x41/0x19b
[ 0.000000] [<ffffffff80dbeba8>] setup_arch+0x46d/0x5d8
[ 0.000000] [<ffffffff802896a0>] ? kernel_text_unlock+0x10/0x12
[ 0.000000] [<ffffffff80263b86>] ? raw_notifier_chain_register+0x9/0xb
[ 0.000000] [<ffffffff80dba140>] ? early_idt_handler+0x0/0x73
[ 0.000000] [<ffffffff80dbac5a>] start_kernel+0xf4/0x3b3
[ 0.000000] [<ffffffff80dba140>] ? early_idt_handler+0x0/0x73
[ 0.000000] [<ffffffff80dba2a4>] x86_64_start_reservations+0xa9/0xad
[ 0.000000] [<ffffffff80dba3b8>] x86_64_start_kernel+0x110/0x11f
[ 0.000000]
http://redhat.com/~mingo/misc/crash.log-Tue_Jul__1_10_55_47_CEST_2008.bad
http://redhat.com/~mingo/misc/config-Tue_Jul__1_10_55_47_CEST_2008.bad
Excluding the x86/xen-64bit topic solves the problem.
It triggered on two 64-bit machines so it seems readily reproducible
with that config.
i've pushed the failing tree out to tip/tmp.xen-64bit.Tue_Jul__1_10_55
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|