linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
	Dave Airlie <airlied@gmail.com>,
	DRI <dri-devel@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>
Subject: Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
Date: Fri, 1 Mar 2013 17:30:23 +0100	[thread overview]
Message-ID: <CA+icZUXXYDY6rkcBF91qKy_1H7pchWAwW6koCRgY4E3b1oQvnw@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUWcipb4XG7HvbShP+RWa_Y8ewcGWJmcxRfQ0-owzgrx=g@mail.gmail.com>

On Thu, Feb 28, 2013 at 6:59 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni <przanoni@gmail.com> wrote:
>> Hi
>>
>> 2013/2/28 Sedat Dilek <sedat.dilek@gmail.com>:
>>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni <przanoni@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> 2013/2/28 Chris Wilson <chris@chris-wilson.co.uk>:
>>>>>> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote:
>>>>>>> On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>>>>>> > Hi,
>>>>>>> >
>>>>>>> > I am seeing this also on Linux-Next.
>>>>>>> >
>>>>>>> > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [   28.202381]
>>>>>>> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout
>>>>>>> > (has irq: 1)!
>>>>>>> > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [   28.210588]
>>>>>>> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout
>>>>>>> > (has irq: 1)!
>>>>>>> >
>>>>>>> > /var/log/kern.log.1:Feb 22 07:36:04 fambox kernel: [   27.408280]
>>>>>>> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout
>>>>>>> > (has irq: 1)!
>>>>>>> >
>>>>>>> > This seems to be hard reproducible...
>>>>>>> > Laptop-LCD... Sandybridge Mobile-GT2.
>>>>>>> >
>>>>>>> > Is there a way to force the error?
>>>>>>> >
>>>>>>> > Possible patch see [1].
>>>>>>> >
>>>>>>> > - Sedat -
>>>>>>> >
>>>>>>> > [1] https://patchwork.kernel.org/patch/2192721/
>>>>>>
>>>>>> That was:
>>>>>>
>>>>>> +       if (!done) {
>>>>>> +               status = I915_READ_NOTRACE(ch_ctl);
>>>>>> +               DRM_ERROR("dp aux hw did not signal timeout (has irq:
>>>>>> %i), status=%08x!\n",
>>>>>> +                         has_aux_irq, status);
>>>>>> +       }
>>>>>>
>>>>>> You applied
>>>>>>
>>>>>> +       if (!done) {
>>>>>> +               status = I915_READ_NOTRACE(ch_ctl);
>>>>>> +               DRM_ERROR("dp aux hw did not signal timeout (has irq:
>>>>>> %i), status=%08x!\n",
>>>>>> +                         has_aux_irq, status);
>>>>>> +       {
>>>>>
>>>>> In addition to this, after the problem happens can you please dump the
>>>>> registers 0x44008 (DEIIR) and 0xC4008 (SDEIIR)? You can do this either
>>>>> by running intel-reg-read (from intel-gpu-tools) or by changing the
>>>>> DRM_ERROR above to also print the result of I915_READ(0x44008) and
>>>>> I915_READ(0xC4008).
>>>>>
>>>>
>>>> Do I need a specific version of intel-gpu-tools?
>>>> Ubuntu/precise has v1.2 in its archives - sufficient?
>>>> Note: The error was twice after dozenz of Linux-Next kernel builds.
>>>>
>>>> - Sedat -
>>>>
>>>> [1] http://packages.ubuntu.com/precise/intel-gpu-tools
>>>>
>>>
>>> Installed intel-gpu-tools.
>>>
>>> # intel_reg_read
>>> Usage: intel_reg_read [-f | addr]
>>>          -f : read back full range of registers.
>>>               WARNING! This could be danger to hang the machine!
>>>          addr : in 0xXXXX format
>>>
>>> # intel_reg_read 0x44008
>>> Couldn't map MMIO region: Resource temporarily unavailable
>>>
>>> [  368.281707] intel_reg_read:3657 conflicting memory types
>>> f0000000-f0400000 uncached-minus<->write-combining
>>> [  381.521912] intel_reg_read:3658 conflicting memory types
>>> f0000000-f0400000 uncached-minus<->write-combining
>>> [  401.136291] intel_reg_read:3659 conflicting memory types
>>> f0000000-f0400000 uncached-minus<->write-combining
>>>
>>> Wrong i-g-t version? Missing enabled kernel-config option? Boot with
>>> i915 debug enabled?
>>
>> Just build the version from git and it should work
>> (http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/).
>>
>
> NO.
>
> $ git clone git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> intel-gpu-tools-git
>
> $ cd intel-gpu-tools-git/
>
> $ ./autogen.sh --disable-dumper <--- requires swig2.0 and python >=3.x
>
> $ sudo ./tools/intel_reg_read 0x44008
> 0x44008 : 0x0
>
> $ sudo ./tools/intel_reg_read 0xC4008
> 0xC4008 : 0x0
>
> $ sudo ./tools/intel_reg_dumper > /tmp/intel_reg_dumper.txt <--- see attachment
>
> Does this help you?
>

Ping Paulo.

- Sedat -

> - Sedat -
>
>
>>>
>>> - Sedat -
>>>
>>>>> If you conclude that the value of 0x44008 is 0x0 while the value of
>>>>> 0xC4008 is not, then this patch should help:
>>>>> https://patchwork.kernel.org/patch/2177841/
>>>>>
>>>>>>
>>>>>> That second '{' is the source of the compile error.
>>>>>> -Chris
>>>>>>
>>>>>> --
>>>>>> Chris Wilson, Intel Open Source Technology Centre
>>>>>> _______________________________________________
>>>>>> Intel-gfx mailing list
>>>>>> Intel-gfx@lists.freedesktop.org
>>>>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Paulo Zanoni
>>
>>
>>
>> --
>> Paulo Zanoni

  reply	other threads:[~2013-03-01 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 22:36 [git pull] drm merge for 3.9-rc1 Sedat Dilek
2013-02-27 23:06 ` Sedat Dilek
2013-02-28 11:18   ` Chris Wilson
2013-02-28 14:31     ` [Intel-gfx] " Paulo Zanoni
2013-02-28 17:12       ` Sedat Dilek
2013-02-28 17:29         ` Sedat Dilek
2013-02-28 17:33           ` Paulo Zanoni
2013-02-28 17:59             ` Sedat Dilek
2013-03-01 16:30               ` Sedat Dilek [this message]
2013-03-05 18:28       ` Imre Deak
2013-02-28 17:07     ` Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+icZUXXYDY6rkcBF91qKy_1H7pchWAwW6koCRgY4E3b1oQvnw@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=przanoni@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).