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

Re: [Xen-ia64-devel] PATCH: xencomm



Hi, Tristan

I tested your patch.
But after I enabled network on domU and pinged another machine,
the following message is shown, then domU hang up.
I try to check your patches.

[root@para ~]# BUG: soft lockup detected on CPU#0!
Modules linked in: netloop xennet xenblk          
                                        
Pid: 0, CPU 0, comm:              swapper
psr : 0000021008026030 ifs : 800000000000030b ip  : [<a00000010006d9e1>]  
  Not tainted
ip is at xencomm_mini_hypercall_memory_op+0x1a1/0x1e0                     
             
unat: 0000000000000000 pfs : 800000000000030b rsc : 0000000000000008
rnat: 0000000000000000 bsps: 0000000000000000 pr  : 0000000000055a65
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
csd : 0000000000000000 ssd : 0000000000000000                       
b0  : a00000010006d9b0 b6  : a00000010006d8b0 b7  : a000000100693aa0
f6  : 000000000000000000000 f7  : 1003e6db6db6db6db6db7             
f8  : 1003e000000000002e750 f9  : 1003e0000000000006a30
f10 : 1003e000000000002e750 f11 : 1003e6db6db6db6db6db7
r1  : a000000101035240 r2  : 000000000000000c r3  : 5fffffff00000000
r8  : 0000000000000000 r9  : 0000000000003fff r10 : a000000100c13a88
r11 : 0000000004c13a80 r12 : a000000100c13a30 r13 : a000000100c0c000
r14 : 0000000000000001 r15 : 0000000004c13a80 r16 : 0000000000000003
r17 : a000000100c13ac8 r18 : a000000100c13af1 r19 : a000000100c13b80
r20 : a000000100c13a84 r21 : 0000000000000001 r22 : 0000000000000002
r23 : 0000000000000002 r24 : a000000100c13a98 r25 : a000000100c13a90
r26 : 0000000000000002 r27 : 0000000058434f4d r28 : 0000000000000000
r29 : 0000000000000001 r30 : a000000000000000 r31 : a000000100c0c318
                                                                    
Call Trace:
 [<a00000010001af50>] show_stack+0x50/0xa0
                                sp=a000000100c13680 bsp=a000000100c0d6c0
 [<a00000010001b820>] show_regs+0x820/0x840                             
                                sp=a000000100c13850 bsp=a000000100c0d678
 [<a0000001000d7f10>] softlockup_tick+0x150/0x180                       
                                sp=a000000100c13850 bsp=a000000100c0d648
 [<a0000001000a1190>] do_timer+0x990/0x9c0                              
                                sp=a000000100c13860 bsp=a000000100c0d600
 [<a000000100040500>] timer_interrupt+0x200/0x3c0                       
                                sp=a000000100c13860 bsp=a000000100c0d5b8
 [<a0000001000d8690>] handle_IRQ_event+0x190/0x280                      
                                sp=a000000100c13860 bsp=a000000100c0d578
 [<a0000001000d8a40>] __do_IRQ+0x2c0/0x3e0                              
                                sp=a000000100c13860 bsp=a000000100c0d528
 [<a000000100692600>] evtchn_do_upcall+0x160/0x240                      
                                sp=a000000100c13860 bsp=a000000100c0d4a0
 [<a0000001000684a0>] xen_leave_kernel+0x0/0x3b0                        
                                sp=a000000100c13860 bsp=a000000100c0d4a0
 [<a00000010006d9e0>] xencomm_mini_hypercall_memory_op+0x1a0/0x1e0      
                                sp=a000000100c13a30 bsp=a000000100c0d448
 [<a000000100068e70>] ia64_xenmem_reservation_op+0xf0/0x1e0             
                                sp=a000000100c13ac0 bsp=a000000100c0d410
 [<a000000200049f10>] network_alloc_rx_buffers+0x890/0xa00 [xennet]     
                                sp=a000000100c13af0 bsp=a000000100c0d3a0
 [<a00000020004d380>] netif_poll+0x1700/0x1b80 [xennet]                 
                                sp=a000000100c13b20 bsp=a000000100c0d298
 [<a000000100904310>] net_rx_action+0x310/0x6c0                         
                                sp=a000000100c13ba0 bsp=a000000100c0d238
 [<a000000100092db0>] __do_softirq+0x1f0/0x380                          
                                sp=a000000100c13bb0 bsp=a000000100c0d1a8
 [<a000000100093080>] do_softirq+0x140/0x2a0                            
                                sp=a000000100c13bb0 bsp=a000000100c0d140
 [<a0000001000933f0>] irq_exit+0x70/0xa0                                
                                sp=a000000100c13bb0 bsp=a000000100c0d128
 [<a000000100692610>] evtchn_do_upcall+0x170/0x240                      
                                sp=a000000100c13bb0 bsp=a000000100c0d0a0
 [<a0000001000684a0>] xen_leave_kernel+0x0/0x3b0                        
                                sp=a000000100c13bb0 bsp=a000000100c0d0a0
 [<e000000000000810>] 0xe000000000000810                                
                                sp=a000000100c13d80 bsp=a000000100c0d050
 [<a000000100068c10>] xen_pal_call_static+0xd0/0x100                    
                                sp=a000000100c13d80 bsp=a000000100c0d030
                                

Its cset is the below.

# xm info
host                   : tiger154
release                : 2.6.16.29-xen
version                : #2 SMP Thu Sep 28 10:34:55 JST 2006
machine                : ia64
nr_cpus                : 16
nr_nodes               : 1
sockets_per_node       : 4
cores_per_socket       : 2
threads_per_core       : 2
cpu_mhz                : 1595
hw_caps                : 00000000:00000000:00000000:00000000:00000000:
00000000:00000000:00000000:
total_memory           : 8166
free_memory            : 7075
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-ia64 hvm-3.0-ia64
xen_pagesize           : 16384
platform_params        : virt_start=0xe800000000000000
xen_changeset          : Tue Sep 26 19:11:33 2006 -0600 11635:
f34e37d0742d
cc_compiler            : gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
cc_compile_by          : root
cc_compile_domain      : 
cc_compile_date        : Thu Sep 28 10:01:11 JST 2006
xend_config_format     : 2

Best Regards,

Akio Takebe

>Hi,
>
>here are 3 patches for xencomm.
>
>The first one (a2) is the xencomm in itself.  Compatibility is broken.
>The second one (b2) renumbered dom0vp.  Because compatibility is broken 
>dom0vp 
>can be renumbered safely.
>[Are there good reasons why the numbering was sparse ?]
>The last one (c2) is a small optimization for physdevop eoi.
>
>tested by booting domU with netbk,netloop and blkbk as modules in dom0.
>
>Tristan.
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel


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


 


Rackspace

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