Comment # 34
on bug 63935
from Dave Witbrodt
(In reply to comment #33) > As somewhat expected, v3.10-rc2 still has this. > > Has anyone done a bisection to find out which commit causes the corruption? Austin, this is new support for previously unsupported hardware present on several generations of AMD GPUs. My understanding is that it is an unforeseen problem with initializing the new support on certain kinds of systems. The developers are not really able to reproduce the problem being reported by several us. No (official) kernel has been released yet with this new support, and we have at least 6 weeks to work on it before the first such kernel will be released. Can you tell us a bit about your system? 1) What kind of hardware are you using -- can you show us the error messages from you log files? 2) Are you using the necessary firmware for your system to allow this new support to work? (Most distributions haven't packaged it yet, so most of us have to download the new firmware directly; see comment 2.) 3) Is your system built around a newer EFI motherboard, or do have a traditional non-EFI BIOS? There may still be some question of whether us users are doings something wrong -- although I personally have 2 systems that initialize UVD correctly and only 1 (EFI) system giving me trouble -- but if you have the firmware which enables this new UVD support, then maybe you could offer to do some register dumps if Christian or one of the other developers thinks it would be helpful to them?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
