https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #50 from Alex Deucher ---
Go ahead and open new bugs for those issues.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #49 from Alexandre Demers ---
Also, the bug I saw when testing patches with kernel 3.12-rc1 just happened
with 3.11.0. The screen turns white and everything is frozen. I can't connect
through ssh (without the patches, when the screen
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #47 from Alex Deucher ---
(In reply to comment #46)
> It seems to allow the system to work properly. No crash with patches on
> 3.11.0 (but another problem with 3.12-rc1, probably a new bug). I added a
> printk to show what are the ma
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #46 from Alexandre Demers ---
It seems to allow the system to work properly. No crash with patches on 3.11.0
(but another problem with 3.12-rc1, probably a new bug). I added a printk to
show what are the max values. Here is what I get
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #45 from Alex Deucher ---
Created attachment 86297
--> https://bugs.freedesktop.org/attachment.cgi?id=86297&action=edit
patch 2/2
apply these two patches independent of any others.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #44 from Alex Deucher ---
Created attachment 86296
--> https://bugs.freedesktop.org/attachment.cgi?id=86296&action=edit
patch 1/2
This patch set works around the issue by limiting the sclk and mclk to the
highest levels listed in t
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #43 from Alexandre Demers ---
Created attachment 86168
--> https://bugs.freedesktop.org/attachment.cgi?id=86168&action=edit
dmesg with 86147
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #42 from Alexandre Demers ---
(In reply to comment #41)
> Created attachment 86147 [details] [review]
> mclk debugging pll debugging output
>
> Can you attach the dmesg output with this patch applied? I want to make
> sure the mclk
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #41 from Alex Deucher ---
Created attachment 86147
--> https://bugs.freedesktop.org/attachment.cgi?id=86147&action=edit
mclk debugging pll debugging output
Can you attach the dmesg output with this patch applied? I want to make su
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #40 from Alexandre Demers ---
Should I continu to see what value I can reach?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #39 from Alexandre Demers ---
Running with mclk at 125000
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.o
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #38 from Alexandre Demers ---
Running with mclk at 12.
I went under Windows and launch GPU-Z. We should be able to reach 1300MHz.
I've read that some Cayman cards were made to use a VDDCi between 1.15 and
1.16. I'm pretty sure I
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #37 from Alexandre Demers ---
Went to pl->mclk = 115000, runs fine.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.fre
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #36 from Alexandre Demers ---
A test of my own:
diff --git a/drivers/gpu/drm/radeon/ni_dpm.c b/drivers/gpu/drm/radeon/ni_dpm.c
index f7b625c..c1875d2 100644
--- a/drivers/gpu/drm/radeon/ni_dpm.c
+++ b/drivers/gpu/drm/radeon/ni_dpm.c
@
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #35 from Alexandre Demers ---
(In reply to comment #34)
> Created attachment 86112 [details] [review]
> testing patch - force mclk to high
>
> Sorry, had some garbage in my tree. use this one instead.
Tested and the screen ended up
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alex Deucher changed:
What|Removed |Added
Attachment #86111|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #33 from Alex Deucher ---
Created attachment 86111
--> https://bugs.freedesktop.org/attachment.cgi?id=86111&action=edit
testing patch - force mclk to high
Try this patch by itself. This patch will force the mclk to the highest for
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #32 from Alexandre Demers ---
(In reply to comment #31)
> Created attachment 85989 [details] [review]
> testing patch
>
> Try this patch independent from any other patches. It forces the engine and
> memory clocks of all performance
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #31 from Alex Deucher ---
Created attachment 85989
--> https://bugs.freedesktop.org/attachment.cgi?id=85989&action=edit
testing patch
Try this patch independent from any other patches. It forces the engine and
memory clocks of all
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #30 from Alexandre Demers ---
If there were any fixes pushed in kernel 3.12-rc1, none changed anything.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-de
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #29 from Alexandre Demers ---
Created attachment 85798
--> https://bugs.freedesktop.org/attachment.cgi?id=85798&action=edit
dpm=1 with partial patch applied on 3.11.0
dmesg output when dpm=1 with partial patch applied (deactivation
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #28 from Alex Deucher ---
(In reply to comment #27)
> (In reply to comment #26)
> > Can you attach your dmesg with dpm enabled?
>
> Do you mean with the patch applied (total and/or problematic part left
> alone)?
Doesn't matter. I
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #27 from Alexandre Demers ---
(In reply to comment #26)
> Can you attach your dmesg with dpm enabled?
Do you mean with the patch applied (total and/or problematic part left alone)?
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #26 from Alex Deucher ---
Can you attach your dmesg with dpm enabled?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.f
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #25 from Alexandre Demers ---
(In reply to comment #22)
> (In reply to comment #20)
> > Ok, if I apply the whole suggested patch but the following, it hangs:
> > @@ -4152,14 +4152,14 @@ int ni_dpm_init(struct radeon_device *rdev)
> >
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #24 from Alexandre Demers ---
(In reply to comment #22)
> (In reply to comment #20)
> > Ok, if I apply the whole suggested patch but the following, it hangs:
> > @@ -4152,14 +4152,14 @@ int ni_dpm_init(struct radeon_device *rdev)
> >
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #23 from Alex Deucher ---
(In reply to comment #21)
> Adding printk(KERN_DEBUG "DEBUG: about to pass the following value of
> module_index to radeon_atom_init_mc_reg_table(): %d", module_index); just
> before calling radeon_atom_init_
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #22 from Alex Deucher ---
(In reply to comment #20)
> Ok, if I apply the whole suggested patch but the following, it hangs:
> @@ -4152,14 +4152,14 @@ int ni_dpm_init(struct radeon_device *rdev)
> }
> ni_pi->mclk_rtt_mode_t
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #21 from Alexandre Demers ---
Adding printk(KERN_DEBUG "DEBUG: about to pass the following value of
module_index to radeon_atom_init_mc_reg_table(): %d", module_index); just
before calling radeon_atom_init_mc_reg_table() returns 2.
-
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #20 from Alexandre Demers ---
Ok, if I apply the whole suggested patch but the following, it hangs:
@@ -4152,14 +4152,14 @@ int ni_dpm_init(struct radeon_device *rdev)
}
ni_pi->mclk_rtt_mode_threshold = eg_pi->mclk_edc_wr_en
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #19 from Alexandre Demers ---
(In reply to comment #16)
> (In reply to comment #14)
> > Created attachment 85578 [details] [review] [review]
> > disable various dpm features
> >
> > I would suggest disabling various dpm features and
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #17 from Alexandre Demers ---
(In reply to comment #15)
> Another thing worth checking, what is the value of module_index passed to
> radeon_atom_init_mc_reg_table() in ni_initialize_mc_reg_table() in ni_dpm.c
> on your system?
How c
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #16 from Alexandre Demers ---
(In reply to comment #14)
> Created attachment 85578 [details] [review]
> disable various dpm features
>
> I would suggest disabling various dpm features and see if you can narrow
> down which, if any, h
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #18 from Alex Deucher ---
(In reply to comment #17)
> (In reply to comment #15)
> > Another thing worth checking, what is the value of module_index passed to
> > radeon_atom_init_mc_reg_table() in ni_initialize_mc_reg_table() in ni_dp
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #15 from Alex Deucher ---
Another thing worth checking, what is the value of module_index passed to
radeon_atom_init_mc_reg_table() in ni_initialize_mc_reg_table() in ni_dpm.c on
your system?
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #14 from Alex Deucher ---
Created attachment 85578
--> https://bugs.freedesktop.org/attachment.cgi?id=85578&action=edit
disable various dpm features
I would suggest disabling various dpm features and see if you can narrow down
whic
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #13 from Alexandre Demers ---
Is there anything else I can do to give a better idea of what is happening and
why it crashes?
If this can be of any value, my 6950 is of the following model: XFX
HD-695X-ZNDC (1GB DDR5, 830MHz Core Clo
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #12 from Alexandre Demers ---
Created attachment 85157
--> https://bugs.freedesktop.org/attachment.cgi?id=85157&action=edit
Cayman 6950 XFX vbios
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #11 from Alexandre Demers ---
So, after getting out at different points from ni_dpm_set_power_state(), it
seems I can go down to ni_power_control_set_level() without problem. However,
if I move to the next call which is ret = ni_dpm_f
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #10 from Alexandre Demers ---
If ret=1 just after ni_restrict_performance_levels_before_switch(),
ni_dpm_set_power_state() doesn't go any further and there is no hang. So, it
seems like if the problem is not with
ni_restrict_performan
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #9 from Alexandre Demers ---
Still the same with kernel 3.11.0. Tried with VM=0, aspm=0, disconnected my UPC
(just in case it was something with a "battery" state or something similar),
tried Gnome 3 and XFCE, all the same. The only t
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #8 from Alexandre Demers ---
Tested with
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-gcc-fixes and
it does exactly the same thing: it boots fine, show the login screen. I can
even login in if it doesn't hang righ
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #7 from Alexandre Demers ---
Hi Alex. I'm about to test your suggestion. Meanwhile, I identified the
original commit that broke the driver before being fixed by
f90555cbe629e14c6af1dcec1933a3833ecd321f (but ending by the display hangi
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #8 from Alexandre Demers ---
Tested with
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-gcc-fixes and
it does exactly the same thing: it boots fine, show the login screen. I can
even login in if it doesn't hang righ
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #7 from Alexandre Demers ---
Hi Alex. I'm about to test your suggestion. Meanwhile, I identified the
original commit that broke the driver before being fixed by
f90555cbe629e14c6af1dcec1933a3833ecd321f (but ending by the display hangi
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #6 from Alexandre Demers ---
(In reply to comment #5)
> You might try this branch in case gcc is having problems with the variable
> sized arrays used in the driver:
> http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #5 from Alex Deucher ---
You might try this branch in case gcc is having problems with the variable
sized arrays used in the driver:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-gcc-fixes
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #6 from Alexandre Demers ---
(In reply to comment #5)
> You might try this branch in case gcc is having problems with the variable
> sized arrays used in the driver:
> http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #5 from Alex Deucher ---
You might try this branch in case gcc is having problems with the variable
sized arrays used in the driver:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.12-wip-gcc-fixes
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #4 from Alexandre Demers ---
After bisect in one direction, I've ended up with the following commit:
f90555cbe629e14c6af1dcec1933a3833ecd321f is the first bad commit
commit f90555cbe629e14c6af1dcec1933a3833ecd321f
Author: Alex Deucher
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #4 from Alexandre Demers ---
After bisect in one direction, I've ended up with the following commit:
f90555cbe629e14c6af1dcec1933a3833ecd321f is the first bad commit
commit f90555cbe629e14c6af1dcec1933a3833ecd321f
Author: Alex Deucher
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #3 from Alexandre Demers ---
kernel 3.11.0-rc1 was experiencing a bug, but not the one seen in rc2 and
beyond. I'll dig on the "fix" that brought us to the state seen since rc2. If
nothing can be found, I'll go up the drm-next branch
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #3 from Alexandre Demers ---
kernel 3.11.0-rc1 was experiencing a bug, but not the one seen in rc2 and
beyond. I'll dig on the "fix" that brought us to the state seen since rc2. If
nothing can be found, I'll go up the drm-next branch
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #2 from Alexandre Demers ---
I began bisecting tonight. Rc2 was already having this bug. More news to come
before the weekend.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #2 from Alexandre Demers ---
I began bisecting tonight. Rc2 was already having this bug. More news to come
before the weekend.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #1 from Alexandre Demers ---
Created attachment 84186
--> https://bugs.freedesktop.org/attachment.cgi?id=84186&action=edit
errors when freeze happens
Errors logged from my two last try at booting and logging with kernel
3.11.0-rc5
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #1 from Alexandre Demers ---
Created attachment 84186
--> https://bugs.freedesktop.org/attachment.cgi?id=84186&action=edit
errors when freeze happens
Errors logged from my two last try at booting and logging with kernel
3.11.0-rc5
60 matches
Mail list logo
