With 2.6.28-git5 the problem is not reproducible with the steps
described in the original report, but still occurs under other
circumstances (which I do not have a simple testcase for, but
which work fine under 2.6.18).



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to