xorg-dev + intel driver + KMS
Andrey Kosachenko
andrey.kosachenko at gmail.com
Wed Aug 24 09:12:13 UTC 2011
On 24.08.2011 11:13, Kostik Belousov wrote:
> 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=-g
> cd $SRC/lib/libc
> make obj&& make all install DEBUG_FLAGS=-g
> cd $SRC/lib/libthr
> make obj&& make all install DEBUG_FLAGS=-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.
ok, thanks for instructions: will do and let you know as soon as I'll be
able to reproduce it (again, with xorg-dev it happens more seldom,
sporadically and I've no exact STR for it)
> 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.
No, I don't use VB at all.
In the vast majority of cases I've observed so far crashes took place
while was working in browser (cwww/chromium). One more thing (well... I
know it sounds a bit odd... but still): it never crashed during surfing
heavy pages or audio/video playback but on submitting simple text
messages (issue tracking system, code review tool, wiki and so forth).
--
WBR,
Andrey Kosachenko
More information about the freebsd-x11
mailing list