Bug 91197

Summary: Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck executing BF64
Product: DRI Reporter: dennis.jansen
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
lspci
none
dmesg 4.1
none
Xorg log
none
vbios.rom
none
dmesg 4.1+drm-next boot only
none
dmesg 4.1+daily boot and vt switch and xrandr try
none
dmesg
none
vbios.rom
none
Xorg.log none

Description dennis.jansen 2015-07-02 18:05:44 UTC
I have several issues trying to connect a 4k display to the radeon card via HDMI (@30Hz). If I boot with the screen connected, when trying to take over modesetting from EFI, the internal notebook display goes black as well as the external.

When I try to attach it during runtime, I can see the 3840 mode, but when I tryt to select it I get 
[   97.667521] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
[   97.667549] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BF64 (len 962, WS 0, PS 0) @ 0xC1A1

Switching back to 1920 works fine, trying again simply causes the same error again. Tested Linux kernels 4.1.0 and 3.19. Ubuntu 15.04.

I might not be able to test for long, will probably send the screen back before long if I can't get it working in full resolution at all.
Comment 1 dennis.jansen 2015-07-02 18:06:44 UTC
Created attachment 116883 [details]
lspci
Comment 2 dennis.jansen 2015-07-02 18:07:56 UTC
Created attachment 116884 [details]
dmesg 4.1
Comment 3 Alex Deucher 2015-07-02 18:09:45 UTC
Please attach your xorg log.
Comment 4 Alex Deucher 2015-07-02 18:10:41 UTC
Please also attach a copy of your vbios:

(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom
Comment 5 dennis.jansen 2015-07-02 18:11:08 UTC
Created attachment 116885 [details]
Xorg log
Comment 6 dennis.jansen 2015-07-02 18:13:15 UTC
Created attachment 116886 [details]
vbios.rom
Comment 7 dennis.jansen 2015-07-02 18:14:23 UTC
I'll try linux-drm-next real quick, brb.
Comment 8 dennis.jansen 2015-07-02 18:28:12 UTC
Same issue in linux-drm-next and linux-daily from the Ubuntu repositories.
Comment 9 dennis.jansen 2015-07-02 18:29:16 UTC
Created attachment 116889 [details]
dmesg 4.1+drm-next boot only
Comment 10 dennis.jansen 2015-07-02 18:30:24 UTC
Created attachment 116890 [details]
dmesg 4.1+daily boot and vt switch and xrandr try
Comment 11 dennis.jansen 2015-07-06 14:23:19 UTC
I've found a workaround:

xrandr --newmode "3840x2160_30"   262.92   3840 3888 3920 4000   2160 2163 2168 2191  +hsync 
xrandr --addmode HDMI-0 "3840x2160_30"
xrandr --output HDMI-0 --mode 3840x2160_30

I'm guessing the pixel clock might have been too high. Same problem with the Windows driver. The page (http://www.epanorama.net/faq/vga2rgb/calc.html) allowed me to convert the modeline with lower clock created with cru (http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU) in Windows to Linux. I was pleasantly surprised to find even vdpau working well, of course only up to FullHD video, but smooth playback on 4k resolution.
Comment 12 NeverMind 2015-07-18 12:27:37 UTC
Created attachment 117226 [details]
dmesg

Same bug with Radeon HD 8370D
Comment 13 NeverMind 2015-07-18 12:28:18 UTC
Created attachment 117227 [details]
vbios.rom

Same bug with Radeon HD 8370D
Comment 14 NeverMind 2015-07-18 12:30:16 UTC
Created attachment 117228 [details]
Xorg.log

Same bug with Radeon HD 8370D
Comment 15 NeverMind 2015-08-21 15:22:25 UTC
Since the last update this bug no longer occur
Comment 16 dennis.jansen 2016-02-07 17:14:49 UTC
(In reply to NeverMind from comment #15)
> Since the last update this bug no longer occur

Could you clarify? What was updated? How was it fixed? 
Because the bug is still present for me in 4.2.
If it was fixed for you, maybe you had a different bug. As this is the bug I've created, I'm reopening it.
Comment 17 dennis.jansen 2016-02-07 17:16:40 UTC
Update: I get the BF64 error each time I switch between X and console. So it takes about 5 seconds each time. I still have to manually had modes to get 4k to work.
Comment 18 Martin Peres 2019-11-19 09:06:57 UTC
-- 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/627.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.