preprocess_seqid_op: bad seqid (expected 2, got 50)

[J. Bruce Fields]

On Wed, Apr 04, 2007 at 06:52:24PM -0700, Bryce Harrington wrote:
> I'm working my way through the testruns that ran while I was gone last
> month.  Most of the errors are either known things already reported,
> but I noticed this one that looks interesting.

OK, thanks.  I'll take a look.  Obviously this may be difficult to track
down until we can figure out a reliable way to reproduce the problem.

I suppose we might want to demote more of these warnings to dprintk's,
on the theory that if they cause real problems then it should be up to
the client to complain.

But I can't see how a bad seqid error like that could be anything but a
bug on either the client or server's part, so I guess we should figure
that out first....

--b.