From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91861] [Radeon RS780] Blank screen (no signal) on HDMI after boot in 3.15 & later
Date: Fri, 30 Jan 2015 15:43:55 +0000 [thread overview]
Message-ID: <bug-91861-2300-OIZCvN7pvQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-91861-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=91861
--- Comment #10 from Christian König <deathsimple@vodafone.de> ---
(In reply to Alex Deucher from comment #9)
> (In reply to Mike S. from comment #8)
> > Thanks for the explanation.
> >
> > Can I suggest that you delay committing this patch for a week or so - I want
> > to check that it is really stable. Yesterday I had one incident where the
> > screen froze with diagonal coloured stripes for a couple of seconds, which I
> > have never seen before. It recovered itself OK without having to re-boot.
> > Could this have been caused by the higher divider values?
>
> Probably not. Usually PLL problems manifest themselves as no signal or
> periodic signal drop outs. Keep in mind that prior to kernel 3.15, the
> driver used a different algorithm that had its own limitations.
Yeah, agree. For PLLs you usually know in a few minutes if your setup works or
not.
The only thing that could affect it a bit is the temperature, but then you are
driving the PLL so close to the edge that you will notice problems relatively
soon as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-30 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 7:29 [Bug 91861] New: [Radeon RS780] Blank screen (no signal) on HDMI after boot in 3.15 & later bugzilla-daemon
2015-01-23 7:35 ` [Bug 91861] " bugzilla-daemon
2015-01-23 19:15 ` bugzilla-daemon
2015-01-24 11:05 ` bugzilla-daemon
2015-01-27 8:08 ` bugzilla-daemon
2015-01-27 9:15 ` bugzilla-daemon
2015-01-28 23:46 ` bugzilla-daemon
2015-01-29 13:00 ` bugzilla-daemon
2015-01-29 22:20 ` bugzilla-daemon
2015-01-30 1:21 ` bugzilla-daemon
2015-01-30 15:43 ` bugzilla-daemon [this message]
2015-01-30 22:44 ` bugzilla-daemon
2015-01-31 9:55 ` bugzilla-daemon
2015-02-01 22:19 ` bugzilla-daemon
2015-02-06 9:44 ` bugzilla-daemon
2015-02-06 9:52 ` bugzilla-daemon
2015-02-06 10:08 ` bugzilla-daemon
2015-02-06 10:20 ` 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-91861-2300-OIZCvN7pvQ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 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.