From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dxGVg2DpZz331k for ; Wed, 21 Jan 2026 20:48:11 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dxGVb5f69z2xHh for ; Wed, 21 Jan 2026 20:48:07 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dxGVZ5RrtzN7 for ; Wed, 21 Jan 2026 20:48:06 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769028486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=iZTiui7gCB7DrLcxhRBuc9SRwdT9UTZn1YqoM/Xh16s=; b=bsug2UEvbKhAXlp0fuA9b4SSFSP+BS50mtsorYeVehPukjgAw3anhbodH1JdwgZLjNgFB4 WCuEKATuNLSAxdBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769028486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=iZTiui7gCB7DrLcxhRBuc9SRwdT9UTZn1YqoM/Xh16s=; b=X7NByLLJqyqQA1nSyTP7NUeav9gG1GUfxaXvrVVutylyYphhEFkgN5SaeDRNauUjMNW0CI 5vU74Xm29hNK0EAwkBESUSDGr/LuBxZCnOjfkydt66HmTQ1dhAdeYzyhV+8WJqVlshU2vt M11V83dvkL3dAm4mE19lvLB8te3sW68uNmTyv8mobZ7GDbCSmEJ1r51i6kCQTj+vrHzAs0 D+jNdvmWKiURWPARp4X+uE/ZcdOuA0u0Kx4Y2AkiQxgX/2Wwn0xCnJQ6Obqw7wF68DxFop qkgoxZgSu19pz+E3KuaIqAUQVC8Uv1gxxmaUTvZ5wUedQIbFqZRwAbDbC4eUbw== Message-ID: Date: Wed, 21 Jan 2026 21:47:59 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-US To: "IPFire: Development-List" From: Matthias Fischer Subject: Core 199 - collectd - cpufreq-plugin floods syslog Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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