| Summary: | [KBL] Video corrupted during playback with audio in KBL NUC using Clear Linux OS (Root Caused to GuC/HuC Firmware Authentication Issue) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | yat.seng.lam | ||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Severity: | major | ||||||||
| Priority: | medium | CC: | eero.t.tamminen, intel-gfx-bugs, jon.ewins | ||||||
| Version: | unspecified | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | Triaged | ||||||||
| i915 platform: | KBL | i915 features: | |||||||
| Attachments: |
|
||||||||
|
Description
yat.seng.lam
2019-05-06 07:51:14 UTC
Have you tried to verify the issue with latest kernel 5.1 on KBL? @Jon, any comments? GuC and HuC are closed source signed binaries. They are loaded, with the GuC first authenticated based on its embedded key and the GuC then supporting authentication of the HuC. Of the kernel params you mentioned, i915.enable_guc=0x02 configures the system for use of the HuC. The nuclear flip param should not be relevant. One observation is that the kernel in use here appears to have late uc loading (i915_gem_init_hw_late) that was required for Android boot operation, but never part of the upstream kernel. It is not clear if that is related. * Please confirm that HuC authentication is successful on APL, not just that no video corruption is seen. Mihgt be case if case media operation is different on APL. * Is the guc/huc failure consistent on every run? Note that we have confirmed locally that current drm-tip kernel with v32.0.3 GuC fw is not showing an issue for KBL on general boot, IGT tests. To aid further debugging, please enable following logging. First ensure the drm i915 debug level is set drm.debug=0xe For GUC logs, set: i915.guc_log_level=3 This requires that debugfs is configured. GuC logs will be located after the test run at: /sys/kernel/debug/dri/0/i915_guc_log_dump (no debugfs must be enabled) If an issue happens in guc load such that the driver load fails, the driver will copy the log to /sys/kernel/debug/dri/0/i915_guc_load_err_log_dump before the driver is unrolled. please update the content of these files to this bugzilla, along with kernel dmesg log. For reference, commit f774f09649192f326fa030564afd3f8f5d82c1e4 (drm-intel/for-linux-next, drm-intel/drm-intel-next-queued, drm-intel-next-queued) Author: Michal Wajdeczko <michal.wajdeczko@intel.com> Date: Fri Jul 12 11:14:45 2019 +0000 drm/i915/guc: Turn on GuC/HuC auto mode Using "enable_guc" modparam auto mode (-1) will let driver decide on which platforms and in which configuration we want to use GuC/HuC firmwares. Today driver will enable HuC firmware authentication by GuC only on Gen11+ platforms as HuC firmware is required to unlock advanced video codecs in media driver. Legacy platforms with GuC/HuC are not affected by this change as for them driver still defaults to disabled(0) in auto mode. (In reply to Jon Ewins from comment #3) > GuC and HuC are closed source signed binaries. They are loaded, with the > GuC first authenticated based on its embedded key and the GuC then > supporting authentication of the HuC. Of the kernel params you mentioned, > i915.enable_guc=0x02 configures the system for use of the HuC. The nuclear > flip param should not be relevant. > One observation is that the kernel in use here appears to have late uc > loading (i915_gem_init_hw_late) that was required for Android boot > operation, but never part of the upstream kernel. It is not clear if that is > related. > * Please confirm that HuC authentication is successful on APL, not just that > no video corruption is seen. Mihgt be case if case media operation is > different on APL. > > * Is the guc/huc failure consistent on every run? > > Note that we have confirmed locally that current drm-tip kernel with v32.0.3 > GuC fw is not showing an issue for KBL on general boot, IGT tests. > > To aid further debugging, please enable following logging. > First ensure the drm i915 debug level is set > drm.debug=0xe > For GUC logs, set: > i915.guc_log_level=3 > This requires that debugfs is configured. GuC logs will be located after > the test run at: > /sys/kernel/debug/dri/0/i915_guc_log_dump > (no debugfs must be enabled) > If an issue happens in guc load such that the driver load fails, the driver > will copy the log to > /sys/kernel/debug/dri/0/i915_guc_load_err_log_dump > before the driver is unrolled. > please update the content of these files to this bugzilla, along with kernel > dmesg log. Reporter, can you please provide all necessary details as requested above. Created attachment 144906 [details]
attachment-20701-0.html
I am currently away and will respond when I return
|
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.