lkml.org 
[lkml]   [2020]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86/irq: Lower unhandled irq error severity
Hello,

On Fri, Nov 27, 2020, at 02:12, Thomas Gleixner wrote:
> On Thu, Nov 26 2020 at 09:47, Laurențiu Nicola wrote:
> > These messages are described as warnings in the MSI code.
>
> Where and what has MSI to do with these messages?

There's a comment referring to it as a warning, but an error seemed a more appropriate severity:

* If the vector is unused, then it is marked so it won't
* trigger the 'No irq handler for vector' warning in
* common_interrupt().

> > Spotted because they break quiet boot on a Ryzen 5000 CPU.
>
> They don't break the boot.
>
> The machine boots fine, but having interrupts raised on a vector which
> is unused is really bad.

That's right, sorry. It still boots, but it's no longer "quiet", that's what I meant.

> Can you please provide the actual message from dmesg?

Sure:

[ 0.316902] __common_interrupt: 1.55 No irq handler for vector
[ 0.316902] __common_interrupt: 2.55 No irq handler for vector
[ 0.316902] __common_interrupt: 3.55 No irq handler for vector
[ 0.316902] __common_interrupt: 4.55 No irq handler for vector
[ 0.316902] __common_interrupt: 5.55 No irq handler for vector
[ 0.316902] __common_interrupt: 6.55 No irq handler for vector
[ 0.316902] __common_interrupt: 7.55 No irq handler for vector
[ 0.316902] __common_interrupt: 8.55 No irq handler for vector
[ 0.316902] __common_interrupt: 9.55 No irq handler for vector
[ 0.316902] __common_interrupt: 10.55 No irq handler for vector

These only show up during boot (and not e.g. when a disabling and enabling again a CPU).

Laurențiu

\
 
 \ /
  Last update: 2020-11-27 09:04    [W:0.072 / U:1.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site