Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board

[Jared McNeill <jmcneill%invisible.ca@localhost>]

Need more info to analyze this:

 - Please include the full dmesg, not just the panic message.
 - Version of U-Boot used (is it from pkgsrc?).
 - Is the dtb the one built with the kernel or from somewhere else?

Thanks!
Jared


On Sat, 22 Oct 2022, oirammm%gmail.com@localhost wrote:

> > Number:         57068
> > Category:       kern
> > Synopsis:       a9tmr kernel panic on zynq-zturn Myir Board
> > Confidential:   no
> > Severity:       serious
> > Priority:       medium
> > Responsible:    kern-bug-people
> > State:          open
> > Class:          sw-bug
> > Submitter-Id:   net
> > Arrival-Date:   Sat Oct 22 10:00:00 +0000 2022
> > Originator:     Mario O.
> > Release:        9.3 4 Aug. 2022
> > Organization:
> > Environment:
> Cannot give uname -a, the system panics.
> > Description:
> Hi all,
> I suspect there is a problem at least on the evbarm-earmv7hf binary release of install images. After booting from an sd card with the GENERIC.ub kernel, using U-Boot and giving the right dtb zynq-zturn.dtb, the system panics after initializing the ehci0 usb controller, complaining about the a9tmr0.
>
> Using a prebuilt image from    https://nycdn.netbsd.org/pub/arm/ ( 32bit Generic Build: 202210211110Z ) the problem becomes clear, here is the output of the kernel panic:
>
> [   1.0000000] panic: kernel diagnostic assertion "freq != 0" failed: file "/usr/src/sys/arch/arm/cortex/a9tmr.c", line 299
> [   1.0000000] cpu0: Begin traceback...
> [   1.0000000] 0x80c8da2c: netbsd:db_panic+0x14
> [   1.0000000] 0x80c8da4c: netbsd:vpanic+0x114
> [   1.0000000] 0x80c8da64: netbsd:kern_assert+0x40
> [   1.0000000] 0x80c8daa4: netbsd:a9tmr_delay+0x14c
> [   1.0000000] 0x80c8dae4: netbsd:zynqusb_attach_common+0x284
> [   1.0000000] 0x80c8dbac: netbsd:zynqusb_attach+0xd0
> [   1.0000000] 0x80c8dbe4: netbsd:config_attach_internal+0x1d8
> [   1.0000000] 0x80c8dc2c: netbsd:config_found+0xe4
> [   1.0000000] 0x80c8dd9c: netbsd:fdt_scan+0x2ac
> [   1.0000000] 0x80c8ddbc: netbsd:fdt_rescan+0x58
> [   1.0000000] 0x80c8ddf4: netbsd:config_attach_internal+0x1d8
> [   1.0000000] 0x80c8de3c: netbsd:config_found+0xe4
> [   1.0000000] 0x80c8de7c: netbsd:arm_fdt_attach+0xa4
> [   1.0000000] 0x80c8deb4: netbsd:config_attach_internal+0x1d8
> [   1.0000000] 0x80c8def4: netbsd:config_rootfound+0x74
> [   1.0000000] 0x80c8df14: netbsd:cpu_configure+0x68
> [   1.0000000] 0x80c8df9c: netbsd:main+0x32c
> [   1.0000000] 0x80c8dfac: netbsd:kernel_text+0x54
> [   1.0000000] cpu0: End traceback...
> Stopped in pid 0.0 (system) at  netbsd:cpu_Debugger+0x4:        bx      r14
>
> It is a systematic problem, every time you try booting the board it panics. It could be a problem on my specific board, it is part of a project and I work only on the OS part of the system, not on the fpga side.
>
> The board uses a MYS-7Z020-C(766)PCBA as main CPU ( Zynq family 7020 ) and works without any problem with a custom built poky linux distribution.
>
> I hope this can help.
> M.
>
> > How-To-Repeat:
>
> > Fix: