From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755991AbeASPYm (ORCPT ); Fri, 19 Jan 2018 10:24:42 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:51424 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755973AbeASPYe (ORCPT ); Fri, 19 Jan 2018 10:24:34 -0500 Date: Fri, 19 Jan 2018 16:24:31 +0100 (CET) From: Thomas Gleixner To: "jianchao.wang" cc: "linux-kernel@vger.kernel.org" , Christoph Hellwig , Keith Busch , Sagi Grimberg , Jens Axboe Subject: Re: [BUG] do_IRQ: 7.33 No irq handler for vector In-Reply-To: <67ef24d5-ba2a-7f4b-2c28-fbec5335b174@oracle.com> Message-ID: References: <67ef24d5-ba2a-7f4b-2c28-fbec5335b174@oracle.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Jan 2018, jianchao.wang wrote: > When I did cpu hotplug stress test, I found this log on my machine. > > [ 267.161043] do_IRQ: 7.33 No irq handler for vector > > I add a dump_stack below the bug and get following log: Well, that's pretty uninteresting. What's interesting is which CPU got unplugged. > The vector 33 here is used by a NVMe card. CC'ed NVME folks Thanks, tglx