NetBSD Problem Report #57068
From www@netbsd.org Sat Oct 22 09:58:13 2022
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 5F06A1A9239
for <gnats-bugs@gnats.NetBSD.org>; Sat, 22 Oct 2022 09:58:13 +0000 (UTC)
Message-Id: <20221022095742.55CE61A923A@mollari.NetBSD.org>
Date: Sat, 22 Oct 2022 09:57:42 +0000 (UTC)
From: oirammm@gmail.com
Reply-To: oirammm@gmail.com
To: gnats-bugs@NetBSD.org
Subject: a9tmr kernel panic on zynq-zturn Myir Board
X-Send-Pr-Version: www-1.0
>Number: 57068
>Category: kern
>Synopsis: a9tmr kernel panic on zynq-zturn Myir Board
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Oct 22 10:00:00 +0000 2022
>Closed-Date: Tue Oct 25 22:28:24 +0000 2022
>Last-Modified: Tue Oct 25 22:30:01 +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:
>Release-Note:
>Audit-Trail:
From: Jared McNeill <jmcneill@invisible.ca>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board
Date: Sat, 22 Oct 2022 08:00:34 -0300 (ADT)
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 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:
>
>
>
From: Mario Oriani <oirammm@gmail.com>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board
Date: Sat, 22 Oct 2022 14:40:26 +0200
--000000000000a30f6205eb9eddf6
Content-Type: text/plain; charset="UTF-8"
This is the full dmesg from the dowloaded arm image:
Press return to boot now, any other key for boot prompt
booting netbsd - starting in 0 seconds.
9125300+2446304+1403936 [455801+758192+576846]=0xe21abc
[ 1.0000000] NetBSD/evbarm (fdt) booting ...
[ 1.0000000] [ Kernel symbol table missing! ]
[ 1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
2003, 2004, 2005,
[ 1.0000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014,
2015, 2016, 2017,
[ 1.0000000] 2018, 2019, 2020, 2021, 2022
[ 1.0000000] The NetBSD Foundation, Inc. All rights reserved.
[ 1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[ 1.0000000] The Regents of the University of California. All rights
reserved.
[ 1.0000000] NetBSD 9.99.101 (GENERIC) #0: Wed Oct 19 22:34:10 UTC 2022
[ 1.0000000] mkrepro@mkrepro.NetBSD.org:
/usr/src/sys/arch/evbarm/compile/GENERIC
[ 1.0000000] total memory = 1024 MB
[ 1.0000000] avail memory = 987 MB
[ 1.0000000] armfdt0 (root)
[ 1.0000000] simplebus0 at armfdt0: Digilent Zybo Z7 board
[ 1.0000000] simplebus1 at simplebus0
[ 1.0000000] cpus0 at simplebus0
[ 1.0000000] simplebus2 at simplebus0
[ 1.0000000] cpu0 at cpus0: Cortex-A9 r3p0 (Cortex V7A core)
[ 1.0000000] cpu0: DC enabled IC enabled WB enabled LABT branch
prediction enabled
[ 1.0000000] cpu0: L1 32KB/32B 4-way (256 set) VIPT Instruction cache
[ 1.0000000] cpu0: L1 32KB/32B 4-way (256 set) write-back-locking-C PIPT
Data cache
[ 1.0000000] cpu0: L2 512KB/32B 8-way (2048 set) write-back-locking-D
PIPT Unified cache
[ 1.0000000] vfp0 at cpu0: NEON MPE (VFP 3.0+), rounding, NaN
propagation, denormals
[ 1.0000000] cpufreqdt0 at cpu0
[ 1.0000000] cpu1 at cpus0: disabled (unresponsive)
[ 1.0000000] syscon0 at simplebus1: System Controller Registers
[ 1.0000000] gic0 at simplebus1: GIC
[ 1.0000000] armgic0 at gic0: Generic Interrupt Controller, 96 sources
(85 valid)
[ 1.0000000] armgic0: 32 Priorities, 64 SPIs, 5 PPIs, 16 SGIs
[ 1.0000000] l2cc0 at simplebus1
[ 1.0000000] arml2cc0 at l2cc0: ARM PL310 r3p2 L2 Cache Controller
(disabled)
[ 1.0000000] arml2cc0: cache enabled
[ 1.0000000] a9tmr0 at simplebus1: couldn't get clock
[ 1.0000000] a9ptmr0 at simplebus1: couldn't get clock
[ 1.0000000] zynquart0 at simplebus1zynquart0: interrupting on GIC irq 82
[ 1.0000000] zynquart0: console
[ 1.0000000] fregulator0 at simplebus0: VCCPINT
[ 1.0000000] usbnopphy0 at simplebus0: USB PHY
[ 1.0000000] /amba/slcr@f8000000/clkc@100 at syscon0 not configured
[ 1.0000000] /amba/devcfg@f8007000 at simplebus1 not configured
[ 1.0000000] cemac0 at simplebus1cemac0: interrupting on GIC irq 54
[ 1.0000000] : Cadence Gigabit Ethernet Controller
[ 1.0000000] ukphy0 at cemac0 phy 3: OUI 0x0010a1, model 0x0022, rev. 2
[ 1.0000000] ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
1000baseT, 1000baseT-FDX, auto
[ 1.0000000] /amba/gpio@e000a000 at simplebus1 not configured
[ 1.0000000] /fpga-full at simplebus0 not configured
[ 1.0000000] armpmu0 at simplebus0: Performance Monitor Unit
[ 1.0000000] gpioleds0 at simplebus0:
[ 1.0000000] /amba/adc@f8007100 at simplebus1 not configured
[ 1.0000000] /amba/memory-controller@f8006000 at simplebus1 not configured
[ 1.0000000] /amba/spi@e000d000 at simplebus1 not configured
[ 1.0000000] sdhc0 at simplebus1: SD/MMC host controller
[ 1.0000000] sdhc0: interrupting on GIC irq 56
[ 1.0000000] sdhc0: SDHC 2.0, rev 137, PIO, 33333 kHz, embedded slot, HS
3.3V, 512 byte blocks
[ 1.0000000] sdmmc0 at sdhc0 slot 0
[ 1.0000000] /amba/dmac@f8003000 at simplebus1 not configured
[ 1.0000000] /amba/efuse@f800d000 at simplebus1 not configured
[ 1.0000000] /amba/timer@f8001000 at simplebus1 not configured
[ 1.0000000] /amba/timer@f8002000 at simplebus1 not configured
[ 1.0000000] ehci0 at simplebus1ehci0: interrupting on GIC irq 53
[ 1.0000000] ehci0: Zynq USB Controller id=5 revision=2 version=2
[ 1.0000000] ehci0: HCI revision=0x100
[ 1.0000000] ehci0: 1 host port, device capable, 12 endpoints
[ 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
The dtb is taken from here:
https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.3/evbarm-earmv7hf/binary/kernel/
zynq-zturn.dtb
The UBoot is from here:
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv7hf/9.3/All/u-boot-zynq-zybo-z7-2018.11.tgz
Thank you.
M.
Il giorno sab 22 ott 2022 alle ore 13:05 Jared McNeill <
jmcneill@invisible.ca> ha scritto:
> The following reply was made to PR kern/57068; it has been noted by GNATS.
>
> From: Jared McNeill <jmcneill@invisible.ca>
> To: gnats-bugs@netbsd.org
> Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org
> Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board
> Date: Sat, 22 Oct 2022 08:00:34 -0300 (ADT)
>
> 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 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:
> >
> >
> >
>
>
--000000000000a30f6205eb9eddf6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">This is the full dmesg from the dowloaded arm image:<div><=
br><div>Press return to boot now, any other key for boot prompt<br>booting =
netbsd - starting in 0 seconds.<br>9125300+2446304+1403936 [455801+758192+5=
76846]=3D0xe21abc<br>[ =C2=A0 1.0000000] NetBSD/evbarm (fdt) booting ...<br=
>[ =C2=A0 1.0000000] [ Kernel symbol table missing! ]<br>[ =C2=A0 1.0000000=
] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,=
<br>[ =C2=A0 1.0000000] =C2=A0 =C2=A0 2006, 2007, 2008, 2009, 2010, 2011, 2=
012, 2013, 2014, 2015, 2016, 2017,<br>[ =C2=A0 1.0000000] =C2=A0 =C2=A0 201=
8, 2019, 2020, 2021, 2022<br>[ =C2=A0 1.0000000] =C2=A0 =C2=A0 The NetBSD F=
oundation, Inc.=C2=A0 All rights reserved.<br>[ =C2=A0 1.0000000] Copyright=
(c) 1982, 1986, 1989, 1991, 1993<br>[ =C2=A0 1.0000000] =C2=A0 =C2=A0 The =
Regents of the University of California.=C2=A0 All rights reserved.<br><br>=
[ =C2=A0 1.0000000] NetBSD 9.99.101 (GENERIC) #0: Wed Oct 19 22:34:10 UTC 2=
022<br>[ =C2=A0 1.0000000] =C2=A0mkrepro@mkrepro.NetBSD.org:/usr/src/sys/ar=
ch/evbarm/compile/GENERIC<br>[ =C2=A0 1.0000000] total memory =3D 1024 MB<b=
r>[ =C2=A0 1.0000000] avail memory =3D 987 MB<br>[ =C2=A0 1.0000000] armfdt=
0 (root)<br>[ =C2=A0 1.0000000] simplebus0 at armfdt0: Digilent Zybo Z7 boa=
rd<br>[ =C2=A0 1.0000000] simplebus1 at simplebus0<br>[ =C2=A0 1.0000000] c=
pus0 at simplebus0<br>[ =C2=A0 1.0000000] simplebus2 at simplebus0<br>[ =C2=
=A0 1.0000000] cpu0 at cpus0: Cortex-A9 r3p0 (Cortex V7A core)<br>[ =C2=A0 =
1.0000000] cpu0: DC enabled IC enabled WB enabled LABT branch prediction en=
abled<br>[ =C2=A0 1.0000000] cpu0: L1 32KB/32B 4-way (256 set) VIPT Instruc=
tion cache<br>[ =C2=A0 1.0000000] cpu0: L1 32KB/32B 4-way (256 set) write-b=
ack-locking-C PIPT Data cache<br>[ =C2=A0 1.0000000] cpu0: L2 512KB/32B 8-w=
ay (2048 set) write-back-locking-D PIPT Unified cache<br>[ =C2=A0 1.0000000=
] vfp0 at cpu0: NEON MPE (VFP 3.0+), rounding, NaN propagation, denormals<b=
r>[ =C2=A0 1.0000000] cpufreqdt0 at cpu0<br>[ =C2=A0 1.0000000] cpu1 at cpu=
s0: disabled (unresponsive)<br>[ =C2=A0 1.0000000] syscon0 at simplebus1: S=
ystem Controller Registers<br>[ =C2=A0 1.0000000] gic0 at simplebus1: GIC<b=
r>[ =C2=A0 1.0000000] armgic0 at gic0: Generic Interrupt Controller, 96 sou=
rces (85 valid)<br>[ =C2=A0 1.0000000] armgic0: 32 Priorities, 64 SPIs, 5 P=
PIs, 16 SGIs<br>[ =C2=A0 1.0000000] l2cc0 at simplebus1<br>[ =C2=A0 1.00000=
00] arml2cc0 at l2cc0: ARM PL310 r3p2 L2 Cache Controller (disabled)<br>[ =
=C2=A0 1.0000000] arml2cc0: cache enabled<br>[ =C2=A0 1.0000000] a9tmr0 at =
simplebus1: couldn't get clock<br>[ =C2=A0 1.0000000] a9ptmr0 at simple=
bus1: couldn't get clock<br>[ =C2=A0 1.0000000] zynquart0 at simplebus1=
zynquart0: interrupting on GIC irq 82<br><br>[ =C2=A0 1.0000000] zynquart0:=
console<br>[ =C2=A0 1.0000000] fregulator0 at simplebus0: VCCPINT<br>[ =C2=
=A0 1.0000000] usbnopphy0 at simplebus0: USB PHY<br>[ =C2=A0 1.0000000] /am=
ba/slcr@f8000000/clkc@100 at syscon0 not configured<br>[ =C2=A0 1.0000000] =
/amba/devcfg@f8007000 at simplebus1 not configured<br>[ =C2=A0 1.0000000] c=
emac0 at simplebus1cemac0: interrupting on GIC irq 54<br>[ =C2=A0 1.0000000=
] : Cadence Gigabit Ethernet Controller<br>[ =C2=A0 1.0000000] ukphy0 at ce=
mac0 phy 3: OUI 0x0010a1, model 0x0022, rev. 2<br>[ =C2=A0 1.0000000] ukphy=
0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX=
, auto<br>[ =C2=A0 1.0000000] /amba/gpio@e000a000 at simplebus1 not configu=
red<br>[ =C2=A0 1.0000000] /fpga-full at simplebus0 not configured<br>[ =C2=
=A0 1.0000000] armpmu0 at simplebus0: Performance Monitor Unit<br>[ =C2=A0 =
1.0000000] gpioleds0 at simplebus0:<br>[ =C2=A0 1.0000000] /amba/adc@f80071=
00 at simplebus1 not configured<br>[ =C2=A0 1.0000000] /amba/memory-control=
ler@f8006000 at simplebus1 not configured<br>[ =C2=A0 1.0000000] /amba/spi@=
e000d000 at simplebus1 not configured<br>[ =C2=A0 1.0000000] sdhc0 at simpl=
ebus1: SD/MMC host controller<br>[ =C2=A0 1.0000000] sdhc0: interrupting on=
GIC irq 56<br>[ =C2=A0 1.0000000] sdhc0: SDHC 2.0, rev 137, PIO, 33333 kHz=
, embedded slot, HS 3.3V, 512 byte blocks<br>[ =C2=A0 1.0000000] sdmmc0 at =
sdhc0 slot 0<br>[ =C2=A0 1.0000000] /amba/dmac@f8003000 at simplebus1 not c=
onfigured<br>[ =C2=A0 1.0000000] /amba/efuse@f800d000 at simplebus1 not con=
figured<br>[ =C2=A0 1.0000000] /amba/timer@f8001000 at simplebus1 not confi=
gured<br>[ =C2=A0 1.0000000] /amba/timer@f8002000 at simplebus1 not configu=
red<br>[ =C2=A0 1.0000000] ehci0 at simplebus1ehci0: interrupting on GIC ir=
q 53<br><br>[ =C2=A0 1.0000000] ehci0: Zynq USB Controller id=3D5 revision=
=3D2 version=3D2<br>[ =C2=A0 1.0000000] ehci0: HCI revision=3D0x100<br>[ =
=C2=A0 1.0000000] ehci0: 1 host port, device capable, 12 endpoints<br>[ =C2=
=A0 1.0000000] panic: kernel diagnostic assertion "freq !=3D 0" f=
ailed: file "/usr/src/sys/arch/arm/cortex/a9tmr.c", line 299<br>[=
=C2=A0 1.0000000] cpu0: Begin traceback...<br>[ =C2=A0 1.0000000] 0x80c8da=
2c: netbsd:db_panic+0x14<br>[ =C2=A0 1.0000000] 0x80c8da4c: netbsd:vpanic+0=
x114<br>[ =C2=A0 1.0000000] 0x80c8da64: netbsd:kern_assert+0x40<br>[ =C2=A0=
1.0000000] 0x80c8daa4: netbsd:a9tmr_delay+0x14c<br>[ =C2=A0 1.0000000] 0x8=
0c8dae4: netbsd:zynqusb_attach_common+0x284<br>[ =C2=A0 1.0000000] 0x80c8db=
ac: netbsd:zynqusb_attach+0xd0<br>[ =C2=A0 1.0000000] 0x80c8dbe4: netbsd:co=
nfig_attach_internal+0x1d8<br>[ =C2=A0 1.0000000] 0x80c8dc2c: netbsd:config=
_found+0xe4<br>[ =C2=A0 1.0000000] 0x80c8dd9c: netbsd:fdt_scan+0x2ac<br>[ =
=C2=A0 1.0000000] 0x80c8ddbc: netbsd:fdt_rescan+0x58<br>[ =C2=A0 1.0000000]=
0x80c8ddf4: netbsd:config_attach_internal+0x1d8<br>[ =C2=A0 1.0000000] 0x8=
0c8de3c: netbsd:config_found+0xe4<br>[ =C2=A0 1.0000000] 0x80c8de7c: netbsd=
:arm_fdt_attach+0xa4<br>[ =C2=A0 1.0000000] 0x80c8deb4: netbsd:config_attac=
h_internal+0x1d8<br>[ =C2=A0 1.0000000] 0x80c8def4: netbsd:config_rootfound=
+0x74<br>[ =C2=A0 1.0000000] 0x80c8df14: netbsd:cpu_configure+0x68<br>[ =C2=
=A0 1.0000000] 0x80c8df9c: netbsd:main+0x32c<br>[ =C2=A0 1.0000000] 0x80c8d=
fac: netbsd:kernel_text+0x54<br>[ =C2=A0 1.0000000] cpu0: End traceback...<=
br>Stopped in pid 0.0 (system) at =C2=A0netbsd:cpu_Debugger+0x4: =C2=A0 =C2=
=A0 =C2=A0 =C2=A0bx =C2=A0 =C2=A0 =C2=A0r14<br></div><div><br></div><div>Th=
e dtb is taken from here:</div><div><br></div><div><a href=3D"https://cdn.n=
etbsd.org/pub/NetBSD/NetBSD-9.3/evbarm-earmv7hf/binary/kernel/">https://cdn=
.netbsd.org/pub/NetBSD/NetBSD-9.3/evbarm-earmv7hf/binary/kernel/</a><br></d=
iv><div><br></div><div>zynq-zturn.dtb</div><div><br></div><div>The UBoot is=
from here:</div><div><br></div><div><a href=3D"http://cdn.netbsd.org/pub/p=
kgsrc/packages/NetBSD/earmv7hf/9.3/All/u-boot-zynq-zybo-z7-2018.11.tgz">htt=
p://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv7hf/9.3/All/u-boot-zynq-=
zybo-z7-2018.11.tgz</a><br></div><div><br></div><div>Thank you.</div><div>M=
.</div><div><br></div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">Il giorno sab 22 ott 2022 alle ore 13:05 Jare=
d McNeill <<a href=3D"mailto:jmcneill@invisible.ca">jmcneill@invisible.c=
a</a>> ha scritto:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">The following reply was made to PR kern/57068; it has been noted by G=
NATS.<br>
<br>
From: Jared McNeill <<a href=3D"mailto:jmcneill@invisible.ca" target=3D"=
_blank">jmcneill@invisible.ca</a>><br>
To: <a href=3D"mailto:gnats-bugs@netbsd.org" target=3D"_blank">gnats-bugs@n=
etbsd.org</a><br>
Cc: <a href=3D"mailto:kern-bug-people@netbsd.org" target=3D"_blank">kern-bu=
g-people@netbsd.org</a>, <a href=3D"mailto:gnats-admin@netbsd.org" target=
=3D"_blank">gnats-admin@netbsd.org</a>, <a href=3D"mailto:netbsd-bugs@netbs=
d.org" target=3D"_blank">netbsd-bugs@netbsd.org</a><br>
Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board<br>
Date: Sat, 22 Oct 2022 08:00:34 -0300 (ADT)<br>
<br>
=C2=A0Need more info to analyze this:<br>
<br>
=C2=A0 =C2=A0- Please include the full dmesg, not just the panic message.<b=
r>
=C2=A0 =C2=A0- Version of U-Boot used (is it from pkgsrc?).<br>
=C2=A0 =C2=A0- Is the dtb the one built with the kernel or from somewhere e=
lse?<br>
<br>
=C2=A0Thanks!<br>
=C2=A0Jared<br>
<br>
<br>
=C2=A0On Sat, 22 Oct 2022, <a href=3D"mailto:oirammm@gmail.com" target=3D"_=
blank">oirammm@gmail.com</a> wrote:<br>
<br>
=C2=A0>> Number:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A057068<br>
=C2=A0>> Category:=C2=A0 =C2=A0 =C2=A0 =C2=A0kern<br>
=C2=A0>> Synopsis:=C2=A0 =C2=A0 =C2=A0 =C2=A0a9tmr kernel panic on zy=
nq-zturn Myir Board<br>
=C2=A0>> Confidential:=C2=A0 =C2=A0no<br>
=C2=A0>> Severity:=C2=A0 =C2=A0 =C2=A0 =C2=A0serious<br>
=C2=A0>> Priority:=C2=A0 =C2=A0 =C2=A0 =C2=A0medium<br>
=C2=A0>> Responsible:=C2=A0 =C2=A0 kern-bug-people<br>
=C2=A0>> State:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 open<br>
=C2=A0>> Class:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 sw-bug<br>
=C2=A0>> Submitter-Id:=C2=A0 =C2=A0net<br>
=C2=A0>> Arrival-Date:=C2=A0 =C2=A0Sat Oct 22 10:00:00 +0000 2022<br>
=C2=A0>> Originator:=C2=A0 =C2=A0 =C2=A0Mario O.<br>
=C2=A0>> Release:=C2=A0 =C2=A0 =C2=A0 =C2=A0 9.3 4 Aug. 2022<br>
=C2=A0>> Organization:<br>
=C2=A0>> Environment:<br>
=C2=A0> Cannot give uname -a, the system panics.<br>
=C2=A0>> Description:<br>
=C2=A0> Hi all,<br>
=C2=A0> I suspect there is a problem at least on the evbarm-earmv7hf bin=
ary release of install images. After booting from an sd card with the GENER=
IC.ub kernel, using U-Boot and giving the right dtb zynq-zturn.dtb, the sys=
tem panics after initializing the ehci0 usb controller, complaining about t=
he a9tmr0.<br>
=C2=A0><br>
=C2=A0> Using a prebuilt image from=C2=A0 =C2=A0 <a href=3D"https://nycd=
n.netbsd.org/pub/arm/" rel=3D"noreferrer" target=3D"_blank">https://nycdn.n=
etbsd.org/pub/arm/</a> ( 32bit Generic Build: 202210211110Z ) the problem b=
ecomes clear, here is the output of the kernel panic:<br>
=C2=A0><br>
=C2=A0> [=C2=A0 =C2=A01.0000000] panic: kernel diagnostic assertion &quo=
t;freq !=3D 0" failed: file "/usr/src/sys/arch/arm/cortex/a9tmr.c=
", line 299<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] cpu0: Begin traceback...<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8da2c: netbsd:db_panic+0x14<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8da4c: netbsd:vpanic+0x114<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8da64: netbsd:kern_assert+0x40<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8daa4: netbsd:a9tmr_delay+0x14c<br=
>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dae4: netbsd:zynqusb_attach_commo=
n+0x284<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dbac: netbsd:zynqusb_attach+0xd0<=
br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dbe4: netbsd:config_attach_intern=
al+0x1d8<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dc2c: netbsd:config_found+0xe4<br=
>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dd9c: netbsd:fdt_scan+0x2ac<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8ddbc: netbsd:fdt_rescan+0x58<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8ddf4: netbsd:config_attach_intern=
al+0x1d8<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8de3c: netbsd:config_found+0xe4<br=
>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8de7c: netbsd:arm_fdt_attach+0xa4<=
br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8deb4: netbsd:config_attach_intern=
al+0x1d8<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8def4: netbsd:config_rootfound+0x7=
4<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8df14: netbsd:cpu_configure+0x68<b=
r>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8df9c: netbsd:main+0x32c<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] 0x80c8dfac: netbsd:kernel_text+0x54<br>
=C2=A0> [=C2=A0 =C2=A01.0000000] cpu0: End traceback...<br>
=C2=A0> Stopped in pid 0.0 (system) at=C2=A0 netbsd:cpu_Debugger+0x4:=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 bx=C2=A0 =C2=A0 =C2=A0 r14<br>
=C2=A0><br>
=C2=A0> 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 pro=
ject and I work only on the OS part of the system, not on the fpga side.<br=
>
=C2=A0><br>
=C2=A0> 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 distrib=
ution.<br>
=C2=A0><br>
=C2=A0> I hope this can help.<br>
=C2=A0> M.<br>
=C2=A0><br>
=C2=A0>> How-To-Repeat:<br>
=C2=A0><br>
=C2=A0>> Fix:<br>
=C2=A0><br>
=C2=A0><br>
=C2=A0><br>
<br>
</blockquote></div>
--000000000000a30f6205eb9eddf6--
From: Robert Swindells <rjs@fdy2.co.uk>
To: gnats-bugs@NetBSD.org
Cc: oirammm@gmail.com, jmcneill@invisible.ca
Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board
Date: Sat, 22 Oct 2022 14:25:56 +0100
A NetBSD/arm GENERIC kernel isn't expected to boot on a Zynq system.
It requres someone to write a clock and reset driver for it.
From: Jared McNeill <jmcneill@invisible.ca>
To: Robert Swindells <rjs@fdy2.co.uk>
Cc: gnats-bugs@NetBSD.org, oirammm@gmail.com
Subject: Re: kern/57068: a9tmr kernel panic on zynq-zturn Myir Board
Date: Sat, 22 Oct 2022 11:17:57 -0300 (ADT)
In the context of a9tmr there is Zynq specific code to bypass the
requirement for a clock driver (see zync_platform_device_register):
https://nxr.netbsd.org/xref/src/sys/arch/arm/xilinx/zynq_platform.c#128
Lets find out why it doesn't work.
On Sat, 22 Oct 2022, Robert Swindells wrote:
>
> A NetBSD/arm GENERIC kernel isn't expected to boot on a Zynq system.
>
> It requres someone to write a clock and reset driver for it.
>
State-Changed-From-To: open->closed
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Tue, 25 Oct 2022 22:28:24 +0000
State-Changed-Why:
Fixed in -current, thanks for testing and thanks for the report!
From: "Jared D. McNeill" <jmcneill@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:
Subject: PR/57068 CVS commit: src/sys/arch
Date: Tue, 25 Oct 2022 22:27:49 +0000
Module Name: src
Committed By: jmcneill
Date: Tue Oct 25 22:27:49 UTC 2022
Modified Files:
src/sys/arch/arm/xilinx: files.zynq
src/sys/arch/evbarm/conf: GENERIC
Added Files:
src/sys/arch/arm/xilinx: zynq7000_clkc.c
Log Message:
Add basic Zynq-7000 PS clock subsystem driver.
PR# kern/57068
To generate a diff of this commit:
cvs rdiff -u -r1.1 -r1.2 src/sys/arch/arm/xilinx/files.zynq
cvs rdiff -u -r0 -r1.1 src/sys/arch/arm/xilinx/zynq7000_clkc.c
cvs rdiff -u -r1.108 -r1.109 src/sys/arch/evbarm/conf/GENERIC
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2022
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home