> Unless there is some bad race in the code, the hardware seems to be > pretty broken. Otherwise pure MSR read should not cause such a bug, > or? UV serial being what actual hardware and system ? > So to prevent the bug, revert to the old behavior. I.e. read modem > status only if we really have to -- for non-CLOCAL set serials. > Non-CLOCAL works on this hardware OK, I tried. See? I don't. The old behaviour is rather driver dependant eg whether it used serial_core or not. Doesn't look an unreasonable change though. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html