linux-kernel - Re: arm64: next-20170614 panics on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170615123337.5qkrh72vt53jnwnf@yury-thinkpad>
Date:   Thu, 15 Jun 2017 15:33:37 +0300
From:   Yury Norov <ynorov@...iumnetworks.com>
To:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: arm64: next-20170614 panics on boot

On Thu, Jun 15, 2017 at 03:08:40PM +0300, Yury Norov wrote:
> Hi all,
> 
> Today's linux next falls into panic in init_IRQ():
> arch/arm64/kernel/irq.c:
>  53 void __init init_IRQ(void)
>  54 {
>  55         irqchip_init();
>  56         if (!handle_arch_irq)
>  57                 panic("No interrupt controller found.");
>  58 }
> 
> 
> Bisecting points to the patch 6fedb069def034 ("of: Provide dummy
> of_device_compatible_match() for compile-testing"), but reverting it
> doesn't help. It seems like yesterday's linux-next also hangs.  Right
> now I cannot continue with debugging, but if nothing will get clear,
> I'll back to it at this evening.

Sorry, forgot to attach the config. This is it. Also, I run arm64 on
qemu.

Yury

Download attachment "config.gz" of type "application/gzip" (35566 bytes)