Reproduced with kernel testing tag drm-intel-testing-2016-01-24

On BXT, this is correct because the firmware is only for SKL. The fw loading will be skipped on BXT and submission is fallback to ExecList mode. BXT fw is not available yet on 01.org.

On SKL, could you provide more information? Such as what files look like in your system folder /lib/firmware/i915. Is there a kernel dmesg log?

Could you post the full message of running commands:

cat /sys/kernel/debug/dri/0/i915_guc_load_status 
cat /sys/kernel/debug/dri/0/i915_guc_info

Created attachment 121307 [details]
i915_guc_info_bxt

Created attachment 121308 [details]
i915_guc_info_skl

Created attachment 121309 [details]
i915_guc_load_stat_skl

Created attachment 121310 [details]
i915_guc_load_status_bxt

Thanks for the log. The only case this happens is that patch http://patchwork.freedesktop.org/patch/69500/ is not applied properly. I noticed that in Pre-conditions, it is applied to BXT. Is this done for SKL as well? Is there a link of this kernel I can try it?

Created attachment 121354 [details]
i915 dmesg log

I attach the dmesg log.

Thanks for the dmsg. Again, this was from BXT. As I said, this is currently not enabled for BXT.

I believe the patches mentioned here are not applied for SKL. Please double check and collect debug info from SKL system.

I installed this kernel on my SKL system. It looks like everything works fine. This is so confused to me.

root@alexSkylake:/sys/kernel/debug/dri/0# uname -a
Linux alexSkylake 4.4.0-drm-intel-nightly-bxt-guc+ #3 SMP PREEMPT Mon Jan 25 18:00:09 CET 2016 x86_64 x86_64 x86_64 GNU/Linux
root@alexSkylake:/sys/kernel/debug/dri/0# cat i915_guc_load_status
GuC firmware status:
    path: i915/skl_guc_ver4.bin
    fetch: SUCCESS
    load: SUCCESS
    version wanted: 4.3
    version found: 4.3
    header: offset is 0; size = 128
    uCode: offset is 128; size = 127936
    RSA: offset is 128064; size = 256

GuC status 0x800330ec:
    Bootrom status = 0x76
    uKernel status = 0x30
    MIA Core status = 0x3

Scratch registers:
     0:     0xf0000000
     1:     0x3
     2:     0x0
     3:     0x5f5e100
     4:     0x600
     5:     0x0
     6:     0x0
     7:     0x8
     8:     0x3
     9:     0x430200
    10:     0x0
    11:     0x0
    12:     0x0
    13:     0x0
    14:     0x0
    15:     0x0

In dmesg, on my system I see command line option with "BOOT_IMAGE=/boot/vmlinuz-4.4.0-drm-intel-nightly-bxt-guc+". But in the version attached here it is "vmlinuz-4.4.0-bxt-guc". Does this make any different?

alex@alexSkylake:~/intel-gpu-tools/tests$ dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-drm-intel-nightly-bxt-guc+ (oberthierx@VANAHEIMR) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ) #3 SMP PREEMPT Mon Jan 25 18:00:09 CET 2016
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-drm-intel-nightly-bxt-guc+ root=UUID=df4be8cc-29b5-421a-861c-d507a91dd6cb ro noprompt persistent quiet splash vt.handoff=7

Created attachment 121394 [details]
dmesg log file for SKL

On broxton the files initrd and vmlinuz are manualy copied on the EFI partition, sometimes we use a customized name, I don't think this make a difference.

I attach a dmesg captured on SKL Y with the same kernel.

The installed GUC is the one from 01.org :
Release Date: 23 Jul, 2015
Version: ver4_3

Thanks. This helps.

[    3.805335] [drm:intel_guc_ucode_init] GuC firmware pending, path i915/skl_guc_ver4.bin
[    3.805337] [drm:guc_fw_fetch] before requesting firmware: GuC fw fetch status PENDING
[    3.805477] i915 0000:00:02.0: Direct firmware load for i915/skl_guc_ver4.bin failed with error -2
[    3.805497] [drm:guc_fw_fetch] GuC fw fetch status FAIL; err -2, fw           (null), obj           (null)
[    3.805548] [drm:intel_guc_ucode_init [i915]] *ERROR* Failed to fetch GuC firmware from i915/skl_guc_ver4.bin (error -2)

The "Direct firmware load" failure means kernel does not find it in file system. Can you check if fw is installed correctly? It should be in /lib/firmware/i915/. A symbolic link of skl_guc_ver4.bin should link to skl_guc_v4_3.bin.

Maybe you can try "dpkg-reconfigure linux-image-4.4.0-drm-intel-nightly-bxt-guc+". Whenever I updated the fw, I run dpkg-reconfigure to make sure the fw is built into kernel image.

Thanks, this resolve the problem.
The symbolic link and the md5sum were correct, but after reconfiguring the kernel the guc is correctly loaded :

# cat /sys/kernel/debug/dri/0/i915_guc_load_status 
GuC firmware status:
        path: i915/skl_guc_ver4.bin
        fetch: SUCCESS
        load: SUCCESS
        version wanted: 4.3
        version found: 4.3
        header: offset is 0; size = 128
        uCode: offset is 128; size = 127936
        RSA: offset is 128064; size = 256

