From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757013AbdLWT7p (ORCPT ); Sat, 23 Dec 2017 14:59:45 -0500 Received: from mail-qt0-f181.google.com ([209.85.216.181]:38440 "EHLO mail-qt0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751295AbdLWT7m (ORCPT ); Sat, 23 Dec 2017 14:59:42 -0500 X-Google-Smtp-Source: ACJfBotCF8w9ipN/UyV6QpWcpkE37NDHNHEm4Rb1+S9mOrUPfh6B1K8Z60I5NB32QN8be1Q4yzFdJA== Date: Sat, 23 Dec 2017 15:01:12 -0500 From: Alexandru Chirvasitu To: Thomas Gleixner Cc: Dexuan Cui , 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 Message-ID: <20171223200112.GC1138@arch-chirva.localdomain> References: <20171220131929.GC24638@arch-chirva.localdomain> <20171220194506.GD24638@arch-chirva.localdomain> <20171221022356.GE24638@arch-chirva.localdomain> <1bd74ca3-afca-9d61-6911-61250f459891@cn.fujitsu.com> <20171222142053.3cbhi2nhh24w7yoo@D-69-91-141-110.dhcp4.washington.edu> <20171222222917.GA1138@arch-chirva.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 23, 2017 at 02:32:52PM +0100, Thomas Gleixner wrote: > On Sat, 23 Dec 2017, Dexuan Cui wrote: > > > > From: Alexandru Chirvasitu [mailto:achirvasub@gmail.com] > > > Sent: Friday, December 22, 2017 14:29 > > > > > > The output of that precise command run just now on a freshly-compiled > > > copy of that commit is attached. > > > > > > On Fri, Dec 22, 2017 at 09:31:28PM +0000, Dexuan Cui wrote: > > > > > From: Alexandru Chirvasitu [mailto:achirvasub@gmail.com] > > > > > Sent: Friday, December 22, 2017 06:21 > > > > > > > > > > In the absence of logs, the best I can do at the moment is attach a > > > > > picture of the screen I am presented with on the apic=debug boot > > > > > attempt. > > > > > Alex > > > > > > > > The panic happens in irq_matrix_assign_system+0x4e/0xd0 in your picture. > > > > IMO we should find which line of code causes the panic. I suppose > > > > "objdump -D kernel/irq/matrix.o" can help to do that. > > > > > > > > Thanks, > > > > -- Dexuan > > > > The BUG_ON panic happens at line 147: > > BUG_ON(!test_and_clear_bit(bit, cm->alloc_map)); > > > > I'm sure Thomas and Dou know it better than me. > > I'll have a look after the holidays. > Thanks for that! A quick follow-up on my inability to make kexec / kdump work in order to perhaps produce better logs: I've done another bisect for that with this result: # first bad commit: [e802a51ede91350438c051da2f238f5e8c918ead] x86/idt: Consolidate IDT invalidation I am quite certain this is the one for that issue. Its only parent is # good: [8f55868f9e42fea56021b17421914b9e4fda4960] x86/idt: Remove unused set_trap_gate() (i.e. one of the "good" commits I hit upon during the bisect). On the core 2 duo machine I've been referring to e802a51 and later commits simply return me to a regular BIOS boot when issuing either kexec -e on a loaded crash kernel or crashing with echo c > /proc/sysrq-trigger. Alex