From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754213AbdL1TbP (ORCPT ); Thu, 28 Dec 2017 14:31:15 -0500 Received: from mga06.intel.com ([134.134.136.31]:51741 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753480AbdL1TbO (ORCPT ); Thu, 28 Dec 2017 14:31:14 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,472,1508828400"; d="scan'208";a="19588246" Message-ID: <1514489471.7000.463.camel@linux.intel.com> Subject: Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1 From: Andy Shevchenko To: Thomas Gleixner Cc: "alan@linux.intel.com" , "Ailus, Sakari" , "linux-kernel@vger.kernel.org" , "linux-media@vger.kernel.org" Date: Thu, 28 Dec 2017 21:31:11 +0200 In-Reply-To: References: <1514481444.7000.451.camel@intel.com> <1514482448.7000.460.camel@linux.intel.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > CPU#0, > > > > should never happen. > > > > [ 85.199886] atomisp-isp2 0000:00:03.0: stream[0] started. > > > > > > > > and Ctrl+C does NOT work. Machine just hangs. > > > > > > > > It might be related to this: > > > > https://lkml.org/lkml/2017/12/22/697 > > > > > > I don't think so. > > > > > > Does the patch below cure it? > > > > Unfortunately, no. > > > > Same behaviour. > > > > Tell me if I need to provide some debug before it hangs. For now I > > have > > apic=debug (AFAIR it doesn't affect this). > > The interesting question is why that spurious APIC interrupt through > vector > ff happens. Can you please add the following to the kernel command > line: > > 'trace_events=irq_vectors:* ftrace_dump_on_oops' > > and apply the patch below. That should spill out the trace over serial > (I > hope you have that ...) With or without CONFIG_FUNCTION_TRACER=y I have got [ 28.977918] Dumping ftrace buffer: [ 28.988115] (ftrace buffer empty) followed by BUG() output. ... [ 28.930154] RIP: 0010:smp_spurious_interrupt+0x67/0xb0 ... Anything I missed? P.S. I didn't apply your previous patch. > Thanks, > > tglx > > 8<--------------- > --- a/arch/x86/kernel/apic/apic.c > +++ b/arch/x86/kernel/apic/apic.c > @@ -1978,6 +1978,8 @@ void __init register_lapic_address(unsig > /* see sw-dev-man vol 3, chapter 7.4.13.5 */ > pr_info("spurious APIC interrupt through vector %02x on > CPU#%d, " > "should never happen.\n", vector, > smp_processor_id()); > + tracing_off(); > + BUG(); > > trace_spurious_apic_exit(vector); > exiting_irq(); > -- Andy Shevchenko Intel Finland Oy