> That was too good to be true: the problem is back, and I confirmed that > it doesn't appear right after boot but only "after a while". > So far it has appeared after a suspend+resume but not just after any > suspend/resume.
It re-appeared again (I rebooted in the mean time) and this time it appeared without being linked to any suspend+resume, so that was a red herring. What still seems to be valid is that once the problem appears only a reboot will "fix" it. === Stefan
