Summary: | high cpu usage by kded if using knemo when a ppp connection exists | ||
---|---|---|---|
Product: | [Applications] knemo | Reporter: | yamal <kubuntu> |
Component: | general | Assignee: | John Stamp <jstamp> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
yamal
2007-05-21 13:49:36 UTC
Hi, there is already a ticket (https://bugs.kde.org/show_bug.cgi?id=138182) about the high CPU load with the sysbackend. I still cannot reproduce it, some say it depends on VPN connections, others like you say it happens with PPP. I personally can only test PPP and ETH and it works perfect for both types. There were also some suggestions that it only happens with certain (newer) kernels. Could you please comment on this and maybe test if the current version 0.4.7 still has the bug? Thank you for your quick reponse. I had noticed the other bug, but since it makes no mention of anything ppp/vpn related, and reports only 50-75% cpu usage, I assumed it was a different issue. Bug still happens in 0.4.7, basically no difference at all; as soon as a ppp connection exists and knemo is running kded uses all cpu, even when there's little or no traffic. Doesn't matter which of the two is started first. Problem indeed only happens with "sys" backend, "nettools" seems fine with very low cpu usage. System is a 32 bit install on AMD64 with 2 ethernet cards (ppp on eth1) and one wireless network card; kernel is Ubuntu's 2.6.20-15, pppd version 2.4.4, KDE 3.5.6. Also tried removing all the interfaces from knemorc that are (apparently) there by default but don't exist on my system like eth2,ra0,ra1,wlan1 without any result or effect whatsoever. Thanks also for your quick response! :-) I think I will get a live CD of a distribution using a more recent kernel than my Mandriva does and see if I can reproduce this with a PPP connection... Thanks again! Sometimes a quick and detailed response can push me more to fix a bug than a bunch of votes... Could you please test http://www.eris23.de/knemo/knemo-0.4.7-2.tar.bz2 It solves the issue for me. Seems to do the trick here too. When monitoring only the ppp connection, cpu usage of kded stays 0.0% most of the time. For every other monitored interface (eth0, eth1, ath0, sit0) cpu usage increases by 1.5-2.0% per additional interface. Whether or not a ppp connection exists makes no difference anymore. Job well done I'd say. Marking as resolved. Fixed in KNemo 0.4.8 Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug. |