From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb
Date: Wed, 15 Jul 2015 20:14:50 +0900 [thread overview]
Message-ID: <20150715111450.GB3998@swordfish> (raw)
In-Reply-To: <55A5CAAD.7060500@daenzer.net>
On (07/15/15 11:51), Michel Dänzer wrote:
> On 14.07.2015 22:41, Sergey Senozhatsky wrote:
> >
> > sometimes `xset dpms force off' just turns off the panel for a second,
> > sometimes -- until I generate a `wakeup' event (key press, etc.)
>
> FWIW, the former case is because releasing the enter key generates an
> input event, which changes the DPMS state to on again. You can avoid
> that with something like "sleep 1 && xset dpms force off".
>
Yeah, sure. That's the expected behaviour. 'turns off the panel for a second'
is sort of wrong here.
-ss
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb
Date: Wed, 15 Jul 2015 20:14:50 +0900 [thread overview]
Message-ID: <20150715111450.GB3998@swordfish> (raw)
In-Reply-To: <55A5CAAD.7060500@daenzer.net>
On (07/15/15 11:51), Michel Dänzer wrote:
> On 14.07.2015 22:41, Sergey Senozhatsky wrote:
> >
> > sometimes `xset dpms force off' just turns off the panel for a second,
> > sometimes -- until I generate a `wakeup' event (key press, etc.)
>
> FWIW, the former case is because releasing the enter key generates an
> input event, which changes the DPMS state to on again. You can avoid
> that with something like "sleep 1 && xset dpms force off".
>
Yeah, sure. That's the expected behaviour. 'turns off the panel for a second'
is sort of wrong here.
-ss
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-15 11:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 12:51 [-next] WARNING at i915_gem_track_fb Sergey Senozhatsky
2015-07-13 12:51 ` Sergey Senozhatsky
2015-07-13 14:35 ` [Intel-gfx] " Daniel Vetter
2015-07-13 14:35 ` Daniel Vetter
2015-07-13 14:44 ` Sergey Senozhatsky
2015-07-13 14:44 ` Sergey Senozhatsky
2015-07-13 15:05 ` [Intel-gfx] " Daniel Vetter
2015-07-13 15:05 ` Daniel Vetter
2015-07-14 11:39 ` [Intel-gfx] " Sergey Senozhatsky
2015-07-14 11:39 ` Sergey Senozhatsky
2015-07-14 12:44 ` Daniel Vetter
2015-07-14 12:44 ` Daniel Vetter
2015-07-14 13:41 ` Sergey Senozhatsky
2015-07-14 13:41 ` Sergey Senozhatsky
2015-07-14 15:11 ` [Intel-gfx] " Daniel Vetter
2015-07-14 15:11 ` Daniel Vetter
2015-07-15 11:12 ` Sergey Senozhatsky
2015-07-15 11:12 ` Sergey Senozhatsky
2015-07-15 2:51 ` Michel Dänzer
2015-07-15 11:14 ` Sergey Senozhatsky [this message]
2015-07-15 11:14 ` Sergey Senozhatsky
2015-07-13 14:46 ` Maarten Lankhorst
2015-07-13 14:46 ` Maarten Lankhorst
2015-07-13 14:57 ` [Intel-gfx] " Sergey Senozhatsky
2015-07-13 14:57 ` Sergey Senozhatsky
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=20150715111450.GB3998@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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.