Xorg Crashing - Since Update

[Brian A. Seklecki]

You can use ktrace/ktruss + kdump on the X.org or the Opera process, but
that might not be as revealing as a core dump.  Be aware that running X
or Opera in ktrace has a performance offset.

~lava

On Sun, 2006-02-05 at 22:16, Rob Clark wrote:
> Hello,
> 
> I've searched google and site:freebsd.org for this issue,
> and I see nothing like it, nor on the mailing lists. I hope
> this is the correct place to post, if not please let me
> know where it would be more welcome.
> 
> FreeBSD Version: FreeBSD 6.0-STABLE FreeBSD
> 6.0-STABLE #0: Sat Jan 28 18:35:36 EST 2006 
> 
> Problems with: xorg-6.9.0 & Opera 8.51 for FreeBSD
> 
> Problem I'm having is Xorg crashes when using Opera - this
> seems to have only started since I updated ports on
> 2006.01.23.0611. (I can provide the full port update log if
> needed).
> 
> Clicking on a single Opera button, or a hyperlink in
> the browser crashes Xorg (without warning) and takes the
> system straight to user console mode.  This is a random
> occurence, and seems to follow no pattern.  I can use Opera
> for many hours or just a few minutes, this behavior is
> unexpected.  It's happened 5 times thus far.  I can find no
> way to intentionally reproduce the crash.
> 
> The only pertinent info I see relating to this problem is on
> the console when X crashes (as follows):
> 
>    *** be the reason for the server aborting.
> 
> Fatal server error:
> Caught signal 11.  Server aborting
> 
> 
> Please consult the The X.Org Foundation support
>          at http://wiki.X.Org
>  for help.
> Please also check the log file at "/var/log/Xorg.0.log" for
> additional informati on.
> 
> X connection to :0.0 broken (explicit kill or server
> shutdown). /usr/X11R6/bin/xinit:  connection to X server
> lost. opera: Fatal IO error: client killed
> Failed to load groupfile:
> XIO:  fatal IO error 2 (No such file or directory) on X
> server ":0.0"      after 602187 requests (602154 known
> processed) with 0 events remaining. xterm:  fatal IO error
> 32 (Broken pipe) or KillClient on X server ":0.0" xterm: 
> fatal IO error 32 (Broken pipe) or KillClient on X server
> ":0.0" xterm:  fatal IO error 32 (Broken pipe) or KillClient
> on X server ":0.0" xterm:  fatal IO error 32 (Broken pipe)
> or KillClient on X server ":0.0" xterm:  fatal IO error 32
> (Broken pipe) or KillClient on X server ":0.0" Gdk-ERROR **:
> X connection to :0.0 broken (explicit kill or
> server shutdown). $
> 
> I do not see anything unusual in the /var/log/Xorg.0.log -
> then again, I'm not sure what I should be looking for.
> 
> I've tried monitoring top while Xorg and Opera are running,
> It doesn't seem like a memory leak with opera. The only
> thing suspicious is when scrolling in Opera the Xorg entry
> in top goes from RUN to *giant then back to system - mozilla
> doesn't seem to follow this behavior (I've only tested
> mozilla for a short period).  Scrolling does not, however,
> crash X - only clicking within the Opera browser makes this
> happen (again, there is no pattern to follow and repeating
> the same click on the same link will not reproduce it).
> 
> Any help would be appreciated since I use this server in a
> production related evironment.
> 
> Thanks,
> Rob
>