I believe that this problem is now resolved. A recent MFC overlooked one critical change. That change was MFCed a few minutes ago. So, please update your kernel. Regards, Alan