similar to: too many wakeups/sec?

On Wed, Oct 21, 2009 at 5:53 PM, Karl Heyes <karl at xiph.org> wrote: >> I'm seeing quite a few wakeups/sec in icecast2 2.3.2 on Debian Testing. >> In fact, whether icecast is doing anything or not, powertop reports 44.3 >> wakeups per second. This is pretty big number, on my laptop it means >> icecast alone is responsible for every third wakeup on idle. > >

PowerEdge 2850 with PERC SCSI RAID controller. 16GB RAM Dual Intel(R) Xeon(TM) CPU 3.00GHz Using megaraid driver and xfs on 3x 300GB SCSI disks as /dev/sdb (total 572GB) (RAID-5) Stock Centos 6.4 x64, everything updated. Kernel : 2.6.32-358.2.1.el6.x86_64 #1 SMP My Load always shows : top - 10:30:21 up 23:09, 1 users, load average: 0.99, 0.96, 0.79 yet there is no services what-so-ever

Hi all ! Le mardi 8 d?cembre 2009 05:36:53, Jussi Kukkonen a ?crit : > > The valgrind output seems to indicate a leak in libxml2, I'm gonna try > > to see if this is linked to the way the icecast or libxml package is > > compiled/patched in debian, but I'm not too familiar with this kind of > > problems, so if you have something to say about this issue, I'd

Hi, My laptop runs a local IMAP server so that I'm immune from breaking my mail client, and when playing around with powertop I discovered that Dovecot (in particular imap-login) wakes up every 1000ms and then every 50ms even when no clients are connected. A bit of stracing shows this: gettimeofday({1180875699, 667917}, NULL) = 0 <0.000010> poll([{fd=7,

hello tincers, when I on battery on my notebook, running powertop, I get nic:<tinc-net-name> as the most power consuption resource in my notebook just after the screen. This happens no matter if I have traffic or not. I am not really sure that if this is really a tinc fault or a tap/tun implementation that never sleeps. any advice? -------------- next part -------------- An HTML

Le jeudi 13 mai 2010 05:46:12, jaromil a ?crit : > re all, Hi, > this patch has not been integrated in Debian yet, hence the Icecast2 > package still segfaults after filling up all the memory with its leak. > > as this is a critical bug, while it seems that the current Debian > mantainer for the icecast2 package has abandoned its duty, i'm kindly > asking

Hi, I've been noticing a huge memory usage on Icecast 2.3.2 on multiple debian instances. They are using like 100 MB after a day and going on until they hit like 1 GB.. So I ran one in valgrind, and killed it after ~24h, here is the output: ==30481== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 38 from 3) ==30481== malloc/free: in use at exit: 44,448,584 bytes in 44,470 blocks.

From: Colin Ian King <colin.king at canonical.com> trivial fix to spelling mistake in an error message. Signed-off-by: Colin Ian King <colin.king at canonical.com> --- tools/virtio/virtio_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virtio/virtio_test.c b/tools/virtio/virtio_test.c index 76d6f583c249..0fecaec90d0d 100644 ---

From: Colin Ian King <colin.king at canonical.com> trivial fix to spelling mistake in an error message. Signed-off-by: Colin Ian King <colin.king at canonical.com> --- tools/virtio/virtio_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virtio/virtio_test.c b/tools/virtio/virtio_test.c index 76d6f583c249..0fecaec90d0d 100644 ---

On 09/12/2009 16:59, Romain Beauxis wrote: > Hi ! > > Le mardi 8 d?cembre 2009 19:59:23, Karl Heyes a ?crit : >>> But since you asked, attached are the missing frees for icecast2_2.3.2-4 >>> in a totally untested drive-by-patching manner. Like I said the -kh17 I >>> also happened to have did not have this specific code at all and the >>>

Hi, I have quite a few low-end development/test servers running continuously and I would like to better manage their power consumption. I have found interesting information on how to perform CPU scaling (e.g. [1] or [2]). But I cannot find if there is a way to (software) monitor power consumption on CentOS (or other such data like CPU temperature, fan speed etc.). What I read so far is that

This may be a stupid question - but why does ssh-agent fork off a child and then exec the subcommand in the *parent* process? It forces the agent in the child process to poll the parent, so it can exit when the parent finishes. If the agent was the parent process, it could use wait() instead. I'm sure there's some reason. It'd be nice to take ssh-agent off the list of polling

Hello, I was not happy with the power consumption of CentOS 6 x86_64 on a new Lenovo Thinkpad x220 Tablet and I worked on reducing it. I just wanted to share with the list one of the changes which gave me the most significant improvement. As per http://www.williambrownstreet.net/blog/?p=387, add the following kernel arguments to the GRUB boot configuration: pcie_aspm=force

https://bugs.freedesktop.org/show_bug.cgi?id=101404 Bug ID: 101404 Summary: GTX 970M (GM204-A) not powered off when not in use (DynPwr in stead of DynOff) Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium

Howdy, So, I have a Thinkpad P70 with hybrid graphics. 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M600M] (rev a2) that one works fine, I can use i915 for the main screen, and nouveau to display on the external ports (external ports are only wired to nvidia chip, so it's impossible to use them without turning the nvidia chip on). I now got a newer P73 also with the

Hello guys, Did anyone noticed how green CentOS 6 is compared to the previous release? I've been running a couple of "CentOS 6" VMs (on our vSphere environment) for the last couple of weeks and noticed a BIG difference when it comes to CPU usage when the VM is completely idle. I would like to share what I've seen in our environment: PfSense 2.0 (FreeBSD) VM: 40 Mhz CentOS

On 2018/08/03 12:07, Jason Wang wrote: > On 2018?08?02? 17:23, Jason Wang wrote: >>>>>>> >>>>>> No need to enable rx virtqueue, if we are sure handle_rx() will be >>>>>> called soon. >>>>> If we disable rx virtqueue in handle_tx and don't send packets from >>>>> guest anymore(handle_tx is not called), so

On Tue, Apr 26, 2016 at 03:35:53AM -0400, Jason Wang wrote: > We don't stop polling socket during rx processing, this will lead > unnecessary wakeups from under layer net devices (E.g > sock_def_readable() form tun). Rx will be slowed down in this > way. This patch avoids this by stop polling socket during rx > processing. A small drawback is that this introduces some overheads

On Tue, Apr 26, 2016 at 03:35:53AM -0400, Jason Wang wrote: > We don't stop polling socket during rx processing, this will lead > unnecessary wakeups from under layer net devices (E.g > sock_def_readable() form tun). Rx will be slowed down in this > way. This patch avoids this by stop polling socket during rx > processing. A small drawback is that this introduces some overheads

Hello, I have been learning Rails for several weeks now. I am working through Michael Hartl''s tutorial and other various things. My question is basically regarding what type of environment to do my development in. First, some background: I have used different linux distros on and off throughout the years, so it was easy and familiar for me to set up my desktop computer with Mint and