From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] win woe
Date: Mon, 18 Jun 2007 11:08:18 -0400 [thread overview]
Message-ID: <f8c229fdb95577f67c4753bcc5c224d7@coraid.com> (raw)
In-Reply-To: <737f7061a8946454b4636f893e6d30d6@coraid.com>
just cleaning out my mailbox. this is still an annoying problem i haven't
had the time to track down.
it happens anytime one hits del with buffered data to be written out, not just with
serial consoles.
On Mon Nov 27 20:49:15 EST 2006, quanstro@coraid.com wrote:
> has anybody else had trouble with win giving "win: pendingS = -6" (or whatever
> negative number it happens to be) messages? they seem to be frequent and
> unrecoverable with serial consoles.
>
> the relevant code seems to be:
>
> main.c:465: if(pendingS < 0)
> main.c:466: fprint(2, "win: pendingS = %d\n", pendingS);
>
> but it's not clear why this code is firing. is it just the case the q1 and q0 have been swapped?
> or are events getting out-of-order?
>
> - erik
prev parent reply other threads:[~2007-06-18 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 20:07 erik quanstrom
2007-06-18 15:08 ` erik quanstrom [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=f8c229fdb95577f67c4753bcc5c224d7@coraid.com \
--to=quanstro@coraid.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).