panic: arm_unmask_irq [was: Re: TI platforms code update: switching to vendor FDT data]

[Ian Lepore]

On Sun, 2015-05-24 at 17:31 -0700, Marcel Moolenaar wrote:
> > On May 24, 2015, at 5:12 PM, Oleksandr Tymoshenko <gonzo at FreeBSD.org> wrote:
> > 
> > 
> > ti_scm and ti_pinmux should be detected right after simplebus.
> > Could you make sure if dtb loaded by u-boot is not
> > from previous builds? You can decompile it using dtc:
> > dtc -I dtb -O dts beaglebone-black.dtb
> 
> I’m pretty sure that’s not possible, since I’ve never built ARM
> kernels in this particular VM before :-)
> 
> From the fdt command in the loader I can see it’s the first device
> mentioned, so that’s not it.
> 
> loader> fdt ls
> Using DTB provided by U-Boot at address 0x80000100.
> 
> /am335x
> /am335x/interrupt-controller at 48200000
> /am335x/pmu
> /am335x/scm at 44e10000
> /am335x/prcm at 44E00000
> /am335x/dmtimers at 44E05000
> /am335x/rtc at 44E3E000
> /am335x/adc at 44E0D000
> /am335x/wdt1 at 44E35000
> /am335x/gpio
> 	*snip*
> 
> A verbose boot gives me:
> 
> ofwbus0: <Open Firmware Device Tree>
> simplebus0: <Flattened device tree simple bus> on ofwbus0
> simplebus0: <interrupt-controller at 48200000> mem 0x48200000-0x48200fff compat ti,aintc (no driver attached)
> 
> Ok, so this is a problem.
> 
> fbsdvm64% nm kernel.debug | grep aintc
> c0681584 r __set_modmetadata_set_sym__mod_metadata_md_aintc_simplebus
> c0681580 r __set_modmetadata_set_sym__mod_metadata_md_aintc_simplebus_on_kernel
> c0680984 r __set_sysinit_set_sym_aintc_simplebusmodule_sys_init
> c07306d0 d _aintc_simplebus_depend_on_kernel
> c05f749c t aintc_post_filter
> c06039f8 t fdt_aintc_decode_ic
> c05f7334 t ti_aintc_attach
> c061c874 r ti_aintc_methods
> c05f72dc t ti_aintc_probe
> 
> Poking some more…
> 

"ti,aintc" is the compat string from the old fdt data, the new one that
teh driver now recognizes would be "ti,am33xx-intc".

-- Ian