linux-kernel - Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUXhW_yAie25DPVXzhi2_pYQTjJpDqa7EzRfvtQ0gFYYHQ@mail.gmail.com>
Date:	Thu, 25 Jul 2013 12:37:44 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Jani Nikula <jani.nikula@...ux.intel.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org,
	DRI <dri-devel@...ts.freedesktop.org>, linux-next@...r.kernel.org
Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm |
 drm-intel related? ]

On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
<jani.nikula@...ux.intel.com> wrote:
> On Thu, 25 Jul 2013, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula
>>> <jani.nikula@...ux.intel.com> wrote:
>>>> On Thu, 25 Jul 2013, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>>>> On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20130724:
>>>>>>
>>>>>> Removed tree:
>>>>>>         arm-dt (at maintainer's request)
>>>>>>
>>>>>> The wireless-next tree lost its build failure and gained a conflict
>>>>>> against Linus' tree.
>>>>>>
>>>>>> The tty tree lost its build failure.
>>>>>>
>>>>>> The staging tree gained a build failure for which I disabled a driver.
>>>>>>
>>>>>> ----------------------------------------------------------------------------
>>>>>>
>>>>>
>>>>> [ CCing drm and drm-intel folks ]
>>>>>
>>>>> With today's next-20130725 I see the following:
>>>>
>>>> Use of dev_priv->gt_lock in I915_WRITE through
>>>> intel_disable_gt_powersave before spin lock init, caused by
>>>>
>>>> commit 181d1b9e31c668259d3798c521672afb8edd355c
>>>> Author: Daniel Vetter <daniel.vetter@...ll.ch>
>>>> Date:   Sun Jul 21 13:16:24 2013 +0200
>>>>
>>>>     drm/i915: fix up gt init sequence fallout
>>>>
>>>
>>> Ah, cool.
>>>
>>> I assumed/tested "drm/i915: fix the racy object accounting", but this
>>> does not fix it.
>>> Will try with yours.
>>>
>>
>> Sorry, Jani.
>>
>> next-20130725 ships the patch you pointed, too.
>
> Confused. I meant that the above mentioned commit "drm/i915: fix up gt
> init sequence fallout" causes the problem. The patch I included in my
> mail should fix it. Could you try that please?
>

[ Note2myself: Do not read half of the message... ]

The bad... Your patch needed some refresh against next-20130725 (guess
it's against drm-intel-nightly).

The good... YES, your patch fixes the issue for me!

The ugly... /me.

Feel free to add my:

       Tested-by: Sedat Dilek <sedat.dilek@...il.com>

Thanks for the quick fix!

- Sedat -

- Sedat -

> BR,
> Jani.
>
>
>
>>
>> - Sedat -
>>
>> [1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/?id=next-20130725&qt=grep&q=drm%2Fi915%3A+fix+up+gt+init+sequence+fallout
>> [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=181d1b9e31c668259d3798c521672afb8edd355c
>>
>
> --
> Jani Nikula, Intel Open Source Technology Center

View attachment "dmesg_3.11.0-rc2-next20130725-4-iniza-small.txt" of type "text/plain" (82731 bytes)

Download attachment "0001-drm-i915-initialize-gt_lock-early-with-other-spin-lo.patch" of type "application/octet-stream" (1838 bytes)

Download attachment "3.11.0-rc2-next20130725-4-iniza-small.patch" of type "application/octet-stream" (7109 bytes)

Download attachment "config-3.11.0-rc2-next20130725-4-iniza-small" of type "application/octet-stream" (115044 bytes)