| Summary: | Heavy artifacts and unusable graphics system with the latest DPM changes | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | tobi | ||||||||||||||||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||||||||||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||||||||||||||
| Severity: | blocker | ||||||||||||||||||||
| Priority: | medium | CC: | queryv+fd, tobi | ||||||||||||||||||
| Version: | unspecified | ||||||||||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
tobi
2013-07-16 00:57:49 UTC
Created attachment 82464 [details]
dmesg output
Created attachment 82465 [details]
lspci output
Are you using radeon as a module or built into the kernel? I use it as a module. Will test it inbuilt ASAP, needs some minutes to compile. OK, took me some time to figure out that I also need the firmware inbuilt (and which one, isn't quite obvious that I need firmware from BARTS, BTC and SUMO to boot). Anyways, problem persists, same errors in dmesg. If you want to see how it actually looks, I have made a short video (sorry for the bad quality, need a better camera): http://slackeee.de/public/drm-next-3.11.mp4 (In reply to comment #4) > I use it as a module. Will test it inbuilt ASAP, needs some minutes to > compile. Sorry, no need to do that, modules should be fine. Sometimes there are problems with firmware when the driver is built in. I have this issue too (same card), and I made a comment about it in one of the Phoronix threads mentioning that the problem started post wip-5 patch-set. Having read most of the other related threads, I've noticed that most/all owners who try enabling DPM with a 6870 run into this problem. If any other information is needed to find a commonality from whence this issue originates (separate from OPs), let me know an I'll attach the needed logs. Created attachment 82504 [details] [review] add module parameter to disable aspm Try this patch which adds a new module parameter to disable aspm. Add radeon.aspm=0 to your kernel command line in grub to disable aspm support. (In reply to comment #8) > Created attachment 82504 [details] [review] [review] > add module parameter to disable aspm > > Try this patch which adds a new module parameter to disable aspm. Add > radeon.aspm=0 to your kernel command line in grub to disable aspm support. The issue still persists for me after using that patch and disabling aspm. I've attached a dmesg log taken after booting (to console, no X) using a 3.10 kernel, patched with the latest changes from the drm-fixes-3.11 branch (a01c34) and your aspm patch. And I've also attached the output from lspci since mine differs from OPs. I'm still kind of new to the whole patching thing (I'm a newb) so there's a chance that I may have done something wrong, but everything seemed like it went OK to me. Created attachment 82509 [details]
dmesg w/ dpm enabled & aspm disabled
Created attachment 82510 [details]
lspci output different user
Created attachment 82517 [details] [review] debugging output Can you attach a dmesg output with dpm enabled with this patch? Created attachment 82520 [details]
dmesg w/ dpm enabled & debug patch
dmesg output after booting to console.
Created attachment 82521 [details] dmesg with dpm=1 and aspm=0 after patch from comment #12 Same here, problem not fixed with patch from #8, attached output from dmesg with dpm=1 and aspm=0 after patch from #12 *** This bug has been marked as a duplicate of bug 66932 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.