Hi Francois,
this is what I found and sent:
The error exists from patch 2 on. I did some network testing with
patch 1 and currently use it and have no errors so far.
From my experiences up to now patch 1 should be error free.
Do you need additional info?
2007/9/12, Francois Romieu [off-list ref]:
Karl Meyer [off-list ref] :
[...]
quoted
am am looking for this issue for some time now, but there where no
errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
officially), I also ran git-bisect (for more information see the older
messages in this thread).
2.6.22-r2 in gentoo is based on 2.6.22.1. It is way before
0e4851502f846b13b29b7f88f1250c980d57e944 that you reported to work.
Thus it is not surprizing that it works.
Any update regarding the patchkit that I sent on 2007/08/16 ?
It would help to narrow the culprit.
--
Ueimor