NetBSD Problem Report #53967

From www@NetBSD.org  Sun Feb 10 04:26:50 2019
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-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 179007A1D0
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 10 Feb 2019 04:26:50 +0000 (UTC)
Message-Id: <20190210042649.2190A7A1F5@mollari.NetBSD.org>
Date: Sun, 10 Feb 2019 04:26:49 +0000 (UTC)
From: dmarquess@gmail.com
Reply-To: dmarquess@gmail.com
To: gnats-bugs@NetBSD.org
Subject: CURRENT crashes on Raspberry Pi 3
X-Send-Pr-Version: www-1.0

>Number:         53967
>Category:       port-arm
>Synopsis:       CURRENT crashes on Raspberry Pi 3
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    skrll
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 10 04:30:00 +0000 2019
>Closed-Date:    Wed Mar 06 07:31:31 +0000 2019
>Last-Modified:  Wed Mar 06 07:31:31 +0000 2019
>Originator:     Dustin Marquess
>Release:        8.99.34
>Organization:
N/A
>Environment:
NetBSD 8.99.34 (GENERIC64) #0: Sat Feb  9 08:08:32 UTC 2019 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/GENERIC64
>Description:
Using NetBSD-evbarm-aarch64-201902090820Z-generic.img from http://www.invisible.ca/arm/ or ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201902091930Z/evbarm-aarch64/binary/gzimg/arm64.img.gz on a Raspberry PI 3, the kernel crashes every time with:

[   1.9934452] cpu_boot_secondary_processors: secondary processors hatched
[   2.0434498] sdmmc0 at sdhost0
[   2.0434498] sdhc0: SDHC 3.0, rev 153, platform DMA, 200000 kHz, HS 3.3V, re-tuning mode 1, 1024 byte blocks
[   2.0544874] sdmmc1 at sdhc0 slot 0
[   2.0544874] usb0 at dwctwo0: USB revision 2.0
[   2.0657679] panic: kernel assertion "src != ((void *)0)" failed: file "/usr/src/sys/lib/libkern/../../../common/lib/libc/string/strlcpy.c", line 61
[   2.0744897] cpu1: Begin traceback...
[   2.0844910] trace fp ffffffc0331fbb80
[   2.0844910] fp ffffffc0331fbba0 vpanic() at ffffffc00045eca8 netbsd:vpanic+0x198
[   2.0944911] fp ffffffc0331fbc00 kern_assert() at ffffffc00058e8e4 netbsd:kern_assert+0x5c
[   2.1044934] fp ffffffc0331fbc90 strlcpy() at ffffffc000572618 netbsd:strlcpy+0xc8
[   2.1044934] fp ffffffc0331fbcc0 pic_establish_intr() at ffffffc0000033e0 netbsd:pic_establish_intr+0x98
[   2.1144925] fp ffffffc0331fbd20 fdtbus_intr_establish_raw() at ffffffc00054dbb8 netbsd:fdtbus_intr_establish_raw+0x40
[   2.1244936] fp ffffffc0331fbd50 fdtbus_intr_establish() at ffffffc00054dc6c netbsd:fdtbus_intr_establish+0x44
[   2.1344938] fp ffffffc0331fbd90 pmu_fdt_init() at ffffffc00004af08 netbsd:pmu_fdt_init+0xc8
[   2.1444955] fp ffffffc0331fbea0 config_interrupts_thread() at ffffffc0004443a0 netbsd:config_interrupts_thread+0x60
address 0x100 is invalid
address 0xe8 is invalid
[   2.1644959] cpu1: End traceback...
Stopped in pid 0.45 (system) at netbsd:cpu_Debugger+0x4:        ret
db{1}> bt
trace tf 0xffffffc000cce8b0
---- trapframe 0xffffffc000cce8b0 (304 bytes) ----
    pc=ffffffc000068690,   spsr=0000000020000005
   esr=00000000f2000000,    far=d036a5b4ad5fdeba
    x0=0000000000000001,     x1=0000000000000000
    x2=ffffffc00000ee10,     x3=0000000000000001
    x4=0000000000000003,     x5=0000000000000000
    x6=0000000000000007,     x7=0000000000000000
    x8=0000000000000000,     x9=0000000000000006
   x10=0000000000000040,    x11=ffffffc0331fb930
   x12=ffffffc000444340,    x13=ffffffc000b4be75
   x14=ffffffc000adc920,    x15=ffff00003da3d044
   x16=ffffffc00072d858,    x17=0000000000000018
   x18=ffffffc000be8918,    x19=ffffffc000d51688
   x20=ffffffc000d516b0,    x21=0000000000000104
   x22=ffffffc0331fbc10,    x23=ffffffc0006ba5c8
   x24=ffffffc000d50000,    x25=0000000000000103
   x26=0000000000000000,    x27=ffffffc000070cb0
   x28=ffff00003d9a9600, fp=x29=ffffffc0331fbba0
