Date: Wed, 24 Aug 2011 02:30:48 +0300 From: Andrey Kosachenko <andrey.kosachenko@gmail.com> To: freebsd-x11@freebsd.org Subject: Re: xorg-dev + intel driver + KMS Message-ID: <4E543828.2040703@gmail.com> In-Reply-To: <20110823085937.GC17489@deviant.kiev.zoral.com.ua> References: <CAK8LArPHWe6-O7BR74EsDpi94Om%2B3rwfGcGAiUOMA435png-vw@mail.gmail.com> <20110823085937.GC17489@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Konstantin, 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 with > debug information, then get the backtrace. > > Also, check the kernel messages right after the server crashed. I second that. Similar issues observed over here (latest sources from CURRENT, amd64, all.8.1.patch + all instruction from wiki page are followed). Both (xorg and xorg-dev) are affected (though I'd like to admit that with legacy xorg from standard ports tree (in comparison to xorg-dev) crashes happened way more often). gdb backtrace: http://pastebin.com/ZzpTHar9 Xorg.log: http://pastebin.com/s2bgpF07 messages log content (around Xorg crash): http://pastebin.com/g3qHvNyB hw.dri.0.info.i915_error_state: no error state collected PS: what interesting is that mentioned core dump is somewhat outstanding. Saying that I meant that earlier all crashes I saw (~15 for the last week) happened around *uxa_put_image() (the same place described in previous post of this thread). I didn't report about those crashes as I thought you are not interested in them (it is not a kernel stuff). Anyway, if you consider the info above helpful, need to acquire more or smth. just let me know. thanks! -- WBR, Andrey Kosachenko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E543828.2040703>