public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <tom@rymes.net>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>,
	"IPFire: Tremer, Michael" <michael.tremer@ipfire.org>
Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog
Date: Wed, 21 Jan 2026 19:49:04 -0500	[thread overview]
Message-ID: <DF703D68-1844-4AE8-849F-01AD1F48242A@rymes.net> (raw)
In-Reply-To: <c077418d-deb1-4d78-9d69-5430b68418ea@ipfire.org>

Matthias,

I always get your emails to the list, followed by a second message that your emails aren’t appearing on the list. I’m guessing the issue is that you are not receiving a copy of your own e-mails?

Either way, it always seems to be working properly to me.

Tom

> On Jan 21, 2026, at 5:52 PM, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> 2cd try:
> For reasons unknown to me, my Mails no longer appear on the list, even
> though I can send them there without any errors.
> 
> Therefore: next attempt - plus CC to MT [Hi Michael... ;-) ]
> 
> -----------------
> 
> Hi,
> 
> just in case that this happens to somebody else:
> 
> Some days ago I made a fresh install of Core 199 with a new machine and
> rather old cpu (i7-2700). Runs fine and has more power than the old Duo
> box. Fits my needs.
> 
> But I couldn't disable HT in BIOS - 'htop' finds eight CPUs. Should be
> no problem - but it is.
> 
> The problem came with the 'cpufreq'-plugin, my logs were flooded with
> warnings:
> "cpufreq plugin: Reading
> "/sys/devices/system/cpu/cpu4[5,6,7]/cpufreq/scaling_cur_freq" failed."
> 
> Because of the deactivation, 'scaling_cur_freq' was empty, there were
> complains about CPU 4-7 (the deactivated ones) and in no time my log was
> filled with about 10000 'collectd'-entries.
> 
> My solution was to change the loglevel of the 'Plugin syslog' in
> 'collectd.conf' from 'info' to 'err'.
> 
> Can anyone confirm this behaviour?
> 
> Best
> Matthias
> 



  reply	other threads:[~2026-01-22  0:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 22:52 Matthias Fischer
2026-01-22  0:49 ` Tom Rymes [this message]
2026-01-22  6:32   ` Matthias Fischer
  -- strict thread matches above, loose matches on Subject: below --
2026-01-21 20:47 Matthias Fischer
2026-01-22 11:02 ` Adolf Belka
2026-01-22 14:04   ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DF703D68-1844-4AE8-849F-01AD1F48242A@rymes.net \
    --to=tom@rymes.net \
    --cc=development@lists.ipfire.org \
    --cc=matthias.fischer@ipfire.org \
    --cc=michael.tremer@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox