From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Eric Anholt <eric@anholt.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for rc1
Date: Tue, 11 Jan 2011 11:12:03 -0800 [thread overview]
Message-ID: <20110111111203.279eae50@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTi=eRHbgerpdPYdoOo45LruNTk0rNsWvOO-kYxyQ@mail.gmail.com>
On Tue, 11 Jan 2011 11:00:13 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Jan 11, 2011 at 8:01 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > But yes, it worked before pulling Dave's tree, IOW, I haven't seen
> > this message on this machine before.
>
> .. and it's not a fluke. It happened again, and once more while I was
> away from the machine and the screen saver was running. So it does
> seem to have something to do with power-saving modes or something.
Have you tried reproducing it using xset dpms force off or similar?
Chris, what are you using to trigger the watermark related issues
you've found?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-11 19:12 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 22:59 Dave Airlie
2011-01-11 4:16 ` Linus Torvalds
2011-01-11 4:48 ` Dave Airlie
2011-01-11 4:51 ` Dave Airlie
2011-01-11 10:58 ` Chris Wilson
2011-01-11 6:06 ` Jesse Barnes
2011-01-11 6:28 ` Dave Airlie
2011-01-11 7:04 ` Dave Airlie
2011-01-11 10:35 ` Anca Emanuel
2011-01-11 13:33 ` Pavel Machek
2011-01-11 14:14 ` Chris Wilson
2011-02-23 18:53 ` Pavel Machek
2011-01-11 16:01 ` Linus Torvalds
2011-01-11 16:11 ` Anca Emanuel
2011-01-11 16:25 ` Anca Emanuel
2011-01-11 17:58 ` Anca Emanuel
2011-01-11 19:00 ` Linus Torvalds
2011-01-11 19:12 ` Jesse Barnes [this message]
2011-01-11 19:25 ` Linus Torvalds
2011-01-11 19:45 ` Jesse Barnes
2011-01-11 19:53 ` Linus Torvalds
2011-01-11 20:05 ` Chris Wilson
2011-01-11 22:16 ` Linus Torvalds
2011-01-11 22:31 ` Chris Wilson
2011-01-11 23:01 ` Linus Torvalds
2011-01-12 1:36 ` Linus Torvalds
2011-01-12 1:54 ` Dave Airlie
2011-01-11 23:20 ` Christian Borntraeger
2011-01-11 23:28 ` Linus Torvalds
2011-01-12 11:21 ` Christian Borntraeger
2011-01-12 12:49 ` James Simmons
2011-01-12 13:03 ` Christian Borntraeger
2011-01-12 13:32 ` James Simmons
2011-01-12 13:45 ` Christian Borntraeger
2011-01-12 15:55 ` Linus Torvalds
2011-01-12 16:39 ` James Simmons
2011-01-12 13:36 ` Anca Emanuel
2011-01-12 13:45 ` James Simmons
2011-01-12 13:55 ` Anca Emanuel
2011-01-12 14:35 ` Christian Borntraeger
2011-01-12 16:53 ` James Simmons
2011-01-12 15:13 ` Anca Emanuel
2011-01-12 15:25 ` Anca Emanuel
2011-01-12 15:40 ` James Simmons
2011-01-12 15:55 ` Anca Emanuel
2011-01-13 17:55 ` James Simmons
2011-01-13 19:53 ` Anca Emanuel
2011-01-14 16:29 ` Anca Emanuel
2011-01-14 16:38 ` James Simmons
2011-01-14 18:22 ` Anca Emanuel
2011-01-14 18:26 ` James Simmons
2011-01-14 18:40 ` Anca Emanuel
2011-01-14 19:02 ` Anca Emanuel
2011-02-19 15:14 ` Alex Riesen
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=20110111111203.279eae50@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®