I know it's been a year and a half since you submitted this report to the 
mailing list, but was this problem ever resolved?  I think I'm seeing 
something similar in the 2.4.23 kernel.

Thanks!

Reply via email to