kanenas wrote: > 3. This is the only SuSE system besides 10.1 where a reboot "makes things ok > for a while, then shtuff lapses into an almost predictable pattern of > problems". 10.1 is guilty too, but does the dirty deed with much less > frequency. >
You know, I hate to say it, but my experience is that this is a classic symptom of bad RAM. Have you run something like MEMTEST86 to verify that's not your issue? I've had systems with bad RAM where Windows would run OK most of the time but Linux would have all kinds of problems. I had one system (actually running FreeBSD) that had a SIMM with two stuck bits. The system would run great for about two days, then some important kernel structure would hit the defective memory locations and the system would lock solid. That took a lot of head-scratching to figure out. 10.2 has been quite stable for me ever since I disabled zmd. ;) That said, I'm on 32-bit platforms, and it's possible you're hitting some bug specific to 64-bit systems. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
