From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pipewrite hi 80107fd4
Date: Thu, 4 Nov 2004 14:51:48 -0500 [thread overview]
Message-ID: <ee9e417a0411041151505acacd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0411040912540.1002@linux.site>
> This is on Xen/Plan 9.
>
> I'm still seeing these, even though I keep thinking I've fixed it.
>
> Any comments on what to look for are welcome :-)
you're running spl hi when you shouldn't be.
the problem is likely nowhere near the pipe code.
look for code fiddling with spl that you have changed
recently.
russ
next prev parent reply other threads:[~2004-11-04 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 16:13 Ronald G. Minnich
2004-11-04 19:51 ` Russ Cox [this message]
2004-11-04 20:31 ` Ronald G. Minnich
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=ee9e417a0411041151505acacd@mail.gmail.com \
--to=russcox@gmail.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).