Summary: | mesa 18.2.x line is crashing and disabling kwin_x11 and effects thereof, no problem with 18.1.x | ||
---|---|---|---|
Product: | Mesa | Reporter: | jeckferson |
Component: | Drivers/DRI/i915 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | blocker | ||
Priority: | medium | CC: | mike |
Version: | 18.2 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
various 18.2.x mesa crashing kwin_x11; not before 18.2.x
It occurred again with 18.2.3 |
hi, could you please clarify the CPU model? CPU model is intel haswell pentium. Might be worth deleting the Mesa shader cache and the Qt shader cache ~/.cache/mesa_shader_cache ~/.cache/qtshadercache After the cleaning of .cache, it's going fine. Will report back after a week or two. So I think your distro uses the same build time for all their Mesa builds which means the cache is trying to reuse Mesa 18.1 shaders on Mesa 18.2 There's a fix to use the build-id on the mailing list, so hopefully this will be fixed properly soon Created attachment 142317 [details]
It occurred again with 18.2.3
Occurring repeatedly with 18.2.4. Almost every login. 2nd gen laptop is fine. It's only on my 4th gen haswell intel. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/789. |
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 141760 [details] various 18.2.x mesa crashing kwin_x11; not before 18.2.x The gpu is intel 4th gen. I have my 2nd gen laptop which is fine with 18.2.x. I use Arch Linux. I've encounter the problem before. I hesitate to open an issue because I think it'll eventually be ok after a release or next. All of the 18.2.x is affected. But not 18.1.x line.