https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #32 from Alexandre Demers ---
Created attachment 89246
--> https://bugs.freedesktop.org/attachment.cgi?id=89246=edit
journalctl from last couple of boot/hang cycles
This could be interesting:
I've been bisecting. The first usable
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #31 from Alexandre Demers ---
(In reply to comment #30)
> (In reply to comment #29)
> > Just in case, I went back in time for bisection between v3.11 and v3.10,
> > began at commit 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 when dpm
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #30 from Alex Deucher ---
(In reply to comment #29)
> Just in case, I went back in time for bisection between v3.11 and v3.10,
> began at commit 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 when dpm was
> implemented on Cayman. I applied
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #29 from Alexandre Demers ---
Just in case, I went back in time for bisection between v3.11 and v3.10, began
at commit 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 when dpm was implemented on
Cayman. I applied patches from bug 68235 so I
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #28 from Alexandre Demers ---
Alex, as I quoted you earlier, mclk depends on both vddc and vddci. How can we
know mclk at 125000 is stable when vddc is 1000 and vddci 1150 (here, vddc is
not at its max of 1050)?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #27 from Alexandre Demers ---
(In reply to comment #26)
> Alex, in drivers/gpu/drm/radeon/ni_dpm.c, when we are limiting the sclk and
> mclk to the max speed according to vddc and vddci, aren't we screwing
> possibly something with
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #26 from Alexandre Demers ---
Alex, in drivers/gpu/drm/radeon/ni_dpm.c, when we are limiting the sclk and
mclk to the max speed according to vddc and vddci, aren't we screwing possibly
something with mclk? I mean, could we be setting
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #25 from Alexandre Demers ---
(In reply to comment #24)
> (In reply to comment #23)
> > Well, maybe the first thing would be to identify when or what sequence leads
> > to the hang. That's why I was suggesting to trace it. But if I
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #24 from Alex Deucher ---
(In reply to comment #23)
> Well, maybe the first thing would be to identify when or what sequence leads
> to the hang. That's why I was suggesting to trace it. But if I understand
> you correctly, you are
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #23 from Alexandre Demers ---
(In reply to comment #22)
> (In reply to comment #19)
> > Official kernel 3.12 still failing with latest mesa and drm. It always ends
> > up with a white screen when it freezes and it is impossible to
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #22 from Alex Deucher ---
(In reply to comment #19)
> Official kernel 3.12 still failing with latest mesa and drm. It always ends
> up with a white screen when it freezes and it is impossible to connect
> remotely by SSH.
>
> Would
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #21 from Alex Deucher ---
(In reply to comment #20)
> I was thinking, since DPM is to be enabled by default in 3.13, maybe the
> severity of this bug should be increased? I mean, lots of computers are
> going to hard freeze by
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #20 from klavkalashj at gmail.com ---
I was thinking, since DPM is to be enabled by default in 3.13, maybe the
severity of this bug should be increased? I mean, lots of computers are going
to hard freeze by default. I don't know much
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #19 from Alexandre Demers ---
Official kernel 3.12 still failing with latest mesa and drm. It always ends up
with a white screen when it freezes and it is impossible to connect remotely by
SSH.
Would it be possible to add some
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #18 from Alexandre Demers ---
Could the kworker warning be a sign to look at?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #17 from Alexandre Demers ---
Here is the last thing I have before freezing and just after I rebooted (from
journal with systemd, no more dmesg). As you'll see, there is nothing there.
I'll look into other logs just in case.
Oct 26
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #16 from Alexandre Demers ---
By the way, even if setting mclk and vddci at fixed values, it eventually
freezes. It takes longer though. It will happen when scrolling a window or
focusing on a new one. Problem is, I can't seem to get
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #15 from Alexandre Demers ---
Still there with 3.12.0-rc6. If I just force the mclk to 125000 and vddci to
1150, I'm running fine. I don't know where to look at anymore. Any other
suggestions?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #14 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 86945
-- https://bugs.freedesktop.org/attachment.cgi?id=86945action=edit
A small simplification to low state adjustment
This doesn't solve the problem,
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #11 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #10)
Just to be sure: vddc is associated only to sclk and vddci to mclk, right?
Not exactly. Mclk is tied to vddci (memory interface voltage), but both mclk
and sclk
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #12 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(In reply to comment #11)
(In reply to comment #10)
Just to be sure: vddc is associated only to sclk and vddci to mclk, right?
Not exactly. Mclk is tied to vddci
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #13 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(In reply to comment #12)
(In reply to comment #11)
(In reply to comment #10)
Just to be sure: vddc is associated only to sclk and vddci to mclk, right?
Not
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #9 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Created attachment 86889
-- https://bugs.freedesktop.org/attachment.cgi?id=86889action=edit
dmesg with 3.12.0-rc3
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #10 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Just to be sure: vddc is associated only to sclk and vddci to mclk, right?
Also, how are a new freq and a new voltage applied to the card? Are they
applied simultanously or
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #8 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #7)
Alex, using debugfs, should I see the maxed values (sclk and mclk) or the
theorical value from the table? For now, even if I have confirmation in
dmesg the values
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #7 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Alex, using debugfs, should I see the maxed values (sclk and mclk) or the
theorical value from the table? For now, even if I have confirmation in dmesg
the values were maxed
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #4 from Alexandre Demers alexandre.f.dem...@gmail.com ---
Definitively something about sclk or mclk and the voltages, but I haven't had
the time to dig deeper for now. I've added some printk to be sure everything
was being maxed as
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #5 from Alex Deucher ag...@yahoo.com ---
Take a look at ni_apply_state_adjust_rules() to see how the power state is
adjusted based on various factors.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #6 from Alexandre Demers alexandre.f.dem...@gmail.com ---
(In reply to comment #5)
Take a look at ni_apply_state_adjust_rules() to see how the power state is
adjusted based on various factors.
Ok, but I may have to wait until this
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #2 from Alexandre Demers alexandre.f.dem...@gmail.com ---
It doesn't seem to be one of these, it still happens. While it is not always
related to a change in power state, I do experience it more often when I'm
launching games or just
https://bugs.freedesktop.org/show_bug.cgi?id=69723
Alexandre Demers alexandre.f.dem...@gmail.com changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #3 from Alexandre Demers alexandre.f.dem...@gmail.com ---
I'll try playing with patch 85578, which was the same thing as this patch with
a bit more. I'm pretty sure we are hitting something wrong again with mclk, but
in a different
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #1 from Alex Deucher ag...@yahoo.com ---
Created attachment 86424
-- https://bugs.freedesktop.org/attachment.cgi?id=86424action=edit
disable various dpm features
Try this patch and see if you can narrow down which, if any, of these
33 matches
Mail list logo
