I ran with just X (no KDE) & Firefox with a Java applet & it hung after about 2 hours. This rules out Qt/KDE. After that I had to rebuild the kernel due to CRC error again, & because I had missed turning on DMA. I stayed in console mode for several hours with no problems. I then ran X/Firefox/Xterm/Xclock for about an hour, quit all X stuff then did emerge --sync & emerge system (2 minor items). Next morning the emerges had finished (no hang) so I started an emerge world (including glibc & kdebase) which finished with no problems. All this points to X as has been suggested. I'm currintly building a kernel with magic sysrq turned on.
On Mon, Feb 16, 2009 at 5:01 PM, Duncan <[email protected]> wrote: > Daiajo Tibdixious <[email protected]> posted > [email protected], excerpted > below, on Mon, 16 Feb 2009 13:05:14 +1100: > First, make sure you have the Magic SysRq option turned on in the > kernel. In menuconfig, that's Kernel hacking > Magic SysRq key, > 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. 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. I rebuild all the X11-drivers I had installed with no joy. Going to rebuild all of X, then try downgrading the drivers.
