From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Booting on slow CPUs
Date: Fri, 15 Mar 2002 20:10:11 +0200 [thread overview]
Message-ID: <20020315201011.J18259@cackle.proxima.alt.za> (raw)
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
next reply other threads:[~2002-03-15 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 18:10 Lucio De Re [this message]
2002-03-15 20:07 Russ Cox
2002-03-16 18:31 ` Lucio De Re
2002-03-16 18:55 Russ Cox
2002-03-17 7:26 ` Lucio De Re
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020315201011.J18259@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).