linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: 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: [git pull] drm merge for 3.9-rc1
Date: Wed, 27 Feb 2013 23:36:44 +0100	[thread overview]
Message-ID: <CA+icZUXG7WgRap2-oQGBr_s=QbE0QW6_zChDRqC-eEzrWR3Y5g@mail.gmail.com> (raw)

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/

             reply	other threads:[~2013-02-27 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 22:36 Sedat Dilek [this message]
2013-02-27 23:06 ` [git pull] drm merge for 3.9-rc1 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
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+icZUXG7WgRap2-oQGBr_s=QbE0QW6_zChDRqC-eEzrWR3Y5g@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 \
    /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).