From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48772] Signal unstable over Display Port on 2560x1440 monitor
Date: Mon, 16 Apr 2012 15:30:32 +0000 [thread overview]
Message-ID: <bug-48772-502-H020N5wDdW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48772-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #2 from Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk> 2012-04-16 08:30:32 PDT ---
radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
frequency between screen blackouts, but my sample size is small and randomness
of the timings makes me uneasy to claim so yet. Would it make sense for it to
have such effect?
Is testing with tiling disabled relevant given the problem happens also without
X running?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-04-16 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 15:09 [Bug 48772] New: Signal unstable over Display Port on 2560x1440 monitor bugzilla-daemon
2012-04-16 8:13 ` [Bug 48772] " bugzilla-daemon
2012-04-16 15:30 ` bugzilla-daemon [this message]
2012-04-16 15:43 ` bugzilla-daemon
2012-04-16 15:49 ` bugzilla-daemon
2012-04-16 16:10 ` bugzilla-daemon
2012-04-16 16:11 ` bugzilla-daemon
2012-04-17 10:20 ` bugzilla-daemon
2012-04-17 13:18 ` bugzilla-daemon
2012-04-18 21:21 ` bugzilla-daemon
2012-04-20 10:43 ` bugzilla-daemon
2012-04-20 15:19 ` bugzilla-daemon
2012-04-20 19:01 ` bugzilla-daemon
2012-04-23 7:49 ` bugzilla-daemon
2012-04-23 7:52 ` bugzilla-daemon
2012-04-23 18:43 ` bugzilla-daemon
2012-04-23 18:44 ` bugzilla-daemon
2015-09-22 9:42 ` bugzilla-daemon
2015-09-22 12:37 ` bugzilla-daemon
2015-09-22 14:30 ` bugzilla-daemon
2019-11-19 8:26 ` bugzilla-daemon
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=bug-48772-502-H020N5wDdW@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox