| Summary: | i915 driver crashes kernel, forces reboot | ||
|---|---|---|---|
| Product: | DRI | Reporter: | josh <josh.fryman> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | SKL | i915 features: | |
| Attachments: | |||
Created attachment 130160 [details]
Example 2 - second crash example, just the key log portions
Please be advised that the two crashes appear to be different. In neither case did the "error" log file on the card have anything in it (0 byte file) after the required reboot. (Reboot required because the machine was hung.) Created attachment 130161 [details]
Example 3 - a crash from this evening
(In reply to josh from comment #2) > Please be advised that the two crashes appear to be different. In neither > case did the "error" log file on the card have anything in it (0 byte file) > after the required reboot. > > (Reboot required because the machine was hung.) Eg: [jbf@jbfryman-linux ~] $ ls -l /sys/class/drm/card0/error -rw------- 1 root root 0 Mar 10 21:31 /sys/class/drm/card0/error commit 1f7b847d72c3583df5048d83bd945d0c2c524c28 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Feb 8 14:30:33 2017 +0000 drm/i915: Disable engine->irq_tasklet around resets Please check against https://cgit.freedesktop.org/drm-tip |
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.
Created attachment 130159 [details] Example 1 - includes pre-crash kernel log for basic context if needed Fedora 24 + Cinnamon, all current patches applied. Lenovo x260 laptop, all BIOS updates applied. i915 driver randomly crashes the laptop, logging a kernel oops event (see attachments for two examples) and forcing a reboot. This will happen randomly - it can happen in back-to-back sessions within minutes, or it can happen every few days. It can happen on a docking station or without, on AC power or without. I have not been able to discern any pattern at all.