Re: About support for rtVAX300

[Johnny Billquist <bqt%update.uu.se@localhost>]

On 2013-01-14 19:56, Martin Husemann wrote:
> On Mon, Jan 14, 2013 at 02:15:43PM +0100, Martin Husemann wrote:
> > I am not sure anyone tested the 6.0 release with a LOCKDEBUG kernel, I can
> > easily test -current or the tip of the netbsd-6 branch at least later today,
> > just to make sure this isn't something completely unrelated to your
> > hacking.
>
> I just tested -current with LOCKDEBUG:
>
> booted from type 46 unit 0 csr 0x26000080 adapter 27000000 slave 0
> boot device: sd0
> root on sd0a dumps on sd0b
> mountroot: trying nfs...
> mountroot: trying ffs...
> root file system type: ffs
> init: copying out path `/sbin/init' 11
> Mutex error: lockdebug_wantlock: locking against myself
>
> lock address : 0x00000000801c0620 type     :               spin
> initialized  : 0x00000000800a2602
> shared holds :                  0 exclusive:                  1
> shares wanted:                  0 exclusive:                  1
> current cpu  :                  0 last held:                  0
> current lwp  : 0x0000000087e4e800 last held: 0x0000000087e4e800
> last locked* : 0x00000000800a2eed unlocked : 000000000000000000
> owner field  : 0x0000000000011700 wait/spin:                0/1
>
> panic: LOCKDEBUG
>
> Bah - too many bugs everywhere.
>
> Holm: you should remove LOCKDEBUG for now.

Yup. But there are still plenty of other debug options that can be 
helpful as you try to get things running. LOCKDEBUG is actually one of 
those I don't think is that useful right here and now.

        Johnny

--
Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol