Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3982428imj; Tue, 19 Feb 2019 13:02:29 -0800 (PST) X-Google-Smtp-Source: AHgI3IZFgodzMXxUJOEt/zKm6s1nMxqOQ+NF5kXCjcFq/JMCE3afwb/g1XWXCtagmyJHieKE9SWz X-Received: by 2002:a17:902:48c8:: with SMTP id u8mr33034099plh.79.1550610149769; Tue, 19 Feb 2019 13:02:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550610149; cv=none; d=google.com; s=arc-20160816; b=cBS/lGRoYpED/5dKqaBI4Lbrlq2qiOcvyYSnrIfwKnCcSDxlaKPslSci3j3ZXqBOHw AVndEwjuh05bSAKRc1bzXM3+SwwPIf24SR2G3I/Kq4MEl91lFLAdRe2D++G621gUrRtX OpTwm5DxKFsXp/GyNPQoaF6McOrwYXutw31tLmOQgFUdXVNI9aOj+Z8TevGzAKQXT6yj nwUb6Z0zSnMERUkOrzdWK9CeX3qPm8a54gu3iLCnoIaamGTLu6p40Sm+VUudSDiY3fwz UBXc1rEleE71sLnvqZ04QUThOA6biY2gLF+9D0AmXdYeh67JTfKyAHYnNFfW6pXGOve+ BkkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=xD2TvNCxhcp2NFQg++phMr8hu31TY76TAX9EBjXgNbY=; b=M3kbveZOdaTQnXk/JuPf5q+aKULmjJ0mLR06Vfc66Gaib4sBv5ikekrPeFLwm93Klt WeoolYceblbcffulrnuNLFElTP3xkuQQYjEaLIEm/fhENSUSER8h9XY+MboY2tBURqqi TMflIIhIdVdzMOoWKJ2N39aTemAFDSdVuNp2AgqH/NLDUGQWC3a5Q7bzWRLT3CB1CfdA qxHbPszw34p0I4TAGU7XxrmMx9jabR3bBnHQmIx9WEIoSDwVeMVwmS1HIZUFS32nmfgr h2noBff8ihkVck/alIeIGXu4AP+nCtOBDHeUFC4xjkhhY2H5BfXHDyc66j559pXrIncu CUZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l22si17040353pfg.275.2019.02.19.13.02.13; Tue, 19 Feb 2019 13:02:29 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726986AbfBSVBw (ORCPT + 99 others); Tue, 19 Feb 2019 16:01:52 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:35977 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725829AbfBSVBw (ORCPT ); Tue, 19 Feb 2019 16:01:52 -0500 Received: from p5492e0d8.dip0.t-ipconnect.de ([84.146.224.216] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gwCWP-00009n-KW; Tue, 19 Feb 2019 22:01:45 +0100 Date: Tue, 19 Feb 2019 22:01:45 +0100 (CET) From: Thomas Gleixner To: Hans de Goede cc: Linux Kernel Mailing List , "Rafael J. Wysocki" , Borislav Petkov , Tom Lendacky Subject: Re: False positive "do_IRQ: #.55 No irq handler for vector" messages on AMD ryzen based laptops In-Reply-To: <95e76875-f6b2-cbea-cd74-dc14ee77b2f8@redhat.com> Message-ID: References: <95e76875-f6b2-cbea-cd74-dc14ee77b2f8@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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