lr=x30=ffffffc00045ecac,     sp=ffffffc0331fbba0
------------------------------------------------
fp ffffffc0331fbba0 cpu_Debugger() at ffffffc00006868c netbsd:cpu_Debugger
fp ffffffc0331fbc00 kern_assert() at ffffffc00058e8e4 netbsd:kern_assert+0x5c
fp ffffffc0331fbc90 strlcpy() at ffffffc000572618 netbsd:strlcpy+0xc8
fp ffffffc0331fbcc0 pic_establish_intr() at ffffffc0000033e0 netbsd:pic_establish_intr+0x98
fp ffffffc0331fbd20 fdtbus_intr_establish_raw() at ffffffc00054dbb8 netbsd:fdtbus_intr_establish_raw+0x40
fp ffffffc0331fbd50 fdtbus_intr_establish() at ffffffc00054dc6c netbsd:fdtbus_intr_establish+0x44
fp ffffffc0331fbd90 pmu_fdt_init() at ffffffc00004af08 netbsd:pmu_fdt_init+0xc8
fp ffffffc0331fbea0 config_interrupts_thread() at ffffffc0004443a0 netbsd:config_interrupts_thread+0x60
address 0x100 is invalid
address 0xe8 is invalid
db{1}>
>How-To-Repeat:
Load image on microSD and boot it
>Fix:

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: skrll@NetBSD.org
State-Changed-When: Sun, 10 Feb 2019 08:41:41 +0000
State-Changed-Why:
Please try an image with sys/arch/arm/broadcom/bcm2835_intr.c:1.17


From: Dustin Marquess <dmarquess@gmail.com>
To: gnats-bugs@netbsd.org
Cc: port-arm-maintainer@netbsd.org, netbsd-bugs@netbsd.org, 
	gnats-admin@netbsd.org, skrll@netbsd.org
Subject: Re: port-arm/53967 (CURRENT crashes on Raspberry Pi 3)
Date: Sun, 10 Feb 2019 23:33:33 -0600

 Didn't fix it, but it did change it at least:

 [   2.0504452] panic: kernel diagnostic assertion "pic ==
 &bcm2836mp_pic[cpuid]" failed: file
 "/usr/src/sys/arch/arm/broadcom/bcm2835_intr.c",
 [   2.0704464] cpu2: Begin traceback...
 [   2.0804474] trace fp ffffffc0331ebb70
 [   2.0804474] fp ffffffc0331ebb90 vpanic() at ffffffc00045f980
 netbsd:vpanic+0x198
 [   2.0904482] fp ffffffc0331ebbf0 kern_assert() at ffffffc00058f564
 netbsd:kern_assert+0x5c
 [   2.1104493] fp ffffffc0331ebc80 bcm2836mp_pic_unblock_irqs() at
 ffffffc00000f324 netbsd:bcm2836mp_pic_unblock_irqs+0x13c
 [   2.1204521] fp ffffffc0331ebcc0 pic_establish_intr() at
 ffffffc000003514 netbsd:pic_establish_intr+0x1cc
 [   2.1404512] fp ffffffc0331ebd20 fdtbus_intr_establish_raw() at
 ffffffc00054e848 netbsd:fdtbus_intr_establish_raw+0x40
 [   2.1504514] fp ffffffc0331ebd50 fdtbus_intr_establish() at
 ffffffc00054e8fc netbsd:fdtbus_intr_establish+0x44
 [   2.1704524] fp ffffffc0331ebd90 pmu_fdt_init() at ffffffc00004af08
 netbsd:pmu_fdt_init+0xc8
 [   2.1804537] fp ffffffc0331ebea0 config_interrupts_thread() at
 ffffffc000445068 netbsd:config_interrupts_thread+0x60
 address 0x100 is invalid
 address 0xe8 is invalid
 [   2.2104548] cpu2: End traceback..

 On Sun, Feb 10, 2019 at 2:41 AM <skrll@netbsd.org> wrote:
 >
 > Synopsis: CURRENT crashes on Raspberry Pi 3
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: skrll@NetBSD.org
 > State-Changed-When: Sun, 10 Feb 2019 08:41:41 +0000
 > State-Changed-Why:
 > Please try an image with sys/arch/arm/broadcom/bcm2835_intr.c:1.17
 >
 >
 >

