Comment 6 for bug 1355624

Thanks for the reply. I'll see how it goes after todays upgrade to 3.13.0-34 first...
Problem with previous errorr is that I rebooted to 0-33 later that day, and well.. problem did not occur again.