All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: intel-gfx@lists.freedesktop.org
Subject: Re: hotplug storms still here
Date: Tue, 8 Jun 2010 06:43:35 -0400	[thread overview]
Message-ID: <AANLkTik5WGEzvgh3_joBDNVOuWQ7aIl1bItFV-Bf-VTG@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikMioIlfJkdz6vGCyL102qcG_Z_Csm57MF1JMp8@mail.gmail.com>

On Tue, Jun 8, 2010 at 4:12 AM, Andrew Lutomirski <luto@mit.edu> wrote:
> On my trusty X200s (GM45), I still have such frequent i915 hotplug
> storms that any standard kernel is essentially unusable.
>

[...]

>
> I'll try selectively disabling outputs and seeing if I can narrow it down.

This patch did *not* fix it:

diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo
index 87d9536..448ad7a 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -2779,6 +2779,7 @@ bool intel_sdvo_init(struct drm_device *dev, int sdvo_reg)

        u8 ch[0x40];
        int i;
+       return false;

        intel_encoder = kcalloc(sizeof(struct intel_encoder)+sizeof(struct intel
        if (!intel_encoder) {


The output looked like this:

[  109.480089] hotplug event received, iir 0x00020000, stat
0x20200000, mask 0x38000800
[  109.666704] hotplug event received, iir 0x00020000, stat
0x20200000, mask 0x38000800
[  109.668747] hotplug event received, iir 0x00020000, stat
0x20200000, mask 0x38000800
[  109.669083] hotplug event received, iir 0x00020000, stat
0x28200000, mask 0x38000800
[  109.670007] hotplug event received, iir 0x00020000, stat
0x28200000, mask 0x38000800
[  109.670218] hotplug event received, iir 0x00020000, stat
0x28200000, mask 0x38000800
[  109.670656] hotplug event received, iir 0x00020000, stat
0x08200000, mask 0x38000800
[  109.671394] hotplug event received, iir 0x00020000, stat
0x20200000, mask 0x38000800

And it kept happening (in bursts of a couple seconds with a few
seconds of silence between) even after I switched to a console and did
killall -STOP Xorg.

Time for the next try.

--Andy

  reply	other threads:[~2010-06-08 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  8:12 hotplug storms still here Andrew Lutomirski
2010-06-08 10:43 ` Andrew Lutomirski [this message]
2010-06-08 13:24   ` Andrew Lutomirski
2010-06-08 14:09 ` Adam Jackson
2010-06-08 23:17   ` Andrew Lutomirski

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=AANLkTik5WGEzvgh3_joBDNVOuWQ7aIl1bItFV-Bf-VTG@mail.gmail.com \
    --to=luto@mit.edu \
    --cc=intel-gfx@lists.freedesktop.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 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.