I filed a bug report - "System takes over 2 additional minutes to boot after updating to kernel 2.6.38.8-35".
This was in July. The problem was erratic. If I tried to trace it, it seemed to disappear. It persisted even after upgrading to 2.6.40. In fact, it seemed to be more consistent. Removing VirtualBox 'solved' the problem but not for long.
Then finally an entry in the system log messages helped!
Fortunately, I had not rebooted the system and let it try to boot for over 5 minutes.
It led to the realisation that I had been running network service even though it was not needed any more when using NetworkManager.
Now for the last three days, the system has been booting fine after I disabled the network service.
I will wait a few more days before filing a bug report against systemd - just to be sure.
This was in July. The problem was erratic. If I tried to trace it, it seemed to disappear. It persisted even after upgrading to 2.6.40. In fact, it seemed to be more consistent. Removing VirtualBox 'solved' the problem but not for long.
Then finally an entry in the system log messages helped!
Oct 25 15:22:28 amd avahi-daemon[1792]: Registering new address record for fe80::217:31ff:fe93:e65a on eth0.*.
Oct 25 15:27:26 amd systemd[1]: network.service operation timed out. Terminating.
Fortunately, I had not rebooted the system and let it try to boot for over 5 minutes.
It led to the realisation that I had been running network service even though it was not needed any more when using NetworkManager.
Now for the last three days, the system has been booting fine after I disabled the network service.
I will wait a few more days before filing a bug report against systemd - just to be sure.
No comments:
Post a Comment