Back to bug 90410
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| conselvan2 | 2015-05-12 11:40:56 UTC | Status | NEW | NEEDINFO |
| yex.tian | 2015-05-13 02:44:45 UTC | Status | NEEDINFO | NEW |
| yex.tian | 2015-05-13 02:45:04 UTC | Summary | [BDW-H]System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) | [BDW-H bisected]System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) |
| conselvan2 | 2015-05-13 07:13:52 UTC | Status | NEW | NEEDINFO |
| Assignee | intel-gfx-bugs | conselvan2 | ||
| yex.tian | 2015-05-13 07:37:21 UTC | Status | NEEDINFO | NEW |
| conselvan2 | 2015-05-13 08:41:37 UTC | Status | NEW | NEEDINFO |
| yex.tian | 2015-05-13 08:53:04 UTC | Status | NEEDINFO | NEW |
| conselvan2 | 2015-05-13 09:00:41 UTC | Status | NEW | NEEDINFO |
| yex.tian | 2015-05-15 03:04:55 UTC | Status | NEEDINFO | NEW |
| conselvan2 | 2015-05-15 08:28:55 UTC | Status | NEW | ASSIGNED |
| conselvan2 | 2015-05-18 06:41:23 UTC | Summary | [BDW-H bisected]System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) | [HSW/BDW/SKL] System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) |
| conselvan2 | 2015-05-18 07:38:03 UTC | Summary | [HSW/BDW/SKL] System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) | [HSW/BDW/SKL HDMI] System boot up causes [drm:check_crtc_state [i915]] *ERROR* mismatch in ddi_pll_sel (expected 0x00000000, found 0x80000000) |
| conselvan2 | 2015-05-20 07:33:26 UTC | Status | ASSIGNED | RESOLVED |
| Resolution | --- | FIXED | ||
| yex.tian | 2015-05-22 02:36:10 UTC | Status | RESOLVED | VERIFIED |
| elizabethx.de.la.torre.mena | 2017-10-06 14:30:01 UTC | Status | VERIFIED | CLOSED |
Back to bug 90410
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.