This is happening regularly during the first boot(s) after kernel or xorg updates. Is it possible it could be related to something like ureadahead?
This is happening regularly during the first boot(s) after kernel or xorg updates. Is it possible it could be related to something like ureadahead?