Date: Mon, 02 Nov 2015 11:54:48 -0500 From: "John D. Hendrickson" <johnandsara2@cox.net> To: bugzilla-noreply@freebsd.org Cc: x11@FreeBSD.org Subject: Re: [Bug 204225] x11-servers/xorg-server crashes with segfault when creating new window Message-ID: <56379558.8020804@cox.net> In-Reply-To: <bug-204225-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-204225-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204225 > > Bug ID: 204225 > Summary: x11-servers/xorg-server crashes with segfault when > creating new window > Product: Ports & Packages > Version: Latest > Hardware: amd64 > OS: Any > Status: New > Severity: Affects Only Me > Priority: --- > Component: Individual Port(s) > Assignee: x11@FreeBSD.org > Reporter: pch-freebsd-bugs@u-1.phicoh.com > Flags: maintainer-feedback?(x11@FreeBSD.org) > Assignee: x11@FreeBSD.org > > Created attachment 162707 > --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162707&action=edit > X server log file > > After creating an X session with a few xterms, firefox, vtwm, pidgin, creating > a new window will often crash the X server. This never happened in the previous > version. > > Hardware is a thinkpad x201 with integrated intel video card. > > Stack trace from gdb: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 803406400 (LWP 100067/Xorg)] > 0x00000008012b1935 in _pixman_internal_only_get_implementation () > from /usr/local/lib/libpixman-1.so.0 > (gdb) where > #0 0x00000008012b1935 in _pixman_internal_only_get_implementation () > from /usr/local/lib/libpixman-1.so.0 > #1 0x000000080128f397 in pixman_image_get_format () > from /usr/local/lib/libpixman-1.so.0 > #2 0x00000008012472c6 in pixman_blt () from /usr/local/lib/libpixman-1.so.0 > #3 0x0000000805c606b8 in fbCopyNtoN () > from /usr/local/lib/xorg/modules/libfb.so > #4 0x000000000057dc5f in miCopyRegion () > #5 0x000000000057dfea in miDoCopy () > #6 0x0000000805c61294 in fbCopyArea () > from /usr/local/lib/xorg/modules/libfb.so > #7 0x00000008058011b6 in ?? () > from /usr/local/lib/xorg/modules/drivers/intel_drv.so > #8 0x000000000051fe8e in DamageReportDamage () > #9 0x00000000004ccaa9 in CompositeRegisterImplicitRedirectionException () > #10 0x00000000004cc899 in CompositeRegisterImplicitRedirectionException () > #11 0x00000000004ca1a6 in CompositeRegisterImplicitRedirectionException () > #12 0x0000000000467b05 in MapWindow () > #13 0x000000000043522b in ProcBadRequest () > #14 0x00000000004345e4 in UpdateCurrentTimeIf () > #15 0x000000000043de97 in remove_fs_handlers () > #16 0x000000000042919f in _start () > ---Type <return> to continue, or q <return> to quit--- > #17 0x000000080081d000 in ?? () > #18 0x0000000000000000 in ?? () > (gdb) > > I attached the X server log. > > #3 0x0000000805c606b8 in fbCopyNtoN () ./uxa/uxa-accel.c: fbCopyNtoN(pSrcDrawable, pDstDrawable, pGC, pbox, nbox, it's obviously telling you > #15 0x000000000043de97 in remove_fs_handlers () it could be bsd file handlers (or recent code added by linux hacks that hickups when not having new features*) i wrote to ask: if you can trace all functions to pixman why can't you show line of code is at fault ? especially on freebsd where "being fully sourced" should be easier than any other distro ? > #15 0x000000000043de97 in remove_fs_handlers () it looks like to me intel asks for (a GC) but that what breaks is freeBSD code added to X.org "fs_handlers". (i'm GUESSING if this post is honest that intel driver is ? using pixman to allocate screens it finds modelines for ? but i've not read X code line by line i'm sure i might have missed that) [ 86157.673] (II) intel(0): Modeline "1280x800"x0.0 57.59 1280 NOTE: you cannot be sure the intel driver didn't exit and that another program cause the actual segfault. you'd have to use gdb(1) to be sure. !!!!!! some people seem to have patens on inventing ways to create INTEL problems for intel consumers !!!!!! i use an intel laptop driver: never had an issue with it (X11R7.6) obviously: keep debugging and you'll know what to blame. make sure first you chose any kernel options right (ie, when you boot likely your text screen should change to small text - signifying X11R7 will load properly) you might revert to previous BSD version or use a different (ie VESA) driver in the mean time ------------------------- you know i never thought of that but the more file kernel features linux (or bsd) adds the more complicated it will be for software to run on both bsd and linux
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56379558.8020804>