-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pi4 hard crash with FKMS and 4k60 (4096x2160-60) #4271
Comments
also, I'm getting this in dmesg: |
seems like it doesn't always completely crash the hardware just lock the current DRM opening app. When it doesn't crash the hardware I was able to ssh in and check the log, and got this further detail: [ 98.998235] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] ERROR [CRTC:87:crtc-0] flip_done timed out in this situation killing the stuck app doesn't bring video back so a reboot is stilll required, but at least it's not a hard power cord pull. |
tested with 922deae6d1ff141d53cf9e703ffecd6f994e9d4e (newest firmware), same problem. |
All rpi-update releases are logged in https://github.com/Hexxeh/rpi-firmware/commits/master If you could narrow down the release that causes the issue it would be useful. |
test: modetest -s 89:4096x2160 [ 189.432092] raspberrypi-firmware soc:firmware: Request 0x00048015 returned status 0x80000001 |
I went back to 8c2ba64b27a4b6a1dfcd114203c6309f766e2ef4 which I thought had been working perfectly, producing video output at 4096' but it seems my memory is wrong, as it runs but doesn't produce an image my tv can detect. it definitely doesn't lock up though. 3840' is fine (video output and no lock), in all these versions of the firmware. There is definitely some kind of bug here as the locking up and dmesg stack traces reveal. But perhaps it has to do with something unusual about my TV (XBR43X800D) when trying to start up 4096'. here's the regular suspects: root@raspberrypi:~# edidparser edid root@raspberrypi:~# modetest | grep '#' |
fyi I had a chance to test the latest firmware with another 4k tv (tcl 50S423) and it also hard crashes modetest and/or locks up the pi4 when I run modetest -s 89:4096x2160. So this isn't limited to one tv. here's the edid from this tv as well: HDMI:EDID version 1.3, 1 extensions, screen size 111x62 cm and dmesg from when it just crashes modetest opposed to locking the hardware: [ 570.203953] raspberrypi-firmware soc:firmware: Request 0x00048015 returned status 0x80000001 |
binary copy of edid's uploaded to #3842 |
Add core_freq=600 to /boot/config.txt and selecting 4096x2160@60 works, no crashes (tested about 5x times). probably needs to be documented somewhere before it makes sense to call this one "closed". |
I believe this issue was resolved in #5038 |
rpi-update'ing to the latest firmware (acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31), I can get a hard crash (have to unplug the power to reset) using the official modetest:
modetest -s 89:4096x2160-60
much older versions of the firmware (January?) did not crash with this command, but the problem was also observed with the current firmware of last week (since rpi-update has no log I can't say which exact release that was).
modetest -s 89:4096x2160-50 works with the current firmware.
modetest -s 89:3840x2160-60 also works.
it's a shame because this new firmware is better otherwise - less tearing.
The text was updated successfully, but these errors were encountered: