Date: Tue, 23 Aug 2011 11:59:37 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: m irya <xmirya@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: xorg-dev + intel driver + KMS Message-ID: <20110823085937.GC17489@deviant.kiev.zoral.com.ua> In-Reply-To: <CAK8LArPHWe6-O7BR74EsDpi94Om%2B3rwfGcGAiUOMA435png-vw@mail.gmail.com> References: <CAK8LArPHWe6-O7BR74EsDpi94Om%2B3rwfGcGAiUOMA435png-vw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ivrYgu7Blr7TDhD9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 23, 2011 at 11:55:34AM +0300, m irya wrote: > Hello, >=20 > I'm currently evaluating the XOrg from xorg-dev svn repo + KMS-aware > intel driver (from the same repo) + KMS patches (8.1 patchset > currently) at recent -CURRENT. Everything works fine except for the > fact running VirtualBox Windows 7 guest makes Xserver crash. No 2D/3D > acceleration is switched on, but running it for 5 minutes is often > enough for the Xserver to coredump. The problem doesn't occur if > running it via VBoxHeadless and connecting via VNC, for example. > Xserver has no debug symbols complied in, however, some extracts from > the backtrace may be useful, if someone wants to investigate it: >=20 > #0 0x0000000802c12ccc in thr_kill () from /lib/libc.so.7 > #1 0x0000000802caf4cb in abort () from /lib/libc.so.7 > #2 0x000000000046ba7e in OsAbort () > #3 0x00000000004785d7 in ddxGiveUp () > #4 0x0000000000469a8d in AbortServer () > #5 0x000000000046a20f in FatalError () > #6 0x000000000046ae41 in OsInit () > #7 0x00000008029a552e in pthread_sigmask () from /lib/libthr.so.3 > #8 0x00000008029a56bc in pthread_sigmask () from /lib/libthr.so.3 > #9 0x00007ffffffff003 in ?? () > #10 0x00000008029a55e0 in pthread_sigmask () from /lib/libthr.so.3 > #11 0x0000000000000000 in ?? () > #12 0x0000000000000000 in ?? () > ... > #33 0x0000000000000006 in ?? () > #34 0x0000000802cb1fb6 in memcpy () from /lib/libc.so.7 > #35 0x0000000000000043 in ?? () > ... > #135 0x0000000000000004 in ?? () > #136 0x000000000000002f in ?? () > #137 0x00000008044edd3f in drm_intel_gem_bo_map_gtt () from > /usr/local/lib/libdrm_intel.so.1 > #138 0x00000008042b5b47 in intel_uxa_pixmap_put_image () from > /usr/local/lib/xorg/modules/drivers/intel_drv.so > #139 0x00000008042b72d9 in intel_uxa_put_image () from > /usr/local/lib/xorg/modules/drivers/intel_drv.so > #140 0x00000008042ccba7 in uxa_put_image () from > /usr/local/lib/xorg/modules/drivers/intel_drv.so > #141 0x00000000004df13a in DamageRegionAppend () > #142 0x0000000000438181 in ProcPutImage () > #143 0x0000000000439b55 in Dispatch () > #144 0x000000000042de25 in main () The backtrace is not useful at all. You need to compile and install the server itself, ddx driver and libdrm wi= th debug information, then get the backtrace. Also, check the kernel messages right after the server crashed. --ivrYgu7Blr7TDhD9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5Ta/kACgkQC3+MBN1Mb4gqCQCdEnMj3Dl3HlPRHNPXXtYsGrT4 cnEAoMKH9dENKWtGNRGWKbdEaFsxm9+o =XXdd -----END PGP SIGNATURE----- --ivrYgu7Blr7TDhD9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110823085937.GC17489>