https://bugzilla.kernel.org/show_bug.cgi?id=61941
Denis Ollier changed:
What|Removed |Added
CC||larchunix+kernel at gmail.com
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #24 from Mihai Coman ---
Still happens on 3.19.2-1-ARCH. After blanking, sometimes the image comes back
on; I can move the cursor, but the interface is unresponsive.
--
You are receiving this mail because:
You are watching the assign
https://bugzilla.kernel.org/show_bug.cgi?id=61941
Pavol KlaÄanský changed:
What|Removed |Added
CC||pavol at klacansky.com
--- Comment #2
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #22 from Ilya Tumaykin ---
Reproducible with 3.14.0 kernel.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
Victor Zhang changed:
What|Removed |Added
CC||victzhang at gmail.com
--- Comment #21 fro
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #20 from Ilya Tumaykin ---
(In reply to Ilya Tumaykin from comment #19)
Same with 3.13.3.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #19 from Ilya Tumaykin ---
Still occurs with 3.13.2 kernel.
Ping.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #18 from Ilya Tumaykin ---
This issue still occurs with 3.12.8 kernel.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #17 from Ilya Tumaykin ---
Just got another lockup with 3.12.6 kernel.
Ping.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #16 from Ilya Tumaykin ---
I've noticed that this bug happens more frequently on my machine while running
Virtualbox. However, it does occur without Virtualbox as well.
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #15 from Shawn Starr ---
My Theory is incorrect, but what is interesting was I could get the GPU to
reset quicker, still, using EXA is unreliable use GLAMOR in your xorg.conf (if
you dont have a newer stack).
This was stable even if i
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #14 from Shawn Starr ---
Somehow, when the CPU shifts frequency this is causing voltage changes that are
affecting the GPU's switching DPM power states.
I will be trying this week my old tests with EXA to see if this holds true but
th
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #13 from Ilya Tumaykin ---
(In reply to Shawn Starr from comment #12)
Hello, Shawn.
I don't have any such daemon, but my cpufreq governor is set to conservative
both on AC and battery.
Ok, I will try your suggestion, but could you pl
https://bugzilla.kernel.org/show_bug.cgi?id=61941
Shawn Starr changed:
What|Removed |Added
CC||shawn.starr at rogers.com
--- Comment #12 f
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #11 from Ilya Tumaykin ---
Recently Phoronix site published a series of Radeon cards tests. Their setup
was kernel 3.12 with dpm enabled, Mesa 10.0 pre-release and Ubuntu 13.10. They
had the same problem as me [0]:
"The Radeon HD 3650
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #10 from Ilya Tumaykin ---
I've just had another suck lockup on 3.12 vanilla kernel without specifying
aspm option to the driver. What should I test now?
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #9 from Ilya Tumaykin ---
Changing gfx_clock_gating also doesn't help. There's one more thing though that
I've changed alongside dpm: I've enabled aspm=1 for kernel driver.
I will remove aspm=1 from modprobe.conf so the driver will ch
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #8 from Ilya Tumaykin ---
I've just noticed that after such lockup if I only restart X server without
full reboot of the machine then video playback (mplayer) is unavailable. xvinfo
shows this:
X-Video Extension version 2.2
screen #0
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #7 from Ilya Tumaykin ---
mclk_ss doesn't help either. Last option is gfx_clock_gating. Will try it next.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #6 from Ilya Tumaykin ---
Disabling dynamic_pcie_gen2 also doesn't help. Will try mclk_ss next.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #5 from Ilya Tumaykin ---
Disabling voltage control doesn't help. i.e. I still have this issue after the
following change:
- pi->voltage_control =
- radeon_atom_is_voltage_gpio(rdev,
SET_VOLTAGE_TYPE_ASIC_VDDC, 0);
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #4 from Ilya Tumaykin ---
(In reply to Alex Deucher from comment #3)
> Do you only get the lockups with dpm enabled? If so, try disabling certain
> dpm features and see if any of them help. See if you can narrow down which
> if any o
https://bugzilla.kernel.org/show_bug.cgi?id=61941
Alex Deucher changed:
What|Removed |Added
CC||alexdeuc...@gmail.com
--- Comment #3 from
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #1 from Ilya Tumaykin ---
Created attachment 109321
--> https://bugzilla.kernel.org/attachment.cgi?id=109321&action=edit
dmesg after lockup
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=61941
--- Comment #2 from Ilya Tumaykin ---
Created attachment 109331
--> https://bugzilla.kernel.org/attachment.cgi?id=109331&action=edit
another dmesg after lockup
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
25 matches
Mail list logo
