mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: False positive "do_IRQ: #.55 No irq handler for vector" messages on AMD ryzen based laptops
Date: Tue, 19 Feb 2019 16:53:41 +0100	[thread overview]
Message-ID: <95e76875-f6b2-cbea-cd74-dc14ee77b2f8@redhat.com> (raw)

Hi Thomas,

Various people are reporting false positive "do_IRQ: #.55 No irq handler for vector"
messages on AMD ryzen based laptops, see e.g.:

https://bugzilla.redhat.com/show_bug.cgi?id=1551605

Which contains this dmesg snippet:

Feb 07 20:14:29 localhost.localdomain kernel: smp: Bringing up secondary CPUs ...
Feb 07 20:14:29 localhost.localdomain kernel: x86: Booting SMP configuration:
Feb 07 20:14:29 localhost.localdomain kernel: .... node  #0, CPUs:      #1
Feb 07 20:14:29 localhost.localdomain kernel: do_IRQ: 1.55 No irq handler for vector
Feb 07 20:14:29 localhost.localdomain kernel:  #2
Feb 07 20:14:29 localhost.localdomain kernel: do_IRQ: 2.55 No irq handler for vector
Feb 07 20:14:29 localhost.localdomain kernel:  #3
Feb 07 20:14:29 localhost.localdomain kernel: do_IRQ: 3.55 No irq handler for vector
Feb 07 20:14:29 localhost.localdomain kernel: smp: Brought up 1 node, 4 CPUs
Feb 07 20:14:29 localhost.localdomain kernel: smpboot: Max logical packages: 1
Feb 07 20:14:29 localhost.localdomain kernel: smpboot: Total of 4 processors activated (15968.49 BogoMIPS)

It seems that we get an IRQ for each CPU as we bring it online,
which feels to me like it is some sorta false-positive.

I temporarily have access to a loaner laptop for a couple of weeks which shows
the same errors and I would like to fix this, but I don't really know how to
fix this.

Note if you want I can set up root ssh-access to the laptop.

Regards,

Hans


             reply	other threads:[~2019-02-19 15:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 15:53 Hans de Goede [this message]
2019-02-19 21:01 ` Thomas Gleixner
2019-02-19 21:47   ` Lendacky, Thomas
2019-02-21 12:30     ` Hans de Goede
2019-03-03 10:57       ` Hans de Goede
2019-03-05 14:06         ` Lendacky, Thomas
2019-03-05 16:02           ` Hans de Goede
2019-03-05 19:19             ` Hans de Goede
2019-03-05 19:31               ` Lendacky, Thomas
2019-03-05 19:40                 ` Hans de Goede
2019-03-05 19:54                   ` Borislav Petkov
2019-03-06  8:41                     ` Hans de Goede
2019-03-06 10:14                       ` Thomas Gleixner
2019-03-07 11:20                         ` Hans de Goede
2019-02-21 12:28   ` Hans de Goede
2021-01-09  5:50 Christopher William Snowhill

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=95e76875-f6b2-cbea-cd74-dc14ee77b2f8@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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®