> On Mon, Feb 07, 2005 at 08:27:42AM -0800, Bob Sanders wrote: > > 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 - > > Then, when it hang again, ssh in and killall xscreensaver. > > Well, a lockup happened again last night (of course *not* while I > was using the computer). Funny thing is, I can ping the locked > machine, and it responds as though everything was okay. But I > cannot ssh into the computer. ssh does not timeout (like it would > if the host were down); after I type "ssh host" and press enter, it > just sits there---I let it sit there for about 30 minutes before I > got impatient and hard-rebooted the machine.
Ssh will react like this when there is significant load on the target machine. Same thing happened to me when I had an ebuild that started forking like crazy. The system was so busy spawning and reclaiming processes that it appeared to freeze (even the screen saver was stuck). Are the lockups occurring at a consistent time? If so, you might be able to track down a cron or at task that might be hammering your system... > > > Look in /proc/driver/nvidia/agp/card > > ... > > If you have SBA and Fast Writes on, try turning them > > off - /etc/modules.d/nvidia > > I'm hesitant to try this, only because the lockups are so random. > It's been almost two weeks since it last happened; I have a feeling > that I could get lucky and it won't happen again forever (or it > could happen in the next five minutes). Either way, it's hard to > determine the solution when I make a change and then just wait. My lockups were from the nvidia drivers. Swapped out nvidia for a radeon card and had no lockups since. So do give this a try; if it eliminates the lockups then it will be well worth it for you. -- [email protected] mailing list
