On Thursday April 05 2018 14:20:58 Bug Reporter wrote: Hi, >How can I resolve this error I'm seeing in the logs? > ksysguardd - Internal buffer too small to read '/proc/cpuinfo' I suggest you file a bug report on bugs.kde.org, the size for this buffer should be determined dynamically. (Or set to 640Kb which should be more than enough for all time ;) ) >cat /proc/cpuinfo lists 40 processors. The system has two Intel(R) Xeon(R) >CPU E5-2630 v4 @ 2.20GHz with 10 cores each. 2 x 10 = 40?? R.
Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- From: René J.V. Bertin <rjvbertin@xxxxxxxxx>
- Date: Thu, 05 Apr 2018 21:14:13 +0200
- Arc-authentication-results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=GGYtSLMW; spf=pass (google.com: best guess record for domain of kde-bounces@xxxxxxxxxxxx designates 46.4.96.248 as permitted sender) smtp.mailfrom=kde-bounces@xxxxxxxxxxxx; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:list-subscribe:list-help:list-post :list-unsubscribe:list-id:reply-to:precedence :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:message-id:date:subject:to:from:dkim-signature :delivered-to:arc-authentication-results; bh=BoDwgkSAl+nqTfcDj8HVdR/oNPfJ6rpgzZTu/9MOPE4=; b=eBsHYMzUhogJr8OcA3UUes6VWxWHv4cL6++98/VvQZ0+AVSrMnY4LjB7DmOQJb2o6Q ut0FsfEpsxxlZlsnyZZvrAYqBOIaLVljiA8ylQ5MZJiqwdB4nrMWnDfhYZ1fLJ9RGnMP ON1+TKWQvhOeiOOM/dJR8tFJQTyrThgvL3LzF6QaFSDXkjcZLNy/Ech1h+JqShr+oTi2 9wOIM0JLTILVRMWtooX+t/aI4XTXH8atpe5vAjr5yXOKCnM3yzbkk8+IuUtkhMSeyO3W 433/o9KLY3Iyda8GpCm+5S00tarecLVUeWuNmuiG6N71J19lR+mAgrAS0L62WPJtk3B1 YK5A==
- Arc-seal: i=1; a=rsa-sha256; t=1522955690; cv=none; d=google.com; s=arc-20160816; b=iwiyTcZA+yepV+tCNd+XPL2LwgBGhBPW+Q4Swom41JPw3otfOEkTAWb4puktTjDrx/ 8frARM2GhPMUWwnCe34s0ApvEVaeoLi9oWTYSqcXc7MU2uOQbWUtvs3iLIVmTxsOXSvR zbU2+7Oufg3VIKCaCwIJT63qxbjTHn/tUZZe5yZvDTQik7zonv1FnCisn+VHyB3qQCce R9Nx/IJJrQejLXpnwAmQGYhREspgh72NIcuM4oew6MEGsR55kG4IP2xvwFwEjaG+K+Vg gJZLBGhApkpW13UyJOYNFzgnerqtzX5Wmawt3DBtzHomvr2TdKfRuTY78eDpE426USx8 eW4A==
- In-reply-to: <CAPNrkC-BWXDXvzcwWAgAhXa95SFShoEdXLKvko6-mTeaoNv58g@mail.gmail.com>
- References: <CAPNrkC-BWXDXvzcwWAgAhXa95SFShoEdXLKvko6-mTeaoNv58g@mail.gmail.com>
- User-agent: KMail/4.13.3 (Linux/4.14.23-ck1-mainline-core2-rjvb; KDE/4.14.38; x86_64; ; )
- Follow-Ups:
- Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- From: Bug Reporter
- Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- References:
- error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- From: Bug Reporter
- error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- Prev by Date: Re: kdialog: sound file from notifyrc file was not found,
- Next by Date: Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- Previous by thread: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- Next by thread: Re: error: ksysguardd - Internal buffer too small to read '/proc/cpuinfo'
- Index(es):
 |