From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <dd6fe68a0909212251s2c2e6222tcfdf541e4285f311@mail.gmail.com>
References: <13426df10909211129n33481db3gb0ddf024cd67d90a@mail.gmail.com>
	<dd6fe68a0909212251s2c2e6222tcfdf541e4285f311@mail.gmail.com>
Date: Tue, 22 Sep 2009 10:27:01 -0700
Message-ID: <13426df10909221027u4279cd72hf7b651dfd120339b@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] 9vx (is this the right list)? import issue
Topicbox-Message-UUID: 754537da-ead5-11e9-9d60-3106f5b1d025

OK, a little more fooling around.

term% grep full *.c

(wait about a second, hit DEL)
grep: can't open apic.c: 'apic.c' './sys/src/9/pc/grep' does not exist
grep: can't open apm.c: 'apm.c' mount rpc error
grep: can't open archmp.c: 'archmp.c' mount rpc error
grep: can't open bios32.c: 'bios32.c' mount rpc error
grep: can't open cga.c: 'cga.c' mount rpc error

etc. in fact I get an error for each file in the directory.

I also get one of these for each file.
mnt: proc grep 90: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/devlml.c rep 0x16d7010 tag 3 fid 533 T112 R111 rp 3
mnt: proc grep 90: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/devlml.c rep 0x16d7010 tag 3 fid 533 T120 R113 rp 3
mnt: proc grep 90: mismatch from /net/tcp/0/data /n/o/sys/src/9/pc rep
0x16d7010 tag 3 fid 524 T110 R121 rp 3
mnt: proc grep 90: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/devmoipv6.c rep 0x16d7010 tag 3 fid 534 T112 R111 rp
3
mnt: proc grep 90: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/devmoipv6.c rep 0x16d7010 tag 3 fid 534 T120 R113 rp
3
mnt: proc grep 90: mismatch from /net/tcp/0/data /n/o/sys/src/9/pc rep
0x16d7010 tag 3 fid 524 T110 R121 rp 3
mnt: proc grep 90: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/devrtc.c rep 0x16d7010 tag 3 fid 535 T112 R111 rp 3

so what is interesting is that the grep did not die. It keeps trying
to open files and keeps failing. And then, finally:

term% ls
ls: .: clone failed
term%

So, we see lots of guys with the same tag, with a T and R mismatch,
with T and R like open and clunk, with the apparent problem that they
are all using tag 3.

I'm wondering if there is not a problem with the way tags are flushed
when there is an interrupt.

As an experiment I commented out the free in the freetag code.

Better: now I just get this:
mnt: proc grep 78: mismatch from /net/tcp/0/data
/n/o/sys/src/9/pc/apic.c rep 0x1491c60 tag 2 fid 454 T120 R117 rp 2
after the DEL, TCLUNK gets an RREAD (which makes a sort of sense)

and the when I ls .

mnt: proc rc 80: mismatch from /net/tcp/0/data /n/o/sys/src/9/pc rep
0x1491c60 tag 2 fid 421 T110 R121 rp 2

Twalk for the ls gets the RCLUNK

And from that point on it's all over.


Interesting.

ron