https://bugs.freedesktop.org/show_bug.cgi?id=57567
Priority: medium Bug ID: 57567 Assignee: dri-devel@lists.freedesktop.org Summary: 3.7 radeonfb broken on efivga screens Severity: normal Classification: Unclassified OS: All Reporter: bobahu4@gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI
Ubuntu 12.10 MacPro3,1
stock 3.5 kernel and 3.7-rcX ppa kernel
booting via efi with grub2
ati cards have broken framebuffer on 3.7 (all is fine on 3.5)
tried 2600xt, 6870, 6970 (all have efi part in rom, showing efi boot screen)
on 3.7, when radeonfb activates, I see for a moment two sides of screen (left and right) swapped (not mirrored), then(when X start) only very few lines on top of screen is actualy showing something(I can see part of mouse pointer there), rest is filled with one color.
Same result with all cards I mentioned.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #1 from Alex Deucher agd5f@yahoo.com --- Can you bisect? Please also attach your xorg log and dmesg output.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #2 from Vladimir bobahu4@gmail.com --- Created attachment 70606 --> https://bugs.freedesktop.org/attachment.cgi?id=70606&action=edit 3.5.0 dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #3 from Vladimir bobahu4@gmail.com --- Created attachment 70607 --> https://bugs.freedesktop.org/attachment.cgi?id=70607&action=edit 3.7 dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #4 from Vladimir bobahu4@gmail.com --- Created attachment 70608 --> https://bugs.freedesktop.org/attachment.cgi?id=70608&action=edit Xorg log on 3.5 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #5 from Vladimir bobahu4@gmail.com --- Created attachment 70609 --> https://bugs.freedesktop.org/attachment.cgi?id=70609&action=edit Xorg log on 3.7 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #6 from Vladimir bobahu4@gmail.com --- Added logs with 3.5 kernel (where it works fine) and 3.7 kernel
videocard - 6870, 1920x1080 display.
Video of what's happening - http://www.youtube.com/watch?v=-m3geT3RMXM&feature=g-upl
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #7 from Alexandre Demers alexandre.f.demers@gmail.com --- Could this be related to bug 56139? Description is similar to what is shown in recorded boot process videos.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #8 from Alexandre Demers alexandre.f.demers@gmail.com --- In fact, Vladimir, could you edit your grub entry and see if there is "set gfxpayload=keep". If so, change it to "set gfxpayload=text" or remove the line completely. If it solves your boot issue, this would be a start. Could you also test suspend/resume if it fixes your boot process?
From your posted video, I'm pretty sure this is what I also see in bug 56139.
You could check if the same commit shows up to be the culprit.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #9 from Vladimir bobahu4@gmail.com --- I disabled that line (here it was inside a function) before commiting this bug, due to another, probably ubuntu-specific bug - https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069452
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #10 from Vladimir bobahu4@gmail.com --- Some news which makes it easier to isolate the bug
ubuntu updated kernel to 3.5.0-22 and bug appeared on this kernel 3.5.0-21 - no bug
looks like they added some upstream changes.
here is list of changes 21 to 22 from their deb pkg for kernel - http://pastebin.com/4uUWUtLV
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #11 from Alex Deucher agd5f@yahoo.com --- this looks like it may be a duplicate of bug 59431.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #12 from Vladimir bobahu4@gmail.com --- I found the exact commit that causes this bug
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=commit;h=8f53b544...
drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2)
BugLink: http://bugs.launchpad.net/bugs/1091251
commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 upstream.
- Stop the displays from accessing the FB - Block CPU access - Turn off MC client access
This should fix issues some users have seen, especially with UEFI, when changing the MC FB location that result in hangs or display corruption.
v2: fix crtc enabled check noticed by Luca Tettamanti
Signed-off-by: Alex Deucher alexander.deucher@amd.com [ herton: adjust context ] Signed-off-by: Herton Ronaldo Krzesinski herton.krzesinski@canonical.com
Hope you guys can fix it
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alexandre Demers alexandre.f.demers@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=55692, | |https://bugs.freedesktop.or | |g/show_bug.cgi?id=56139
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alexandre Demers alexandre.f.demers@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.freedesktop.or | |g/show_bug.cgi?id=55692 |
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #13 from Alex Deucher agd5f@yahoo.com --- Does this patch help? http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=bb58...
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #14 from Vladimir bobahu4@gmail.com --- No, that doesn't fix it. still the same
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #15 from Alex Deucher agd5f@yahoo.com --- Does adding: udelay(100); at the end of evergreen_mc_stop() help?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #16 from Vladimir bobahu4@gmail.com --- didn't help either
btw, reverting that commit(62444b7462a2b98bc78d68736c03a7c4e66ba7e2) fixed 3.8-rc5 for me. finally ogl 3.0 :D
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Florian Mickler florian@mickler.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |florian@mickler.org
--- Comment #17 from Florian Mickler florian@mickler.org --- A patch referencing this bug report has been merged in Linux v3.8-rc7:
commit ed39fadd6df01095378e499fac3674883f16b853 Author: Alex Deucher alexander.deucher@amd.com Date: Thu Jan 31 09:00:52 2013 -0500
drm/radeon/evergreen+: wait for the MC to settle after MC blackout
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #18 from Vladimir bobahu4@gmail.com --- That patch didn't help ass I wrote earlier.
The only thing that helps 3.7/3.8 kernel is reverting 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 commit
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #19 from Alex Deucher agd5f@yahoo.com --- Created attachment 77383 --> https://bugs.freedesktop.org/attachment.cgi?id=77383&action=edit possible fix
Does this kernel patch (against 3.9) help?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alexandre Demers alexandre.f.demers@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=43655
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #20 from Vladimir bobahu4@gmail.com --- Created attachment 77406 --> https://bugs.freedesktop.org/attachment.cgi?id=77406&action=edit new dmesg with drm.debug=14
It's a little bit better now, framebuffer is always shifted. (previously framebuffer usualy was lost, or messed up). it's 3.9-rc5 + patch
I've also tried 3.8.5+patch, and saw no difference to just 3.8.5, just saying.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #21 from Vladimir bobahu4@gmail.com --- Created attachment 77407 --> https://bugs.freedesktop.org/attachment.cgi?id=77407&action=edit screenshot of 3.9
screenshot of what happens
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77407|text/plain |image/jpeg mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #22 from Vladimir bobahu4@gmail.com --- I've just tested vanilla 3.9-rc5, to be sure that it's actually your patch that make things a little bit better, not 3.9 kernel itself.
unpatched 3.9-rc5 - same ersult as 3.7/3.8 kernel, so yeah, it's definetly a patch.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #23 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #21)
Created attachment 77407 [details] screenshot of 3.9
screenshot of what happens
I don't have a picture as neat as yours. I also saw a change in the display, but my display is flickering after the first few vertical lines (only the first few lines are stable, but they are still shifted as in your screenshot).
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77383|0 |1 is obsolete| |
--- Comment #24 from Alex Deucher agd5f@yahoo.com --- Created attachment 77441 --> https://bugs.freedesktop.org/attachment.cgi?id=77441&action=edit updated patch
Does this patch work any better?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #25 from Vladimir bobahu4@gmail.com --- I have strange results
few notes first, 3.8-ati is 3.8.5 kernel + reverted 62444b7462a2b98bc78d68736c03a7c4e66ba7e2
3.9-rc5_patched is 3.9-rc5 with your latest patch
3.8 - ubuntu vanilla 3.8.5
so, here is all results:
1) cold boot, boot 3.9-rc5_patched - same screen as with 3.8 (bad) 2) boot macosx, reboot, boot 3.9-rc5_patched - same screen as with 3.8 3) boot 3.8-ati, reboot, boot 3.9-rc5_patched - result like on previous screenshot I've posted, horizontal shift is always different
I didnt test 3.9 with your first patch with all cases.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #26 from Vladimir bobahu4@gmail.com --- Ah, and without patch it is always same as with 3.8. So patch matters.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77441|0 |1 is obsolete| |
--- Comment #27 from Alex Deucher agd5f@yahoo.com --- Created attachment 77602 --> https://bugs.freedesktop.org/attachment.cgi?id=77602&action=edit updated patch
Does this variant work any better?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #28 from Vladimir bobahu4@gmail.com --- Created attachment 77625 --> https://bugs.freedesktop.org/attachment.cgi?id=77625&action=edit New screenshot
It actually became worse, hard to replicate scenario with shifted screen(most of time looks like 3.8), and then it panics on reboot. Sshot of panic attached.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77602|0 |1 is obsolete| |
--- Comment #29 from Alex Deucher agd5f@yahoo.com --- Created attachment 77705 --> https://bugs.freedesktop.org/attachment.cgi?id=77705&action=edit possible fix
Does this patch help?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #30 from Alex Deucher agd5f@yahoo.com --- Created attachment 77706 --> https://bugs.freedesktop.org/attachment.cgi?id=77706&action=edit additional fix
Apply this along with attachment 77705.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #31 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #30)
Created attachment 77706 [details] [review] additional fix
Apply this along with attachment 77705 [details] [review].
Using a Cayman 6950 with both patches didn't help over here. Tried two times, two times where the screen was shifted (like in Vladimir's screenshot). First time flickering, second only shifted.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #32 from Alex Deucher agd5f@yahoo.com --- Created attachment 77743 --> https://bugs.freedesktop.org/attachment.cgi?id=77743&action=edit additional fix
Try this one in addition to the previous two (apply all 3).
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #33 from Vladimir bobahu4@gmail.com --- Tried all three patches, still same, shifted after 3.8-ati reboot.
and same as 3.8 after cold start.
btw, am I supposed to apply it against 3.9-rc5 or 3.9-rc6, or it doesn't matter ?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #34 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #33)
btw, am I supposed to apply it against 3.9-rc5 or 3.9-rc6, or it doesn't matter ?
Doesn't matter.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #35 from Alex Deucher agd5f@yahoo.com --- Are there any "frame never updated!" messages in your dmesg with the patches applied?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #36 from Vladimir bobahu4@gmail.com --- Created attachment 77761 --> https://bugs.freedesktop.org/attachment.cgi?id=77761&action=edit dmesg with 3 patches
Looks like there is none.
dmesg from boot with sshifted screen.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #37 from Alex Deucher agd5f@yahoo.com --- When the display is shifted, does a dpms cycle fix it?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #38 from Vladimir bobahu4@gmail.com --- How to do dpms cycle ?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #39 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #38)
How to do dpms cycle ?
On the console, just wait for the screen to blank. In X: xset dpms force off will force a dpms cycle.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #40 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #39)
(In reply to comment #38)
How to do dpms cycle ?
On the console, just wait for the screen to blank. In X: xset dpms force off will force a dpms cycle.
That would valid if we were able to log in X. Is there a way to do it if we are still in the console?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #41 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #40)
(In reply to comment #39)
(In reply to comment #38)
How to do dpms cycle ?
On the console, just wait for the screen to blank. In X: xset dpms force off will force a dpms cycle.
That would valid if we were able to log in X. Is there a way to do it if we are still in the console?
I think you can adjust the console blanking with setterm. Can you start X and force a dpms cycle even if the screen is garbled?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #42 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #41)
(In reply to comment #40)
(In reply to comment #39)
(In reply to comment #38)
How to do dpms cycle ?
On the console, just wait for the screen to blank. In X: xset dpms force off will force a dpms cycle.
That would valid if we were able to log in X. Is there a way to do it if we are still in the console?
I think you can adjust the console blanking with setterm. Can you start X and force a dpms cycle even if the screen is garbled?
X starts, but I'm never getting to the log screen. Once X is started, if I go into console and come back, only my mouse pointer is being displayed correctly, the background stays as what was in the console. I suppose something is hanging or crashing X.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #43 from Vladimir bobahu4@gmail.com --- Exactly same happens here
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #44 from Alex Deucher agd5f@yahoo.com --- Does disabling acceleration help?
Option "NoAccel" "True"
In the device section of you xorg.conf
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #45 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #44)
Does disabling acceleration help?
Option "NoAccel" "True"
In the device section of you xorg.conf
I was able to log in, launch "xset dpms force off". My screen turned off. After waking it up, the display was still shifted.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #46 from Alex Deucher agd5f@yahoo.com --- Created attachment 77808 --> https://bugs.freedesktop.org/attachment.cgi?id=77808&action=edit temporary workaround
Apply this on top of the previous patches. It's a hack to workaround the issue until I can sort out what is going on with the hw guys.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #47 from Vladimir bobahu4@gmail.com --- That works.
Will any of these four patches land in 3.9 kernel ?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #48 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #47)
That works.
Will any of these four patches land in 3.9 kernel ?
Possibly. I'm hoping to get hear back from the hw guys early next week to see if I can get teh existing code to work as it's supposed to. If not, I'll just send these patches upstream for now. If they don't make 3.9 final, they'll show up via the stable kernel stream.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #49 from Alexandre Demers alexandre.f.demers@gmail.com --- Vladimir, do you see a page fault in your dmesg after applying the four patches? Something that would look like: [ 8.727726] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041000 flags=0x0010] [ 8.727737] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800042400 flags=0x0010] [ 8.727750] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041040 flags=0x0010] [ 8.727753] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041080 flags=0x0010] [ 8.727756] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041240 flags=0x0010] [ 8.727759] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f8000410c0 flags=0x0010] [ 8.727762] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041280 flags=0x0010] [ 8.727764] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041100 flags=0x0010] [ 8.727767] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f8000412c0 flags=0x0010] [ 8.727770] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0016 address=0x000000f800041140 flags=0x0010]
Alex, is this expected for the workaround?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #50 from Alexandre Demers alexandre.f.demers@gmail.com --- Created attachment 77915 --> https://bugs.freedesktop.org/attachment.cgi?id=77915&action=edit Page Fault with four patches applied
AMD-Vi -> IO PAGE FAULTS in dmesg when using 3.9-rc6 with the four patches applied (77705, 77706, 77743, 77808).
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #51 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #49)
Alex, is this expected for the workaround?
No. So it appears turning off the displays doesn't help either :/
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #52 from Vladimir bobahu4@gmail.com --- I don't have these messages, all is quiet here with 3.9-rc5 + 4 patches.
6870
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #53 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #51)
(In reply to comment #49)
Alex, is this expected for the workaround?
No. So it appears turning off the displays doesn't help either :/
Well, it does help: the screen switches from GRUB to kernel correctly set (displaying the console), then the screen flashes for a moment (one white flash instead of one blue flash when the reported bug happens), comes back to normal in console (where there is now the AMD-Vi IO PAGE FAULT messages) and continues to work even after Xorg is started.
A difference between Vladimir and I is we don't have the same video card (6950 over here).
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #54 from Vladimir bobahu4@gmail.com --- Just tested with 6970, still fine, no AMD-Vi messages in dmesg.
I have gfxmode/gfxpayload commented out from grub.cfg, maybe that's the difference between your and mine setups.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #55 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #54)
Just tested with 6970, still fine, no AMD-Vi messages in dmesg.
I have gfxmode/gfxpayload commented out from grub.cfg, maybe that's the difference between your and mine setups.
Maybe, I'll test it later then. After all, I do have gfxmode and gxpayload used in my grub.cfg.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #56 from Vladimir bobahu4@gmail.com --- I have a panic back on reboot tho, same as in https://bugs.freedesktop.org/attachment.cgi?id=77625
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #57 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #55)
(In reply to comment #54)
Just tested with 6970, still fine, no AMD-Vi messages in dmesg.
I have gfxmode/gfxpayload commented out from grub.cfg, maybe that's the difference between your and mine setups.
Maybe, I'll test it later then. After all, I do have gfxmode and gxpayload used in my grub.cfg.
Even with gfxpayload=text (which is working correctly without all the patches), I still have the AMD-Vi IO PAGE FAULT messages.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77808|0 |1 is obsolete| |
--- Comment #58 from Alex Deucher agd5f@yahoo.com --- Created attachment 77999 --> https://bugs.freedesktop.org/attachment.cgi?id=77999&action=edit temporary workaround v2
Try this patch as a replacement for attachment 77808. Do you still get the iommu errors?
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77999|0 |1 is obsolete| |
--- Comment #59 from Alex Deucher agd5f@yahoo.com --- Created attachment 78000 --> https://bugs.freedesktop.org/attachment.cgi?id=78000&action=edit temporary workaround v3
argh. typo in that one. try this one as a replacement instead.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #60 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #59)
Created attachment 78000 [details] [review] temporary workaround v3
argh. typo in that one. try this one as a replacement instead.
After fixing the patch (it was not applying correctly on the previous three patches 77705, 77706 and 77743) and recompiling, it seems to fix the error.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #77706|0 |1 is obsolete| |
--- Comment #61 from Alex Deucher agd5f@yahoo.com --- Created attachment 78081 --> https://bugs.freedesktop.org/attachment.cgi?id=78081&action=edit one more test
One more thing to try. Can you try this patch on top of the previous patches (attachment 77705, attachment 77743, attachment 78000).
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #62 from Alex Deucher agd5f@yahoo.com --- Created attachment 78090 --> https://bugs.freedesktop.org/attachment.cgi?id=78090&action=edit another test
Please also try this patch on top of only attachment 77705. No other patches.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #63 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to comment #62)
Created attachment 78090 [details] [review] another test
Please also try this patch on top of only attachment 77705 [details] [review]. No other patches.
Both patches don't fix anything over here. They do pretty much as if nothing was applied.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #64 from Alexandre Demers alexandre.f.demers@gmail.com --- Any of the patchs pushed in drm-next? I've been playing with drm-next since yesterday and display is running fine when setting GRUB_GFXPAYLOAD_LINUX=keep at GRUB's launch.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #65 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #64)
Any of the patchs pushed in drm-next? I've been playing with drm-next since yesterday and display is running fine when setting GRUB_GFXPAYLOAD_LINUX=keep at GRUB's launch.
Yes.
https://bugs.freedesktop.org/show_bug.cgi?id=57567
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #66 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/314.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org