Back to bug 108456
Who | When | What | Removed | Added |
---|---|---|---|---|
daniel | 2018-10-17 17:16:45 UTC | CC | chris, tvrtko.ursulin | |
daniel | 2018-10-18 07:05:01 UTC | QA Contact | intel-3d-bugs | intel-gfx-bugs |
Component | Drivers/DRI/i965 | DRM/Intel | ||
Product | Mesa | DRI | ||
CC | intel-gfx-bugs | |||
lakshminarayana.vudum | 2018-10-18 10:28:20 UTC | i915 platform | SKL | |
i915 features | GEM/Other | |||
Whiteboard | Triaged | |||
luis.strano | 2018-10-19 18:06:07 UTC | Assignee | jason | francesco.balestrieri |
francesco.balestrieri | 2018-10-22 15:12:20 UTC | Priority | medium | high |
francesco.balestrieri | 2018-10-23 07:58:04 UTC | Whiteboard | Triaged | Triaged, ReadyForDev |
daniel | 2018-10-24 19:45:04 UTC | Summary | VulkanCTS 1.1.2 Kernel error: dEQP-VK.pipeline.render_to_image.core.cube_array.huge.width_height_layers | userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex |
francesco.balestrieri | 2018-11-01 13:36:19 UTC | Assignee | francesco.balestrieri | joonas.lahtinen |
francesco.balestrieri | 2018-11-06 12:34:14 UTC | Assignee | joonas.lahtinen | chris |
clayton.a.craft | 2018-11-21 17:50:07 UTC | Blocks | 108530 | |
mark.a.janes | 2018-11-29 17:11:20 UTC | CC | jason, rafael.antognolli | |
emil.l.velikov | 2018-12-03 16:13:07 UTC | Blocks | 108530 | |
mark.a.janes | 2018-12-03 23:20:36 UTC | CC | francesco.balestrieri | |
chris | 2019-01-15 17:23:52 UTC | Status | NEW | RESOLVED |
Resolution | --- | FIXED | ||
mark.a.janes | 2019-01-29 17:02:53 UTC | Resolution | FIXED | DUPLICATE |
mark.a.janes | 2019-01-31 18:12:20 UTC | Resolution | DUPLICATE | --- |
Status | RESOLVED | REOPENED | ||
eero.t.tamminen | 2019-02-12 11:44:55 UTC | CC | eero.t.tamminen | |
caio.oliveira | 2019-03-14 17:50:32 UTC | CC | caio.oliveira | |
francesco.balestrieri | 2019-06-03 05:13:01 UTC | Priority | high | medium |
martin.peres | 2019-11-29 17:56:09 UTC | Status | REOPENED | RESOLVED |
Resolution | --- | MOVED |
Back to bug 108456
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.