mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@kernel.org>
To: Simon Richter <Simon.Richter@hogyros.de>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: POWER9: duplicate interrupt line in /proc/interrupts, kernel problem or userspace problem?
Date: Thu, 24 Jul 2025 20:39:33 +1000	[thread overview]
Message-ID: <877bzxdg9m.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <c4e878ae-e97c-4826-9962-fab15d7da632@hogyros.de>

Simon Richter <Simon.Richter@hogyros.de> writes:
> 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?)

It probably is supposed to be unique. In the early days it was just the
irq number (which is unique), and then later the named entries were
added. There's no formal spec for the format, and it's really intended
to be human readable, so who can say for sure.

But yeah I think it's reasonable to call it a powerpc kernel bug.

Having said that, it's been like that on powerpc since 2013, so although
we can fix it now, there's 12 years of kernels out there that have the
duplicate entries.

cheers

      reply	other threads:[~2025-07-24 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 10:48 Simon Richter
2025-07-24 10:39 ` Michael Ellerman [this message]

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=877bzxdg9m.fsf@mpe.ellerman.id.au \
    --to=mpe@kernel.org \
    --cc=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

all inboxes | Powered by JetHome®