Ubuntu
eglibc package

  1. Precise (12.04)
  2. Bug #956051
  3. Comment #16

Comment 16 for bug 956051

Revision history for this message
Tom Worley (tom-worley) wrote :

I am also affected by this bug (dual Opteron 12 core 6238), but when starting /etc/init.d/xcp-xapi
Fresh install of Ubuntu 12.04

About to try the cpuid_mask_ext_ecx fix.
Adam: I'll test the backport if you need?

# /etc/init.d/xcp-xapi start
Error: Connection refused (calling connect )

syslog:
Jun 19 14:17:08 host1 xapi: [ info|host1|0 thread_zero||watchdog] (Re)starting xapi...
Jun 19 14:17:08 host1 kernel: [ 8209.795675] xapi[32494] trap invalid opcode ip:7f8fe3cbae11 sp:7fff711645c0 error:0 in libm-2.15.so[7f8fe3c78000+f9000]
Jun 19 14:17:09 host1 kernel: [ 8210.027119] apport[32496] trap invalid opcode ip:7ff62e2625fc sp:7fffe5a49970 error:0 in libm-2.15.so[7ff62e220000+f9000]
Jun 19 14:17:09 host1 kernel: [ 8210.027231] Process 32496(apport) has RLIMIT_CORE set to 1
Jun 19 14:17:09 host1 kernel: [ 8210.027245] Aborting core
Jun 19 14:17:09 host1 xcp-fe: 32494 (/usr/sbin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.cookie -writ...) exitted with signal -5
Jun 19 14:17:09 host1 xapi: [ info|host1|0 thread_zero||watchdog] received signal -5
Jun 19 14:17:09 host1 xapi: [ info|host1|0 thread_zero||watchdog] xapi watchdog exiting.
Jun 19 14:17:09 host1 xapi: [ info|host1|0 thread_zero||watchdog] Fatal: xapi died with signal -5: not restarting (watchdog never restarts on this signal)