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

[Xen-users] XS 6.2 Crash



Hi i am running XS 6.2 with only a single domU - [centos 6.3_64 bit hvm] with 7000Mb ram.
When performed apache benchmark with ab
ie 
   ab -n 10000 -c 100 http://server.com//
after  successfully completing the test XS became unresponsive and showed this in crash_log.

[i dont remember what exactly i was doing after ab test,so i am blaming ab for this.]


From dom0.log:

<4>[322699.276939] /local/domain/15/device/vif/0: Connected
<4>[322724.120768] vif15.0: draining TX queue
<0>[333985.181875] NMI: IOCK error (debug interrupt?)
<4>[333985.181881] Modules linked in: tun nfs nfs_acl auth_rpcgss tcp_diag inet_diag lockd sunrpc openvswitch_mod ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables binfmt_misc nls_utf8 isofs dm_mirror video output sbs sbshc fan battery ac parport_pc lp parport nvram usbhid container evdev thermal sg button processor thermal_sys hpilo e1000e serio_raw rtc_cmos rtc_core rtc_lib 8250_pnp 8250 serial_core tpm_tis tpm tpm_bios pcspkr dm_region_hash dm_log dm_mod ahci libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd usbcore fbcon font tileblit bitblit softcursor [last unloaded: microcode]
<4>[333985.181917]
<4>[333985.181919] Pid: 5334, comm: ovs-vswitchd Not tainted (2.6.32.43-0.4.1.xs1.8.0.835.170778xen #1) ProLiant DL120 G7
<4>[333985.181921] EIP: 0061:[<f0a1672e>] EFLAGS: 00010246 CPU: 0
<4>[333985.181926] EIP is at ovs_flow_tbl_lookup+0x5e/0x80 [openvswitch_mod]
<4>[333985.181928] EAX: 00000030 EBX: ec42e834 ECX: 00000012 EDX: 4d8c04a6
<4>[333985.181929] ESI: ec42e85e EDI: eda21cf2 EBP: eda21cc4 ESP: eda21ca8
<4>[333985.181931]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069
<0>[333985.181932] Process ovs-vswitchd (pid: 5334, ti=eda20000 task=ec782670 task.ti=eda20000)
<0>[333985.181936] Stack:
<4>[333985.181937]  ec42e82c 00000030 eda21cd4 4d8c04a6 c100e9a0 edadcac0 edc1c2c0 eda21d5c
<4>[333985.181940] <0> f0a143e2 eda21d4c edca8000 00000000 00000000 00000000 00000001 240a2600
<4>[333985.181943] <0> 846a00b0 5cd61cda 00080000 003f0006 b06a7c73 92687c73 50002d82 00000000
<0>[333985.181947] Call Trace:
<4>[333985.181952]  [<f0a143e2>] ? ovs_dp_process_received_packet+0xa2/0xf0 [openvswitch_mod]
<4>[333985.181956]  [<c01d6f40>] ? pollwake+0x0/0x70
<4>[333985.181960]  [<f0a1b525>] ? ovs_vport_receive+0x75/0x90 [openvswitch_mod]
<4>[333985.181964]  [<f0a1d33f>] ? netdev_frame_hook+0x4f/0x90 [openvswitch_mod]
<4>[333985.181968]  [<c03527bb>] ? netif_receive_skb+0x1bb/0x6a0
<4>[333985.181971]  [<c03530fa>] ? __napi_gro_receive+0xda/0xf0
<4>[333985.181973]  [<c0352d68>] ? napi_skb_finish+0x38/0x40
<4>[333985.181975]  [<c035318d>] ? napi_gro_receive+0x2d/0x40
<4>[333985.181980]  [<f0627df8>] ? e1000_receive_skb+0x68/0xf0 [e1000e]
<4>[333985.181984]  [<f062d2aa>] ? e1000_clean_rx_irq+0x21a/0x360 [e1000e]
<4>[333985.181990]  [<f062cf7d>] ? e1000e_poll+0x19d/0x2b0 [e1000e]
<4>[333985.181992]  [<c0356005>] ? net_rx_action+0x155/0x260
<4>[333985.181996]  [<c013a952>] ? __do_softirq+0xc2/0x200
<4>[333985.181998]  [<c02dfce5>] ? end_pirq+0x95/0x110
<4>[333985.182001]  [<c013ab05>] ? do_softirq+0x75/0x80
<4>[333985.182002]  [<c013b1c5>] ? irq_exit+0x35/0x40
<4>[333985.182005]  [<c03dc83c>] ? evtchn_do_upcall+0x2fc/0x4a9
<4>[333985.182007]  [<c010477f>] ? hypervisor_callback+0x43/0x4b
<0>[333985.182008] Code: 08 eb 37 8b 1b 85 db 74 31 8b 03 0f 18 00 90 8d 43 f8 8b 55 f0 89 45 e4 3b 50 10 75 e6 8b 45 e8 8d 73 0c 8b 7d ec fc 39 c0 89 c1 <f3> a6 75 d4 8b 45 e4 83 c4 10 5b 5e 5f 5d c3 c7 45 e4 00 00 00


xl info

host                   : dvstest.ec.com
release                : 2.6.32.43-0.4.1.xs1.8.0.835.170778xen
version                : #1 SMP Wed May 29 18:06:30 EDT 2013
machine                : i686
nr_cpus                : 4
max_cpu_id             : 3
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 3093
hw_caps                : bfebfbff:28100800:00000000:00003f40:13bae3ff:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 8157
free_memory            : 197
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .5
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xff400000
xen_changeset          : 23509:aa273b47bcbe, pq 572:5c414f7cb3b1
xen_commandline        : mem=1024G dom0_max_vcpus=4 dom0_mem=752M,max:752M watchdog_timeout=300 lowmem_emergency_pool=1M crashkernel=64M@32M cpuid_mask_xsave_eax=0 console=vga vga=mode-0x0311
cc_compiler            : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)
cc_compile_by          : root
cc_compile_domain      : uk.xensource.com
cc_compile_date        : Fri Jun 14 09:04:06 EDT 2013
xend_config_format     : 4

ovs-vsctl -V
ovs-vsctl (Open vSwitch) 1.4.6
Compiled Jun 14 2013 09:23:27

C-State is enabled.

Attached full logs 


Can some one please help me find out why XS crashed,does this has anything to do with ovs?

Attachment: dom0.log
Description: Text Data

Attachment: dom15.log
Description: Text Data

Attachment: lspci-vv.out
Description: Binary data

Attachment: xen.log
Description: Text Data

Attachment: xen-crashdump-analyser.log
Description: Text Data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

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