I've found that the problem was backported into the stable stream since I cannot reproduce the issue with 2.6.26 but I can with 2.6.26.5. This is quite useful since there are only 3 relevant looking changesets in that range. I will bisect between these before confirming the culprit on mainline. I've had a private reply from someone who is seeing the same issue with 2.6.26.5 against a server running 2.6.18 (Debian Etch) which I think largely discounts the server from being at fault. Ian. -- Ian Campbell Everything ends badly. Otherwise it wouldn't end.
Attachment:
signature.asc
Description: This is a digitally signed message part
