severity normal thanks DamentZ wrote:
I found source of the hangs on NetworkManager - apparently if syslog is not running, it'll freeze after trying to enable my eth0 interface. I rebooted with syslogd enabled to catch a log and to my amazement, knetworkmanager was fully functional and reported that I was connected to a wired network.Curiously, I disabled syslogd and klogd and proceeded to reboot again. After logging in, knetworkmanager was stuck on the green orb icon (indicating it's in the process of some sort of connection). Then, I rebooted with NetworkManager set not to enable during boot and ran *NetworkManager --no-daemon*. It was able to correctly connect through my wired network without hanging. So, I'm not sure how to capture a log of it actually hanging for you guys, but I'm sure disabling syslogd and klogd makes it always reproducible.
Hm, unfortunately I'm unable to reproduce your problem. I disabled the syslogd and the only thing that changes during boot, is that the output of NetworkManager is sent to stdout instead to a log file, that's all.
It is still working fine and successfully connects.
Another interesting point, with syslogd running, NetworkManager doesn't output to the first virtual terminal during boot - maybe thats how its tied to its hanging...
No, it's intended behaviour. When syslogd is running, the output of NM is sent to the syslogd, if syslogd is not running, the output is sent to stdout/stderr.
I can't reproduce your problem here. Do you use static IPs, dhcp, anythingspecial?No, just standard dhcp, nothing special.
Could you strace the hanging NM instance please? Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
