NetBSD Problem Report #54138

From martin@aprisoft.de  Wed Apr 24 07:12:52 2019
Return-Path: <martin@aprisoft.de>
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 884D67A149
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 24 Apr 2019 07:12:52 +0000 (UTC)
Message-Id: <20190424071242.D85F95CC86C@emmas.aprisoft.de>
Date: Wed, 24 Apr 2019 09:12:42 +0200 (CEST)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: KASSERT fires: !cpu_intr_p()
X-Send-Pr-Version: 3.95

>Number:         54138
>Category:       kern
>Synopsis:       KASSERT fires: !cpu_intr_p()
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 24 07:15:00 +0000 2019
>Closed-Date:    Fri Sep 15 18:40:11 +0000 2023
>Last-Modified:  Fri Sep 15 18:40:11 +0000 2023
>Originator:     Martin Husemann
>Release:        NetBSD 8.99.37
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD nelly.aprisoft.de 8.99.37 NetBSD 8.99.37 (NELLY) #27: Tue Apr 23 15:22:06 CEST 2019 martin@seven-days-to-the-wolves.aprisoft.de:/work/src/sys/arch/sparc64/compile/NELLY sparc
Architecture: sparc
Machine: sparc
>Description:

This happend on a sparc64 machine (running a 64 bit sparc64 kernel) with sparc
(32bit) userland (but I guess that is irrelevant), while extracting sets
via NFS to a local raid (on sd0/sd1).

[ 339.0665453] panic: kernel diagnostic assertion "!cpu_intr_p()" failed: file "../../../../kern/subr_xcall.c", line 436 high priority xcall for function 0x11e36a0
[ 339.2411931] cpu0: Begin traceback...
[ 339.2859824] cpu0: End traceback...
[ 339.3266095] Frame pointer is at 0x1779630f1
[ 339.3266095] Call traceback:
[ 339.3266095]  netbsd:cpu_reboot+0x244(130ca78, 0, ffff, 0, 1211fe0, 1439400) fp = 1779631d1
[ 339.3266095]  netbsd:vpanic+0x174(104, 0, 1329858, 1469000, 4, 101dcb0c0) fp = 177963281
[ 339.3266095]  netbsd:kern_assert+0x34(1329858, 177963c78, 1471000, 1472400, 104, 1472508) fp = 177963331
[ 339.3266095]  netbsd:xc__highpri_intr+0xd8(1329858, 12fa0a0, 1308108, 1329838, 1b4, 11e36a0) fp = 1779633f1
[ 339.3266095]  netbsd:softint_dispatch+0x138(143d800, 0, 1322800, 1322800, 143d800, 6) fp = 1779634a1
[ 339.3266095]  netbsd:softint_fastintr+0x80(1000, 4, 0, 2000, 101dcb0c0, 177950360) fp = 177963571
[ 339.3266095]  netbsd:intr_biglock_wrapper+0x20(101dcb0c0, 4, 0, 1ffe8c06328, 1814000, 1) fp = 177963621
[ 339.3266095]  netbsd:100030+0(f005eaf0, 147a558, fffb1c88, 1, fffb1b88, 0) fp = fffb1e90

The function refferenced in the panic is:

(gdb) x/16i 0x11e36a0   
   0x11e36a0 <nullop>:  retl 
   0x11e36a4 <nullop+4>:        clr  %o0        ! 0x0


>How-To-Repeat:
n/a

>Fix:
n/a

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/54138: KASSERT fires: !cpu_intr_p()
Date: Thu, 25 Apr 2019 12:45:20 +0200

 I have one machine where I see this a lot, it makes -current completely
 unusabel there. Not sure what is special about it :-/

 Martin

State-Changed-From-To: open->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Fri, 15 Sep 2023 18:40:11 +0000
State-Changed-Why:
jdc recently fixed this by moving interrupt priorities above softint


>Unformatted:

Home	PR Database Search