> Kernel devq seem to be aware of this problem, so maybe we need just to > wait a little more. Yes, I also think we should wait. My feeling is that this will get solved soon. - Dietmar