Subject: Re: lock errors on DIAGNOSTIC kernel after yamt-idlelwp merge
To: None <mhitch@lightning.msu.montana.edu>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: port-amiga
Date: 05/20/2007 15:07:59
In <Pine.NEB.4.64.0705191348240.19377@lightning.msu.montana.edu>
mhitch@lightning.msu.montana.edu wrote:
> Did this work after the newlock2 merge (before the idlelwp merge)?
Yes.
In <Pine.NEB.4.64.0705192230330.19377@lightning.msu.montana.edu>
mhitch@lightning.msu.montana.edu wrote:
> I've fixed the missing call to lwp_startup() in lwp_trampoline()
> (renamed from proc_trampoline to match other ports), and a DIAGNOSTIC
> kernel now boots and runs.
Thanks, both hp300 and news68k now work with DIAGNOSTIC.
> My LOCKDEBUG kernel gets further now, but fails later when starting
> init.
On hp300 and news68k, DIAGNOSTIC + LOCKDEBUG kernels seem working
even on multiuser.
---
Izumi Tsutsui