From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file server page faulting
Date: Sun, 15 Sep 2002 08:21:21 +0100 [thread overview]
Message-ID: <32b55f2d1ea41133b5a0754c29a7e1bd@9fs.org> (raw)
> maybe this will further confuse matters but provide more information on
> this problem:
>
Yes, I think so. The problem seems more motherboard related.
next reply other threads:[~2002-09-15 7:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 7:21 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 15:36 nigel
2002-09-15 2:22 Geoff Collyer
2002-09-13 15:57 Fco.J.Ballesteros
2002-09-13 15:37 nigel
2002-09-13 16:37 ` Andrew
2002-09-13 15:14 nigel
2002-09-13 15:23 ` Andrew
2002-09-14 2:09 ` Andrew
2002-09-16 9:47 ` Douglas A. Gwyn
2002-09-16 15:13 ` Jack Johnson
2002-09-16 15:30 ` Andrew
2002-09-13 15:06 Fco.J.Ballesteros
2002-09-13 15:28 ` Andrew
2002-09-12 6:57 nigel
2002-09-13 15:01 ` Andrew
2002-09-12 4:50 Andrew
2002-09-12 14:04 ` FJ Ballesteros
2002-09-14 14:27 ` Andrew
2002-09-14 23:48 ` Andrew
2002-09-15 23:51 ` Andrew
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=32b55f2d1ea41133b5a0754c29a7e1bd@9fs.org \
--to=nigel@9fs.org \
--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).