Comment # 10 on bug 960153 from Jan Kara

Created attachment 710597 [details]
Journal log from the resume

Here are interesting system messages from the reboot (full messages attached).
You can see NetworkManager reestablishing connections there and at one point:

Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: <info>  NetworkManager
state is now CONNECTED_SITE
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: <info>  Policy set 'Auto
Ethernet' (em1) as default for IPv4 routing and DNS.
Jan 18 08:24:39 quack2.suse.cz dns-resolver[23908]: ATTENTION: You have
modified /etc/resolv.conf. Leaving it untouched...
Jan 18 08:24:39 quack2.suse.cz dns-resolver[23910]: You can find my version in
/etc/resolv.conf.netconfig
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: <13>Jan 18 08:24:39
dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it
untouched...
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: <13>Jan 18 08:24:39
dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: ATTENTION: You have
modified /etc/resolv.conf.  Leaving it untouched...
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: You can find my version in
/etc/resolv.conf.netconfig ...
Jan 18 08:24:39 quack2.suse.cz nscd[968]: 968 monitored file `/etc/resolv.conf`
was moved into place, adding watch
Jan 18 08:24:39 quack2.suse.cz NetworkManager[1066]: <info>  (em1): Activation:
successful, device activated.

So at this point /etc/resolv.conf has apparently already been modified by the
NetworkManager but NetworkManager apparently *also* tried to update the
nameservers in resolv.conf via netconfig.

Also note that there is activation on wlan0 interface running in parallel,
however we got DHCP response on that interface only at 08:24:41 so that does
not seem directly responsible for this problem.