Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752541AbbLUXMb (ORCPT ); Mon, 21 Dec 2015 18:12:31 -0500 Received: from mout.kundenserver.de ([212.227.17.10]:61563 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751491AbbLUXM3 (ORCPT ); Mon, 21 Dec 2015 18:12:29 -0500 From: Arnd Bergmann To: Alexander Aring Subject: Re: [PATCH v2 0/8] Raspberry Pi 2 support. Date: Tue, 22 Dec 2015 00:11:32 +0100 User-Agent: KMail/1.12.2 (Linux/3.19.0-27-generic; KDE/4.3.2; x86_64; ; ) Cc: Eric Anholt , linux-rpi-kernel@lists.infradead.org, Mark Rutland , devicetree@vger.kernel.org, Ian Campbell , Florian Fainelli , Jason Cooper , Scott Branden , Marc Zyngier , Ray Jui , linux-kernel@vger.kernel.org, Rob Herring , bcm-kernel-feedback-list@broadcom.com, Kumar Gala , Thomas Gleixner , linux-arm-kernel@lists.infradead.org References: <1450310115-22163-1-git-send-email-eric@anholt.net> <20151218100826.GB1145@omega> <20151220221158.GA6416@omega> In-Reply-To: <20151220221158.GA6416@omega> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201512220011.32234.arnd@arndb.de> X-Provags-ID: V03:K0:qQxUuIkASlAso7jqxs62FBF/fo/hjqZqqgUcg+ZLt7ZA3j8ChhD Lx4cOcQ0fuVKfiAaPgAmqum6C5Z6MrOCcrww+Cijy6qHWZRepxKZ+CH5ZtrueUQFtoaSySe vyg8pN9wET8S3S8hwo7C9KZ1XbEyJP94aZvCLz8nyp0Tr8kWseMI3zYrdWZX9Cp/Al4gF55 Yanw9i50/+1Iy4giJB0RA== X-UI-Out-Filterresults: notjunk:1;V01:K0:Pf3HjpE9uPo=:g2+GKtnKuggWKZSS79PI4Q fQkjwqcQjiIeAV+a1kusFoaCZ5f6DgXrY1kuy1RTtbupf6ugA7WZ0q0jH2V+nN7qjW8FPGoMA Iw0zEAY14UDb0kiy2YdBxJRoG5q1hVA2aFTJkEOrBKV2RCk8wFitBEOyhJ25CCi/t9BnGQEt8 ffIvMqRz9n3VQ3PvteBZmWcOC1M7PwChZjI/n4YQ/RM/BeJerwyVYEipPcRexSMaglBndYz6f TVcl7lYJZ/Be8KwuQZyFvEm92RIoj8lJp7cys29e1lcfLxoSFY9GrdiLIzNebK+WiwUq3iwAL zcjF84EDkUuK3CK99GMq8Yt4rm5vZyguEUnxqYEIuf3zN4MfjWtRWPywpj2VBeXzcdRQ6x5hD MFrHBztomesw+1TdVn8xaG5eHSozrpv15qB/bJU/8Y0S0Hvh0rdXV+t5XOgPZ/R44YwGlyKuU ySDJPw1aH7Xu7AOPsdda0S9v2ZrISUha2HdMQ+OkuepPZau8SHcBL5QExbuk50OcXNXzlZ83J h0fqo0Xp3xB8cPRSgjZGpT4YF4UVcGklhoaGOHF7UJm352BuMLuhUr0IQx57XKgXJhWXtJc4z cE88U85wPxGVoi1gh/5WCNS/bFdws3QcmEcVbiq/1NzVsAZztrSzO9c0pRtSRmDEO2bx+JU4u rCLRhY9ZrD+bCCxI8kdL/YGUyQBQMti1OEdFzEX2NAnX/l9oiTLUG8zLnRGW6LGUkOJvlFFEj fTRTPi3VVLtHtZdc Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4452 Lines: 73 On Sunday 20 December 2015, Alexander Aring wrote: > On Fri, Dec 18, 2015 at 11:08:26AM +0100, Alexander Aring wrote: > > [ 0.000000] Memory policy: Data cache writeback > > [ 0.000000] BUG: mapping for 0x3f201000 at 0xf0201000 out of vmalloc space This is a separate bug, right? > > [ 0.000000] ------------[ cut here ]------------ > > [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/arm/kernel/devtree.c:149 arm_dt_init_cpu_maps+0x100/0x1a4() > > [ 0.000000] DT /cpu 2 nodes greater than max cores 1, capping them > > [ 0.000000] Modules linked in: > > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-rc5+ #989 > > [ 0.000000] Hardware name: BCM2835 > > [ 0.000000] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) > > [ 0.000000] [] (show_stack) from [] (dump_stack+0x20/0x28) > > [ 0.000000] [] (dump_stack) from [] (warn_slowpath_common+0x9c/0xc4) > > [ 0.000000] [] (warn_slowpath_common) from [] (warn_slowpath_fmt+0x40/0x48) > > [ 0.000000] [] (warn_slowpath_fmt) from [] (arm_dt_init_cpu_maps+0x100/0x1a4) > > [ 0.000000] [] (arm_dt_init_cpu_maps) from [] (setup_arch+0x6f4/0x89c) > > [ 0.000000] [] (setup_arch) from [] (start_kernel+0x74/0x3a4) > > [ 0.000000] [] (start_kernel) from [<00008078>] (0x8078) > > [ 0.000000] ---[ end trace cb88537fdc8fa200 ]--- > > [ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map > > [ 0.000000] CPU: All CPU(s) started in SVC mode. > > I can remove this WARNING when I enable CONFIG_SMP. I think we should try to change this in the code. > > [ 0.000000] Virtual kernel memory layout: > > [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) > > [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) > > [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) > > [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) > > [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) > > [ 0.000000] .text : 0xc0008000 - 0xc074a7cc (7434 kB) > > [ 0.000000] .init : 0xc074b000 - 0xc07b4000 ( 420 kB) > > [ 0.000000] .data : 0xc07b4000 - 0xc081e910 ( 427 kB) > > [ 0.000000] .bss : 0xc081e910 - 0xc08ca80c ( 688 kB) > > [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 > > [ 0.000000] NR_IRQS:16 nr_irqs:16 16 > > [ 0.000000] Kernel panic - not syncing: /soc/local_intc: unable to map local interrupt registers > > [ 0.000000] > > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Tainted: G W 4.4.0-rc5+ #989 > > [ 0.000000] Hardware name: BCM2835 > > [ 0.000000] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) > > [ 0.000000] [] (show_stack) from [] (dump_stack+0x20/0x28) > > [ 0.000000] [] (dump_stack) from [] (panic+0x84/0x210) > > [ 0.000000] [] (panic) from [] (bcm2836_arm_irqchip_l1_intc_of_init+0x94/0x110) > > [ 0.000000] [] (bcm2836_arm_irqchip_l1_intc_of_init) from [] (of_irq_init+0x1a0/0x2a8) > > [ 0.000000] [] (of_irq_init) from [] (irqchip_init+0x14/0x1c) > > [ 0.000000] [] (irqchip_init) from [] (init_IRQ+0x28/0x88) > > [ 0.000000] [] (init_IRQ) from [] (start_kernel+0x20c/0x3a4) > > [ 0.000000] [] (start_kernel) from [<00008078>] (0x8078) > > [ 0.000000] ---[ end Kernel panic - not syncing: /soc/local_intc: unable to map local interrupt registers > > > > But still getting this panic, your patches does not contain some > defconfig, so I still try to figure out what I need to enable to get it > working. Maybe it is some missing config entry which should be enabled. > > But, for me it looks like some devicetree issue, because of_iomem returns > NULL, at [0]. Don't know what I am doing wrong. That is the most likely cause, yes. You can try replacing it with an ioremap with a hardcoded physical address to see if that works. Arnd -- 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/