On Saturday October 11 2003 01:16 pm, Heather/Femme wrote:
help?
i've never seen this before am at a loss as to what to do or
where to look...
my system was OCed till last night..but vid problems are forcing
me to look at this issue further...
i was running Ksysguard to keep an eye on a program that tends to
have a memory leak.
ideas???
From what you wrote, I believe I've had a similar issue recently.
With the added variable that I run cooker 9.2+. In my case,
whenever I run pan and d/l from binary newsgroups, I need to close
pan before I do anything else, particularly with the files I just
d/l'd, or the X server sometimes loses connection and the screen
goes screwy or just black. Requires a cold shutdown for at least 30
seconds to a minute. Safer yet was not to close pan normally, but
to kill it with Ctrl+Alt+Esc. You might experiment with the same
for the app you suspect has a memory leak.
BUT, most problems like this are hardware related. I finally
found that reducing ram tweaks, specially pre-charge from 2T
(ticks) to 3, all but eliminates the pan problem. I also set Cas to
3, and disabled banking just to be cautious. I believe the real
problem is I foolishly bought Kingston DDR ram recently, instead of
Crucial or Corsair, as I knew I should'a. So much for payin
attention to rave Website hardware reviews. Of course with any oc'd
system, the first step should be to un-overclock, set default
values for FSB, multiplier, voltages, etc. Seems you've already
done that.
Don't bother with memtest86. It's not a very good ram test. But
you could try it first. Too often tho it doesn't find ram problems.
So get http://mersenne.org/gimps/mprime2212.tar.gzand run
./mprime -mand choose menu item 17 (torture test). Let it run
for hours. You're probly OK it it doesn't stop an give a hardware
error message (seti is not a substitute for this). As always, heat
could be the problem if errors are seen. Take the case cover off an
point a table fan directly into the box. Try again. Until
hardware error (and/or mis-configuration) possibility is eliminated
first, there's no sense lookin for software reasons for problems.
If you really wanna verify the hardware is solid as configured,
install the Mandrake 'cpuburn' rpm (it's on your CD's) and run the
module appropriate for your cpu. In your case Femme, I think that's
'burnP6'. It'd probly be wise to check with memtest86 and mprime
first tho. Another opinion (?), I'm beginning to believe there's
no sense overclocking new systems that are already wicked fast and
high Ghz. Hard to admit for an oldtime overclocker ;)
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
