Back to bug 102294
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| martin.peres | 2017-08-18 13:56:43 UTC | Priority | medium | highest |
| Severity | normal | critical | ||
| Whiteboard | ReadyForDev | |||
| i915 platform | KBL | |||
| i915 features | display/LSPCON | |||
| martin.peres | 2017-08-18 13:59:16 UTC | Summary | [CI][BAT][KBL] *ERROR* Failed to probe lspcon | [CI][BAT][KBL] *ERROR* LSPCON read(0x80, 0x41) failed |
| jani.saarinen | 2017-08-21 09:06:01 UTC | Assignee | intel-gfx-bugs | shashank.sharma |
| ricardo.vega | 2017-09-11 20:46:14 UTC | CC | ricardo.vega | |
| ricardo.vega | 2017-09-11 21:37:48 UTC | i915 platform | CFL | |
| ricardo.vega | 2017-09-11 21:37:58 UTC | Summary | [CI][BAT][KBL] *ERROR* LSPCON read(0x80, 0x41) failed | [CI][BAT] *ERROR* LSPCON read(0x80, 0x41) failed |
| marta.lofstedt | 2017-09-25 09:40:33 UTC | Summary | [CI][BAT] *ERROR* LSPCON read(0x80, 0x41) failed | [CI][BAT][KBL][CFL] *ERROR* LSPCON read(0x80, 0x41) failed |
| jani.saarinen | 2017-09-28 15:37:19 UTC | i915 platform | CFL | |
| jani.saarinen | 2017-09-28 15:37:42 UTC | Summary | [CI][BAT][KBL][CFL] *ERROR* LSPCON read(0x80, 0x41) failed | [CI][BAT] *ERROR* LSPCON read(0x80, 0x41) failed |
| jani.saarinen | 2017-10-13 13:08:35 UTC | Resolution | --- | FIXED |
| Status | NEW | RESOLVED | ||
| marta.lofstedt | 2017-10-16 07:58:11 UTC | Status | RESOLVED | CLOSED |
| prochazka.nicolas | 2017-12-07 14:22:53 UTC | Status | CLOSED | REOPENED |
| Resolution | FIXED | --- | ||
| prochazka.nicolas | 2017-12-26 20:41:21 UTC | CC | prochazka.nicolas | |
| martin.peres | 2018-04-17 14:46:43 UTC | Severity | critical | normal |
| Priority | highest | high | ||
| jani.saarinen | 2018-06-06 09:58:54 UTC | Blocks | 105979 | |
| martin.peres | 2018-06-06 10:00:20 UTC | CC | arkadiusz.hiler | |
| martin.peres | 2019-11-29 17:25:03 UTC | Status | REOPENED | RESOLVED |
| Resolution | --- | MOVED |
Back to bug 102294
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.