Back to bug 69693
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| daniel | 2013-09-25 10:24:00 UTC | Status | NEW | NEEDINFO |
| huax.lu | 2013-09-26 05:43:16 UTC | Status | NEEDINFO | NEW |
| jbarnes | 2013-09-27 19:59:50 UTC | Assignee | intel-gfx-bugs | jbarnes |
| jani.nikula | 2013-10-11 11:13:37 UTC | Status | NEW | NEEDINFO |
| qingshuai.tian | 2013-10-15 03:18:59 UTC | Status | NEEDINFO | NEW |
| daniel | 2013-10-18 14:11:36 UTC | Status | NEW | RESOLVED |
| Resolution | --- | DUPLICATE | ||
| daniel | 2013-10-18 14:14:13 UTC | Status | RESOLVED | REOPENED |
| Resolution | DUPLICATE | --- | ||
| Summary | [BYT]igt/kms_flip causes [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting | [BYT]igt/kms_flip: DP link train fail due to IOSF sideband fabric timeout | ||
| gordon.jin | 2013-11-01 07:58:05 UTC | Priority | medium | high |
| Severity | normal | major | ||
| daniel | 2013-11-05 15:50:24 UTC | Status | REOPENED | NEEDINFO |
| huax.lu | 2013-11-08 05:09:57 UTC | Status | NEEDINFO | REOPENED |
| daniel | 2013-11-11 08:44:44 UTC | Status | REOPENED | NEEDINFO |
| huax.lu | 2013-11-15 02:05:58 UTC | Status | NEEDINFO | REOPENED |
| daniel | 2013-11-16 12:30:27 UTC | Status | REOPENED | ASSIGNED |
| jbarnes | 2013-11-19 01:05:30 UTC | Status | ASSIGNED | NEEDINFO |
| huax.lu | 2013-11-20 03:24:35 UTC | Status | NEEDINFO | REOPENED |
| przanoni | 2013-12-04 21:23:59 UTC | CC | przanoni | |
| guang.a.yang | 2013-12-05 00:49:24 UTC | Status | REOPENED | NEEDINFO |
| huax.lu | 2013-12-05 07:17:32 UTC | Status | NEEDINFO | REOPENED |
| daniel | 2013-12-05 07:35:00 UTC | Status | REOPENED | NEEDINFO |
| huax.lu | 2013-12-06 06:29:48 UTC | Status | NEEDINFO | REOPENED |
| przanoni | 2013-12-11 19:42:23 UTC | Status | REOPENED | RESOLVED |
| Resolution | --- | FIXED | ||
| huax.lu | 2013-12-13 02:41:58 UTC | Status | RESOLVED | VERIFIED |
| jari.tahvanainen | 2016-09-28 13:21:22 UTC | Status | VERIFIED | CLOSED |
Back to bug 69693
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.