From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71891] 3.13 fails to boot with the radeon module
Date: Mon, 12 May 2014 07:42:08 +0000 [thread overview]
Message-ID: <bug-71891-2300-OAdoHQrbXc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71891-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #32 from Christian König <deathsimple@vodafone.de> ---
(In reply to sdh from comment #30)
> Hi. Any update on this?
I've pushed the workaround upstream. So you should at least have a booting
system. Just don't try to use any accelerated video decoding since that would
crash the box again.
My best guess is that the information in the BIOS about the reference frequency
is wrong, but without having the hardware here I can't do much else to get UVD
working properly.
(In reply to sdh from comment #31)
> I just noticed I'm getting the following errors during the sleep and wake up
> cycle:
>
> [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low
> [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed
>
> Kernel is 3.14.2-1-git-dirty with above patch
Sounds like an unrelated DPM problem to me, but who knows.
--
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:[~2014-05-12 7:42 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 14:14 [Bug 71891] New: 3.13 fails to boot with the radeon module bugzilla-daemon
2014-03-11 14:19 ` [Bug 71891] " bugzilla-daemon
2014-03-11 14:53 ` bugzilla-daemon
2014-03-11 15:46 ` bugzilla-daemon
2014-03-11 16:22 ` bugzilla-daemon
2014-04-06 15:22 ` bugzilla-daemon
2014-04-06 15:35 ` bugzilla-daemon
2014-04-06 18:23 ` bugzilla-daemon
2014-04-06 18:50 ` bugzilla-daemon
2014-04-10 9:57 ` bugzilla-daemon
2014-04-10 14:12 ` bugzilla-daemon
2014-04-12 8:59 ` bugzilla-daemon
2014-04-12 9:25 ` bugzilla-daemon
2014-04-12 10:18 ` bugzilla-daemon
2014-04-12 10:27 ` bugzilla-daemon
2014-04-12 18:12 ` bugzilla-daemon
2014-04-15 7:29 ` bugzilla-daemon
2014-04-18 14:15 ` bugzilla-daemon
2014-04-19 10:25 ` bugzilla-daemon
2014-04-19 13:58 ` bugzilla-daemon
2014-04-24 3:06 ` bugzilla-daemon
2014-04-24 7:58 ` bugzilla-daemon
2014-04-24 8:58 ` bugzilla-daemon
2014-04-24 11:59 ` bugzilla-daemon
2014-04-26 1:35 ` bugzilla-daemon
2014-04-26 8:40 ` bugzilla-daemon
2014-04-27 0:12 ` bugzilla-daemon
2014-04-27 5:52 ` bugzilla-daemon
2014-04-29 13:51 ` bugzilla-daemon
2014-04-29 13:55 ` bugzilla-daemon
2014-05-06 5:15 ` bugzilla-daemon
2014-05-12 5:25 ` bugzilla-daemon
2014-05-12 7:42 ` bugzilla-daemon [this message]
2014-05-12 14:59 ` bugzilla-daemon
2014-05-12 15:11 ` bugzilla-daemon
2014-05-12 17:07 ` bugzilla-daemon
2014-05-12 18:21 ` bugzilla-daemon
2014-05-13 5:44 ` bugzilla-daemon
2014-06-26 0:14 ` bugzilla-daemon
2014-06-26 8:21 ` bugzilla-daemon
2014-07-03 15:11 ` bugzilla-daemon
2014-07-04 13:08 ` bugzilla-daemon
2014-07-04 13:16 ` bugzilla-daemon
2014-08-15 12:51 ` bugzilla-daemon
2014-08-15 15:08 ` bugzilla-daemon
2014-10-29 18:08 ` bugzilla-daemon
2014-10-29 19:21 ` bugzilla-daemon
2015-06-03 6:57 ` bugzilla-daemon
2015-06-03 12:48 ` bugzilla-daemon
2016-09-20 1:28 ` bugzilla-daemon
2016-09-20 1:45 ` bugzilla-daemon
2020-06-08 10: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-71891-2300-OAdoHQrbXc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).