Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jun 2003 17:12:20 -0700 (PDT)
From:      Julian Elischer <julian@elischer.org>
To:        Khairil Yusof <kaeru@pd.jaring.my>
Cc:        threads@freebsd.org
Subject:   Re: Guide for KSE testers?
Message-ID:  <Pine.BSF.4.21.0306041703390.5054-100000@InterJet.elischer.org>
In-Reply-To: <1054770782.765.10.camel@daemon.home.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi and thanks for trying it..

There are several things to keep in mind when debugging KSE.
Firstly, the action is spread between the kernel and the library.

Secondly, Only threads that are either running, or waiting on a kernel
resource are visible to the kernel.

If you have a "lockup" it is first important to distiguish between a
program lockup and a system lockup. (you'd be surprised how many people
don't give that information..)

For a system problem we need to check the scope of the lockup..
1/ can you ping the system?
2/ if X is not active, can you swith to other virtual consoles?
2A/ if yes, do you still get a 'password' prompt at the new console
if you enter 'root'
3/ does <CTL><ALT><ESC> work?


If you can get to the kernel debugger with <CTL><ALT><ESC>,
what does 'ps' show for that process?


depending on the answers we'll decide where to go next :-)


On 5 Jun 2003, Khairil Yusof wrote:

> With libmap.conf and kse much more stable now than before, I can finally
> test it out running day to day apps.
> 
> I don't however have much info on how to get debugging information that
> would help the KSE team.
> 
> Right now, there is a system lockup on my dual PIII system every few
> hours (much better than a few seconds a few weeks back).
> 
> How do I go about getting a stacktrace or something else, that could
> help the KSE team?
> 
> Just pointers to docs/faqs would be fine.
> 
> At least these are working relatively stable right now. (I'm not sure
> yet, what is causing the lockups)
> 
> evolution
> evolution-mail
> evolution-addressbook
> nautilus
> metacity
> mozilla-firebird
> gkrellm2
> gnome-terminal
> gnome-panel
> openoffice

That's pretty impressive..

As part of the debugging it is also probably worth seeing if you get
lockups using the N:N threads (libthr) option.

> 
> Keep up the great work.. KSE has made a big improvement in speed and
> response time for evolution-mail.
> 
> --



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0306041703390.5054-100000>