[Xen-bugs] [Bug 678] New: Process SEGVs running a 2 CPU SMP HVM Guest

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=678

           Summary: Process SEGVs running a 2 CPU SMP HVM Guest
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: esmith@xxxxxxxxxxxxxxx


Various ltp tests get SEGVs when running on a RHEL4U2-64bit 2 CPU SMP fully
virtualized guest.

Test Log:

11:37:20        INFO    Reporting status: 'Test Running' for test: ltp_page01
11:37:20        INFO    Preparing to run test 'ltp_page01' using profile:
/qa/conductor/profiles/ltp/mm/page01.xml
11:37:20        INFO    Starting test 'ltp_page01' using profile:
/qa/conductor/profiles/ltp/mm/page01.xml
11:37:20        INFO    Dispatching operation: RemoteShell
11:37:20        FINE    Client sequencer got message requesting the start of a
new test: ltp_page01
11:37:20        FINER   Client sequencer sent message of type: 4 with seq num:
1 of size: 278 bytes
11:37:20        FINER   Client sequencer handling new operation from control
sequencer
11:37:20        FINE    Client sequencer looking for class:
com.katana.conductor.operations.RemoteShell
11:37:20        INFO    Operation RemoteShell running
11:37:20        FINE    Client sequencer was told that an operation is now
running
11:37:20        INFO    RemoteShell: target node(s) = vs170
11:37:20        INFO    ssh: /usr/bin/ssh root@vs170 cd
/qa/conductor/tests/ltp/testcases/bin; page01
11:37:20        FINE    ssh: waiting for command to finish
11:37:22        INFO       ssh: page01 1 FAIL : Test failed
11:37:22        FINE    executeShellCmd(ssh): exit value is 1
11:37:22        SEVERE  RemoteShell: command failed with error = 1
11:37:22        SEVERE  Operation RemoteShell failed
11:37:22        SEVERE  Reporting status: 'Test Failed' for test: ltp_page01
11:37:22        FINE    Client sequencer detected operation completed with
status of: Fail
11:37:22        FINER   Client sequencer sent message of type: 5 with seq num:
2 of size: 422 bytes
11:37:22        SEVERE  Crash Collection disabled for queue : RHEL4U2-64b-XEN64
11:37:22        INFO    Cleaning up after test


SEGV core produced:

[root@vs170 /]# uname -a
Linux vs170 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:00:54 EDT 2005 x86_64 x86_64
x86_64 GNU/Linux
[root@vs170 /]# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
[root@vs170 /]# cat /proc/cpuinfo | grep processor
processor       : 0
processor       : 1
[root@vs170 /]# ls -l /qa/conductor/corefiles/vs170_page01_core.31837
-rw-------  1 root root 204800 May 31 11:37
/qa/conductor/corefiles/vs170_page01_core.31837
[root@vs170 /]# gdb /qa/conductor/tests/ltp/testcases/bin/page01
/qa/conductor/corefiles/vs170_page01_core.31837
GNU gdb Red Hat Linux (6.3.0.0-1.63rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db
library "/lib64/libthread_db.so.1".

Core was generated by `page01'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib64/libc.so.6...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
#0  0x000000374f3078c3 in _dl_lookup_symbol_x () from
/lib64/ld-linux-x86-64.so.2
(gdb) bt
#0  0x000000374f3078c3 in _dl_lookup_symbol_x () from
/lib64/ld-linux-x86-64.so.2
#1  0x000000374f30a60a in fixup () from /lib64/ld-linux-x86-64.so.2
#2  0x000000374f30a4d2 in _dl_runtime_resolve () from
/lib64/ld-linux-x86-64.so.2
#3  0x00000000004013a5 in main (argc=Variable "argc" is not available.
) at page01.c:130
(gdb)

XEN info:

[root@tst177 ~]# xm info
host                   : tst177
release                : 2.6.16.13-xen
version                : #1 SMP Wed May 31 01:23:18 EDT 2006
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2793
hw_caps                :
bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory           : 2047
free_memory            : 7
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Tue May 30 11:44:23 2006 +0100 10177:d5f98d23427a
cc_compiler            : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by          : build
cc_compile_domain      : katana-technology.com
cc_compile_date        : Wed May 31 00:44:13 EDT 2006
[root@tst177 ~]# xm list

Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     1737     2 r-----  3663.0
vs170                              5      256     2 ------  9504.6
[root@tst177 ~]#
[root@tst177 ~]# (XEN) spurious IRQ irq got=-1


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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