arch: amd64
branch: merge
triggering executable: bt (note: file is compressed)
triggering example's input: A file called inputbt.data in same directory from which you execute bt containing the following
10 number of time steps
0.01e0 dt for class A = 0.0008d0. class B = 0.0003d0 class C = 0.0001d0
2 2 2
kernel config:
CONFIG_ARCH_SUPPORTS_POPCORN=y
CONFIG_POPCORN=y
CONFIG_POPCORN_DEBUG=y
# CONFIG_POPCORN_DEBUG_PROCESS_SERVER is not set
# CONFIG_POPCORN_DEBUG_PAGE_SERVER is not set
# CONFIG_POPCORN_DEBUG_VMA_SERVER is not set
# CONFIG_POPCORN_DEBUG_VERBOSE is not set
# CONFIG_POPCORN_CHECK_SANITY is not set
# CONFIG_POPCORN_REMOTE_INFO is not set
# CONFIG_POPCORN_STAT is not set
CONFIG_POPCORN_KMSG=y
CONFIG_POPCORN_KMSG_SOCKET=m
# CONFIG_POPCORN_KMSG_TEST is not set
# CONFIG_POPCORN_DEBUG_MSG_LAYER is not set
After executing bt a couple of times, the remote node will eventually deadlock and execution on the origin will halt as it waits for the remote node to finish.
There are no interesting message in the origin's kernel log when this happens, however the remote node's console contains:
Message from syslogd@x86 at Feb 12 14:38:28 ...
kernel:[ 589.388764] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bt:668]
Message from syslogd@x86 at Feb 12 14:39:16 ...
kernel:[ 637.391605] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bt:668]
Message from syslogd@x86 at Feb 12 14:39:44 ...
kernel:[ 665.389329] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bt:668]
Message from syslogd@x86 at Feb 12 14:40:32 ...
kernel:[ 713.388493] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bt:668]
arch: amd64 branch: merge triggering executable: bt (note: file is compressed) triggering example's input: A file called inputbt.data in same directory from which you execute
bt
containing the followingkernel config:
After executing
bt
a couple of times, the remote node will eventually deadlock and execution on the origin will halt as it waits for the remote node to finish.There are no interesting message in the origin's kernel log when this happens, however the remote node's console contains:
The remote node's kernel log contains: