LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-01-2013, 05:34 AM   #1
geep999
LQ Newbie
 
Registered: Dec 2011
Posts: 6

Rep: Reputation: Disabled
Unhappy 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:
Code:
dmesg | grep i915
[    6.862034] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    6.862684] i915 0000:00:02.0: setting latency timer to 64
[    6.917060] i915 0000:00:02.0: irq 53 for MSI/MSI-X
[    7.651517] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 6467.574708] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[ 6467.574717] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[ 6467.578198] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 1668973 at 1668972, next 1668974)
If it does this a few more time I'll be reverting to the original kernel.

Cheers,
Peter
 
Old 06-01-2013, 07:50 AM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,573

Rep: Reputation: 429Reputation: 429Reputation: 429Reputation: 429Reputation: 429
Did you use build 1 or build 2? Pat has rebuilt the kernel by removing the commit that causes this problem
 
Old 06-01-2013, 07:58 AM   #3
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
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
 
Old 06-01-2013, 10:25 AM   #4
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by geep999 View Post
Just applied the latest patches including the kernel update. 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.
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

Last edited by Philip Lacroix; 06-01-2013 at 10:49 AM.
 
Old 06-02-2013, 06:15 AM   #5
geep999
LQ Newbie
 
Registered: Dec 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
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
 
Old 06-02-2013, 06:17 AM   #6
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883
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.
 
Old 06-02-2013, 09:15 AM   #7
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 438

Rep: Reputation: Disabled
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':
Code:
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i915 0000:00:02.0: irq 46 for MSI/MSI-X
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
 
Old 06-02-2013, 09:24 AM   #8
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883
Quote:
Originally Posted by TommyC7 View Post
I think this might be fixed in 3.2.46 (I haven't checked the source code, though).
It isn't. Quotes from above and the main thread.

Quote:
Originally Posted by Philip Lacroix View Post
This issue is not fixed by the latest Linux 3.2.46 update.
Quote:
Originally Posted by Philip Lacroix View Post
Ok, Linux 3.2.46 is now available on kernel.org, however the patch doesn't revert the lines discussed above. I decided to try it anyway, so I updated the original 3.2.45 sources with today's 3.2.46 incremental patch, rebuilt the kernel, modules, initrd and so on, and the previous issues are here again. Just FYI
Quote:
Originally Posted by ruario View Post
the 3.2.46 ChangeLog makes no reference to either of the troublesome commits (e12a2d53ae45a69aea499b64f75e7222cca0f12f and 393143615d9f2f581d87387268dc11b95adc339c).
 
Old 06-02-2013, 10:39 AM   #9
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by ruario View Post
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.
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

Last edited by Philip Lacroix; 06-02-2013 at 10:51 AM.
 
Old 06-04-2013, 05:18 AM   #10
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883Reputation: 883
New kernel package provided by Pat with the second problematic commit removed.

Quote:
Originally Posted by Philip Lacroix View Post
Now I'm back to 3.2.45, as removing that commit made the kernel rock-stable again.
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.
 
Old 06-04-2013, 07:37 AM   #11
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by ruario View Post
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.

Last edited by Philip Lacroix; 06-07-2013 at 10:16 AM. Reason: Corrected a few sentences.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error message with graphic card: i915_hangcheck_elapsed GPU hung peterlu Linux - Hardware 2 05-11-2013 12:34 PM
CentOS 6.4 x86_64 skips initial installations steps and gets hung r4ym4r Linux - Distributions 1 04-02-2013 11:59 AM
Kernel Error echo 0 > /proc/sys/kernel/hung _task_timeout_secsin Redhat 5.8 LittleMaster Linux - Server 1 10-18-2012 09:32 AM
Hangcheck timer elapsed ... GPU hung kidsin Debian 6 08-29-2011 02:50 AM
Intel GPU hung 105659 Linux - Kernel 1 09-11-2010 01:23 PM


All times are GMT -5. The time now is 05:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration