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

hs101t004 and hs101t006 hang due to biased locking

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 6
    • Fix Version/s: 6
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Introduced In Build:
      b43
    • Introduced In Version:
      6
    • Resolved In Build:
      b44
    • CPU:
      generic
    • OS:
      generic

      Description

      The biased locking putback appears to have broken the following NSK tests:

          nsk/jvmti/scenarios/hotswap/HS101/hs101t004
          nsk/jvmti/scenarios/hotswap/HS101/hs101t006

      Biased locking was putback to main/baseline on 2005.06.23 and sync'ed
      into service_hs_baseline on 2005.06.24. The above two tests have hung
      on almost every configuration since 2005.06.24.

      I ran hs101t004 on producer using the same bits as nightly (Client VM)
      in a 65 minute stress loop with a 10 minute job timeout. I observed
      6 failures and no passes. When I added the -XX:-UseBiasedLocking option,
      I observed 21 passes and no failures.

      ###@###.### 2005-06-27 23:26:00 GMT


      I ran hs101t006 on producer using the same bits as nightly (Client VM)
      in a 65 minute stress loop with a 10 minute job timeout. I observed
      6 failures and no passes. When I added the -XX:-UseBiasedLocking option,
      I observed 19 passes and no failures.

      ###@###.### 2005-06-28 02:19:09 GMT
      ###@###.### 2005-06-28 04:07:18 GMT

        Attachments

          Activity

            People

            • Assignee:
              kbr Kenneth Russell (Inactive)
              Reporter:
              dcubed Daniel Daugherty
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: