Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8292010

containers/docker/TestJFRNetworkEvents.java fails with SIGBUS

XMLWordPrintable

    • aarch64
    • linux

      The following test failed in the JDK20 CI:

      containers/docker/TestJFRNetworkEvents.java

      Here's a snippet from the log file:

      #section:driver
      ----------messages:(6/265)----------
      command: driver TestJFRNetworkEvents
      reason: User specified action: run driver TestJFRNetworkEvents
      Mode: agentvm
      Agent id: 7
      Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc jdk.jartool/sun.tools.jar
      elapsed time (seconds): 17.081
      ----------configuration:(18/2178)----------

      <snip>

      ----------System.out:(160/7600)----------
      Test Environment: detected availableCPUs = 8
      [COMMAND]
      podman ps
      [2022-08-06T07:49:24.850394316Z] Gathering output for process 3430173
      [ELAPSED: 196 ms]
      [STDERR]

      [STDOUT]
      CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

      Full child process STDOUT was saved to docker-stdout-3430173.log
      [2022-08-06T07:49:25.002942193Z] Waiting for completion for process 3430173
      [2022-08-06T07:49:25.003098513Z] Waiting for completion finished for process 3430173
      DockerfileConfig: using custom image name: jpg-data.us.oracle.com/docker-local/mach5/jdk-test/oraclelinux_8.5_aarch64
      DockerfileConfig: using custom image version: 1.0
      [COMMAND]
      podman build --no-cache --tag jdk-internal:test-containers-docker-TestJFRNetworkEvents-jfr-network jdk-internal-test-containers-docker-TestJFRNetworkEvents-jfr-network
      [2022-08-06T07:49:25.253812757Z] Gathering output for process 3430202
      [ELAPSED: 4605 ms]
      [STDERR]

      [STDOUT]
      STEP 1/4: FROM jpg-data.us.oracle.com/docker-local/mach5/jdk-test/oraclelinux_8.5_aarch64:1.0
      STEP 2/4: COPY /jdk /jdk
      --> 57c5e1e511a
      STEP 3/4: ENV JAVA_HOME=/jdk
      --> 4e7f9b098fa
      STEP 4/4: CMD ["/bin/bash"]
      COMMIT jdk-internal:test-containers-docker-TestJFRNetworkEvents-jfr-network
      --> b86d2388d93
      Successfully tagged localhost/jdk-internal:test-containers-docker-TestJFRNetworkEvents-jfr-network
      b86d2388d938087a413a346831afb5f9a834ccd456b4efc5fe5915714357e1e0

      Full child process STDOUT was saved to docker-stdout-3430202.log
      [2022-08-06T07:49:29.857914986Z] Waiting for completion for process 3430202
      [2022-08-06T07:49:29.858676347Z] Waiting for completion finished for process 3430202
      [COMMAND]
      podman run --tty=true --rm --volume /opt/mach5/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S48905/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4cb84b09-e361-4169-b33b-03a1d2ffaca2/runs/706cb247-6eed-40c5-a0c5-9a63f197c0d4/testoutput/test-support/jtreg_open_test_hotspot_jtreg_containers/classes/2/containers/docker/TestJFRNetworkEvents.d:/test-classes/ --hostname container-unique-8221711 jdk-internal:test-containers-docker-TestJFRNetworkEvents-jfr-network /jdk/bin/java -cp /test-classes/ -XX:MaxRAMPercentage=6.25 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S48905/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4cb84b09-e361-4169-b33b-03a1d2ffaca2/runs/706cb247-6eed-40c5-a0c5-9a63f197c0d4/testoutput/test-support/jtreg_open_test_hotspot_jtreg_containers/tmp -Djdk.test.docker.image.name=jpg-data.us.oracle.com/docker-local/mach5/jdk-test/oraclelinux_8.5_aarch64 -Djdk.test.docker.image.version=1.0 -Djdk.test.container.command=podman JfrNetwork jdk.SocketWrite
      [2022-08-06T07:49:29.866681718Z] Gathering output for process 3430333
      [ELAPSED: 10929 ms]
      [STDERR]

      [STDOUT]
      ServerSocker Local Address: 0.0.0.0/0.0.0.0:41353
      SocketWriter(): sa = 0.0.0.0/0.0.0.0:41353
      ========= Recording event: jdk.SocketWrite
      ServerSocketListener: accepted socket connection: s = Socket[addr=/10.0.2.100,port=35678,localport=41353]
      event = jdk.SocketWrite {
        startTime = 07:49:31.365 (2022-08-06)
        duration = 0.288 ms
        host = "container-unique-8221711"
        address = "10.0.2.100"
        port = 41353
        bytesWritten = 1 byte
        eventThread = "Thread-1" (javaThreadId = 22)
      }


      event = jdk.SocketWrite {
        startTime = 07:49:31.367 (2022-08-06)
        duration = 0.119 ms
        host = "container-unique-8221711"
        address = "10.0.2.100"
        port = 41353
        bytesWritten = 1 byte
        eventThread = "Thread-1" (javaThreadId = 22)
      }


      event = jdk.SocketWrite {
        startTime = 07:49:31.367 (2022-08-06)
        duration = 0.0782 ms
        host = "container-unique-8221711"
        address = "10.0.2.100"
        port = 41353
        bytesWritten = 1 byte
        eventThread = "Thread-1" (javaThreadId = 22)
      }


      jfr_reported_container_hostname=container-unique-8221711
      getLocalIp() returning:
      container-unique-8221711
      10.0.2.100
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # SIGBUS (0x7) at pc=0x0000fffea0763760, pid=1, tid=1
      #
      # JRE version: Java(TM) SE Runtime Environment (20.0+10) (fastdebug build 20-ea+10-540)
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 20-ea+10-540, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
      # Problematic frame:
      # V [libjvm.so+0x1793760] JVM_handle_linux_signal+0x240
      #
      # Core dump will be written. Default location: Core dumps may be processed with "/opt/core.sh %p" (or dumping to //core.1)
      #
      # Can not save log file, dump to screen..
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # SIGBUS (0x7) at pc=0x0000fffea0763760, pid=1, tid=1
      #
      # JRE version: Java(TM) SE Runtime Environment (20.0+10) (fastdebug build 20-ea+10-540)
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 20-ea+10-540, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
      # Problematic frame:
      # V [libjvm.so+0x1793760] JVM_handle_linux_signal+0x240
      #
      # Core dump will be written. Default location: Core dumps may be processed with "/opt/core.sh %p" (or dumping to //core.1)
      #
      # If you would like to submit a bug report, please visit:
      # https://bugreport.java.com/bugreport/crash.jsp
      #

      --------------- S U M M A R Y ------------

      Command Line: -XX:MaxRAMPercentage=6.25 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S48905/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4cb84b09-e361-4169-b33b-03a1d2ffaca2/runs/706cb247-6eed-40c5-a0c5-9a63f197c0d4/testoutput/test-support/jtreg_open_test_hotspot_jtreg_containers/tmp -Djdk.test.docker.image.name=jpg-data.us.oracle.com/docker-local/mach5/jdk-test/oraclelinux_8.5_aarch64 -Djdk.test.docker.image.version=1.0 -Djdk.test.container.command=podman JfrNetwork jdk.SocketWrite

      Host: <container-unique-NNNNNNN>, AArch64, 8 cores, 30G, Linux
      Time: Sat Aug 6 07:49:32 2022 UTC elapsed time: 2.018871 seconds (0d 0h 0m 2s)

      --------------- T H R E A D ---------------

      Current thread is native thread

      Stack: [0x0000ffffe0d40000,0x0000ffffe1540000], sp=0x0000ffffe153ae10, free space=8171k
      Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
      V [libjvm.so+0x1793760] JVM_handle_linux_signal+0x240
      C [linux-vdso.so.1+0x5d0] __kernel_rt_sigreturn+0x0
      C [libc.so.6+0x353cc]
      C [libc.so.6+0x3554c]
      C [libc.so.6+0x20e68] __libc_start_main+0xe8


      siginfo: si_signo: 7 (SIGBUS), si_code: 2 (BUS_ADRERR), si_addr: 0x0000fffea0aa06f0

      This is a very different/strange failure. We have what looks like
      the contents of an hs_err_pid file showing up in the test log, but
      the test run artifacts don't have any hs_err_pid files.

      Although this test is named TestJFRNetworkEvents.java, I'm
      starting this bug off in hotspot/runtime since I don't see any
      indicators of a JFR problem. This looks more like a container
      problem...

            iklam Ioi Lam
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: