lkml.org 
[lkml]   [2019]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: False positive "do_IRQ: #.55 No irq handler for vector" messages on AMD ryzen based laptops
    Hans,

    On Tue, 19 Feb 2019, Hans de Goede wrote:

    Cc+: ACPI/AMD folks

    > 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.

    Sigh, that looks like BIOS value add again.

    It's not a false positive. Something _IS_ sending a vector 55 to these CPUs
    for whatever reason.

    > 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.

    Can you please enable CONFIG_GENERIC_IRQ_DEBUGFS and dig in the files there
    whether vector 55 is used on CPU0 and which device is associated to that.

    I bet its a legacy IRQ and as that space starts at 48 (IRQ0) this should be
    IRQ9 which is usually - DRUMROLL - the ACPI interrupt.

    The kernel clearly sets that up to be delivered to CPU 0 only, but I've
    seen that before that the BIOS value add thinks that this setup is not
    relevant.

    /me goes off and sings LALALA

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

    As a least resort. root ssh - SHUDDER - Ooops now I spilled my preferred
    password for that :)

    Thanks,

    tglx

    \
     
     \ /
      Last update: 2019-02-19 22:02    [W:3.638 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site