Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1181355 > unrolled thread
| Started by | Suman Tripathi <stripathi@apm.com> |
|---|---|
| First post | 2015-07-10 10:20 +0200 |
| Last post | 2015-07-10 11:40 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: ACPI: regression: Failed to initialize GIC IRQ controller Suman Tripathi <stripathi@apm.com> - 2015-07-10 10:20 +0200
Re: ACPI: regression: Failed to initialize GIC IRQ controller Marc Zyngier <marc.zyngier@arm.com> - 2015-07-10 10:30 +0200
Re: ACPI: regression: Failed to initialize GIC IRQ controller Suman Tripathi <stripathi@apm.com> - 2015-07-10 11:40 +0200
| From | Suman Tripathi <stripathi@apm.com> |
|---|---|
| Date | 2015-07-10 10:20 +0200 |
| Subject | Re: ACPI: regression: Failed to initialize GIC IRQ controller |
| Message-ID | <pKBHk-3ui-23@gated-at.bofh.it> |
On Fri, Jul 10, 2015 at 1:28 PM, Marc Zyngier <marc.zyngier@arm.com> 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: > > [<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. > > 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. > > > Thanks, > > M. > > [1] https://lkml.org/lkml/2015/7/6/876 > > -- > Jazz is not dead. It just smells funny... > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Thanks, with regards, Suman Tripathi -- 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/
[toc] | [next] | [standalone]
| From | Marc Zyngier <marc.zyngier@arm.com> |
|---|---|
| Date | 2015-07-10 10:30 +0200 |
| Message-ID | <pKBR1-3yi-33@gated-at.bofh.it> |
| In reply to | #1181355 |
On 10/07/15 09:17, Suman Tripathi wrote: > On Fri, Jul 10, 2015 at 1:28 PM, Marc Zyngier <marc.zyngier@arm.com> 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: >>> [<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. >> >> 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. Thanks, M. -- Jazz is not dead. It just smells funny... -- 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/
[toc] | [prev] | [next] | [standalone]
| From | Suman Tripathi <stripathi@apm.com> |
|---|---|
| Date | 2015-07-10 11:40 +0200 |
| Message-ID | <pKCWK-4bn-25@gated-at.bofh.it> |
| In reply to | #1181374 |
On Fri, Jul 10, 2015 at 1:53 PM, Marc Zyngier <marc.zyngier@arm.com> wrote: > On 10/07/15 09:17, Suman Tripathi wrote: >> On Fri, Jul 10, 2015 at 1:28 PM, Marc Zyngier <marc.zyngier@arm.com> 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: >>>> [<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. >>> >>> 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 the patch mentioned by you fixes the issue. [1] https://lkml.org/lkml/2015/7/6/876 > > Thanks, > > M. > -- > Jazz is not dead. It just smells funny... -- Thanks, with regards, Suman Tripathi -- 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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web