Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753944AbbGJKLc (ORCPT ); Fri, 10 Jul 2015 06:11:32 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:41087 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752224AbbGJKLZ (ORCPT ); Fri, 10 Jul 2015 06:11:25 -0400 MIME-Version: 1.0 In-Reply-To: <559F8115.1060801@arm.com> References: <559F7B2C.6090402@arm.com> <559F8115.1060801@arm.com> Date: Fri, 10 Jul 2015 18:11:23 +0800 Message-ID: Subject: Re: ACPI: regression: Failed to initialize GIC IRQ controller From: Ming Lei To: Marc Zyngier Cc: Suman Tripathi , Bob Moore , Lv Zheng , "Rafael J. Wysocki" , Jason Cooper , Catalin Marinas , Linux Kernel Mailing List , "hanjun.guo@linaro.org" , Thomas Gleixner , linux-arm-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1756 Lines: 44 On Fri, Jul 10, 2015 at 4:23 PM, Marc Zyngier wrote: > On 10/07/15 09:17, Suman Tripathi wrote: >> On Fri, Jul 10, 2015 at 1:28 PM, Marc Zyngier wrote: >>> >>> On 10/07/15 08:45, Ming Lei wrote: >>>> Hi, >>>> >>>> Commit 0cff8dc0099f6d4f(ACPICA: ACPI 6.0: Add changes for MADT table.) >>>> causes the following failure on APM mustang board(arm64) when >>>> booting via UEFI and ACPI: >>>> >>>> No valid GICC entries exist >>>> ACPI: Failed to initialize GIC IRQ controller >>>> Kernel panic - not syncing: No interrupt controller found. >>>> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.2.0-rc1+ #45 >>>> Hardware name: APM X-Gene Mustang board (DT) >>>> Call trace: >>>> [] dump_backtrace+0x0/0x12c >>>> [] show_stack+0x10/0x1c >>>> [] dump_stack+0x8c/0xdc >>>> [] panic+0xe4/0x220 >>>> [] init_IRQ+0x24/0x30 >>>> [] start_kernel+0x274/0x3d8 >>>> ---[ end Kernel panic - not syncing: No interrupt controller found. >>> >>> Isn't that addressed by [1] which Catalin has queued for -rc2? >> >> >> I am also seeing the same . But it fixes after I apply the parking >> protocol patch but that is not upstreamed. > > I'm more interested to find out if the patch I mentioned in my original > email fixes it or not. An additional dependency on something that is not > aimed for mainline yet doesn't really help. Yes, Al's patches do fix the issue. Thanks, Ming -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/