I tried to rollback the kernel to 3.2.35, and the bug does not occur
anymore.

Reply via email to