Yes, It's a kernel bug (3.2.0-38-generic). When I switch kernel to 3.2.0-37-generic, the problem was disappeared.
Yes, It's a kernel bug (3.2.0-38-generic). When I switch kernel to 3.2.0-37-generic, the problem was disappeared.