From: Rob Pike <robpike@gmail.com>
To: axwrt001@yahoo.com,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] It's not like lightning is it ...
Date: Tue, 8 Jun 2004 18:13:34 -0700 [thread overview]
Message-ID: <7359f04904060818134b9c415@mail.gmail.com> (raw)
In-Reply-To: <40C66353.1040805@yahoo.com>
i wonder if you have DMA turned off on your disk.
also, i've known CPUs to disable their caches
sometimes. is the machine healthy when running
other programs?
-rob
next prev parent reply other threads:[~2004-06-09 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 1:09 Matt Pidd-Cheshire
2004-06-09 1:13 ` Rob Pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 22:12 Matt Pidd-Cheshire
2004-06-08 22:17 ` boyd, rounin
2004-06-08 23:07 ` Matt Pidd-Cheshire
2004-06-08 23:32 ` Brantley Coile
2004-06-08 21:37 Matt Pidd-Cheshire
2004-06-07 22:08 ` Charles Forsyth
2004-06-08 22:43 ` Matt Pidd-Cheshire
2004-06-08 22:54 ` Geoff Collyer
2004-06-08 21:42 ` boyd, rounin
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=7359f04904060818134b9c415@mail.gmail.com \
--to=robpike@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=axwrt001@yahoo.com \
/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).