[systemd-devel] systemd-journald watchdog timeout

[Damien Robert]

>From Lennart Poettering, Wed 22 Oct 2014 at 16:59:09 (+0200) :
> On Wed, 22.10.14 13:10, Damien Robert (damien.olivier.robert+gmane at gmail.com) wrote:
> That's difficult to say just from these logs.

Yeah that was what I feared.

> Can you reliably reproduce this? If so, can you attach strace to journald before this happens and see what it is doing?

Un(?)fortunately no.

> What I find interesting is that after the 3min pause suddenly the
> network driver allocates irq 55. This kinda makes me wonder if this
> might be a kernel/driver problem of some kind, where for some reason
> userspace (and hence journald) don't get scheduled?

I am not sure this is related, on a non troublesome boot I also have
similar lines:
Oct 22 09:12:39 feanor systemd[1]: Started Network Service.
Oct 22 09:12:39 feanor systemd[1]: Starting Network.
Oct 22 09:12:39 feanor systemd[1]: Reached target Network.
Oct 22 09:12:39 feanor systemd[1]: Starting Network Name Resolution...
Oct 22 09:12:39 feanor kernel: e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
Oct 22 09:12:39 feanor systemd-resolved[526]: Using system hostname 'feanor'.
Oct 22 09:12:39 feanor systemd[1]: Started Network Name Resolution.
Oct 22 09:12:39 feanor systemd[1]: Starting Multi-User System.
Oct 22 09:12:39 feanor kernel: e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
Oct 22 09:12:39 feanor kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not read
Oct 22 09:12:39 feanor kernel: wlan0: authenticate with f4:ca:e5:cc:c7:40

> What distro/version/arch is this?

Up to date archlinux, kernel 3.16.4-1-ARCH x86_64, systemd 216-3.

-- 
Damien Robert
http://www.normalesup.org/~robert/pro