Re: [Sheflug] Strange freezes

[Mark Broadbent <markb [at] xxxxxxxxxxxxxx>]

On Thu, 2003-11-20 at 13:32, José Luis Gómez Dans wrote:
> Hi,
>     Over the last couple of days, I have been experimenting a number
> of ermm... "unexpected behaviours" running Linux. Basically, X freezes
> of sorts: I can move the mouse around, but the keyboard and windows
> and everything don't respond. So far, I have successfully ssh'ed into
> the box and found that there wasn't a particular task that was running
> amok: only that the cpu usage was close to 100%, and it was all
> system, suggesting that something was running amok in the kernel
> itself. I tried getting rid of a few modules (sound and all that), but
> no changes.
> 
>     I then restarted KDM (restart X and start KDM), and logged in
> normally. HOwever, as KDE was loading, X froze again. This time, the
> mouse would not move. ssh allowed me to shutdown cleanly, and restart
> again without any troubles.
> 
>     I am using the 2.4.22 kernel with Con Kolivas patches. It usually
> works fine (it still skips sounds, but...), and I am not sure whether
> this is an issue. On the other hand, I've been using it for a few
> weeks (or even a month or so) without major problems. I can't think of
> anything I've done to the system, as I've mostly been LaTeXing and
> compiling programs.
> 
>     I suspect that this could be graphics card related (apart from the
> network card, it was the only module that seemed to be used when I
> ssh'ed in). I use DRI with the r128 module and X 4.2.1. However, this
> behaviour is new, and has only started showing up in the last couple
> of days.
> 
>     Hints?

I hate to be a me too but I've come across the exactly same problem
recently.  

I am running a 2.4.22 kernel with CK patches applied (and have run a
number of previous kernels with the CK patches applied) and I had no
problems.  I thought it may have been my binary-only nvidia module and I
removed the XRender extension (but it has been working with the same NV
module version for ages).  The only thing I really changed was I used
GCC v3.2 instead of v2.95 and I believe that is where the problems may
have begun (although the NV module was also compiled with 3.2 instead of
2.95 at the same period).  I have now reverted to 2.95 and it became
more stable (maybe an avenue to try).

BTW System specs are:

NV GF3
X  4.3.0
Kernel 2.4.22 w/ latest CK patches


All Best
Mark


___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.