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 4dxdT33xsPz331g for ; Thu, 22 Jan 2026 11:03:03 +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 4dxdT00Hcsz2xSm for ; Thu, 22 Jan 2026 11:03:00 +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 4dxdSy6dX7zYn; Thu, 22 Jan 2026 11:02:58 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769079779; 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: in-reply-to:in-reply-to:references:references; bh=B/NGjEXg6H3sCni7uY6twsT0UbLSu7yZYF21BaISuPY=; b=y+9m9QrZqRIOYOlqwMYVtzoqek6sqUSuo1ibjD9FYmYecJdSvGcHaSGQmWWJHuBIXIBfFx R6qZxKcMOl1xdYBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769079779; 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: in-reply-to:in-reply-to:references:references; bh=B/NGjEXg6H3sCni7uY6twsT0UbLSu7yZYF21BaISuPY=; b=ViU2jHIPhW9ntmHfjIWwy6eCHZ531MF/nFLK5OaeI4fS248UNEsEY9k/TtnuQ2MfB0qtNl Sq9NZr8UgRX5J4sXzPscmZGbxhpDmddkKM2+jsnkq7Nyogt9Q/Nu345uT4cJf8Sn30OAm3 hQXEc0Nxyd4lzUkOwzgJ4RFA1EbsXTbueTs3qfDypRXMFObCKRT1pM/KC2EMS/jsEX6hj9 COt7KXWygL89RDZT/QTPgpdGXqG4RdtKfLUv0bTFDY4E4uu+DFzdsOGyBOat41trODEtzS bo7OdSsTZxotxvtRrtYRyA4UplSXCogFmVkAjMLJjxlQ5lKBX8nfYjPx52VPIQ== Message-ID: <112b1abc-5ac6-4e52-8fe8-0112ab8a7607@ipfire.org> Date: Thu, 22 Jan 2026 12:02:46 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog To: Matthias Fischer References: From: Adolf Belka Content-Language: en-GB Cc: "IPFire: Development-List" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Matthias, On 21/01/2026 21:47, Matthias Fischer wrote: > 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? Can't confirm it on my system. I have a new mini with a quad core celeron. cpufreq-plugin is working fine. No error messages of any kind in the collectd system logs since I did my CU199 update and all graphs are displaying fine. Regards, Adolf. > Best > Matthias > > -- Sent from my laptop