From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Message-ID: <20020315201011.J18259@cackle.proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [9fans] Booting on slow CPUs
Date: Fri, 15 Mar 2002 20:10:11 +0200
Topicbox-Message-UUID: 68297300-eaca-11e9-9e20-41e7f4b1d025

I seem to have isolated the problem to a race (almost literally)
condition between init0() terminating and whatever may be happening
behind the scenes that seems to beat init0() and cause it to stall.

If I empty init0()'s inner core (the bit controlled by !waserror()),
the booting procedure procceds, however crippled.  Various
strategically placed "print" calls give different degrees of progress.

If anybody can save me much further searching to find out which
operation is trashing init0(), I would appreciate the help greatly.

A question I have to ask, is whether poperror() within a section
controlled by !waserror() isn't in the wrong place.  But I don't for
one moment think this has any bearing on my quest.

++L