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] Freeze on boot pv domU 2.6.31 with Xen 4.1

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Freeze on boot pv domU 2.6.31 with Xen 4.1
From: Eric Chanudet <eric.chanudet@xxxxxxxxxx>
Date: Fri, 21 May 2010 18:35:37 +0100
Cc: Steven Smith <Steven.Smith@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Delivery-date: Fri, 21 May 2010 10:39:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (LNX 1167 2008-08-23)

On Wed, 19 May 2010, Jeremy Fitzhardinge wrote:
Make sure you have "console=hvc0 earlyprintk=xen ignore_loglevel
initcall_debug" on your guest kernel command line to see if we can get
some idea of where its getting up to.

Here is the end of the output on the guest console :
[    0.000999] PCI: System does not support PCI
[    0.000999] PCI: System does not support PCI
[    0.000999] initcall pci_subsys_init+0x0/0x109 returned 0 after 0 usecs
[    0.000999] calling  proto_init+0x0/0x12 @ 1
[    0.000999] initcall proto_init+0x0/0x12 returned 0 after 0 usecs
[    0.000999] calling  net_dev_init+0x0/0x179 @ 1
[    0.000999] initcall net_dev_init+0x0/0x179 returned 0 after 0 usecs
[    0.000999] calling  neigh_init+0x0/0x71 @ 1
[    0.000999] initcall neigh_init+0x0/0x71 returned 0 after 0 usecs
[    0.000999] calling  fib_rules_init+0x0/0xa6 @ 1
[    0.000999] initcall fib_rules_init+0x0/0xa6 returned 0 after 0 usecs
[    0.000999] calling  pktsched_init+0x0/0xc4 @ 1
[    0.000999] initcall pktsched_init+0x0/0xc4 returned 0 after 0 usecs
[    0.000999] calling  tc_filter_init+0x0/0x4c @ 1
[    0.000999] initcall tc_filter_init+0x0/0x4c returned 0 after 0 usecs
[    0.000999] calling  tc_action_init+0x0/0x4c @ 1
[    0.000999] initcall tc_action_init+0x0/0x4c returned 0 after 0 usecs
[    0.000999] calling  genl_init+0x0/0xd8 @ 1

Still nothing wrong on Xen's one :
[    0.000000] Detected 3000.022 MHz processor.
[    0.000999] Console: colour dummy device 80x25
[    0.000999] console [tty0] enabled
[    0.000999] console handover: boot [xenboot0] -> real [hvc0]


Looking further in genetlink.c it seems that the freeze happens in :
synchronize_rcu (af_netlink.c:1540)
netlink_change_ngroups (af_netlink.c:1516)
genl_register_mc_group (genetlink.c:136)
genl_init (genetlink.c:800)

synchronize_rcu does not return after a very long time.

P.S: My first mail seems to be lost, sorry in advance if I double post.

--
Eric Chanudet

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

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