| Summary: | x11-drivers/xf86-video-intel-2.20.7 USE=-uxa - segmentation faults | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Eugene Rosenzweig <ugn> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | nikoli, rei4dan |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Xorg log for the 2.20.7 without uxa, contains segfault backtrace
Xorg log for the 2.20.7 without uxa, contains segfault backtrace, built with -ggdb and splitdebug |
||
|
Description
Eugene Rosenzweig
2012-09-13 04:23:36 UTC
Created attachment 323640 [details]
Xorg log for the 2.20.7 without uxa, contains segfault backtrace
SNA has not got as much testing as UXA, but it is in active development and all the issues are quickly resolved if reported. Please recompile xf86-video-intel with debugging symbols enabled (add -ggdb to CFLAGS; http://www.gentoo.org/proj/en/qa/backtraces.xml) and reproduce the segfault. Then using addr2line get line numbers (if they are not in the backtrace) for the backtrace in your new log file (give it the numbers after + sign in backtrace), e.g. if the current backtrace was with debugging symbols enabled: $ addr2line -e /usr/lib64/xorg/modules/drivers/intel_drv.so 0x456e9 0x8329c 0x7e5a1 0x57802 0x45321 If you have splitdebug feature enabled then change /usr/lib64/xorg/modules/drivers/intel_drv.so for /usr/lib64/debug/usr/lib64/xorg/modules/drivers/intel_drv.so.debug in the above command. Then post the Xorg.0.log and the addr2line command you used together with its output. Also add information about the intel card and windows manager you are using. Windows manager is:
x11-wm/jwm-2.1.0 USE="jpeg truetype -bidi -debug -png -xinerama -xpm"
The graphics subsystem on the laptop (relevant lspci -nnk output):
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Dell Device [1028:01bd]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
Subsystem: Dell Device [1028:01bd]
Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Dell Device [1028:01bd]
or from lshw:
*-display:0
description: VGA compatible controller
product: Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 03
width: 32 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:16 memory:eff00000-eff7ffff ioport:eff8(size=8) memory:d0000000-dfffffff memory:efec0000-efefffff
*-display:1 UNCLAIMED
description: Display controller
product: Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2.1
bus info: pci@0000:00:02.1
version: 03
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: latency=0
resources: memory:eff80000-efffffff
Created attachment 323674 [details]
Xorg log for the 2.20.7 without uxa, contains segfault backtrace, built with -ggdb and splitdebug
addr2line -e /usr/lib64/debug/usr/lib64/xorg/modules/drivers/intel_drv.so.debug 0x45321 0x57802 0x7e5a1 0x8329c 0x456e9
/var/tmp/portage/x11-drivers/xf86-video-intel-2.20.7/work/xf86-video-intel-2.20.7/src/sna/sna_composite.c:991
/var/tmp/portage/x11-drivers/xf86-video-intel-2.20.7/work/xf86-video-intel-2.20.7/src/sna/sna_render.c:1366
/var/tmp/portage/x11-drivers/xf86-video-intel-2.20.7/work/xf86-video-intel-2.20.7/src/sna/gen3_render.c:2417
/var/tmp/portage/x11-drivers/xf86-video-intel-2.20.7/work/xf86-video-intel-2.20.7/src/sna/gen3_render.c:2869
/var/tmp/portage/x11-drivers/xf86-video-intel-2.20.7/work/xf86-video-intel-2.20.7/src/sna/sna_composite.c:543
Did you restart X after recompiling intel driver and before reproducing the crash? Please doublecheck that addresses in your trace are from the recompiled driver. Do you have any local patches applied to xf86-video-intel? Did it again today, rebooted after making the debug emerge and yes, the output seems to be correct, same addresses as I posted last time. No local patches applied to the package. Well, this trace seems to be incorrect since the line numbers doesn't make sense (by upstream). Try running X under gdb and get backtrace. You can connect to your computer from another one trough ssh and attach to running X: # gdb attach $(ps -C Xorg -o pid=) gdb stops the running process when attaching so you have to continue: (gdb) continue Reproduce the crash and get backtrace: (gdb) bt full You might need to copy more than one screen of gdb output to get all intel driver related info. Or probably easier is to get core dump and from that backtrace as described here: http://www.gentoo.org/proj/en/qa/backtraces.xml Also please attach here full build log for xf86-video-intel.
Upstream asked for full debug information. To get that change xf86-video-intel ebuild locally to add debug use flag:
-IUSE="glamor +sna uxa xvmc"
+IUSE="debug glamor +sna uxa xvmc"
and in src_configure to use it:
src_configure() {
XORG_CONFIGURE_OPTIONS=(
+ $(use_enable debug debug full)
$(use_enable dri)
$(use_enable glamor)
$(use_enable sna)
and then compile with debug enabled:
USE="debug" emerge -1 xf86-video-intel
Then reproduce the crash and send compressed Xorg log to chris at chris-wilson.co.uk
Note: debug flag will make quite big Xorg log files so you don't want to keep it enabled normally.
Sent full Xorg log to upstream Fixed in http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=8e9d64203428b344433ac8f86dc1f06d2c32529a Will be in next release. If you want to test you can try to apply the patch locally. The patch fixes the particular crash and there is a new driver version out with the patch incorporated. I am still experiencing crashes with the new driver in same configuration, will lodge a separate bug report? |