NetBSD Problem Report #53033

From www@NetBSD.org  Fri Feb 16 22:57:58 2018
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 2DEE07A104
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 16 Feb 2018 22:57:58 +0000 (UTC)
Message-Id: <20180216225757.4AD237A232@mollari.NetBSD.org>
Date: Fri, 16 Feb 2018 22:57:57 +0000 (UTC)
From: venture37@geeklan.co.uk
Reply-To: venture37@geeklan.co.uk
To: gnats-bugs@NetBSD.org
Subject: panic: lock error: Mutex: mutex_vector_enter,555: locking against myself
X-Send-Pr-Version: www-1.0

>Number:         53033
>Category:       kern
>Synopsis:       panic: lock error: Mutex: mutex_vector_enter,555: locking against myself
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 16 23:00:00 +0000 2018
>Last-Modified:  Wed Sep 19 02:15:00 +0000 2018
>Originator:     Sevan Janiyan
>Release:        NetBSD-HEAD
>Organization:
>Environment:
NetBSD/amd64 8.99.12
>Description:
I have a late 2009 13" Macbook which I have NetBSD installed on. I screwed up the disk partitioning and dk wedges hide the original disklabel info which means I can't correct things easily, so I built a new kernel without the DKWEDGE options, kernel boots and is unable to find root as fstab is incorrect now (expected), system sits at the prompt with the cursor flickering extremely rapidly before more usb devices are detected.
When ukbd0 is detected it reports
"This port is broken, it does not call cnpollc() before calling cngetc()
This show be fixed, but in will work anyway (for now)"

System continues detecting USB devices & panics with "panic: lock error: Mutex: mutex_vector_enter,555: locking against myself"

Backtrace is
vpanic()
snprintf()
lockdebug_abort()
mutex_vector_enter()
ohci_device_intr_start()
usbd_start_next()
ohci_softintr()
usbd_set_polling()
ukbd_cnpollc()
ukbd_cngetc()
wskbd_cngetc()
wsdisplay_getc()
cngetc()
cngetsn()
setroot()
main()
>How-To-Repeat:

>Fix:

>Audit-Trail:
From: Paul Goyette <paul@whooppee.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555:
 locking against myself
Date: Sat, 17 Feb 2018 07:04:41 +0800 (+08)

 > System continues detecting USB devices & panics with "panic: lock error: Mutex: mutex_vector_enter,555: locking against myself"
 >
 > Backtrace is
 > vpanic()
 > snprintf()
 > lockdebug_abort()
 > mutex_vector_enter()
 > ohci_device_intr_start()
 > usbd_start_next()
 > ohci_softintr()
 > usbd_set_polling()
 > ukbd_cnpollc()
 > ukbd_cngetc()
 > wskbd_cngetc()
 > wsdisplay_getc()
 > cngetc()
 > cngetsn()
 > setroot()
 > main()

 Looks pretty similar to my kern/53019



 +------------------+--------------------------+----------------------------+
 | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:          |
 | (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com   |
 | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org |
 +------------------+--------------------------+----------------------------+

From: Sevan Janiyan <venture37@geeklan.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555:
 locking against myself
Date: Fri, 16 Feb 2018 23:08:53 +0000

 Photo of the crash
 http://www.netbsd.org/~sevan/kern53033.jpg

From: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555:
 locking against myself
Date: Fri, 16 Feb 2018 18:44:00 -0500

 I also believe this is the same as I reported as kern/52944 back in
 January. Since in my case I'm running 8.0_BETA, LOCKDEBUG isn't
 enabled, so the basic fault reported looks a bit different than
 kern/53019. (Well, there were two variants depending on the age of
 the kernel.)

 Regards,

 Dave

From: Sevan Janiyan <venture37@geeklan.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555:
 locking against myself
Date: Sat, 17 Feb 2018 03:29:21 +0000

 On 02/16/18 23:10, Paul Goyette wrote:
 >  Looks pretty similar to my kern/53019

 Should I close this as a duplicate??


 Sevan

From: Sevan Janiyan <venture37@geeklan.co.uk>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555: locking against myself
Date: Sat, 17 Feb 2018 04:19:10 +0000

 > On 17 Feb 2018, at 00:55, "David H. Gutteridge" <dhgutteridge@sympatico.ca=
 > wrote:
 >=20
 > Since in my case I'm running 8.0_BETA, LOCKDEBUG isn't
 > enabled,

 I'm running the stock GENERIC config which also doesn't have it enabled by d=
 efault, albeit on -current.


 Sevan=

From: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/53033: panic: lock error: Mutex: mutex_vector_enter,555:
 locking against myself
Date: Sat, 17 Feb 2018 18:41:58 -0500

 On Sat, 17 Feb 2018, at 04:19:10 +0000, Sevan Janiyan wrote:
 >I'm running the stock GENERIC config which also doesn't have it
 >enabled by default, albeit on -current.

 Ah, I had it in my mind that -current had debugging enabled by default.
 That explains why our fault messages are effectively identical, then.
 In my case, there's some sort of underlying hardware issue or
 inconsistent order of execution during boot that intermittently lands
 me in a state where I can reproduce this. That part is separate from
 the USB keyboard issue, I'd guess.

 Dave

From: "David H. Gutteridge" <david@gutteridge.ca>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/53033
Date: Tue, 18 Sep 2018 22:11:46 -0400

 Hi,

 I've filed what I believe is a related bug as kern/52944. mrg@ has
 made some changes in -current that maybe fix this and asked for a
 re-test, so I thought I'd mention that here, too.

 Regards,

 Dave

Home	PR Database Search