[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #32 from queryv+fd at gmail.com --- (In reply to comment #31) > (In reply to comment #29) > > Created attachment 82563 [details] [review] [review] > > additional fix > > > > Try just this patch on top of attachment 82560 [details] [re

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #31 from tobi at slackeee.de --- (In reply to comment #29) > Created attachment 82563 [details] [review] > additional fix > > Try just this patch on top of attachment 82560 [details] [review]. Do not > apply any of the debugging outp

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #30 from Martin Andersson --- (In reply to comment #29) > Created attachment 82563 [details] [review] > additional fix > > Try just this patch on top of attachment 82560 [details] [review]. Do not > apply any of the debugging output

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #29 from Alex Deucher --- Created attachment 82563 --> https://bugs.freedesktop.org/attachment.cgi?id=82563&action=edit additional fix Try just this patch on top of attachment 82560. Do not apply any of the debugging output patche

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #28 from Andre Heider --- (In reply to comment #26) > Also, even if the loop gets skipped, the "last = " lines should still get > printed. Oh right, that makes it even more weird... -- You are receiving this mail because: You are

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #27 from Alex Deucher --- Created attachment 82560 --> https://bugs.freedesktop.org/attachment.cgi?id=82560&action=edit fix I've attached a git version of Andre's patch. I think it should be fine. The logic is preserved. Not sur

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #26 from Alex Deucher --- (In reply to comment #24) > (In reply to comment #22) > > (In reply to comment #18) > > > Created attachment 82559 [details] [review] [review] [review] > > > weird fix > > > > > > > Hmmm, looks like a compi

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #25 from Martin Andersson --- The patch works for me as well -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL:

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #24 from Andre Heider --- (In reply to comment #22) > (In reply to comment #18) > > Created attachment 82559 [details] [review] [review] > > weird fix > > > > Hmmm, looks like a compiler bug. what compiler are you using? gcc versi

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #23 from Martin Andersson --- (In reply to comment #21) > (In reply to comment #19) > > I wasn't very clear in my #12 comment, but what I was trying to say it is > > something fishy about "reg_block->asRegIndexBuf". It is defined in >

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #22 from Alex Deucher --- (In reply to comment #18) > Created attachment 82559 [details] [review] > weird fix > Hmmm, looks like a compiler bug. what compiler are you using? -- You are receiving this mail because: You are the ass

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #21 from Alex Deucher --- (In reply to comment #19) > I wasn't very clear in my #12 comment, but what I was trying to say it is > something fishy about "reg_block->asRegIndexBuf". It is defined in > atombios.h as: > ATOM_MEMORY_SETTIN

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #20 from Martin Andersson --- Dammit copied the wrong line, but my point is still valid: ATOM_INIT_REG_INDEX_FORMAT asRegIndexBuf[1]; -- You are receiving this mail because: You are the assignee for the bug. -- next part

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #19 from Martin Andersson --- I wasn't very clear in my #12 comment, but what I was trying to say it is something fishy about "reg_block->asRegIndexBuf". It is defined in atombios.h as: ATOM_MEMORY_SETTING_DATA_BLOCK asRegDataBuf[1];

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #18 from Andre Heider --- Created attachment 82559 --> https://bugs.freedesktop.org/attachment.cgi?id=82559&action=edit weird fix This magically makes it work... No more stalls, box drops from 125 watt to 62. [7.923448] module

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #17 from Andre Heider --- Same here: [7.563515] module_index = 2 num_entries = 13 [7.563516] 0: s1 = 0x0a2f prd = 0x04 [7.567599] switching from power state: no more "s1 =" and not a single "last =" -- You are receiving

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #16 from Martin Andersson --- Created attachment 82552 --> https://bugs.freedesktop.org/attachment.cgi?id=82552&action=edit dmesg with more debugging -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #15 from Alex Deucher --- Created attachment 82551 --> https://bugs.freedesktop.org/attachment.cgi?id=82551&action=edit more debugging Something appears to be corrupting that structure. Try this patch on top of the previous one an

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added CC||tobi at slackeee.de --- Comment #14 from

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added CC||a.heider at gmail.com --- Comment #13 fro

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #32 from queryv...@gmail.com --- (In reply to comment #31) > (In reply to comment #29) > > Created attachment 82563 [details] [review] [review] > > additional fix > > > > Try just this patch on top of attachment 82560 [details] [revie

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #31 from t...@slackeee.de --- (In reply to comment #29) > Created attachment 82563 [details] [review] > additional fix > > Try just this patch on top of attachment 82560 [details] [review]. Do not > apply any of the debugging output

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #30 from Martin Andersson --- (In reply to comment #29) > Created attachment 82563 [details] [review] > additional fix > > Try just this patch on top of attachment 82560 [details] [review]. Do not > apply any of the debugging output

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #29 from Alex Deucher --- Created attachment 82563 --> https://bugs.freedesktop.org/attachment.cgi?id=82563&action=edit additional fix Try just this patch on top of attachment 82560. Do not apply any of the debugging output patche

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #28 from Andre Heider --- (In reply to comment #26) > Also, even if the loop gets skipped, the "last = " lines should still get > printed. Oh right, that makes it even more weird... -- You are receiving this mail because: You are

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #27 from Alex Deucher --- Created attachment 82560 --> https://bugs.freedesktop.org/attachment.cgi?id=82560&action=edit fix I've attached a git version of Andre's patch. I think it should be fine. The logic is preserved. Not sur

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #26 from Alex Deucher --- (In reply to comment #24) > (In reply to comment #22) > > (In reply to comment #18) > > > Created attachment 82559 [details] [review] [review] [review] > > > weird fix > > > > > > > Hmmm, looks like a compi

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #25 from Martin Andersson --- The patch works for me as well -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedeskto

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #24 from Andre Heider --- (In reply to comment #22) > (In reply to comment #18) > > Created attachment 82559 [details] [review] [review] > > weird fix > > > > Hmmm, looks like a compiler bug. what compiler are you using? gcc versi

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #12 from Martin Andersson --- Take this information with a grain of salt, since I'm testing stuff without really knowing whats going on. I found it interesting that the dmesg with the mc dump didn't print anything from the first for

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #23 from Martin Andersson --- (In reply to comment #21) > (In reply to comment #19) > > I wasn't very clear in my #12 comment, but what I was trying to say it is > > something fishy about "reg_block->asRegIndexBuf". It is defined in >

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #22 from Alex Deucher --- (In reply to comment #18) > Created attachment 82559 [details] [review] > weird fix > Hmmm, looks like a compiler bug. what compiler are you using? -- You are receiving this mail because: You are the ass

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #21 from Alex Deucher --- (In reply to comment #19) > I wasn't very clear in my #12 comment, but what I was trying to say it is > something fishy about "reg_block->asRegIndexBuf". It is defined in > atombios.h as: > ATOM_MEMORY_SETTIN

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #20 from Martin Andersson --- Dammit copied the wrong line, but my point is still valid: ATOM_INIT_REG_INDEX_FORMAT asRegIndexBuf[1]; -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #19 from Martin Andersson --- I wasn't very clear in my #12 comment, but what I was trying to say it is something fishy about "reg_block->asRegIndexBuf". It is defined in atombios.h as: ATOM_MEMORY_SETTING_DATA_BLOCK asRegDataBuf[1];

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #18 from Andre Heider --- Created attachment 82559 --> https://bugs.freedesktop.org/attachment.cgi?id=82559&action=edit weird fix This magically makes it work... No more stalls, box drops from 125 watt to 62. [7.923448] module

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #17 from Andre Heider --- Same here: [7.563515] module_index = 2 num_entries = 13 [7.563516] 0: s1 = 0x0a2f prd = 0x04 [7.567599] switching from power state: no more "s1 =" and not a single "last =" -- You are receiving

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #16 from Martin Andersson --- Created attachment 82552 --> https://bugs.freedesktop.org/attachment.cgi?id=82552&action=edit dmesg with more debugging -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #15 from Alex Deucher --- Created attachment 82551 --> https://bugs.freedesktop.org/attachment.cgi?id=82551&action=edit more debugging Something appears to be corrupting that structure. Try this patch on top of the previous one an

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added CC||t...@slackeee.de --- Comment #14 from Ale

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 Alex Deucher changed: What|Removed |Added CC||a.hei...@gmail.com --- Comment #13 from A

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #11 from Martin Andersson --- Created attachment 82534 --> https://bugs.freedesktop.org/attachment.cgi?id=82534&action=edit dmesg with mc reg dump -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #12 from Martin Andersson --- Take this information with a grain of salt, since I'm testing stuff without really knowing whats going on. I found it interesting that the dmesg with the mc dump didn't print anything from the first for

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #11 from Martin Andersson --- Created attachment 82534 --> https://bugs.freedesktop.org/attachment.cgi?id=82534&action=edit dmesg with mc reg dump -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #10 from Alex Deucher --- Created attachment 82519 --> https://bugs.freedesktop.org/attachment.cgi?id=82519&action=edit debugging output Can you attach a dmesg output with dpm enabled with this patch? -- You are receiving this ma

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #9 from Martin Andersson --- I just tried booting a second time and now experienced exactly the same behaviour as before the patch, that is the screen didn't get blank but continued to display the corrupted screen. Also looked at the

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #8 from Martin Andersson --- (In reply to comment #7) > Created attachment 82501 [details] [review] > add module parameter to disable aspm > > Try this patch which adds a new module parameter to disable aspm. Add > radeon.aspm=0 to

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #7 from Alex Deucher --- Created attachment 82501 --> https://bugs.freedesktop.org/attachment.cgi?id=82501&action=edit add module parameter to disable aspm Try this patch which adds a new module parameter to disable aspm. Add rade

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #6 from Alex Deucher --- (In reply to comment #5) > > Then I commented out: > ni_dpm_force_performance_level(rdev, RADEON_DPM_FORCED_LEVEL_AUTO); > That resulted in screen corruption but it worked when I instead commented > out: > i

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #10 from Alex Deucher --- Created attachment 82519 --> https://bugs.freedesktop.org/attachment.cgi?id=82519&action=edit debugging output Can you attach a dmesg output with dpm enabled with this patch? -- You are receiving this ma

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #5 from Martin Andersson --- (In reply to comment #4) > (In reply to comment #3) > > > > Well I think I'm already building radeon as a module since I have: > > CONFIG_DRM=m > > CONFIG_DRM_RADEON=m > > > > or am I missing something?

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #9 from Martin Andersson --- I just tried booting a second time and now experienced exactly the same behaviour as before the patch, that is the screen didn't get blank but continued to display the corrupted screen. Also looked at the

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #8 from Martin Andersson --- (In reply to comment #7) > Created attachment 82501 [details] [review] > add module parameter to disable aspm > > Try this patch which adds a new module parameter to disable aspm. Add > radeon.aspm=0 to

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #7 from Alex Deucher --- Created attachment 82501 --> https://bugs.freedesktop.org/attachment.cgi?id=82501&action=edit add module parameter to disable aspm Try this patch which adds a new module parameter to disable aspm. Add rade

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #6 from Alex Deucher --- (In reply to comment #5) > > Then I commented out: > ni_dpm_force_performance_level(rdev, RADEON_DPM_FORCED_LEVEL_AUTO); > That resulted in screen corruption but it worked when I instead commented > out: > i

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #4 from Alex Deucher --- (In reply to comment #3) > > Well I think I'm already building radeon as a module since I have: > CONFIG_DRM=m > CONFIG_DRM_RADEON=m > > or am I missing something? That should be fine. I assumed you were b

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #5 from Martin Andersson --- (In reply to comment #4) > (In reply to comment #3) > > > > Well I think I'm already building radeon as a module since I have: > > CONFIG_DRM=m > > CONFIG_DRM_RADEON=m > > > > or am I missing something?

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #4 from Alex Deucher --- (In reply to comment #3) > > Well I think I'm already building radeon as a module since I have: > CONFIG_DRM=m > CONFIG_DRM_RADEON=m > > or am I missing something? That should be fine. I assumed you were b

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #3 from Martin Andersson --- (In reply to comment #2) > (In reply to comment #0) > > > > I did a bisect and found that this commit introduced the corruption: > > > > http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3. >

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #2 from Alex Deucher --- (In reply to comment #0) > > I did a bisect and found that this commit introduced the corruption: > > http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3. > 11&id=7ad8d0687bb5030c3328bc7229a3183ce

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #3 from Martin Andersson --- (In reply to comment #2) > (In reply to comment #0) > > > > I did a bisect and found that this commit introduced the corruption: > > > > http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3. >

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #2 from Alex Deucher --- (In reply to comment #0) > > I did a bisect and found that this commit introduced the corruption: > > http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3. > 11&id=7ad8d0687bb5030c3328bc7229a3183ce

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #1 from Martin Andersson --- Created attachment 82449 --> https://bugs.freedesktop.org/attachment.cgi?id=82449&action=edit screenshot of corruption -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66932] Screen corruption on Cayman with dpm enabled

https://bugs.freedesktop.org/show_bug.cgi?id=66932 --- Comment #1 from Martin Andersson --- Created attachment 82449 --> https://bugs.freedesktop.org/attachment.cgi?id=82449&action=edit screenshot of corruption -- You are receiving this mail because: You are the assignee for the bug.