Created attachment 133315 [details] dmesg log The following test cases fail on GLK with latest configuration, these test cases take more than ten minutes and sometimes they never finish of execute. ====================================== Test list ====================================== igt@gem_exec_alignment@many ====================================== Software ====================================== kernel version : 4.13.0-rc3-drm-tip-ww31-commit-372e2eb+ /bin/bash: gfx-desktop: command not found architecture : x86_64 os version : Ubuntu 16.10 os codename : yakkety [sudo] password for gfx: kernel driver : i915 bios revision : 52.23 bios release date : 06/24/2017 ksc : 1.36 hardware acceleration : disabled swap partition : enabled on (/dev/sda3) ====================================== Graphic drivers ====================================== modesetting : enabled modesetting compiled for : 1.18.4 X.Org Video Driver xorg-xserver : 1.18.4 libdrm : 2.4.82 cairo : 1.15.7 intel-gpu-tools (tag) : intel-gpu-tools-1.19-126-g6e1ccfa intel-gpu-tools (commit) : 6e1ccfa ====================================== Hardware ====================================== platform : Geminilake motherboard model : Geminilake motherboard id : GLKRVP1DDR4(05) form factor : Hand Held manufacturer : IntelCorp. cpu family : Other cpu family id : 6 cpu information : Genuine Intel(R) CPU @ 1.10GHz gpu card : Intel Corporation Device 3184 (rev 01) (prog-if 00 [VGA controller]) memory ram : 7.6 GB max memory ram : 16 GB cpu thread : 4 cpu core : 4 cpu model : 122 cpu stepping : 0 socket : Other hard drive : 111GiB (120GB) current cd clock frequency : 79200 kHz maximum cd clock frequency : 316800 kHz displays connected : eDP-1 ====================================== Firmware ====================================== dmc fw loaded : yes dmc version : 1.4 guc fw loaded : SUCCESS guc version wanted : 10.56 guc version found : 10.56 huc fw loaded : yes ====================================== kernel parameters ====================================== quiet splash drm.debug=0x1e log_buf_len=4M i915.alpha_support=1 i915.enable_guc_submission=2 i915.enable_guc_loading=2
Created attachment 133316 [details] kernel log
Created attachment 133317 [details] test log
Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included
After testing and research from our QA team, it was found that the specific config file from FI that was being used to compile the kernel, had a lot of disable parameters to improve performance while running IGT. The problem was that some of those parameters were required to use the firmware effectively. It was agreed to use a generic config file from kernel.org. This test are now passed with the attached kernel and the last configuration known: Gfx stack ===================================================== Component: drm tag: libdrm-2.4.81-46-g9d133dd commit: 9d133dd08720d80dfc8ce098bf0972ebd05c454d Component: cairo tag: 1.15.6-14-gf351595 commit: f3515954e0bc9c9ca413a84a8dd842145cec83a7 Component: intel-gpu-tools tag: intel-gpu-tools-1.19-193-g5a17ee2 commit: 5a17ee2c8f9013f5db852d27564b837f9f2c5a9f Component: piglit tag: piglit-v1 commit: 2a7047a32bb3a9a4fad5bea0a8185d63af6bddf3 Kernel info ===================================================== commit ad6ab9f96437f0cb1f4d8a7840fd9eeb894eb12e Author: Gustavo Padovan <gustavo.padovan@collabora.com> AuthorDate: Fri Aug 18 15:26:42 2017 -0300 Commit: Gustavo Padovan <gustavo.padovan@collabora.com> CommitDate: Fri Aug 18 15:26:42 2017 -0300 drm-tip: 2017y-08m-18d-18h-21m-46s UTC integration manifest
Created attachment 133685 [details] debug.conf
(In reply to Elizabeth from comment #4) > Created attachment 133682 [details] > debug.conf > ... This test are > now passed with the attached kernel and the last configuration known... This test still are failing but with a different issue, they will be tested again and if needed a new bug will be open. Thanks.
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.