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

[Xen-users] Boot problem with current xen-unstable

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Boot problem with current xen-unstable
From: Dave McCracken <dcm@xxxxxxxx>
Date: Mon, 21 Jul 2008 16:48:07 -0500
Delivery-date: Mon, 21 Jul 2008 14:48:44 -0700
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have been using the current xen-unstable tree for awhile along with the 
companion linux-2.6.18-xen tree on my AMD64 box running Debian.

For the past several weeks I have been unable to get this tree to complete 
booting.  It gets as far as running the rc scripts, then oopses in 
netlink_insert.

I don't have a working serial console, but from what's left on the screen I 
can see that the process is udevd, the stack trace is:
netlink_bind
sys_bind
get_empty_filp
sys_setsockopt
system_call

Is this a familiar problem to anyone?  Is there some config option I have set 
wrong?

Thanks,
Dave McCracken

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Boot problem with current xen-unstable, Dave McCracken <=