Although I won't exclude the fact that there may be a kernel bug, as
long as this condition is not reproducible with anything other than
amd, I'm going to need a lot of convincing.
> And I have no idea, how to circle in the
> bug.... (Kernel-debugging???)
That depends a lot on what it is amd actually does. Is it for instance
acting as a proxy between the client and the server, or in any other
way touching those packets?
I've never used amd, so I frankly have no idea what sort of special
thing it does on top of the standard NFS client. That's why I'd prefer
that Ion look into it.
If it turns out that a proper bugreport can be compiled that points to
a kernel NFS client problem, I'll be happy to help fix it. As things
stand, however, I am unable to reproduce any such problems on my own
setups and I have no spare time at the moment to start messing with
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/