Date: Wed, 24 Aug 2011 11:13:03 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Andrey Kosachenko <andrey.kosachenko@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: xorg-dev + intel driver + KMS Message-ID: <20110824081303.GG17489@deviant.kiev.zoral.com.ua> In-Reply-To: <4E543828.2040703@gmail.com> References: <CAK8LArPHWe6-O7BR74EsDpi94Om%2B3rwfGcGAiUOMA435png-vw@mail.gmail.com> <20110823085937.GC17489@deviant.kiev.zoral.com.ua> <4E543828.2040703@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--XdILnuIpG7ZSfS+c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 24, 2011 at 02:30:48AM +0300, Andrey Kosachenko wrote: > Hi, Konstantin, >=20 > On 23.08.2011 11:59, Kostik Belousov wrote: > >The backtrace is not useful at all. > > > >You need to compile and install the server itself, ddx driver and libdrm= =20 > >with > >debug information, then get the backtrace. > > > >Also, check the kernel messages right after the server crashed. >=20 > I second that. > Similar issues observed over here (latest sources from CURRENT, amd64,=20 > all.8.1.patch + all instruction from wiki page are followed). Both (xorg= =20 > and xorg-dev) are affected (though I'd like to admit that with legacy=20 > xorg from standard ports tree (in comparison to xorg-dev) crashes=20 > happened way more often). Does it happen with VirtualBox, or not ? >=20 > gdb backtrace: > http://pastebin.com/ZzpTHar9 >=20 > Xorg.log: > http://pastebin.com/s2bgpF07 >=20 > messages log content (around Xorg crash): > http://pastebin.com/g3qHvNyB >=20 > hw.dri.0.info.i915_error_state: no error state collected >=20 > PS: > what interesting is that mentioned core dump is somewhat outstanding.=20 > Saying that I meant that earlier all crashes I saw (~15 for the last=20 > week) happened around *uxa_put_image() (the same place described in=20 > previous post of this thread). I didn't report about those crashes as I= =20 > thought you are not interested in them (it is not a kernel stuff). >=20 > Anyway, if you consider the info above helpful, need to acquire more or= =20 > smth. just let me know. Again, the backtrace is not useful. To make it useful, debugging symbols must be compiled into the dso loaded into the process. I highly suspect that the real backtrace ends at the frame 10. Try to start with compiling rtld/libc/libthr with debugging symbols. It is enough to do cd $SRC/libexec/rtld-elf make obj && make all install DEBUG_FLAGS=3D-g cd $SRC/lib/libc make obj && make all install DEBUG_FLAGS=3D-g cd $SRC/lib/libthr make obj && make all install DEBUG_FLAGS=3D-g uxa faulting might be an indicator of the bug in the KBI of the new Intel driver, but may be a genuine Xorg/ddx driver bug. Is it only possible to reproduce the issue with VirtualBox installed ? Note that VB has some ugly bugs with the handling of fictitious pages in the kernel module, the area which is overly important for the GEM and which is patched by the drm patch. --XdILnuIpG7ZSfS+c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5Uso8ACgkQC3+MBN1Mb4h0oACg0IuKHzc71QbGEBReO9JRcEPI HssAnjvoj52fYOztbpIoyR1fRVLxK1Xt =bOC4 -----END PGP SIGNATURE----- --XdILnuIpG7ZSfS+c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110824081303.GG17489>