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-users] kernel panic on boot of dom0

To: "Ian P. Christian" <pookey@xxxxxxxxxxxx>, "Ernst Bachmann" <e.bachmann@xxxxxxxx>
Subject: RE: [Xen-users] kernel panic on boot of dom0
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 18 Nov 2005 14:53:18 -0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxx
Delivery-date: Fri, 18 Nov 2005 14:53:40 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXsRXBtrDwW/1bLQ8GNdTJEuM91tQACjhtg
Thread-topic: [Xen-users] kernel panic on boot of dom0
 
> Ernst Bachmann wrote:
> > Had the same problem, disabling "SMT (Hyperthreading) scheduler 
> > support" (found in "Processor type and features") in the 
> domU kernel seems to 
> > work arround it.

I'm suspicious that this Oops is also due to a kernel config file
difference. What happens if you try a stock -xen kernel?

BTW, what kind of box is this? 

Thanks,
Ian
 
> Thanks very much! That's solved it and I can now boot.  On booting 
> though, there is a kernel opps -
> 
> e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
> Unable to read memory/target
> Unable to handle kernel NULL pointer dereference at virtual 
> address 00000000
>   printing eip:
> c03e0d86
> *pde = ma 00000000 pa 55555000
> Oops: 0002 [#1]
> SMP
> Modules linked in:
> CPU:    0
> EIP:    0061:[<c03e0d86>]    Not tainted VLI
> EFLAGS: 00010247   (2.6.12.6.5-xen)
> EIP is at cpu_up+0x0/0x133
> eax: 00000000   ebx: c1167f18   ecx: c1166000   edx: 00000000
> esi: c1167eff   edi: c0349905   ebp: 00000000   esp: c1167ee0
> ds: 007b   es: 007b   ss: 0069
> Process xenwatch (pid: 16, threadinfo=c1166000 task=c112aa20)
> Stack: c0107097 00000000 c1167f18 c03498f1 c0349e28 c1167ef8 696c6e6f 
> c400656e
>         ffffffff c1167f58 c02326a4 c4942e4c c1167f24 0000000a 
> 2f757063 
> ffff0030
>         00000001 c4942e4d c1167f8c c1167f98 c4942ec0 c1167f6c 
> c1167f8c 
> c1167f98
> Call Trace:
>   [<c0107097>] vcpu_hotplug+0x10c/0x111
>   [<c02326a4>] vsscanf+0x368/0x526
>   [<c01070df>] handle_vcpu_hotplug_event+0x43/0x47
>   [<c0291f49>] xenwatch_thread+0x10e/0x133
>   [<c0131922>] autoremove_wake_function+0x0/0x57
>   [<c0131922>] autoremove_wake_function+0x0/0x57
>   [<c0291e3b>] xenwatch_thread+0x0/0x133
>   [<c0131454>] kthread+0xba/0xf0
>   [<c013139a>] kthread+0x0/0xf0
>   [<c0107589>] kernel_thread_helper+0x5/0xb
> Code: 00 00 00 00 00 00 00 00 00 e7 bf 7c 0d f0 01 01 00 00 
> 00 00 00 00 
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ed 81 00 00 6e 
> 00 <00> 00 
> 75 f8 77 43 76 f8 77 43 75 f8 77 43 00 00 00 00 00 00 01
> 
> 
> 
> Kind Regards,
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

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

<Prev in Thread] Current Thread [Next in Thread>