Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

assertion (pinned->l_flag & LW_RUNNING) != 0 failed

To: current-users%netbsd.org@localhost
Subject: assertion (pinned->l_flag & LW_RUNNING) != 0 failed
From: coypu%sdf.org@localhost
Date: Sat, 25 Jan 2020 09:13:49 +0000

hi folks,

-current is getting even less reliable at booting for me.

I think the thing I'm doing unusual is having an Android phone connected
by USB. It's pretty chatty at boot compared to my other USB devices.

It's hitting this assertion (in kern_softint.c:854).

It seems to be new, but I haven't upgraded -current in a while.

Follow-Ups:
- Re: assertion (pinned->l_flag & LW_RUNNING) != 0 failed
  - From: Andrew Doran

Prev by Date: Re: overflow in libsa dosfs, feature for efiboot (patches provided)
Next by Date: config(1) warning for amd64 release
Previous by Thread: Spidermonkey185 fails to build/install
Next by Thread: Re: assertion (pinned->l_flag & LW_RUNNING) != 0 failed
Indexes:

Home | Main Index | Thread Index | Old Index