https://bugzilla.kernel.org/show_bug.cgi?id=196223 Tomi Sarvela (tomi.p.sarvela@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomi.p.sarvela@xxxxxxxxx --- Comment #10 from Tomi Sarvela (tomi.p.sarvela@xxxxxxxxx) --- Out of linux-next builds, 20170626 is known good, results copied out: https://intel-gfx-ci.01.org/CI/next-issues.html https://intel-gfx-ci.01.org/CI/next-all.html 20170627 couldn't be tested because the locking issue (IOMMU panic) 20170628 has been tested bad earlier. The newest build 20170707 has collected the following traces: https://intel-gfx-ci.01.org/CI/next-20170707/fi-ivb-3520m/dmesg-149942861_Panic_1.log https://intel-gfx-ci.01.org/CI/next-20170707/fi-hsw-4770r/dmesg-149942860_Panic_1.log https://intel-gfx-ci.01.org/CI/next-20170707/fi-bxt-j4205/dmesg-149942868_Panic_1.log https://intel-gfx-ci.01.org/CI/next-20170707/fi-skl-x1585l/dmesg-149942869_Panic_1.log https://intel-gfx-ci.01.org/CI/next-20170707/fi-glk-2a/dmesg-149942868_Panic_1.log Marta has left for vacation. I probably don't have time for bisection before next Tuesday. -- You are receiving this mail because: You are watching the assignee of the bug.
