On Mon, 11 Nov 2002 12:35 pm, you wrote: > Let me guess - you have an AMD processor on a KX133 / KT133 motherboard.
Not a bad guess 1.1G Athlon ABit KT7A mobo using the VIA KT133 chip. > This is normal for FVCool - it sits in an idle loop (basically just getting > the CPU to spin it's wheels, but not do anything) to work around a broken > chipset implementation. It sits in the lowest priority that it can, and > issues a "HLT" command to stop the processor if there is nothing for it to > do. > As a comparison - I'm not doing anything funky and here is my top output > last pid: 47682; load averages: 1.10, 2.41, 2.80 up 0+01:01:22 > 12:31:32 > 65 processes: 3 running, 62 sleeping > CPU states: 4.3% user, 92.2% nice, 2.7% system, 0.8% interrupt, 0.0% > idle Mem: 122M Active, 282M Inact, 61M Wired, 3040K Cache, 60M Buf, 31M > Free Swap: 512M Total, 512M Free > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 399 root 97 20 864K 444K RUN 21:16 88.48% 88.48% fvcool > Hope that sheds some light on it - there is some more info in > /usr/local/share/doc/fvcool that will tell you exactly whats going on. > Incidentally, you can get the same functionality out of hacking a kernel > file, but I cannot find the correct location to make the change they > provide in one of the readme files. Since I'm not a kernel hacker, I would > rather have the fvcool solution :) Thanks. Me too! Glad there is nothing amiss. Odd that fvcool works well in console and X/Windowmaker environments, but fails miserably in KDE. Oh well, all the Kapps I want will run in Windowmaker, anyway - and I like WM's simplicity :-) -- Regards, Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
