* William Kenworthy <[EMAIL PROTECTED]> [10-02-2003 00:21]: > In have had this problem with a standard athlon t-bird 1.4 It started > when gnome2/gcc3.2 came out. Found that cflags, specifying i686 instead > of athlon helped but didnt cure the problem. Extra cooling also didnt > do a thing, despite a 10 degree C temp drop under full load. A curious > problem was nautilus and setiathome created instant hard lockup, other > applications took awhile under load plus there were random lockups under > no load. > > Cure was winding the clock speed back to 1.3G (underclocking). Very > unsatisfactory, and I am still suspicious of something in > gnome2/gcc3.2.x has caused the problem - otherwise, why would a system > that was perfectly stable change at the exact time of this update. > > Unfortunately, I have to use this system as my desktop/workstation, so > have left it at 1.3G.
In fact, I have only started to notice the problem after I did an update of gcc to its latest version. I thought about glibc because verything is linked against it. Gcc should be used only to build the programs (isn't it?), so would be an issue just for newer compiled binaries. Well, I just rebooted computer, running for 12 minutes with glibc without those cflags, high load (2.52), heavy dsk access, and still no crash. Running gentoo kernel. I'll let you know if system crashes yet again. -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil |
msg00943/pgp00000.pgp
Description: PGP signature
