When sl client crashes X sooo damn bad that neither
Ctrl-Alt-Backspace ( kill X server ), nor
Ctrl-Alt-F2 ( go to virtual-terminal-2 ), nor
Ctrl-Alt-Del ( kill entire machine-session ), work
try
Alt-SysReq-S ( sync the disk )
Alt-SysReq-U ( emergency unmount, remounting everything readonly )
Alt-SysReq-B ( boot-immediately )
At least Sync/Umount/Boot'll mean less corruption of our filesystems. . .
BTW, you may have to go into your YAST/admin prog, and "enable" Magic Sysreq Keys.
===========
Why do I need this technique?
crashes of X, obviously. . .
How do I know sometimes it's X?
Well, it /probably/ sometimes is X, since often SL won't restart while claiming that it "requires 32-bit", even though it worked in 24-bit, not one minute ago...
The rest of the crashes give different results, or take-down my machine completely.
AMD X2, 4GB ECC RAM
BUG: sl uses only 1 cpu-core, making it very-hot, according to the high-fan-speed, rather-than spreading-out the load over 2 cores!
ATI HD2400XT/256MB, Catalyst 7.12 drivers ( the most recent, as of this posting )... ATI drivers are all 24-bit, so making SL require 32-bit means locking-out all ATI customers, so I believe it's just a problem with /part/ of the SL-client. . . probably. . .
-shrug-
this is posted as a FYI, not expecting any response.
Gonna try an alternative build, to mitigate the system-kills. . .
and no, it isn't the PSU: a 600w 300kh MTBF unit isn't overloaded on so minimal a machine as this, though the wall-power it's getting may be too flaky, causing /some/ of the crashes ( no UPS at the moment ).
Also, I wonder why it sometimes goes into inert-mode for awhile?
using 1.18.5.3
Cheers,