From: Jani Nikula <jani.nikula@linux.intel.com>
To: Greg Stark <stark@mit.edu>, intel-gfx@lists.freedesktop.org
Subject: Re: Performance regression with debug logs spammed with lots of warnings/errors
Date: Thu, 03 Aug 2017 13:37:01 +0300 [thread overview]
Message-ID: <87wp6lgcoi.fsf@nikula.org> (raw)
In-Reply-To: <CAM-w4HP_71BTKXwQUaTx5Ny-39oP=CCWSGAvrkc2o6ocu84kRw@mail.gmail.com>
On Sun, 30 Jul 2017, Greg Stark <stark@mit.edu> wrote:
> On 30 July 2017 at 13:23, Greg Stark <stark@mit.edu> wrote:
>
>> [drm:i915_hotplug_work_func [i915]] running encoder hotplug functions
>> Jul 30 13:17:17 pixel kernel: [ 3221.929831]
>> [drm:i915_hotplug_work_func [i915]] Connector HDMI-A-1 (pin 7)
>> received hotplug event.
>> Jul 30 13:17:17 pixel kernel: [ 3221.929850] [drm:intel_hdmi_detect
>> [i915]] [CONNECTOR:57:HDMI-A-1]
>> Jul 30 13:17:17 pixel kernel: [ 3221.935918] [drm:intel_get_hpd_pins
>> [i915]] hotplug event received, stat 0x00800000, dig 0x00111010, pins
>> 0x00000080
>> Jul 30 13:17:17 pixel kernel: [ 3221.935936]
>> [drm:intel_hpd_irq_handler [i915]] digital hpd port D - short
>
> Hm. This looks like a false alarm. I disconnected and reconnected the
> miniDP cable from the cheap chinese adapter to the monitor and these
> immediately stopped. My guess is that on powerup the chips in the
> adapter didn't quite reach a stable state and were generating these
> spurious events.
Plausible.
If this keeps happening, please file a bug over at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-08-03 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 12:23 Performance regression with debug logs spammed with lots of warnings/errors Greg Stark
2017-07-30 14:47 ` Greg Stark
2017-08-03 10:37 ` Jani Nikula [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=87wp6lgcoi.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stark@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.