[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system


  • To: "Ryan Harper" <ryanh@xxxxxxxxxx>
  • From: "Pablo Montesinos" <pablomontesinos@xxxxxxxxx>
  • Date: Thu, 1 Jun 2006 09:11:14 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Uros Trebec <uros.trebec@xxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 01 Jun 2006 09:11:52 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IluCUtjDog8KNb0/TuvVa9orhYnTE4dekIZ+kvzq7UHQF7fxQ26OXSUsRQViIfZ1/D873WsUve8rbZoI/kgvtGiWaedNmvGg4tXthbpS6ZY+jrYeBztMy8FIzWGLUuQqkA3cjttbBSWelWtFEfQp0Kwd0qTx4bTDner6Qkwq9Nk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I installed xen-unstable and it seems to solve that problem. However,
I am getting a kernel bug. xen-unstable downloaded the 2.6.16.13
kernel. It is possible to use a 2.6.16?

Thanks,
Pablo

PS: if you enjoy kernel bugs:


Kernel BUG at drivers/xen/core/smpboot.c:224
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.16.13-xen #2
RIP: e030:[<ffffffff802c5d15>] <ffffffff802c5d15>{cpu_initialize_context+514}
RSP: e02b:ffff8800018bca78  EFLAGS: 00010282
RAX: ffffffffffffffea RBX: ffff8800018bca88 RCX: 0000000000000101
RDX: ffff8800018bca88 RSI: 0000000000000020 RDI: 0000000000000000
RBP: ffff8800018bdee8 R08: ffff8800102b5a20 R09: 0000000000000000
R10: ffff8800018bca88 R11: 0000000000000200 R12: 0000000000000020
R13: 0000000000000140 R14: ffff8800102b5860 R15: ffffffff8040be40
FS:  0000000000000000(0000) GS:ffffffff8052f000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 1, threadinfo ffff8800018bc000, task ffff8800018a4760)
Stack: 00000000002fab4f 0000000000000020 0000000000000000 0000000000000000
      0000000000000000 0000000000000000 0000000000000000 0000000000000000
      0000000000000000 0000000000000000
Call Trace: <ffffffff802c5adb>{cpu_bringup+0} <ffffffff8010b758>{divide_error+0}
      <ffffffff80398fa4>{debug+0} <ffffffff80398fc0>{int3+0}
      <ffffffff8010b65c>{overflow+0} <ffffffff8010b678>{bounds+0}
      <ffffffff8010b694>{invalid_op+0}
<ffffffff8010b640>{device_not_available+0}
      <ffffffff8010b6b0>{coprocessor_segment_overrun+0}
<ffffffff8010b6e8>{invalid_TSS+0}
      <ffffffff8010b704>{segment_not_present+0}
<ffffffff8010b720>{stack_segment+0}
      <ffffffff80398fdc>{general_protection+0} <ffffffff80398f88>{page_fault+0}
      <ffffffff8010b774>{spurious_interrupt_bug+0}
<ffffffff8010b608>{coprocessor_error+0}
      <ffffffff8010b73c>{alignment_check+0}
<ffffffff8010b624>{simd_coprocessor_error+0}
      <ffffffff8011b2e8>{ia32_syscall+0}
<ffffffff8010b2a4>{hypervisor_callback+0}
      <ffffffff8010b3a4>{failsafe_callback+0} <ffffffff8010aa94>{system_call+0}
      <ffffffff80564e5f>{smp_prepare_cpus+456} <ffffffff80108084>{init+60}
      <ffffffff8010b532>{child_rip+8}
<ffffffff80275580>{acpi_ds_init_one_object+0}
      <ffffffff80108048>{init+0} <ffffffff8010b52a>{child_rip+0}

Code: 0f 0b 68 e2 61 3d 80 c2 e0 00 48 81 c4 48 14 00 00 5b 41 5c
RIP <ffffffff802c5d15>{cpu_initialize_context+514} RSP <ffff8800018bca78>
<0>Kernel panic - not syncing: Attempted to kill init!
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Reboot disabled on cmdline: require manual reset

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.