Back to bug 90863
Who | When | What | Removed | Added |
---|---|---|---|---|
shuang.he | 2015-06-16 08:00:21 UTC | CC | christophe.prigent | |
chris | 2015-07-02 08:45:14 UTC | i915 platform | SKL | |
i915 features | power/runtime PM | |||
vijayakannan.a | 2015-07-29 05:21:55 UTC | CC | badex.appalanaidu, girish.ks, raju.rajakumar, vijayakannanx.ayyathurai | |
przanoni | 2015-08-04 14:14:45 UTC | Status | NEW | NEEDINFO |
CC | przanoni | |||
christophe.prigent | 2015-08-16 14:31:21 UTC | Assignee | intel-gfx-bugs | christophe.prigent |
quachtlc | 2016-04-08 18:00:22 UTC | CC | quachtlc | |
jairo.daniel.miramontes.caton | 2016-04-27 00:15:51 UTC | Summary | [SKL]igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | [SKL/KBL]igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) |
i915 platform | KBL | |||
christophe.prigent | 2016-04-29 11:59:40 UTC | i915 platform | KBL | |
Summary | [SKL/KBL]igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | [SKL]igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | ||
humberto.i.perez.rodriguez | 2016-05-26 16:22:02 UTC | Status | NEEDINFO | NEW |
humberto.i.perez.rodriguez | 2016-05-26 16:22:15 UTC | i915 platform | BXT | |
Summary | [SKL]igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | [SKL/BXT-P] igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | ||
christophe.prigent | 2016-10-11 09:19:44 UTC | i915 platform | SKL | |
Summary | [SKL/BXT-P] igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | [BXT-P] igt/pm_rpm causes [drm:skl_set_power_well [i915]] *ERROR* CSR firmware not ready (2) | ||
christophe.prigent | 2016-10-12 16:02:24 UTC | Status | NEW | RESOLVED |
Resolution | --- | WORKSFORME | ||
christophe.prigent | 2016-10-12 16:02:34 UTC | Status | RESOLVED | CLOSED |
Back to bug 90863
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.