Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
igt@fbdev@pan - fail - Failed assertion: ret == expected_ret, No space left on device, ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0
Starting subtest: pan(fbdev:7376) CRITICAL: Test assertion failure function pan_test, file ../tests/fbdev.c:65:(fbdev:7376) CRITICAL: Failed assertion: ret == expected_ret(fbdev:7376) CRITICAL: Last errno: 28, No space left on device(fbdev:7376) CRITICAL: ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0Subtest pan failed.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
The CI Bug Log issue associated to this bug has been updated by Lakshmi Vudum.
New filters associated
ILK SNB GEN9 ICL TGL: igt@fbdev@pan - fail - Failed assertion: ret == expected_ret, No space left on device, ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0
Sadly no 0x10 in drm.debug so couldn't immediately see what's going on. But I managed to reproduce locally by having two different sized displays plugged in.
It's a bug in drm_fb_helper. xres/yres will be based on the smallest display whereas fb/xres_virtual/yres_virtual will be based on the largest display. res < res_virtual is telling the pan test that it can actually pan, which is not true since the largest display already eats up the whole framebuffer. The fix would involve making drm_fb_helper not lie about the virtual resolution we can actually use.
A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:
Description: ADL_P: igt@fbdev@pan - fail - Failed assertion: ret == expected_ret, Last errno: 22, Invalid argument, ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["re-adlp-pub3", "re-adlp-pub2", "re-adlp-5", "re-adlp-11", "bat-adlp-4", "bat-adlp-6", "re-adlp-pub1"] OR machine_tag IS IN ["ADL-P"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@fbdev@pan"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: ret == expected_ret\n.*Last errno: 22, Invalid argument\n.*ioctl\(FBIOPAN_DISPLAY\) returned ret=-1, expected 0'
A CI Bug Log filter associated to this bug has been updated by :
Description: ADL_P ADL_M: igt@fbdev@pan - fail - Failed assertion: ret == expected_ret, ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["re-adlp-pub3", "re-adlp-pub2", "re-adlp-5", "re-adlm", "re-adlp-11", "bat-adlp-4", "bat-adlp-6", "re-adlp-pub1"] OR machine_tag IS IN ["ADL-M", "ADL-P"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@fbdev@pan"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: ret == expected_ret\n.*\n.*ioctl\(FBIOPAN_DISPLAY\) returned ret=-1, expected 0'