Just to clarify, the kapm-idled problem is just for
kernel2.4.3? I hate seeing gkrellm going nuts on CPU
while I'm just sitting there in a VI terminal.
--- Orlin Damyanov <[EMAIL PROTECTED]> wrote:
> For me Mandrake 8 has been quite stable and runs
> smoother than Mandrake
> 7. I had 7 installed before and the Mandrake 8
> update option didn't work
> for me. Thank god I backed up all the data before
> upgrading to 8. I had
> to reformat the disks to get it to install 8. May be
> it's just my case
> but be careful if you plan to "update" your Mandrake
> 7 to 8.
>
> > On jeudi, mai 17, 2001, at 09:26 ,
> [EMAIL PROTECTED] wrote:
> >
> > Has anybody tried 2.4.4 with Mandrake 8?
>
> I have Mandrake 8 on 2 Dell PowerEdge 1300 servers -
> one bi-processor
> and the other single processor, both Pentium III 700
> Mhz, 512 MB ECC
> RAM, Ultra2 LVD SCSI, etc, ATI Rage II (Mach64)
> video card, IntelPro
> network adaptor.
>
> I successfully compiled the 2.4.4 kernel and
> upgraded the bi-processor
> one.
> I didn't want to stay with Mandrake's 2.4.3 kernel
> since the 2.4.4
> corrected 2 security holes - one of them affecting
> ftp transfers. (For
> 2.4.3 problematic issues see below).
>
> The other one bugging me in Mandrake 8 (2.4.3) is
> that the power
> management module is included in the kernel. I have
> no use for it on a
> server and it really messes up my CPU readings. I'm
> talking about the
> famous[kapm-idled] process with PID 3 :-)
> USER PID %CPU %MEM VSZ RSS TTY STAT
> START TIME COMMAND
> root 3 86.6 0.0 0 0 ? SW
> May09 11216:48
> [kapm-idled]
>
>
> The problem I had was the second server. The 2.4.4
> compiled well but I
> couldn't start X. Something to do with the fonts.
> Well, I'll try again
> but maybe it's better to wait for Mandrake's RPM for
> the 2.4.4 kernel
> although I heard they have no plans of releasing the
> 2.4.4.
>
>
> ===================================
> Problems in the 2.4.3 kernel:
> ===================================
> (as quoted by Mihg on slashdot)
>
> "The reader-writer semaphore implementation is
> broken, resulting in
> processes getting stuck in the D state in
> down_semaphore. Heavily
> threaded programs (like Mozilla) are most likely to
> hit this bug,
> resulting in lots of stuck threads and an unusable
> program.
>
> (Nothing actually used the rw-sems until fairly
> recently, which is why
> this bug went undetected for so long.)
>
> Also fixed: the iptables FTP connection tracking
> security hole, some
> potential filesystem corrupting bugs and a bunch of
> other bugs that
> weren't likely to affect anybody.
>
> And Dave Miller's zerocopy networking changes were
> merged in, which is
> pretty cool."
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
