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 4dxKGt05Jmz331g for ; Wed, 21 Jan 2026 22:53:10 +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 4dxKGp37Fmz2xP7 for ; Wed, 21 Jan 2026 22:53:06 +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 4dxKGl487Pz1Mb; Wed, 21 Jan 2026 22:53:03 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769035983; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=B+M0OwqSVxbYChO/5QAXZff3F4vvSQwUbzwdFdjc1XE=; b=tbDtQThIN/qRwfAQciDwJZJ9X+p+Ep15iBpwBHqP2nDXV6OEspoysfJW6NeEMIHxYQUAam GKGa61tsoNDITdAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769035983; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=B+M0OwqSVxbYChO/5QAXZff3F4vvSQwUbzwdFdjc1XE=; b=phWzFSEgnliTMyLJI14bdmcpOiOGQZkLDY6IujaE7uY4zaCfjndbS6zbe6cgVcT6B1KcA/ aYiO34sRhtIAME6PQqUTSnowdlpVxIyAOxr1JD4XSAyU547Zo9ssXQq6yIh2fCv+2dMA0g sfVim5TZ0nkyw2FUwQLY4W4ybqn3YbfWN+hu3m4bYmrKz+jz9potPIPZ9G5G2o4HeMuGpb /OHtcVD1zHRtq6dXmO9s9H1WVzB6gPILJkEkgWDUE8uWAafDtX8rr7y1oSq8bG35EgfHn0 FaUJHv/+aFMz3xp+um/1ef5onAyTpau2iPziI19qyHpqxTIY9DkZeybgVS6B6w== Message-ID: Date: Wed, 21 Jan 2026 23:52:55 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 From: Matthias Fischer Subject: Core 199 - collectd - cpufreq-plugin floods syslog To: "IPFire: Development-List" Content-Language: en-US Cc: "IPFire: Tremer, Michael" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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