Subject: Re: What is wrong in -current?
To: Martin Husemann <martin@duskware.de>
From: Tobias Nygren <tnn@NetBSD.org>
List: port-sparc64
Date: 05/19/2007 14:24:39
On Sat, 19 May 2007 13:02:13 +0200
Martin Husemann <martin@duskware.de> wrote:

> Hi folks,
> 
> here are some details of what goes wrong in -current. This could be a bug
> introdcued with the idle-lwp changes, but the code looks correct; it could
> also be an old bug uncovered by the changes. Any suggestions about the
> cause are greatly appreciated ;-)
> 

I'm using a kernel without scsi or kbd controllers which allows
me to get a bit further:

root on hme0
Not mounting root fs.
Not waking up init.
mi_switch: curlwp is 0x1829bc0, calling cpu_switchto(0x1829bc0, 0xbe83900)
lwp_startup: new lwp 0xbe83900, previous lwp 0x1829bc0
mi_switch: curlwp is 0xbe83900, calling cpu_switchto(0xbe83900, 0xbe83680)
lwp_startup: new lwp 0xbe83680, previous lwp 0x1829bc0
Mutex error: mutex_vector_exit: exiting unheld spin mutex

In the second call to lwp_startup, shouldn't prev be 0xbe83900?
The mutex error comes from lwp_unlock()'ing 0x1829bc0 twice in lwp_startup().