Please attach your xorg log and dmesg output.
Created attachment 113596 [details]
Xorg.0.log
Created attachment 113597 [details]
dmesg log
(In reply to Alex Deucher from comment #1)
> Please attach your xorg log and dmesg output.

Ive attached them sorry about that. I should also point my card is an AMD 7950
and is connected via Dual link DVI.
This may be a duplicate of bug 87796.  Can you try the suggestions in comment
10 on that bug?  If they help can you try the patch I attached and attach the
dmesg output with the patch applied?
Created attachment 113611 [details]
dmesg after trying the first "fix"

dmesg after doing echo high >
/sys/class/drm/card0/device/power_dpm_force_performance_level
(In reply to Alex Deucher from comment #5)
> This may be a duplicate of bug 87796.  Can you try the suggestions in
> comment 10 on that bug?  If they help can you try the patch I attached and
> attach the dmesg output with the patch applied?
Thank you. So I tried "echo high >
/sys/class/drm/card0/device/power_dpm_force_performance_level" without "" as
root and without restarting I set the refresh rate to 144hz and there is no
more artifacting/flickering. Setting it back to auto causes there to be
artifacts/flickering. So its something that has to do with DPM? I havem my
dmesg attached when setting it to high.

*** This bug has been marked as a duplicate of bug 87796 ***
(In reply to Alex Deucher from comment #8)
> 
> *** This bug has been marked as a duplicate of bug 87796 ***

My only concern is if setting DPM to high is safe? Does it increase power
usage/requirement, will it make my card reach high temps or anything damaging?
Also is this sort of the only "fix", will anything be added in the future so it
works with DPM on auto?
(In reply to andre35822 from comment #9)
> (In reply to Alex Deucher from comment #8)
> > 
> > *** This bug has been marked as a duplicate of bug 87796 ***
> 
> My only concern is if setting DPM to high is safe? Does it increase power
> usage/requirement, will it make my card reach high temps or anything
> damaging? Also is this sort of the only "fix", will anything be added in the
> future so it works with DPM on auto?

There is a fix on bug 87796, but it would be helpful to get the debugging
output I mentioned in that bug as well so the patch can be fine tuned.
(In reply to Alex Deucher from comment #10)
> (In reply to andre35822 from comment #9)
> > (In reply to Alex Deucher from comment #8)
> > > 
> > > *** This bug has been marked as a duplicate of bug 87796 ***
> > 
> > My only concern is if setting DPM to high is safe? Does it increase power
> > usage/requirement, will it make my card reach high temps or anything
> > damaging? Also is this sort of the only "fix", will anything be added in the
> > future so it works with DPM on auto?
> 
> There is a fix on bug 87796, but it would be helpful to get the debugging
> output I mentioned in that bug as well so the patch can be fine tuned.
I am up to help you for whatever it is that you need, I am just a bit confused.
You are referring to this bug report yes?
https://bugs.freedesktop.org/show_bug.cgi?id=87796 and want me to apply the
patch that you put as attachment in Comment 15? Or is it Comment 19 or 20? I am
also not sure how to apply the patch, it looks like something to do with git?
Once I know how to apply the patch, to my understanding you then want me to
enable the "problematic mode", which would be setting the screen to 144hz and
then attachming a dmesg output yes?
(In reply to andre35822 from comment #11)
> I am up to help you for whatever it is that you need, I am just a bit
> confused. You are referring to this bug report yes?
> https://bugs.freedesktop.org/show_bug.cgi?id=87796 and want me to apply the
> patch that you put as attachment in Comment 15? Or is it Comment 19 or 20? I
> am also not sure how to apply the patch, it looks like something to do with
> git? Once I know how to apply the patch, to my understanding you then want
> me to enable the "problematic mode", which would be setting the screen to
> 144hz and then attachming a dmesg output yes?

Yes, bug 87796.  I'm interested in the dmesg output after switching to the
problematic mode from the patch in comment 15.  See comment 17 for how to apply
it.

The patches in 19 and 20 will workaround the issue while still letting you use
auto.
(In reply to Alex Deucher from comment #12)
> (In reply to andre35822 from comment #11)
> > I am up to help you for whatever it is that you need, I am just a bit
> > confused. You are referring to this bug report yes?
> > https://bugs.freedesktop.org/show_bug.cgi?id=87796 and want me to apply the
> > patch that you put as attachment in Comment 15? Or is it Comment 19 or 20? I
> > am also not sure how to apply the patch, it looks like something to do with
> > git? Once I know how to apply the patch, to my understanding you then want
> > me to enable the "problematic mode", which would be setting the screen to
> > 144hz and then attachming a dmesg output yes?
> 
> Yes, bug 87796.  I'm interested in the dmesg output after switching to the
> problematic mode from the patch in comment 15.  See comment 17 for how to
> apply it.
> 
> The patches in 19 and 20 will workaround the issue while still letting you
> use auto.
Just thought I would post a little update, I am in the process of getting my
system to use the new kernel. Ive already compiled it with the patch and stuff,
i am just having a bit of trouble creating a ramdisk (I am followeing the arch
linux wiki) although I will figure it out. Will the fixes from comment 19 and
20 be implemented into the next release of video-ati or does it still need
testing? I am asking this so that if I know it isn't I may as well compile
another kernel with the patches from 19 and 20. Thank you btw for everything.
(In reply to andre35822 from comment #13)
> Just thought I would post a little update, I am in the process of getting my
> system to use the new kernel. Ive already compiled it with the patch and
> stuff, i am just having a bit of trouble creating a ramdisk (I am followeing
> the arch linux wiki) although I will figure it out. Will the fixes from
> comment 19 and 20 be implemented into the next release of video-ati or does
> it still need testing? I am asking this so that if I know it isn't I may as
> well compile another kernel with the patches from 19 and 20. Thank you btw
> for everything.

FWIW, using make install in your kernel tree will usually handle the ramdisk
update, but I'm not that familiar with arch, so if you are comfortable with
that, I'd stick with that.

As for the patches from 19 and 20, I'm pretty confident they will work, but it
would be nice to get some confirmation.
Created attachment 113676 [details]
xorg log with patch from comment 15
Created attachment 113677 [details]
dmesg log with patch from comment 15
(In reply to Alex Deucher from comment #14)
> (In reply to andre35822 from comment #13)
> > Just thought I would post a little update, I am in the process of getting my
> > system to use the new kernel. Ive already compiled it with the patch and
> > stuff, i am just having a bit of trouble creating a ramdisk (I am followeing
> > the arch linux wiki) although I will figure it out. Will the fixes from
> > comment 19 and 20 be implemented into the next release of video-ati or does
> > it still need testing? I am asking this so that if I know it isn't I may as
> > well compile another kernel with the patches from 19 and 20. Thank you btw
> > for everything.
> 
> FWIW, using make install in your kernel tree will usually handle the ramdisk
> update, but I'm not that familiar with arch, so if you are comfortable with
> that, I'd stick with that.
> 
> As for the patches from 19 and 20, I'm pretty confident they will work, but
> it would be nice to get some confirmation.
Alright so I tried out the kernel I compiled with the patch from comment 15 on
the other bug report, and either I didn't install the patch correctly (or it
didnt install correctly) or the patch is not solving the problem. I am still
getting the flickering/artifacts. I have attached an xorg log and dmesg log and
added comment15_patch to each of their file names so they are easily
distinguishable. Should I be compiling another kernel with the patches from
comment 19 and 20?
(In reply to andre35822 from comment #17)
> Alright so I tried out the kernel I compiled with the patch from comment 15
> on the other bug report, and either I didn't install the patch correctly (or
> it didnt install correctly) or the patch is not solving the problem. I am
> still getting the flickering/artifacts. I have attached an xorg log and
> dmesg log and added comment15_patch to each of their file names so they are
> easily distinguishable. Should I be compiling another kernel with the
> patches from comment 19 and 20?

The patch from comment 15 doesn't fix anything.  It just adds some additional
debugging output that might be useful in fine tuning the patches in comments 19
and 20.  To fix the issue, use the patches in comments 19 and 20.
(In reply to Alex Deucher from comment #18)
> (In reply to andre35822 from comment #17)
> > Alright so I tried out the kernel I compiled with the patch from comment 15
> > on the other bug report, and either I didn't install the patch correctly (or
> > it didnt install correctly) or the patch is not solving the problem. I am
> > still getting the flickering/artifacts. I have attached an xorg log and
> > dmesg log and added comment15_patch to each of their file names so they are
> > easily distinguishable. Should I be compiling another kernel with the
> > patches from comment 19 and 20?
> 
> The patch from comment 15 doesn't fix anything.  It just adds some
> additional debugging output that might be useful in fine tuning the patches
> in comments 19 and 20.  To fix the issue, use the patches in comments 19 and
> 20.
Oh okay thats good then, that means I applied the patch correctly. Shall I
apply the 19 and 20 patches now or would you prefer for a later date incase you
fine-tune anything more?
(In reply to andre35822 from comment #19)
> (In reply to Alex Deucher from comment #18)
> > (In reply to andre35822 from comment #17)
> > > Alright so I tried out the kernel I compiled with the patch from comment 15
> > > on the other bug report, and either I didn't install the patch correctly (or
> > > it didnt install correctly) or the patch is not solving the problem. I am
> > > still getting the flickering/artifacts. I have attached an xorg log and
> > > dmesg log and added comment15_patch to each of their file names so they are
> > > easily distinguishable. Should I be compiling another kernel with the
> > > patches from comment 19 and 20?
> > 
> > The patch from comment 15 doesn't fix anything.  It just adds some
> > additional debugging output that might be useful in fine tuning the patches
> > in comments 19 and 20.  To fix the issue, use the patches in comments 19 and
> > 20.
> Oh okay thats good then, that means I applied the patch correctly. Shall I
> apply the 19 and 20 patches now or would you prefer for a later date incase
> you fine-tune anything more?
Sorry I misunderstood/forgot what patches 19 and 20 were. I will try them and
see if they solve the issue.
I am actually having trouble c(In reply to Alex Deucher from comment #18)
> (In reply to andre35822 from comment #17)
> > Alright so I tried out the kernel I compiled with the patch from comment 15
> > on the other bug report, and either I didn't install the patch correctly (or
> > it didnt install correctly) or the patch is not solving the problem. I am
> > still getting the flickering/artifacts. I have attached an xorg log and
> > dmesg log and added comment15_patch to each of their file names so they are
> > easily distinguishable. Should I be compiling another kernel with the
> > patches from comment 19 and 20?
> 
> The patch from comment 15 doesn't fix anything.  It just adds some
> additional debugging output that might be useful in fine tuning the patches
> in comments 19 and 20.  To fix the issue, use the patches in comments 19 and
> 20.
Sorry for all of the messages. I am actually having trouble compiling the
kernel with patches 19 and 20 and am getting radeon errors. Here is a pastebin
of the errors incase you can help me http://pastebin.com/B2rFD9R0

What	Removed	Added
Component	Driver/Radeon	DRM/Radeon
Version	7.5 (2009.10)	unspecified
Assignee	xorg-driver-ati@lists.x.org	dri-devel@lists.freedesktop.org
Product	xorg	DRI
QA Contact	xorg-team@lists.x.org

What	Removed	Added
Status	NEW	RESOLVED
Resolution	---	DUPLICATE