From: Adam Jackson <ajax@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make PCH poison interrupt debug only
Date: Wed, 18 Apr 2012 13:29:50 -0400 [thread overview]
Message-ID: <1334770190.32618.10.camel@atropine> (raw)
In-Reply-To: <1334769610-3383-1-git-send-email-jbarnes@virtuousgeek.org>
[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]
On Wed, 2012-04-18 at 10:20 -0700, Jesse Barnes wrote:
> This indicates an internal messaging issue between the CPU and PCH, but
> there's nothing the driver can do about it. We seem to be able to
> trigger it at hotplug time sometimes, possibly due to the interrupt
> corrupting an in-flight message between CPU and PCH. At any rate, the
> error is harmless, so there's no need to bother the user about it.
I'm unconvinced. The bugs I've seen tend to have these messages in
combination with actual output setup problems. If that's going to be
reliably true I'd just as soon always see the message without needing
drm.debug=7.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2012-04-18 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 17:20 [PATCH] drm/i915: make PCH poison interrupt debug only Jesse Barnes
2012-04-18 17:29 ` Adam Jackson [this message]
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=1334770190.32618.10.camel@atropine \
--to=ajax@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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