https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers alexandre.f.dem...@gmail.com changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #50 from Alex Deucher ag...@yahoo.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers alexandre.f.dem...@gmail.com changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #46 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #47 from Alex Deucher ag...@yahoo.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alexandre Demers alexandre.f.dem...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #49 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #44 from Alex Deucher ag...@yahoo.com ---
Created attachment 86296
-- https://bugs.freedesktop.org/attachment.cgi?id=86296action=edit
patch 1/2
This patch set works around the issue by limiting the sclk and mclk to the
highest
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #45 from Alex Deucher ag...@yahoo.com ---
Created attachment 86297
-- https://bugs.freedesktop.org/attachment.cgi?id=86297action=edit
patch 2/2
apply these two patches independent of any others.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #38 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #39 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Running with mclk at 125000
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #40 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Should I continu to see what value I can reach?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #41 from Alex Deucher ag...@yahoo.com ---
Created attachment 86147
-- https://bugs.freedesktop.org/attachment.cgi?id=86147action=edit
mclk debugging pll debugging output
Can you attach the dmesg output with this patch applied? I
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #42 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #43 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 86168
-- https://bugs.freedesktop.org/attachment.cgi?id=86168action=edit
dmesg with 86147
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #33 from Alex Deucher ag...@yahoo.com ---
Created attachment 86111
-- https://bugs.freedesktop.org/attachment.cgi?id=86111action=edit
testing patch - force mclk to high
Try this patch by itself. This patch will force the mclk to
https://bugs.freedesktop.org/show_bug.cgi?id=68235
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Attachment #86111|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #35 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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.
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #36 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
+++
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #37 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Went to pl-mclk = 115000, runs fine.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #30 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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.
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #31 from Alex Deucher ag...@yahoo.com ---
Created attachment 85989
-- https://bugs.freedesktop.org/attachment.cgi?id=85989action=edit
testing patch
Try this patch independent from any other patches. It forces the engine and
memory
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #32 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #25 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #26 from Alex Deucher ag...@yahoo.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #29 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 85798
-- https://bugs.freedesktop.org/attachment.cgi?id=85798action=edit
dpm=1 with partial patch applied on 3.11.0
dmesg output when dpm=1 with partial
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #22 from Alex Deucher ag...@yahoo.com ---
(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 ag...@yahoo.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #24 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #20 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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 #21 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #14 from Alex Deucher ag...@yahoo.com ---
Created attachment 85578
-- https://bugs.freedesktop.org/attachment.cgi?id=85578action=edit
disable various dpm features
I would suggest disabling various dpm features and see if you can
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #15 from Alex Deucher ag...@yahoo.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #18 from Alex Deucher ag...@yahoo.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #16 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #17 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #19 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(In reply to comment #16)
(In reply to comment #14)
Created attachment 85578 [details] [review] [review]
disable various dpm features
I would suggest disabling
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #13 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #11 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #12 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 85157
-- https://bugs.freedesktop.org/attachment.cgi?id=85157action=edit
Cayman 6950 XFX vbios
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #9 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #10 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
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
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #8 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
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:
>
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #5 from Alex Deucher ag...@yahoo.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #6 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(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:
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #7 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Hi Alex. I'm about to test your suggestion. Meanwhile, I identified the
original commit that broke the driver before being fixed by
f90555cbe629e14c6af1dcec1933a3833ecd321f
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #4 from Alexandre Demers alexandre.f.dem...@gmail.com ---
After bisect in one direction, I've ended up with the following commit:
f90555cbe629e14c6af1dcec1933a3833ecd321f is the first bad commit
commit
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 #3 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #2 from Alexandre Demers alexandre.f.dem...@gmail.com ---
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=edit
errors when freeze happens
Errors logged from my two last try at booting and logging with kernel
3.11.0-rc5 when
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #1 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 84186
-- https://bugs.freedesktop.org/attachment.cgi?id=84186action=edit
errors when freeze happens
Errors logged from my two last try at booting and
58 matches
Mail list logo