You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Ivanov (JIRA)" <ji...@apache.org> on 2007/06/07 05:13:27 UTC

[jira] Created: (HARMONY-4080) [drlvm][thread] unexpected return code 139 for DRLVM smoke tests

[drlvm][thread] unexpected return code 139 for DRLVM smoke tests
----------------------------------------------------------------

                 Key: HARMONY-4080
                 URL: https://issues.apache.org/jira/browse/HARMONY-4080
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
         Environment: Linux x86, x86_64
            Reporter: Vladimir Ivanov


During the last day CC/CI systems reports failures for DRLVM smoke tests:

Lnx x86_64, jet:
Running test : shutdown.TestDaemonOnWait
*** FAILED **** : shutdown.TestDaemonOnWait (139 res code)

Lnx x86, jit (default mode):
Running test : gc.ThreadSuspension
*** FAILED **** : gc.ThreadSuspension (139 res code)

Note, to reproduce these failures tests should be run in parallel with "CPU eater".


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (HARMONY-4080) [drlvm][thread] unexpected return code 139 for DRLVM smoke tests

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky closed HARMONY-4080.
--------------------------------------

    Resolution: Duplicate
      Assignee: Gregory Shimansky

Looking at the stack trace I think it is very likely to be a duplication of bug HARMONY-3581.

> [drlvm][thread] unexpected return code 139 for DRLVM smoke tests
> ----------------------------------------------------------------
>
>                 Key: HARMONY-4080
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4080
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux x86, x86_64
>            Reporter: Vladimir Ivanov
>            Assignee: Gregory Shimansky
>
> During the last day CC/CI systems reports failures for DRLVM smoke tests:
> Lnx x86_64, jet:
> Running test : shutdown.TestDaemonOnWait
> *** FAILED **** : shutdown.TestDaemonOnWait (139 res code)
> Lnx x86, jit (default mode):
> Running test : gc.ThreadSuspension
> *** FAILED **** : gc.ThreadSuspension (139 res code)
> Note, to reproduce these failures tests should be run in parallel with "CPU eater".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-4080) [drlvm][thread] unexpected return code 139 for DRLVM smoke tests

Posted by "Rana Dasgupta (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504863 ] 

Rana Dasgupta commented on HARMONY-4080:
----------------------------------------

I could repro shutdown.TestDaemonOnWait problem  and also the stress.Sync problem( very infrequently ) on Linux x86_64. I saw no failures at all on 32 bit. 

It looks like while running under a stress condition ( like cycle eater ), Object.wait() fails...gdb shows...

in _Unwind_FindEnclosingFunction ()
   from /lib64/libgcc_s.so.1
#1  0x00000036cd906b57 in _Unwind_RaiseException () from /lib64/libgcc_s.so.1
#2  0x00000036cd906c4c in _Unwind_ForcedUnwind () from /lib64/libgcc_s.so.1
#3  0x00000036cbd0ac50 in __pthread_unwind () from /lib64/tls/libpthread.so.0
#4  0x00000036cbd05202 in sigcancel_handler () from /lib64/tls/libpthread.so.0
#5  <signal handler called>
#6  0x00000036cbd089ba in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/tls/libpthread.so.0
#7  0x0000002a9559943a in os_cond_timedwait (cond=0x10327f8, mutex=0x10327d0,
    ms=0, nano=0)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/linux/os_condvar.c:42
#8  0x0000002a9559bdee in condvar_wait_impl (cond=0x10327f8, mutex=0x10327d0,
    ms=0, nano=0, interruptable=1)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/thread_native_condvar.c:55
#9  0x0000002a9559c4c9 in monitor_wait_impl (mon_ptr=0x10327d0, ms=0, nano=0,
    interruptable=1)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/thread_native_fat_monitor.c:189
#10 0x0000002a955a0136 in thin_monitor_wait_impl (lockword_ptr=0x2a9c31b53c,
    ms=0, nano=0, interruptable=1)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/thread_native_thin_monitor.c:459
#11 0x0000002a955a01bc in hythread_thin_monitor_wait_interruptable (
    lockword_ptr=0x2a9c31b53c, ms=0, nano=0)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/thread_native_thin_monitor.c:511
#12 0x0000002a993f3e1f in jthread_monitor_timed_wait (monitor=0x43ce8c98,
    millis=0, nanos=0)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/thread/src/thread_java_monitors.c:337
#13 0x0000002a99258800 in Java_java_lang_VMThreadManager_wait (env=0x1012b20,
    clazz=0x43ce8c90, monitor=0x43ce8c98, millis=0, nanos=0)
    at /home/rana/Harmonystuff/trunk/working_vm/vm/vmcore/src/kernel_classes/native/java_lang_VMThreadManager.cpp:202
#14 0x0000002aac81e663 in ?? ()
#15 0x000000000002000a in ?? ()

We hit a very similar problem before on Linux x86_64 during SOE implementation..see reference:

http://mail-archives.apache.org/mod_mbox/harmony-dev/200611.mbox/%3C783bf8b0611170831w6dca1651re2ece230dcfcdd0e@mail.gmail.com%3E

This could be a bug in glibc...let's wait for more occurances.


> [drlvm][thread] unexpected return code 139 for DRLVM smoke tests
> ----------------------------------------------------------------
>
>                 Key: HARMONY-4080
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4080
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux x86, x86_64
>            Reporter: Vladimir Ivanov
>
> During the last day CC/CI systems reports failures for DRLVM smoke tests:
> Lnx x86_64, jet:
> Running test : shutdown.TestDaemonOnWait
> *** FAILED **** : shutdown.TestDaemonOnWait (139 res code)
> Lnx x86, jit (default mode):
> Running test : gc.ThreadSuspension
> *** FAILED **** : gc.ThreadSuspension (139 res code)
> Note, to reproduce these failures tests should be run in parallel with "CPU eater".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-4080) [drlvm][thread] unexpected return code 139 for DRLVM smoke tests

Posted by "Vladimir Ivanov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503008 ] 

Vladimir Ivanov commented on HARMONY-4080:
------------------------------------------

Today the test "stress.Sync" failed with 139 return code on the Linux x86_64 in 'jit' and 'jet' modes.

> [drlvm][thread] unexpected return code 139 for DRLVM smoke tests
> ----------------------------------------------------------------
>
>                 Key: HARMONY-4080
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4080
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux x86, x86_64
>            Reporter: Vladimir Ivanov
>
> During the last day CC/CI systems reports failures for DRLVM smoke tests:
> Lnx x86_64, jet:
> Running test : shutdown.TestDaemonOnWait
> *** FAILED **** : shutdown.TestDaemonOnWait (139 res code)
> Lnx x86, jit (default mode):
> Running test : gc.ThreadSuspension
> *** FAILED **** : gc.ThreadSuspension (139 res code)
> Note, to reproduce these failures tests should be run in parallel with "CPU eater".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.