Daiajo Tibdixious <[email protected]> posted [email protected], excerpted below, on Thu, 19 Feb 2009 09:29:39 +1100:
>> MAGIC_SYSRQ is the config option key. > > When the system is not frozen, SysRq-I works, i.e. everything gets > killed. When the system is locked up, none of the magic keys work at > all. That sucks, but means it's a hard kernel lock. It's so scrambled it either can't even hear the SRQ combo or it can but it doesn't trust itself to write anything anywhere at all. Well, at least that does tell us something, that it's definitely kernel, not userspace, and that it's serious. > With just X running with 1 Xterm, it doesn't hang over 2 days, even with > other things like firefox being used for less than an hour. Leave > firefox up for more than 1 hour & it still hangs. xterm by itself is pretty stressless. firefox, perhaps unfortunately, much more of a workout. Do you perhaps have say flash enabled? Try disabling both it and scripting, and turn animation to one-time-thru only, and see if that has an effect. That would turn down FF's usage and make it a bit more stable. You could also try nothing but a nice long remerge from that xterm. Both of these should exercise memory, etc, a bit, without doing anything too fancy with 3D or something like flash that's known less-than-stable. > I rebuild all the X11-drivers I had installed with no joy. Going to > rebuild all of X, then try downgrading the drivers. Good ideas. It could well be the video driver. That's the likely X culprit when it comes to kernel crashes, since that's what gets its hands on the hardware enough to scramble the kernel, too. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
