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-users

Re: [Xen-users] kernel panic on boot of dom0

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] kernel panic on boot of dom0
From: Ernst Bachmann <e.bachmann@xxxxxxxx>
Date: Fri, 18 Nov 2005 11:38:25 +0100
Delivery-date: Fri, 18 Nov 2005 10:38:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200511180341.28256.pookey@xxxxxxxxxxxx>
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>
References: <200511180341.28256.pookey@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.1
On Friday 18 November 2005 04:41, Ian P. Christian wrote:
> I've managed to compile my dom0 kernel, however on attempting to boot to
> it, I get a kernel panic. After much fiddling aronud with a serial link I
> have managed to get this output.
>
> Any ideas or feedback are most welcome.
>
,,,
> Initializing CPU#1
> Initializing CPU#2
> Brought up 4 CPUs
> Initializing CPU#3
> domain 0: span 0
> ERROR: domain->span does not contain CPU0
> CPU0 attaching sched-domain:
> ERROR: domain->groups does not contain CPU0
>    groups:
> ERROR: empty group
>  0
> ERROR: group is NULL
>
>   domain 1: span f
>    groups: f
> CPU1 attaching sched-domain:
>  domain 0: span 0
> ERROR: domain->span does not contain CPU1
> ERROR: domain->groups does not contain CPU1
>   groups:
> ERROR: empty group
>  0
> ERROR: group is NULL

Had the same problem, disabling "SMT (Hyperthreading) scheduler 
support" (found in "Processor type and features") in the domU kernel seems to 
work arround it.

/Ernst

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