kernel 3.2.45 Slack14 x86_64 - drm:i915_hangcheck_elapsed] *ERROR* ... GPU hung
 

Hi,
Just applied the latest patches including the kernel update.
A big mistake?
PC has Intel graphics.
Typing on command line in konsole the last line became broken up - sort of "smeary". Then X went bananas and all windows locked up.
Restarting X - CTRL-ALT-BACKSPACE - I see that dmesg reports a nasty:
If it does this a few more time I'll be reverting to the original kernel.

Cheers,
Peter

Did you use build 1 or build 2? Pat has rebuilt the kernel by removing the commit that causes this problem

The second build is still causing issues for some Intel users and Pat is considering another rebuild. See the last few posts in this thread:

http://www.linuxquestions.org/questi...ml#post4962341

Some of us could easily fix the problem by removing commit 393143615d9f2f581d87387268dc11b95adc339c from the 3.2.45 kernel source, as suggested by Patrick in the thread mentioned by digger95: you might want to read and post there. This issue is not fixed by the latest Linux 3.2.46 update. There are some useful suggestions in this thread as well.

Best regards,
Philip

Thanks for all the replies. At least I'm not alone.
I got the problem after installing this patch (and all the ones before it):
Wed May 22 14:11:13 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.

As long the problem remains very intermittent I won't bother to revert to older kernel.
And I'll keep on eye on the links listed above, and the Slackware changelog, for a final fix.

Cheers,
Peter

The rebuild from May 22nd was to fix another issue. You will still need to remove the commit that Philip mentioned before your issue will go way.

I think this might be fixed in 3.2.46 (I haven't checked the source code, though).

I'm currently running 3.2.46 also using the i915 driver and this is the output of my `dmesg | grep i915':

It isn't. Quotes from above and the main thread.

Yeah, and that's the only commit I removed from the original 3.2.45 kernel: I didn't even try the second build, as I was doing very well with 3.4.47 and 3.8.13. Now I'm back to 3.2.45, as removing that commit made the kernel rock-stable again. I really like the way Slackware lets you try out things, with no dependency management tools fighting against you.

@geep999, you might want to rebuild the kernel after having that commit removed. You can even delete those few lines manually: look at drivers/gpu/drm/i915/intel_ringbuffer.c in your kernel source, lines 411-414 (for both 3.2.45 and 3.2.46, as the file wasn't touched by the last update). You can gather useful information in the mentioned threads, and if you don't know how to build a kernel Ruarí's post here can be a good start, along with this document from the Slackware Documentation Project.

Philip

New kernel package provided by Pat with the second problematic commit removed.

I also decided to go back to 3.2.45 (with the two problematic commits removed), as I like to stay as close to vanilla Slackware as possible. It helps when helping with others problems or when they are helping with mine if you have very similar setups.

That's true. On the other hand, in a situation like this it was also very helpful to know that alternate solutions were viable. I didn't want to downgrade to 3.2.29, and both 3.4.47 and 3.8.13 kernels proved to be excellent, at least here.

By the way, I had done a custom build with the second commit reverted and the i915 module built in, along with its dependencies. This way no updated modules were required if the older kernel-modules-3.2.45 package was there. I just replaced the original kernel image with my build on a second Intel box with the crashing 3.2.45 upgrade, I run lilo and the issues got fixed. I was managing to upload this somewhere, then the official rebuild was available and made it useless.