GuC status 0x800330ec:
        Bootrom status = 0x76
        uKernel status = 0x30
        MIA Core status = 0x3

Scratch registers:
         0:     0xf0000000
         1:     0x3
         2:     0x0
         3:     0x5f5e100
         4:     0x600
         5:     0x0
         6:     0x0
         7:     0x8
         8:     0x3
         9:     0xd1a00
        10:     0x0
        11:     0x0
        12:     0x0
        13:     0x0
        14:     0x0
        15:     0x0

Works on SKL. We will track the feature for BXT.

Created attachment 121650 [details]
guc 4.3 package with install.sh updated

I've updated the install script to make sure the initrd/initramfs is updated.
Could you please help me by giving a try on this new install script and let me know if it works so I will be able to update the official one at 01.org.

Thanks,
Rodrigo.

Assign to me, I will try it

Perfect timing then! ;)

hm... best way to test this new script in your case is running:
$ sudo rm -rf /lib/firmware/i915/skl_guc_ver4_3.bin 
$ sudo touch /lib/firmware/i915/skl_guc_ver4_2.bin
$ sudo ln -sf /lib/firmware/i915/skl_guc_ver4_2.bin /lib/firmware/i915/skl_guc_ver4.bin 
$ dpkg-reconfigure #with the options you used.

So by this point we would fake an old one is there in your initrd.

Then run this new install script. The output from command line needs to show you it created a backup initrd and a updated it.

During any step, if you want to verify which version is inside your initrd you can use:
$ lsinitramfs /boot/"initrd.img-$(uname -r)" | grep i915

Thanks for the help here!

Hi Rodrigo,
I confirm this new script give the details you mentioned but I still see GuC not loaded:

root@nuc-skl-i3:~/GUC/skl_guc_ver4_3# ./install.sh
Success: /lib/firmware/i915/skl_guc_ver4_3.bin installed!
Old version found in your initramfs. Trying to replace it...
Created a bakcup of your current initramfs /boot/initramfs-4.5.0-rc3-without-patch-guc+.img.i915-fw.backup
update-initramfs: Generating /boot/initrd.img-4.5.0-rc3-without-patch-guc+
WARNING: Your initrd still contains the old firmware. After rebooting please verify you have the desired version loaded by checking  /sys/kernel/debug/dri/0/i915_dmc_info
Success: Please reboot your machine!
root@nuc-skl-i3:~/GUC/skl_guc_ver4_3#
....
....
qa@nuc-skl-i3:~$
qa@nuc-skl-i3:~$
qa@nuc-skl-i3:~$ sudo -s
[sudo] password for qa:
root@nuc-skl-i3:~#
root@nuc-skl-i3:~#
root@nuc-skl-i3:~# cd /sys/kernel/debug/dri/0/
root@nuc-skl-i3:/sys/kernel/debug/dri/0# cat i915_guc_load_status
GuC firmware status:
        path: i915/skl_guc_ver4.bin
        fetch: FAIL
        load: NONE
        version wanted: 4.3
        version found: 0.0
        header: offset is 0; size = 0
        uCode: offset is 0; size = 0
        RSA: offset is 0; size = 0

GuC status 0x00000001:
        Bootrom status = 0x0
        uKernel status = 0x0
        MIA Core status = 0x0

Scratch registers:
         0:     0x0
         1:     0x0
         2:     0x0
         3:     0x0
         4:     0x0
         5:     0x0
         6:     0x0
         7:     0x0
         8:     0x0
         9:     0x0
        10:     0x0
        11:     0x0
        12:     0x0
        13:     0x0
        14:     0x0
        15:     0x0

"WARNING: Your initrd still contains the old firmware. After rebooting please
verify you have the desired version loaded by checking "

:( it seems that my generic script didn't work. Could you please try running the dpkg-reconfigure now and see if this would solve? So it seems that I will need to use that instead of the generic update-initramfs.

Then confirm GuC is successfully loaded if I reinstall DMC and reboot.

Created attachment 121655 [details]
Updated install.sh with dpkg-reconfigure

Hi, could you please try this new version that besides the update-initramfs also does the dpkg-reconfigure.

From what I understand initramfs-update should be enough, but let's keep safe at least on Ubuntu :/

Thanks,
Rodrigo.

Hi Rodrigo,
I confirm this new script (install.sh with dpkg-reconfigure) allows to successfully load the GuC. After a reboot, I see: 
path: i915/skl_guc_ver4.bin
    fetch: SUCCESS
    load: SUCCESS
    version wanted: 4.3
    version found: 4.3

Created attachment 122155 [details]
Another attempt of install.sh

Hi, The one with dpkg-reconfigure wasn't good and not helping in 100% of cases, so I fully updated the install script.

Could you please check if this one solves this issue here.

thanks,
Rodrigo.

Hi,

The GuC is correctly loaded with the new install script.

Packages available at 01.org has been updated with the new script.
Thanks for the reporting and testing.

So closed.