linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Simon Richter <Simon.Richter@hogyros.de>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: POWER9: duplicate interrupt line in /proc/interrupts, kernel problem or userspace problem?
Date: Wed, 23 Jul 2025 19:48:45 +0900	[thread overview]
Message-ID: <c4e878ae-e97c-4826-9962-fab15d7da632@hogyros.de> (raw)

Hi,

I have two lines starting with "LOC:" in /proc/interrupts, one with a 
comment "Local timer interrupts for timer event device", the other 
"Local timer interrupts for others".

This makes collectd unhappy, because it uses the first column as a 
unique identifier.

Is this column supposed to be unique? (i.e. is this a kernel bug, or 
should collectd expect this?)

    Simon


             reply	other threads:[~2025-07-23 13:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 10:48 Simon Richter [this message]
2025-07-24 10:39 ` POWER9: duplicate interrupt line in /proc/interrupts, kernel problem or userspace problem? Michael Ellerman

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=c4e878ae-e97c-4826-9962-fab15d7da632@hogyros.de \
    --to=simon.richter@hogyros.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).