Jeff Vian wrote:
On Mon, 2004-07-19 at 19:03, Micheal wrote:No, the problem related to the very first posts here are NOT screensaver related because those of us that are having "random total lockups" can't ssh in and shut the thing down safely. If others are in the same boat as I am, the box won't even ping after the lockup. Those that are having screen saver-related issues, from what I can gather here, are able to ssh in from another machine.
On Mon, 2004-07-19 at 17:08, Rob Brown-Bayliss wrote:
On Mon, 2004-07-19 at 02:27, Joe(theWordy)Philbrook wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It would appear that on Jul 18, Rob Brown-Bayliss did say:
I have just changed my screen saver to a blank screen, it was an OGLWell I hope that works for you. In my case I found I could let power
screen saver so lets see.
management do the screen blanking with the old kernel, just as long as
So far so good. It seems to be working, as in no crashes for two days. But hell, screen savers causing a total lock up? Thats scary.
--
Rob Brown-Bayliss
______________________________________________________________________ The liar's punishment is not in the least that he is not believed, but that he cannot believe anyone else.
______________________________________________________________________
Yep, had the same problems here, went to a blank screensaver and no lockups. I did find, however that it was just X locked. I "could" ssh into the box and safely reboot it.
My poor .02
Micheal
The problem seems (from postings on this list) to be related to use of GL. If you pick a non-GL screensaver it usually is ok according to those that have had similar problems.
Also, I stand corrected about my supposed solution from before. It's the most bizarre thing... I was having a couple of lockups per day, switched my USB cable to a different slot and thought I had it solved. I went for a full 10 days without a lockup. Now all of a sudden, I've had four lockups over the past three days. I guess I didn't fix it after all. My screensaver has been completely disabled the whole time. I've also tried acpi=off as a boot parameter and have turned off everything I can think of in the BIOS to no avail.
My next plan of attack is to swap my ethernet cards out for two brand new ones, run a memory test with a boot CD, remove all USB in favor of PS/2, and if nothing else works, switch motherboards. If anyone has been having similar problems (especially someone with a similar hardware config as mine) please let me know.
FC2, dual opteron, MSI k8t master-FAR motherboard, USB mouse/kybd with KVM switch.
Cyrus
