Originally posted by bridgman
View Post
Announcement
Collapse
No announcement yet.
Linux 4.18 AMDGPU Tests: Vega Taking A Hit
Collapse
X
-
Originally posted by shmerl View Post
I see. So in practice there is no regression testing at all, or there is "the best we can do" effort?
- Likes 6
Comment
-
If you are having issues with DP, please try this patch:
- Likes 1
Comment
-
Have 4.18-rc4 and a RX480 RX580-tified with bios mod.
Work with 3 DP monitor (HD/4K/HD)
Problems :
* I can turn one or two monitors OFF and turn them back on, it's fine. If I turn the three monitors off, system is alive until I turn them back on then crash.
* Sleep "work" but system crash when I wake it. Might be another Ryzen/stupid motherboard BIOS related issue
Workaround for crash on all screens OFF : I can CTRL-ALT-F1 to text tty, then turn the screens off... then on then I can switch back to X then it's still alive, most of the time.Last edited by RavFX; 10 July 2018, 03:11 PM.
Comment
-
Originally posted by bridgman View PostDisplay testing is actually one of the hardest areas to automate because you either need custom hardware analyzing signals or a custom rig with a camera looking at the display and figuring if the viewed image is "sufficiently close" in all the noise & pixel mismatch.
- Likes 1
Comment
-
Originally posted by RavFX View PostHave 4.18-rc4 and a RX480 RX580-tified with bios mod.
* Sleep "work" but system crash when I wake it. Might be another Ryzen/stupid motherboard BIOS related issue
Workaround for crash on all screens OFF : I can CTRL-ALT-F1 to text tty, then turn the screens off... then on then I can switch back to X then it's still alive, most of the time.
I never thought I would use the "chvt" command so often... and a script like
/usr/bin/openvt -c 12 -f -s -w -- vlock -a
to lock the screen :-(
Comment
-
Originally posted by dwagner View PostFor bugs of what is displayed - sure. But bugs causing system crashes or no image displayed at all should be possible to detect automatically. And sysfs has rtc/rtc0/wakealarm to allow for automated wakeup-after-some-seconds from S3.
Were you thinking about checking page-flip interrupts or is there something else I missed ?Last edited by bridgman; 10 July 2018, 07:03 PM.Test signature
Comment
-
Originally posted by bridgman View Post
System crashes definitely - a watchdog timer can pick that up - but AFAIK "no image displayed at all" is harder because there can frequently still be an image being sent out and page-flip interrupts being generated - it just isn't an image that the display chooses to accept.
If the goal is to identify "no image displayed at all", why would it take anything more than sending a bright test image to the screen and then checking whether the overall result is bright or dark using an external camera? (After all. I've never seen less than 3/4 of the screen be black when a monitor is keeping the backlight on to display an "Out of Range" or "No Signal" popup.)
I don't see why, in a pinch, a proof-of-concept for such an integration test couldn't be concocted using:- A $10 LCD monitor from a thrift-store with visible scratches marring the image (any model with a suitable sync range)
- A cardboard box or some kind of scrap black-out curtain to isolate from variations in external lighting.
- Any sub-$10 Chinese USB webcam which will obey manual exposure settings specified through v4l2 and the USB Video Class driver.
- A test case which captures a frame with predefined exposure settings, takes the arithmetic mean of the pixels, and considers success to be "the result is above a certain threshold".
Last edited by ssokolow; 10 July 2018, 08:40 PM.
Comment
Comment