From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72283] [<ffffffffa01b7ecb>] dce6_afmt_write_speaker_allocation+0xdb/0x140 [radeon]
Date: Fri, 06 Dec 2013 13:13:09 +0000 [thread overview]
Message-ID: <bug-72283-502-Jm6O5F3JDz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72283-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 675 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72283
--- Comment #10 from bgunteriv@gmail.com ---
(In reply to comment #8)
> >
> > Make sure you have installed the latest rlc ucode for your chip and make
> > sure you've updated the ucode in your initrd if you are using one.
>
my system is just not very stable.
sometimes i get the UVD errors
sometimes i get the reference to [<ffffffffa01b7ecb>]
dce6_afmt_write_speaker_allocation+0xdb/0x140 [radeon]
and a couple of times it will get a little bit further, and then freeze. but i
can't get any logs, cause it never gets to loading my network.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1587 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-12-06 13:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 20:05 [Bug 72283] New: [<ffffffffa01b7ecb>] dce6_afmt_write_speaker_allocation+0xdb/0x140 [radeon] bugzilla-daemon
2013-12-03 22:47 ` [Bug 72283] " bugzilla-daemon
2013-12-04 3:23 ` bugzilla-daemon
2013-12-04 14:41 ` bugzilla-daemon
2013-12-04 16:33 ` bugzilla-daemon
2013-12-04 16:33 ` bugzilla-daemon
2013-12-05 15:14 ` bugzilla-daemon
2013-12-05 20:39 ` bugzilla-daemon
2013-12-05 20:42 ` bugzilla-daemon
2013-12-05 21:36 ` bugzilla-daemon
2013-12-06 3:33 ` bugzilla-daemon
2013-12-06 13:13 ` bugzilla-daemon [this message]
2013-12-06 15:24 ` bugzilla-daemon
2013-12-06 15:58 ` bugzilla-daemon
2013-12-09 18:28 ` bugzilla-daemon
2013-12-09 18:30 ` bugzilla-daemon
2013-12-10 14:36 ` bugzilla-daemon
2013-12-10 14:39 ` bugzilla-daemon
2013-12-10 14:45 ` bugzilla-daemon
2013-12-10 14:54 ` bugzilla-daemon
2013-12-10 15:06 ` bugzilla-daemon
2013-12-11 6:12 ` bugzilla-daemon
2013-12-11 22:09 ` bugzilla-daemon
2013-12-12 18:19 ` bugzilla-daemon
2013-12-13 7:19 ` bugzilla-daemon
2013-12-13 7:20 ` bugzilla-daemon
2013-12-13 14:07 ` bugzilla-daemon
2013-12-13 16:22 ` bugzilla-daemon
2013-12-13 16:23 ` bugzilla-daemon
2013-12-13 16:38 ` bugzilla-daemon
2013-12-13 16:41 ` bugzilla-daemon
2013-12-13 17:01 ` bugzilla-daemon
2013-12-13 18:23 ` bugzilla-daemon
2013-12-13 18:51 ` bugzilla-daemon
2019-11-19 8:41 ` 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-72283-502-Jm6O5F3JDz@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