Another odd thing - this time around, the problem appeared when switching from kernel 3.16 to 3.17 (in experimental). Switching back to 3.16 made it disappear. And again, it happens on one computer but not on another. Oh, don't ask why...