Bug 15158
Summary: | oops related to i915_gem_object_save_bit_17_swizzle | ||
---|---|---|---|
Product: | Drivers | Reporter: | Werner Lemberg (wl) |
Component: | Video(DRI - Intel) | Assignee: | Eric Anholt (eric) |
Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
Severity: | normal | CC: | akpm, astarikovskiy, jbarnes, rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.33-rc5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 14230 |
Description
Werner Lemberg
2010-01-28 08:26:44 UTC
Did 2.6.32 crash in the same way? If not, this is a regression, isn't it? 2.6.31 definitely didnt' crash this way (and no other kernel before). IIRC, one of the RC candidates of 2.6.32 introduced the buggy behaviour, but I'm not sure, unfortunately. The developers apparently can't reproduce this issue, so I'm afraid we need to know the change that introduced it and you have the hardware it's visible on. Did you change the Xorg driver in the meantime? I can't reproduce it at will either which means that even bisecting the source wouldn't work. If the crash happens, there's normally a lot of disk activity and swapping involved, for example, using firefox to visit a site with many large images (bikini girls and the like :-). Another related issue might be that I use KDE with six virtual screens, and I do a lot of fast switching between them using key shortcuts. Alas, I can't remember either whether the crashes started before upgrading to xf86-video-intel 2.10.0 or after. Downgrading would be a great pain... What hardware information besides the graphics chip (945GM) do you need? What else can I do to improve the bug report? Is there a possibility to increase the verbosity of the backtrace, or to install a package with better tracing information? Hoping Eric can confirm this is fixed already or narrow down the issue. Patch is available here: https://patchwork.kernel.org/patch/85355/ |