> 
> Now, I know this is about the most vague question I can ask, but
> does anyone have any suggestions on likely places to start looking?
> I haven't changed any hardware, so I'm guessing that it's a software
> issue.  I have no idea what is causing the lockup.
>

Typically it's the graphics drivers hanging the AGP bus.  But you didn't
memtion if you were running xscreensaver.  If you're running xscreensaver,
do - 

   rc-update add sshd default
   /etc/init.d/sshd start

Then, when it hang again, ssh in and killall xscreensaver.

 
> If I had to make a random guess, I would guess it's the nvidia
> drivers (nvidia-kernel and nvidia-glx version 1.0.6629-r1).  But
> that's just a totally wild guess :)
>

Look in /proc/driver/nvidia/agp/card

crosis rsanders # cat /proc/driver/nvidia/agp/card
Fast Writes:     Supported
SBA:             Supported
AGP Rates:       8x 4x
Registers:       0x1f000e1b:0x00000000

If you have SBA and Fast Writes on, try turning them
off - /etc/modules.d/nvidia

Gernerally either of the above will fix most Nvidia/X related hangs.
Though on older VIA based motherboards, (Pre-K{T,M}400A, you might
consider an upgrade.  Note that some of them had some AGP noise
issues, not all of them.

For general system testing - not graphics, but it will rule out other
hardware problems, there is - app-benchmarks/stress.

For Gfx issues, I typically, run - x11-misc/rss-glx
by launching 3 of the OpenGL screen savers from the rss-glx
package while running 5 minute intervals of stress in another
term with paramters to cause up to half of swap to be used.

The other useful tool I've found is setiathome.  It doesn't
do anythign for Gfx testing, but it does help out in keeping
the cpu, cpu bus, memory bus, and ide/scsi bus active enough to
remove doubts that those might be a problem.

Bob
-- 
-  

--
[email protected] mailing list

Reply via email to