From: Keith Packard <keithp@keithp.com>
To: Rainer Dorsch <ml@bokomoko.de>, intel-gfx@lists.freedesktop.org
Subject: Re: xserver-xorg-video-intel does sometimes not resume
Date: Tue, 20 Sep 2011 09:49:48 -0700 [thread overview]
Message-ID: <yunfwjrf9ar.fsf@aiko.keithp.com> (raw)
In-Reply-To: <201109201241.17370.ml@bokomoko.de>
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
On Tue, 20 Sep 2011 12:41:16 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> I am wondering what I could do to figure out the root cause of the problem. I
> forgot to try, but I assume, that I could ssh into the machine and do some
> diagnosis, when the problem occurs. Are there logs which could help? I attach
> the syslog below...
Are you running the current 3.0.0 kernel from testing?
A kernel log with drm debug parameter set to 5 would be ideal; that will
show all of the mode setting logic happening at resume time which is
presumably not working. Two sessions, one working and one not working
would make identifying trouble easier.
You can set the drm debug parameter with a kernel command line option
drm.debug=5
Second, the output of 'intel_reg_dumper', which doesn't appear to be
packaged for debian yet. That's available from:
git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools
Again, having both working and non-working output makes it easy to
identify any differences which may point out the problem.
--
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
prev parent reply other threads:[~2011-09-20 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 10:41 xserver-xorg-video-intel does sometimes not resume Rainer Dorsch
2011-09-20 16:49 ` Keith Packard [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=yunfwjrf9ar.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.