From: Marc Zyngier <marc.zyngier@arm.com> To: "Moore, Robert" <robert.moore@intel.com>, Ming Lei <ming.lei@canonical.com>, "Zheng, Lv" <lv.zheng@intel.com>, "Wysocki, Rafael J" <rafael.j.wysocki@intel.com> Cc: Hanjun Guo <hanjun.guo@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Jason Cooper <jason@lakedaemon.net> Subject: Re: ACPI: regression: Failed to initialize GIC IRQ controller Date: Fri, 10 Jul 2015 15:47:15 +0100 [thread overview] Message-ID: <559FDAF3.10200@arm.com> (raw) In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D30B295@ORSMSX112.amr.corp.intel.com> On 10/07/15 15:28, Moore, Robert wrote: > > >> -----Original Message----- >> From: Ming Lei [mailto:ming.lei@canonical.com] >> Sent: Friday, July 10, 2015 12:46 AM >> To: Moore, Robert; Zheng, Lv; Wysocki, Rafael J >> Cc: Linux Kernel Mailing List; linux-arm-kernel; Thomas Gleixner; Jason >> Cooper; Hanjun Guo >> Subject: ACPI: regression: Failed to initialize GIC IRQ controller >> >> 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: > > > I would be interested to know just what exactly about this change broke things. The gory details are there: https://lkml.org/lkml/2015/7/6/876 Basically, some data structure (acpi_madt_generic_interrupt) grew by 4 bytes from ACPI 5.1 to 6.0, but BAD_MADT_ENTRY only knows about the new size, and not the old one. When booting on an old(er) version of ACPI, the interrupt controller tables are ignore (not the right size), and the machine stops booting very early. Thanks, M. > Bob > > > >> >> 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: >> [<ffffffc000089b94>] dump_backtrace+0x0/0x12c [<ffffffc000089cd0>] >> show_stack+0x10/0x1c [<ffffffc0005fac18>] dump_stack+0x8c/0xdc >> [<ffffffc0005f7218>] panic+0xe4/0x220 [<ffffffc00082631c>] >> init_IRQ+0x24/0x30 [<ffffffc00082486c>] start_kernel+0x274/0x3d8 ---[ end >> Kernel panic - not syncing: No interrupt controller found. >> >> >> Thanks, >> Ming > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier) To: linux-arm-kernel@lists.infradead.org Subject: ACPI: regression: Failed to initialize GIC IRQ controller Date: Fri, 10 Jul 2015 15:47:15 +0100 [thread overview] Message-ID: <559FDAF3.10200@arm.com> (raw) In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D30B295@ORSMSX112.amr.corp.intel.com> On 10/07/15 15:28, Moore, Robert wrote: > > >> -----Original Message----- >> From: Ming Lei [mailto:ming.lei at canonical.com] >> Sent: Friday, July 10, 2015 12:46 AM >> To: Moore, Robert; Zheng, Lv; Wysocki, Rafael J >> Cc: Linux Kernel Mailing List; linux-arm-kernel; Thomas Gleixner; Jason >> Cooper; Hanjun Guo >> Subject: ACPI: regression: Failed to initialize GIC IRQ controller >> >> 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: > > > I would be interested to know just what exactly about this change broke things. The gory details are there: https://lkml.org/lkml/2015/7/6/876 Basically, some data structure (acpi_madt_generic_interrupt) grew by 4 bytes from ACPI 5.1 to 6.0, but BAD_MADT_ENTRY only knows about the new size, and not the old one. When booting on an old(er) version of ACPI, the interrupt controller tables are ignore (not the right size), and the machine stops booting very early. Thanks, M. > Bob > > > >> >> 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: >> [<ffffffc000089b94>] dump_backtrace+0x0/0x12c [<ffffffc000089cd0>] >> show_stack+0x10/0x1c [<ffffffc0005fac18>] dump_stack+0x8c/0xdc >> [<ffffffc0005f7218>] panic+0xe4/0x220 [<ffffffc00082631c>] >> init_IRQ+0x24/0x30 [<ffffffc00082486c>] start_kernel+0x274/0x3d8 ---[ end >> Kernel panic - not syncing: No interrupt controller found. >> >> >> Thanks, >> Ming > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-07-10 14:47 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-10 7:45 ACPI: regression: Failed to initialize GIC IRQ controller Ming Lei 2015-07-10 7:45 ` Ming Lei 2015-07-10 7:58 ` Marc Zyngier 2015-07-10 7:58 ` Marc Zyngier 2015-07-10 8:17 ` Suman Tripathi 2015-07-10 8:17 ` Suman Tripathi 2015-07-10 8:23 ` Marc Zyngier 2015-07-10 8:23 ` Marc Zyngier 2015-07-10 9:37 ` Suman Tripathi 2015-07-10 9:37 ` Suman Tripathi 2015-07-10 10:11 ` Ming Lei 2015-07-10 10:11 ` Ming Lei 2015-07-10 11:10 ` Hanjun Guo 2015-07-10 11:10 ` Hanjun Guo 2015-07-10 10:49 ` Hanjun Guo 2015-07-10 10:49 ` Hanjun Guo 2015-07-10 14:28 ` Moore, Robert 2015-07-10 14:28 ` Moore, Robert 2015-07-10 14:43 ` Ming Lei 2015-07-10 14:43 ` Ming Lei 2015-07-10 14:45 ` Moore, Robert 2015-07-10 14:45 ` Moore, Robert 2015-07-10 15:17 ` Lorenzo Pieralisi 2015-07-10 15:17 ` Lorenzo Pieralisi 2015-07-10 15:47 ` Moore, Robert 2015-07-10 15:47 ` Moore, Robert 2015-07-10 17:02 ` Lorenzo Pieralisi 2015-07-10 17:02 ` Lorenzo Pieralisi 2015-07-10 17:07 ` Moore, Robert 2015-07-10 17:07 ` Moore, Robert 2015-07-10 14:47 ` Marc Zyngier [this message] 2015-07-10 14:47 ` Marc Zyngier 2015-07-10 14:48 ` Lorenzo Pieralisi 2015-07-10 14:48 ` Lorenzo Pieralisi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=559FDAF3.10200@arm.com \ --to=marc.zyngier@arm.com \ --cc=hanjun.guo@linaro.org \ --cc=jason@lakedaemon.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lv.zheng@intel.com \ --cc=ming.lei@canonical.com \ --cc=rafael.j.wysocki@intel.com \ --cc=robert.moore@intel.com \ --cc=tglx@linutronix.de \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.