State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 11 Feb 2019 16:51:46 +0000
State-Changed-Why:
feedback received! thanks


From: Dustin Marquess <dmarquess@gmail.com>
To: gnats-bugs@netbsd.org
Cc: port-arm-maintainer@netbsd.org, netbsd-bugs@netbsd.org, 
	gnats-admin@netbsd.org, dholland@netbsd.org
Subject: Re: port-arm/53967 (CURRENT crashes on Raspberry Pi 3)
Date: Fri, 22 Feb 2019 22:47:49 -0600

 So reverting src/sys/arch/arm/broadcom/bcm2835_intr.c back to revision
 1.15 and rebuilding the kernel makes it work again on my RPi3.  So the
 changes in 1.16 sadly break it.

 -Dustin

 On Mon, Feb 11, 2019 at 10:51 AM <dholland@netbsd.org> wrote:
 >
 > Synopsis: CURRENT crashes on Raspberry Pi 3
 >
 > State-Changed-From-To: feedback->open
 > State-Changed-By: dholland@NetBSD.org
 > State-Changed-When: Mon, 11 Feb 2019 16:51:46 +0000
 > State-Changed-Why:
 > feedback received! thanks
 >
 >
 >

Responsible-Changed-From-To: port-arm-maintainer->skrll
Responsible-Changed-By: skrll@NetBSD.org
Responsible-Changed-When: Sat, 23 Feb 2019 07:44:47 +0000
Responsible-Changed-Why:
Take.


From: Dustin Marquess <dmarquess@gmail.com>
To: gnats-bugs@netbsd.org
Cc: skrll@netbsd.org, port-arm-maintainer@netbsd.org, netbsd-bugs@netbsd.org, 
	gnats-admin@netbsd.org
Subject: Re: port-arm/53967 (CURRENT crashes on Raspberry Pi 3)
Date: Wed, 6 Mar 2019 00:14:59 -0600

 Okay, looks like this bug can be closed.  I just booted from the
 201903050120Z image and it booted correctly!

 Thanks for the hard work!

 On Sat, Feb 23, 2019 at 1:44 AM <skrll@netbsd.org> wrote:
 >
 > Synopsis: CURRENT crashes on Raspberry Pi 3
 >
 > Responsible-Changed-From-To: port-arm-maintainer->skrll
 > Responsible-Changed-By: skrll@NetBSD.org
 > Responsible-Changed-When: Sat, 23 Feb 2019 07:44:47 +0000
 > Responsible-Changed-Why:
 > Take.
 >
 >
 >

State-Changed-From-To: open->closed
State-Changed-By: mrg@NetBSD.org
State-Changed-When: Wed, 06 Mar 2019 07:31:31 +0000
State-Changed-Why:
closed at submitters request.  thanks!


>Unformatted:

Home	PR Database Search