Christopher M. Jones on 25 Jun 2008 07:25:11 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] How to diagnose a lockup?

I did find a note on the LinuxMCE website referencing high cpu usage by 
X, caused by the 'sync to vblanc' option. Disabling this in 
nvidia-settings seems to have fixed the problem.

And thanks to all who offered suggestions.

Stephen Gran wrote:
> On Mon, Jun 23, 2008 at 01:08:17PM -0400, Christopher M. Jones said:
>> When your system locks up, what do you do to find the cause of it?
>> And a related question: when an app segfaults, what does this mean and 
>> what can I do about it?
> Assuming this is mythtv, and that you mean mythtv is locked up, rather
> than the entire machine:
> mythtv will lockup and segfault randomly.  Set a button on your remote
> to restart X.
> A segfault is caused by an invalid memory reference (trying to access
> memory at an address that it doesn't own, etc).
> For debugging mythtv errors, look in ~mythv/.xsession-errors and
> /var/log/mythtv*.  Occasionally something might be written to another
> log (/var/log/syslog being your best bet), but usually not.
> If it is in fact the entire machine locking up, get rid of those binary
> only nvidia drivers and use something debuggable and fixable.  Just a
> guess :)
> ------------------------------------------------------------------------
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --
> Announcements -
> General Discussion  --
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --