From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Via Rhine II and 9pxeload
Date: Mon, 17 Apr 2006 18:26:46 -0500 [thread overview]
Message-ID: <e10ff4cdf4bce9b6e90b40f32a478ae4@swtch.com> (raw)
In-Reply-To: <44440EDF.6030400@gmail.com>
9pxeload isn't the problem. 9pccpu starts over.
9pxeload doesn't have the problem because it doesn't
do the same careful tracking.
The message should tell you which io address is in use.
Then you can cat '#P/ioalloc' after booting to see who has it.
Russ
prev parent reply other threads:[~2006-04-17 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 21:55 Lluís Batlle i Rossell
2006-04-17 23:26 ` Russ Cox [this message]
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=e10ff4cdf4bce9b6e90b40f32a478ae4@swtch.com \
--to=rsc@swtch.com \
--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).