WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] x86_64 smp kernel panic

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] x86_64 smp kernel panic
From: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Date: Tue, 07 Feb 2006 15:17:16 -0500
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>, Ryan Grimm <grimm@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Delivery-date: Tue, 07 Feb 2006 20:28:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E1F6WuJ-00057t-00@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E1F6WuJ-00057t-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

On Tue, 2006-02-07 at 17:45 +0000, Steven Hand wrote:

> I can confirm that 8775 fixes SMP dom0 on 64 for me (the main problem 
> was the cpu_possible_map which is why CONFIG_HOTPLUG_CPU worked - it 
> prefills the possible_map to NR_CPUs)

With that and Chris Wright's ia32_sysenter patch in the tree, things
boot just fine for me now on x86_64 SMP dom0 --- great.

That's without CONFIG_HOTPLUG_CPU, though --- I'll have to check CPU
hotplug out separately, as that's still a useful feature to keep for
Xen, and it does appear to work fine on ia32 right now.

ia32 emulation may still have a problem, though --- I'm digging into
another such oops (appended) right now.

--Stephen

Kernel BUG at arch/x86_64/mm/../../i386/mm/hypervisor.c:196
invalid opcode: 0000 [1] SMP 
CPU 3 
Modules linked in: nfsd exportfs video thermal processor fan button battery ac
Pid: 3859, comm: java Not tainted 2.6.16-rc2-xen0 #1
RIP: e030:[<ffffffff8011d375>] <ffffffff8011d375>{xen_pgd_pin+85}
RSP: e02b:ffff8800241a1bf8  EFLAGS: 00010082
RAX: 00000000ffffffea RBX: ffff88001a857900 RCX: 000000000001f684
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800241a1bf8
RBP: ffff8800241a1c18 R08: ffff8800203ccff8 R09: 0000000000000200
R10: 0000000000007ff0 R11: ffff800000000000 R12: ffff88001a857900
R13: ffff880038bc2dc0 R14: ffff880001ed8360 R15: 0000003b7bcd351b
FS:  00002b2fa6dc81e0(0000) GS:ffffffff80663180(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process java (pid: 3859, threadinfo ffff8800241a0000, task ffff880000922200)
Stack: ffff880000000003 00000000000323d3 ffff880001ed8360 ffff800000000000 
       ffff8800241a1c38 ffffffff8011c9f3 ffff880000922200 0000000000000003 
       ffff8800241a1d18 ffffffff8048e259 
Call Trace: <ffffffff8011c9f3>{mm_pin+371} 
<ffffffff8048e259>{__sched_text_start+1625}
       <ffffffff8013933c>{lock_timer_base+44} 
<ffffffff8013933c>{lock_timer_base+44}
       <ffffffff801394ca>{__mod_timer+186} 
<ffffffff8048f16c>{schedule_timeout+156}
       <ffffffff80138e10>{process_timeout+0} <ffffffff80148fcf>{do_futex+671}
       <ffffffff80304a5c>{end_pirq+76} 
<ffffffff80128190>{default_wake_function+0}
       <ffffffff8030511e>{evtchn_do_upcall+142} 
<ffffffff80150104>{compat_sys_futex+196}
       <ffffffff8011e571>{ia32_sysret+0} <ffffffff8011e506>{ia32_syscall+30}

Code: 0f 0b 68 38 bb 4b 80 c2 c4 00 90 c9 c3 66 66 66 90 66 66 66 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel