Back to bug 103076
Who | When | What | Removed | Added |
---|---|---|---|---|
chris | 2017-10-03 13:15:59 UTC | CC | jkt | |
chris | 2017-10-03 13:16:05 UTC | CC | ganadist | |
chris | 2017-10-03 13:16:41 UTC | Summary | GPU HANG: DMAR: DRHD: handling fault status reg 3 | [v4.13] GPU HANG: DMAR: DRHD: handling fault status reg 3 |
chris | 2017-10-03 13:17:04 UTC | CC | crazymanjinn | |
chris | 2017-10-03 13:17:14 UTC | CC | camtech075 | |
vasyl.demin | 2017-10-03 14:12:12 UTC | CC | vasyl.demin | |
chris | 2017-10-03 22:20:08 UTC | CC | sgh | |
innykto | 2017-10-04 17:43:50 UTC | CC | innykto | |
chris | 2017-10-05 09:26:46 UTC | CC | pablo.doramas | |
chris | 2017-10-05 21:27:08 UTC | CC | mattkrll | |
throwaway19587 | 2017-10-05 21:34:02 UTC | CC | throwaway19587 | |
chris | 2017-10-06 08:35:26 UTC | CC | like.the.23 | |
chris | 2017-10-06 08:36:38 UTC | Summary | [v4.13] GPU HANG: DMAR: DRHD: handling fault status reg 3 | [v4.13 ARCH] GPU HANG: DMAR: DRHD: handling fault status reg 3 (arch reverted the use of intel_iommu=igfx_off) |
chris | 2017-10-07 16:06:49 UTC | CC | quejacq | |
chris | 2017-10-07 20:30:17 UTC | CC | aetf | |
linux | 2017-10-08 12:51:39 UTC | CC | linux | |
martin.stiborsky | 2017-10-10 08:42:34 UTC | CC | martin.stiborsky | |
chris | 2017-10-11 08:17:03 UTC | CC | cfernandez | |
chris | 2017-10-12 07:51:41 UTC | CC | bbykov_1989 | |
jonathan | 2017-10-19 18:47:52 UTC | CC | jonathan | |
geromanas | 2017-11-01 13:07:11 UTC | CC | geromanas | |
andyrtr | 2017-11-20 19:05:49 UTC | CC | andyrtr | |
elizabethx.de.la.torre.mena | 2018-03-28 23:43:21 UTC | i915 platform | SKL, BDW | |
i915 features | GPU hang | |||
jani.saarinen | 2018-04-25 08:13:47 UTC | Status | NEW | RESOLVED |
Resolution | --- | WORKSFORME | ||
jani.saarinen | 2018-04-25 08:13:55 UTC | Status | RESOLVED | CLOSED |
pmenzel+bugs.freedesktop.org | 2019-08-21 09:20:08 UTC | CC | pmenzel+bugs.freedesktop.org |
Back to bug 103076
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.