From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754216AbdL1UPG (ORCPT ); Thu, 28 Dec 2017 15:15:06 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:33272 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751296AbdL1UPC (ORCPT ); Thu, 28 Dec 2017 15:15:02 -0500 Date: Thu, 28 Dec 2017 21:14:54 +0100 (CET) From: Thomas Gleixner To: Dexuan Cui cc: Alexandru Chirvasitu , Dou Liyang , Pavel Machek , kernel list , Ingo Molnar , "Maciej W. Rozycki" , Mikael Pettersson , Josh Poulson , "Mihai Costache (Cloudbase Solutions SRL)" , Stephen Hemminger , Marc Zyngier , "linux-pci@vger.kernel.org" , Haiyang Zhang , Simon Xiao , Saeed Mahameed , Jork Loeser , Bjorn Helgaas , "devel@linuxdriverproject.org" , KY Srinivasan Subject: RE: PROBLEM: 4.15.0-rc3 APIC causes lockups on Core 2 Duo laptop In-Reply-To: Message-ID: References: <20171218082011.GA24638@arch-chirva.localdomain> <20171218101131.GA5338@amd> <20171219083421.GB24638@arch-chirva.localdomain> <20171220131929.GC24638@arch-chirva.localdomain> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 28 Dec 2017, Dexuan Cui wrote: > > From: Thomas Gleixner [mailto:tglx@linutronix.de] > > Sent: Thursday, December 28, 2017 03:03 > > > > On Wed, Dec 20, 2017 at 02:12:05AM +0000, Dexuan Cui wrote: > > > > > > For Linux VM running on Hyper-V, we did get "spurious APIC interrupt > > > > through vector " and a patchset, which included the patch you identifed > > > > ("genirq: Add config option for reservation mode"), was made to fix the > > > > issue. But since you're using a physical machine rathter than a VM, I > > > > suspect it should be a different issue. > > > > Aaargh! Why was this never reported and where is that magic patchset? > > tglx > > Hi Thomas, > The Hyper-V specific issue was reported and you made a patchset to fix it: > https://patchwork.kernel.org/patch/10006171/ > https://lkml.org/lkml/2017/10/17/120 Ah, ok. I did not make the connection. I'll have a scan through the tree to figure out whether there is some other weird place which is missing that. Thanks, tglx