NetBSD Problem Report #52646
From www@NetBSD.org Mon Oct 23 23:32:26 2017
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 456007A16B
for <gnats-bugs@gnats.NetBSD.org>; Mon, 23 Oct 2017 23:32:26 +0000 (UTC)
Message-Id: <20171023233225.636B67A1D3@mollari.NetBSD.org>
Date: Mon, 23 Oct 2017 23:32:25 +0000 (UTC)
From: venture37@geeklan.co.uk
Reply-To: venture37@geeklan.co.uk
To: gnats-bugs@NetBSD.org
Subject: On BeagleBoardxm - Kernel panics on boot
X-Send-Pr-Version: www-1.0
>Number: 52646
>Category: port-arm
>Synopsis: On BeagleBoardxm - Kernel panics on boot
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-arm-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Oct 23 23:35:00 +0000 2017
>Closed-Date: Thu Oct 31 01:30:21 +0000 2019
>Last-Modified: Thu Oct 31 01:30:21 +0000 2019
>Originator: Sevan Janiyan
>Release: HEAD
>Organization:
>Environment:
>Description:
Attempting to boot NetBSD/evbarm on a beagleboardxm results in a panic during boot.
wsdisplay0 at omapfb0 kbdmux 1
omapwdt32k0 at obio1 addr 0x48314000-0x483147ff: rev 3.1
prcm0 at obio1 addr 0x48306000-0x48307fff: Power, Reset and Clock Management
com0 at obio2 addr 0x49020000-0x490203ff intr 74: OMAP UART, working fifo
com0: console
omapmputmr0 at obio2 addr 0x49032000-0x490320ff intr 38: OMAP MPU Timer #2
omapmputmr1 at obio2 addr 0x49034000-0x490340ff intr 39: OMAP MPU Timer #3
omapmputmr2 at obio2 addr 0x49036000-0x490360ff intr 40: OMAP MPU Timer #4
clock: hz=100 stathz=64
data_abort_handler: data_aborts fsr=0x1808 far=0xe103401c
Fatal kernel mode data abort: 'External Non-Linefetch Abort (S)'
trapframe: 0x80b51e60
FSR=00001808, FAR=e103401c, spsr=20000153
r0 =00000000, r1 =e1034000, r2 =0000001c, r3 =00000000
r4 =80865c5c, r5 =80b22eb8, r6 =807aae88, r7 =00000000
r8 =8030eb3c, r9 =9df10ed0, r10=87ffc01b, r11=80b51edc
r12=80b51e80, ssp=80b51eb0, slr=8030607c, pc =8030eb3c
Stopped in pid 0.1 (system) at netbsd:generic_bs_w_4: str r3, [r1, r2]
db> bt
0x80b51edc: netbsd:cpu_initclocks+0xc
0x80b51f44: netbsd:initclocks+0x48
0x80b51f9c: netbsd:main+0x250
0x80b51fac: netbsd:kernel_text+0x50
db> ps
PID LID S CPU FLAGS STRUCT LWP * NAME WAIT
0 20 2 0 200 9fe96860 iic2
0 19 2 0 200 9fe96b20 iic1
0 18 2 0 200 9fe96de0 iic0
0 17 2 0 200 9fe970a0 usbtask-dr
0 16 2 0 200 9fe97360 usbtask-hc
0 15 2 0 200 9fe97620 sysmon
0 14 2 0 200 9fe978e0 pmfsuspend
0 13 2 0 200 9fe97ba0 pmfevent
0 12 2 0 200 9ff28000 sopendfree
0 11 2 0 200 9ff282c0 nfssilly
0 10 2 0 200 9ff28580 cachegc
0 9 2 0 200 9ff28840 vdrain
0 8 2 0 200 9ff28b00 modunload
0 7 2 0 200 9ff28dc0 xcall/0
0 6 1 0 200 9ff29080 softser/0
0 5 1 0 200 9ff29340 softclk/0
0 4 1 0 200 9ff29600 softbio/0
0 3 1 0 200 9ff298c0 softnet/0
0 2 1 0 201 9ff29b80 idle/0
0 > 1 7 0 200 807ae2c0 swapper
I started off initially with u-boot 2017.09 from pkgsrc but also tested the Ti supplied image from 2017.01
>How-To-Repeat:
Boot latest armv7hf-el nightly build on a beagleboardxm
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: sevan@NetBSD.org
State-Changed-When: Thu, 31 Oct 2019 01:30:21 +0000
State-Changed-Why:
System boots fine on a modern FDTized kernel
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.