NetBSD Problem Report #51527

From www@NetBSD.org  Tue Oct  4 05:23:07 2016
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 "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 99F107A274
	for <gnats-bugs@gnats.NetBSD.org>; Tue,  4 Oct 2016 05:23:07 +0000 (UTC)
Message-Id: <20161004052306.76A257A295@mollari.NetBSD.org>
Date: Tue,  4 Oct 2016 05:23:06 +0000 (UTC)
From: dhgutteridge@sympatico.ca
Reply-To: gutteridge@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: 7.99.39/macppc DIAGNOSTIC+DEBUG kernel consistently panics on halt(8) with a mutex error
X-Send-Pr-Version: www-1.0

>Number:         51527
>Category:       port-macppc
>Synopsis:       7.99.39/macppc DIAGNOSTIC+DEBUG kernel consistently panics on halt(8) with a mutex error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 04 05:25:00 +0000 2016
>Last-Modified:  Mon Jan 21 02:29:01 +0000 2019
>Originator:     David H. Gutteridge
>Release:        HEAD
>Organization:
>Environment:
>Description:
I can consistently trigger a kernel panic on 7.99.39/macppc when
invoking halt(8), either in single or multi user mode. (shutdown(8)
does not trigger a panic.) This is with DIAGNOSTIC and DEBUG enabled.

mutex error: mutex_vector_enter: assertion failed: curthread != 0

lock address : 0x0000000000000018
current cpu  :                  0
current lwp  : 000000000000000000
owner field  : 0x000000007c3142a0 wait/spin:               1/0

Skipping crash dump on recursive panic
panic: lock error: Mutex: mutex_vector_enter: assertion failed: curthread != 0: lock 0x0
Stopped in pid 0.0 () at       netbsd:vpanic+0x140:     addi     r4, r0, 0x0
0xff9ce3d0: at panic+0x4c
0xff9ce410: at lockdebug_abort+0x64
0xff9ce430: at mutex_spin_enter+0x214
0xff9ce470: at statclock+0x150
0xff9ce4a0: at hardclock+0xbc
0xff9ce4c0: at decr_intr+0x15c
0xff9ce4f0: at trapstart+0x7d8
0xff9ce5c0: at 0xff8ae574

>How-To-Repeat:
Invoke halt(8) either in single or multi user mode.
>Fix:

>Release-Note:

>Audit-Trail:
From: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-macppc/51527: 7.99.39/macppc DIAGNOSTIC+DEBUG kernel
 consistently panics on halt(8) with a mutex error
Date: Tue, 04 Oct 2016 02:01:13 -0400

 I should add, uname -a:

 NetBSD arcusv.nonus-porta.net 7.99.39 NetBSD 7.99.39 (ARCUSV_DEBUG) #0:
 Mon Oct  3 19:51:49 EDT 2016  disciple@arcus-v3.nonus-porta.net:/home/d
 isciple/netbsd-current/src/sys/arch/macppc/compile/obj/ARCUSV_DEBUG
 macppc

 The source is as of October 3 16:56 EST.

From: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-macppc/51527: 7.99.39/macppc DIAGNOSTIC+DEBUG kernel
 consistently panics on halt(8) with a mutex error
Date: Wed, 01 Feb 2017 15:10:52 -0500

 I just re-tested with 7.99.59, and this is still an issue.

 Dave

From: "David H. Gutteridge" <david@gutteridge.ca>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/51527: 7.99.39/macppc DIAGNOSTIC+DEBUG kernel
 consistently panics on halt(8) with a mutex error
Date: Sun, 28 Oct 2018 22:34:16 -0400

 This is still an issue with 8.99.25; the backtrace is similar, but
 more verbose. (Though ultimately it hits a double fault.)

 Dave


From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: port-macppc-maintainer@netbsd.org, gnats-admin@netbsd.org,
    netbsd-bugs@netbsd.org, dhgutteridge@sympatico.ca
Subject: re: port-macppc/51527: 7.99.39/macppc DIAGNOSTIC+DEBUG kernel consistently panics on halt(8) with a mutex error
Date: Tue, 30 Oct 2018 07:50:07 +1100

 this appears to be saying a that "curlwp" is NULL during shutdown.

 that shouldn't happen :-(


 .mrg.

>Unformatted:

Home	PR Database Search