From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752038AbdJPLFj (ORCPT ); Mon, 16 Oct 2017 07:05:39 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:50740 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751802AbdJPLFg (ORCPT ); Mon, 16 Oct 2017 07:05:36 -0400 Date: Mon, 16 Oct 2017 13:04:50 +0200 (CEST) From: Thomas Gleixner To: Petri Latvala cc: Yu Chen , Juergen Gross , Boris Ostrovsky , Tony Luck , Marc Zyngier , Alok Kataria , Joerg Roedel , "Rafael J. Wysocki" , Steven Rostedt , Christoph Hellwig , Peter Zijlstra , Borislav Petkov , Paolo Bonzini , Rui Zhang , "K. Y. Srinivasan" , Arjan van de Ven , Dan Williams , Len Brown , LKML Subject: Re: Regression in linux-next In-Reply-To: Message-ID: References: <20171013110850.GA5303@yu-chen.sh.intel.com> <149ec6e8-4189-040c-a53c-12b0a51a855e@intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-217332259-1508150715=:1973" Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-217332259-1508150715=:1973 Content-Type: text/plain; CHARSET=ISO-8859-15 Content-Transfer-Encoding: 8BIT Content-ID: On Mon, 16 Oct 2017, Petri Latvala wrote: Please CC LKML next time when you report a problem. I almost missed this thread. > [  174.561006] kernel BUG at arch/x86/kernel/apic/vector.c:154! > [  174.716682]  assign_vector_locked+0x9c/0x150 > [  174.721229]  apic_set_affinity+0x47/0x70 > [  174.725440]  ioapic_set_affinity+0x1a/0x60 > [  174.729838]  irq_do_set_affinity+0x18/0x60 > [  174.734206]  irq_migrate_all_off_this_cpu+0x136/0x270 > [  174.739647]  fixup_irqs+0x2f/0x130 > [  174.743312]  cpu_disable_common+0x1c7/0x1e0 > [  174.747792]  native_cpu_disable+0x20/0x30 > [  174.752073]  take_cpu_down+0x3c/0xa0 > [  174.755869]  multi_cpu_stop+0x8e/0xb0 > [  174.759762]  ? cpu_stop_queue_work+0x90/0x90 > [  174.764360]  cpu_stopper_thread+0x8a/0x100 > [  174.768758]  smpboot_thread_fn+0x165/0x230 > [  174.773168]  kthread+0x10c/0x140 Can you please pick up linux-next of today and merge the x86/apic branch from the tip-tree into it: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic There is a fix which might be related. Though I have no idea yet how the above can happen. Please enable tracing in the kernel configuration and enable the vector tracepoints. # for D in `ls -d /sys/kernel/debug/tracing/events/irq_vectors/vector_*`; do echo 1 > $D/enable; done Also please do # echo 1 > /proc/sys/kernel/ftrace_dump_on_oops That should dump the trace buffer when the bug hits. I try to reproduce myself. Thanks, tglx --8323329-217332259-1508150715=:1973--