Slackware This Forum is for the discussion of Slackware Linux.
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
04-18-2011, 09:18 AM
#1
Member
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403
Rep:
new Intel driver is crashing X
Has anyone had problems with the new Intel driver (2.15)? I've been using it since it was put on current and have been having X crash on me repeatedly or getting a black screen from which I can only recover by a hard reboot. This is happening under a couple of different WMs without compositing (so this isn't the same issue that I was having with KDE and xscreensaver).
I'm using the i915 driver with stock 2.6.37.6, but I also tried a 2.6.38.2 kernel but had the same problem with both.
Here's a backtrace (for what it is worth):
Code:
[ 10161.149] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a02d8]
[ 10161.150] 1: /usr/bin/X (0x400000+0x60fc9) [0x460fc9]
[ 10161.150] 2: /lib64/libc.so.6 (0x7fd25616a000+0x340b0) [0x7fd25619e0b0]
[ 10161.150] 3: /usr/lib64/libdrm_intel.so.1 (drm_intel_bo_emit_reloc+0x0) [0x7fd254a2eb90]
[ 10161.150] 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x2235c) [0x7fd254c5a35c]
[ 10161.150] 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x27edf) [0x7fd254c5fedf]
[ 10161.150] 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x2a2bf) [0x7fd254c622bf]
[ 10161.150] 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x27af9) [0x7fd254c5faf9]
[ 10161.150] 8: /usr/bin/X (0x400000+0xd845d) [0x4d845d]
[ 10161.150] 9: /usr/bin/X (0x400000+0x2a0af) [0x42a0af]
[ 10161.150] 10: /usr/bin/X (0x400000+0x2def1) [0x42def1]
[ 10161.150] 11: /usr/bin/X (0x400000+0x21ffe) [0x421ffe]
[ 10161.150] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fd256188e5d]
[ 10161.150] 13: /usr/bin/X (0x400000+0x21bb9) [0x421bb9]
[ 10161.150] Segmentation fault at address 0x79000022
[ 10161.150]
Fatal server error:
[ 10161.150] Caught signal 11 (Segmentation fault). Server aborting
04-18-2011, 09:23 AM
#2
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 1,377
Rep:
Have you tried upgrading libdrm also (in /testing) ?
Also try using Mesa 7.10.x instead of 7.9.x
1 members found this post helpful.
04-18-2011, 09:24 AM
#3
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Rep:
Here it's working just fine, with xf86-video-intel-2.1.5 and libdrm-2.4.25 from testing/, both at x86_64 arch, kernel 2.6.38.3 and i915 module, as well. Custom kernel compiled, though.
1 members found this post helpful.
04-18-2011, 10:02 AM
#4
Member
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 399
Rep:
Quote:
Originally Posted by
brixtoncalling
Has anyone had problems with the new Intel driver (2.15)? I've been using it since it was put on current and have been having X crash on me repeatedly or getting a black screen from which I can only recover by a hard reboot. This is happening under a couple of different WMs without compositing (so this isn't the same issue that I was having with KDE and xscreensaver).
I'm using the i915 driver with stock 2.6.37.6, but I also tried a 2.6.38.2 kernel but had the same problem with both.
Here's a backtrace (for what it is worth):
Code:
[ 10161.149] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a02d8]
[ 10161.150] 1: /usr/bin/X (0x400000+0x60fc9) [0x460fc9]
[ 10161.150] 2: /lib64/libc.so.6 (0x7fd25616a000+0x340b0) [0x7fd25619e0b0]
[ 10161.150] 3: /usr/lib64/libdrm_intel.so.1 (drm_intel_bo_emit_reloc+0x0) [0x7fd254a2eb90]
[ 10161.150] 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x2235c) [0x7fd254c5a35c]
[ 10161.150] 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x27edf) [0x7fd254c5fedf]
[ 10161.150] 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x2a2bf) [0x7fd254c622bf]
[ 10161.150] 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd254c38000+0x27af9) [0x7fd254c5faf9]
[ 10161.150] 8: /usr/bin/X (0x400000+0xd845d) [0x4d845d]
[ 10161.150] 9: /usr/bin/X (0x400000+0x2a0af) [0x42a0af]
[ 10161.150] 10: /usr/bin/X (0x400000+0x2def1) [0x42def1]
[ 10161.150] 11: /usr/bin/X (0x400000+0x21ffe) [0x421ffe]
[ 10161.150] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fd256188e5d]
[ 10161.150] 13: /usr/bin/X (0x400000+0x21bb9) [0x421bb9]
[ 10161.150] Segmentation fault at address 0x79000022
[ 10161.150]
Fatal server error:
[ 10161.150] Caught signal 11 (Segmentation fault). Server aborting
If you suspect to be something wrong with your graphics stack, try these unofficial (GIT HEAD) packages, together with 2.8.38.3 from
testing :
http://ftp.darkstarlinux.ro/slackware/xdrivers/
If they works in your system, you can stay here, or try to go back into official packages.
Your options:
Intel video driver: 2.15.0 and 2.14.0 from
pasture .
libdrm: 2.4.23 and 2.4.25 from
testing .
Mesa: 7.9.2 and 7.10.2 from
testing .
BTW. Someone noticed that GLIBC is compiled against 2.6.37.5 and the current kernel-headers package is 2.6.37.6?
Last edited by Darth Vader; 04-18-2011 at 10:10 AM .
1 members found this post helpful.
04-18-2011, 10:22 AM
#5
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 248
Quote:
Originally Posted by
Darth Vader
BTW. Someone noticed that GLIBC is compiled against 2.6.37.5 and the current kernel-headers package is 2.6.37.6?
That makes no difference in the case of 2.6.37.5 -> 2.6.37.6, as the kernel headers did not change in any way that glibc would care about.
1 members found this post helpful.
04-18-2011, 10:49 AM
#6
Member
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403
Original Poster
Rep:
Thank for the replies. I will be trying the testing packages and I'm compiling my own 2.6.38.3 kernel to test out as well.
04-18-2011, 11:12 AM
#7
Member
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 399
Rep:
Quote:
Originally Posted by
brixtoncalling
... I'm compiling my own 2.6.38.3 kernel to test out as well.
You already have the 2.6.38.3 kernel packages into
/testing .
04-18-2011, 11:15 AM
#8
Member
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403
Original Poster
Rep:
Yeah, but I want to add a couple of things
04-18-2011, 04:58 PM
#9
Member
Registered: Oct 2007
Distribution: Slackware
Posts: 480
Rep:
The 2.15.0 intel driver was not kind on my hardware with very slow redraw on many screens and a few black screens from Firefox. No X crash though. After doing an intel/drm/mesa dance as suggested I have settled with the 2.14.0 driver from /pasture and so far so good
.
04-18-2011, 05:42 PM
#10
Member
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403
Original Poster
Rep:
It looks like this might be the problem:
i915GM: GPU hangup . I have yet to test myself to see if this is the case.
Quote:
Originally Posted by
andrew.46
The 2.15.0 intel driver was not kind on my hardware with very slow redraw on many screens and a few black screens from Firefox. No X crash though. After doing an intel/drm/mesa dance as suggested I have settled with the 2.14.0 driver from /pasture and so far so good
.
What is your hardware, Andrew?
04-18-2011, 06:31 PM
#11
Member
Registered: Oct 2007
Distribution: Slackware
Posts: 480
Rep:
Quote:
Originally Posted by
brixtoncalling
What is your hardware, Andrew?
Intel 945GM Chipset
04-18-2011, 06:41 PM
#12
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 248
Quote:
Originally Posted by
andrew.46
Intel 945GM Chipset
Odd that I have two of those that work fine. I thought that was the unaffected chipset.
04-18-2011, 06:55 PM
#13
Member
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 399
Rep:
Quote:
Originally Posted by
brixtoncalling
It looks like this might be the problem:
i915GM: GPU hangup . I have yet to test myself to see if this is the case.
The 'relaxed-fencing' is off by default on 2.15.0, if this make you happy ...
Another is the problem! Give me the used versions of libdrm and for those using KDE(4), for Mesa too. Please!
04-18-2011, 07:42 PM
#14
Member
Registered: Oct 2007
Distribution: Slackware
Posts: 480
Rep:
Quote:
Originally Posted by
volkerdi
Odd that I have two of those that work fine. I thought that was the unaffected chipset.
Hmmm.... very odd. I will reinstall the newer Intel driver and have a closer look at the problem.
Edit: Sigh..... I cannot reproduce the problem after reinstalling 2.15.0... my apologies for the noise
.
Re-Edit: I spoke too early, a complete X crash has meant I am retreating to the older intel driver...
Last edited by andrew.46; 04-19-2011 at 12:15 AM .
04-18-2011, 08:51 PM
#15
Member
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403
Original Poster
Rep:
Quote:
Originally Posted by
Darth Vader
The 'relaxed-fencing' is off by default on 2.15.0, if this make you happy ...
A little
I'm trying the new libdrm and mesa under 2.6.38.3 right now. Let's see if it helps.
Thread Tools
Search this Thread
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
All times are GMT -5. The time now is 06:23 AM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News