Back to bug 94900
Who | When | What | Removed | Added |
---|---|---|---|---|
dan.g.tob | 2016-04-11 22:52:29 UTC | Summary | Regression: HD6950 GPU lockup with octodad: dadliest catch | HD6950 GPU lockup with octodad: dadliest catch |
frederic.romagne | 2016-04-14 14:03:35 UTC | CC | frederic.romagne | |
dan.g.tob | 2016-05-03 11:05:59 UTC | Summary | HD6950 GPU lockup with octodad: dadliest catch | HD6950 GPU lockup with various steam games (octodad, saints row 4) |
marcin | 2016-05-04 21:23:21 UTC | CC | marcin | |
dan.g.tob | 2016-05-06 11:37:58 UTC | Component | DRM/Radeon | Drivers/Gallium/r600 |
QA Contact | dri-devel | |||
Version | unspecified | 11.2 | ||
Product | DRI | Mesa | ||
dan.g.tob | 2016-05-06 11:38:10 UTC | OS | All | Linux (All) |
Hardware | Other | x86-64 (AMD64) | ||
dan.g.tob | 2016-05-16 09:05:47 UTC | Summary | HD6950 GPU lockup with various steam games (octodad, saints row 4) | HD6950 GPU lockup loop with various steam games (octodad, saints row 4, grid autosport) |
marcin | 2016-07-13 12:12:56 UTC | CC | marcin | |
dan.g.tob | 2016-07-16 14:18:14 UTC | Summary | HD6950 GPU lockup loop with various steam games (octodad, saints row 4, grid autosport) | HD6950 GPU lockup loop with various steam games (octodad, saints row 4, dead island, grid autosport) |
dan.g.tob | 2016-07-16 16:26:45 UTC | Summary | HD6950 GPU lockup loop with various steam games (octodad, saints row 4, dead island, grid autosport) | HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes]) |
i.kalvachev | 2016-07-17 21:36:00 UTC | CC | iive | |
lil_tux | 2016-07-23 08:43:33 UTC | CC | lil_tux | |
lil_tux | 2016-09-28 17:26:26 UTC | Attachment #125271 Attachment is obsolete | 0 | 1 |
lil_tux | 2016-10-30 09:11:14 UTC | Attachment #126832 Attachment is obsolete | 0 | 1 |
andreas.boll.dev | 2017-01-12 10:53:11 UTC | Resolution | --- | FIXED |
Status | NEW | RESOLVED |
Back to bug 94900
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.