[Bug 96053] [BXT-P] [IGT] pm_rpm sub-tests basic-pci-d3-state & basic-rte are failing

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jun 1 16:25:05 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=96053

--- Comment #8 from Humberto Israel Perez Rodriguez <humberto.i.perez.rodriguez at intel.com> ---
(In reply to Imre Deak from comment #5)
> (In reply to Luis Botello from comment #4)
> > I got the following results:
> > 
> > # ./pm_rpm --run-subtest basic-pci-d3-state --debug
> >[...]
> > Subtest basic-pci-d3-state: SUCCESS (5.910s)
> >[...]
> > Subtest basic-rte: SUCCESS (1.141s)
> 
> Can we close this bug based on the above?
> 
> >[...]
> > vmlinuz root=/dev/sda2 maxcpus=1 initrd=initrd.img
> > acpi_enforce_resources=lax processor.max_cstate=2 no_console_suspend
> > log_buf_len=4M i915.enable_rc6=1 i915.preliminary_hw_support=1 drm.debug=14
> > i915.enable_guc_submission=1
> 
> Any particular reason you're booting with the following parameters, they
> shouldn't be needed AFAICS?:
> maxcpus=1 acpi_enforce_resources=lax i915.enable_rc6=1
> i915.preliminary_hw_support=1
> 
> I think that instead of the processor.max_cstate=2 workaround we should use
> idle=halt until BIOS is fixed, this is the last suggestion from Len Brown.
> 
> Also was there a decision to test things with i915.enable_guc_submission=1?
> Last that I checked this caused problems and it is disabled now by default
> for that reason.

Hi Imre Deak :

actually we noticed a strange behavior with the guc in APL and this parameter
"i915.enable_guc_submission=1", only the first time it was loaded correctly the
guc, but after reboot the guc is not load anymore, the guc version is 8.7, so
you recommend not istall the guc or simply put a different option to enable it
?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160601/9fdf3d9b/attachment.html>


More information about the intel-gfx-bugs mailing list