[Bug 90332] [HSW Bisected]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90332

lu hua <huax.lu at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[HSW                        |[HSW
                   |Regression]ES3-CTS.shaders. |Bisected]ES3-CTS.shaders.un
                   |uniform_block.random.all_sh |iform_block.random.all_shar
                   |ared_buffer.12 fails        |ed_buffer.12 fails

--- Comment #1 from lu hua <huax.lu at intel.com> ---
84d56e66b9b4a646f04ec30696ca1aeea5e654d5 is the first bad commit
commit 84d56e66b9b4a646f04ec30696ca1aeea5e654d5
Author:     Ulrich Obergfell <uobergfe at redhat.com>
AuthorDate: Tue Apr 14 15:43:55 2015 -0700
Commit:     Linus Torvalds <torvalds at linux-foundation.org>
CommitDate: Tue Apr 14 16:48:58 2015 -0700

    watchdog: new definitions and variables, initialization

    The hardlockup and softockup had always been tied together.  Due to the
    request of KVM folks, they had a need to have one enabled but not the
    other.  Internally rework the code to split things apart more cleanly.

    There is a bunch of churn here, but the end result should be code that
    should be easier to maintain and fix without knowing the internals of what
    is going on.

    This patch (of 9):

    Introduce new definitions and variables to separate the user interface in
    /proc/sys/kernel from the internal run state of the lockup detectors.  The
    internal run state is represented by two bits in a new variable that is
    named 'watchdog_enabled'.  This helps simplify the code, for example:

    - In order to check if any of the two lockup detectors is enabled,
      it is sufficient to check if 'watchdog_enabled' is not zero.

    - In order to enable/disable one or both lockup detectors,
      it is sufficient to set/clear one or both bits in 'watchdog_enabled'.

    - Concurrent updates of 'watchdog_enabled' need not be synchronized via
      a spinlock or a mutex. Updates can either be atomic or concurrency can
      be detected by using 'cmpxchg'.

    Signed-off-by: Ulrich Obergfell <uobergfe at redhat.com>
    Signed-off-by: Don Zickus <dzickus at redhat.com>
    Cc: Ingo Molnar <mingo at elte.hu>
    Signed-off-by: Andrew Morton <akpm at linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds at linux-foundation.org>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150506/96f7f7ff/attachment-0001.html>