9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kernel tag bug?
Date: Tue, 24 Mar 2009 12:59:41 -0700	[thread overview]
Message-ID: <dd6fe68a0903241259i3301946ag1a86420ca877b3a7@mail.gmail.com> (raw)
In-Reply-To: <9f3c09cec96bb24e7d8be1b3f2a601c8@quanstro.net>

On Tue, Mar 24, 2009 at 10:59 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> it looks like devcons is suffering from some sort of tag collision.
> a Rwrite is coming back for a Tread.
>
> Sat Jan 24 09:43:47: mnt: proc rc 10946: mismatch from /mnt/temp/data /dev/cons rep 0xf63661a8 tag 1 fid 1170 T116 R119 rp 1
> Sat Jan 24 10:06:26: unexpected reply tag 1; type 117
> Fri Jan 30 15:21:48: 336082 page: checked 75 page table entries
> Wed Mar 18 11:27:27: mnt: proc rc 4632855: mismatch from /mnt/temp/data /dev/cons rep 0xf69e84e8 tag 37 fid 5644 T116 R119 rp 37
>
> i don't immediately see the cause of the problem.

i've seen this for years in various forms
but it had never happened regularly enough
to track down, and it was never clear that it
was the kernel's fault (and not, say, the 9p server).

if you want to look for the problem, you might
find it easier in 9vx.  i see it in 9vx all the time
if i interrupt an outstanding 9p message by
typing DEL.  9fs sources; ls /n/sources; DEL
on a slow connection, for example.

russ


  reply	other threads:[~2009-03-24 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 17:59 erik quanstrom
2009-03-24 19:59 ` Russ Cox [this message]
2009-03-24 20:27   ` erik quanstrom
2009-03-24 20:34     ` Russ Cox

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=dd6fe68a0903241259i3301946ag1a86420ca877b3a7@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).