All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Rainer Dorsch <ml@bokomoko.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: CRT not detected via hotplug on resume
Date: Wed, 21 Sep 2011 10:09:17 -0700	[thread overview]
Message-ID: <yunobydvn42.fsf@aiko.keithp.com> (raw)
In-Reply-To: <201109211815.27862.ml@bokomoko.de>


[-- Attachment #1.1: Type: text/plain, Size: 724 bytes --]

On Wed, 21 Sep 2011 18:15:27 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:

> Since I can ssh into the machine, when the problem occurs, are there some 
> diagnosis scripts/tools I could run?

Hrm. As far as I can tell, we're turning on the monitor successfully.

You might try playing with xrandr over ssh to make sure the system
thinks the monitor is running, then try turning it off and back on to
see if it lights up.

> Do you expect that it can be applied to a Linux 3.0 kernel?

yes, give v6 of the patch a try if you like; it will at least eliminate
the 10-second polling of your device, which won't suck.

Let me know if it actually helps your suspend/resume issues.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 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

  parent reply	other threads:[~2011-09-21 17:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 12:23 CRT not detected via hotplug on resume Rainer Dorsch
2011-09-21 15:31 ` Keith Packard
2011-09-21 16:15   ` Rainer Dorsch
2011-09-21 16:22     ` Simon Farnsworth
2011-09-21 17:09     ` Keith Packard [this message]
2011-09-22  8:36       ` Rainer Dorsch
2011-09-22 14:33         ` Keith Packard
2011-09-23 19:05           ` Rainer Dorsch
2011-09-24  5:29             ` Keith Packard
2011-10-22 18:41               ` Rainer Dorsch
2011-09-24  8:59 Rainer Dorsch

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=yunobydvn42.fsf@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ml@bokomoko.de \
    /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.