pcp
[Top] [All Lists]

Re: New results for cases 154,187,189 and 232

To: "Zhang, Sonic" <sonic.zhang@xxxxxxxxx>
Subject: Re: New results for cases 154,187,189 and 232
From: kenmcd@xxxxxxxxxxxxxxxxx
Date: Mon, 6 Jan 2003 22:00:31 +1100 (EST)
Cc: "PCP (E-mail)" <pcp@xxxxxxxxxxx>
In-reply-to: <957BD1C2BF3CD411B6C500A0C944CA2602AFAF8E@pdsmsx32.pd.intel.com>
Reply-to: kenmcd@xxxxxxxxxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Fri, 3 Jan 2003, Zhang, Sonic wrote:

> Hi,
> 
>       See the attachments. It seems there are some errors in your revised
> cases. Please check.

154
        This makes no sense to me, it works just fine here ... the CR
        stuff looks like the file got mangled in transit or as you
        unpacked it ... I'd need to see the output from:

                $ wc 154
                $ sh -x 154

187
        Ditto

189
        Ditto

I've attached versions of 154, 187 and 189 again in case it is an e-mail
transmission problem.

>       I also attach the 232.nine file, which is the output of command
> "./sudo src-oss/torture_indom -Dall nfs.server.reqs" in your suggestion for
> case 232.

Hmm ... need to look at this some more, but it seems to be a /proc
parsing problem.  Can you send me the output from

        $ cat /proc/net/rpc/nfsd

Mine looks like ...

rc 0 0 0
fh 0 0 0 0 0
io 0 0
th 8 0 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
ra 16 0 0 0 0 0 0 0 0 0 0 0
net 0 0 0 0
rpc 0 0 0 0 0
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

I know that for some versions of Linux the proc2 line is not correct,
and you may be hitting this.

>       We won't test any cisco specific features, so we won't concern case
> 159 any more.

OK.

Attachment: 154
Description: 154

Attachment: 187
Description: 187

Attachment: 189
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>