http://bugzilla.suse.com/show_bug.cgi?id=927776
--- Comment #25 from Cristian Rodríguez
(In reply to Cristian Rodríguez from comment #23)
(In reply to Richard Weinberger from comment #22)
(In reply to Cristian Rodríguez from comment #21)
Ok Richard.. so you are running a self-built kernel right ? ensure http://cgit.freedesktop.org/systemd/systemd/tree/README section REQUIREMENTS is met by your build. In particular it looks like your kernel does not have CONFIG_FHANDLE set.
Yeah, the kernel is self-built (it's my day job)... But CONFIG_FHANDLE *is* set. In fact this config option is default because of me: https://git.kernel.org/linus/15bae280e412e79d74912c7ae6b6a002444edb1f
ok.. let's try something different then:
follow http://freedesktop.org/wiki/Software/systemd/Debugging/ section Early Debug Shell.
when pid 1 is looping too fast...
follow this instructions
http://git.infradead.org/~rw/os132_boot_fail.txt
also your boot log shows that the virtualbox kernel drivers are being loaded..which are known to be ..let say.. "buggy".. try disabling the vboxdrv service before continuing debugging..
oops, wrong instruction link.. here it is http://lists.freedesktop.org/archives/systemd-devel/2015-February/028541.htm...
It could be a coincidence that Apr 16 13:51:01 sandpuppy kernel: vboxdrv: Found 4 processor cores. Apr 16 13:51:01 sandpuppy kernel: vboxdrv: fAsync=0 offMin=0x2ac offMax=0x7a7e Apr 16 13:51:01 sandpuppy kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Apr 16 13:51:01 sandpuppy kernel: vboxdrv: Successfully loaded version 4.3.20 (interface 0x001a0008). Apr 16 13:51:01 sandpuppy kernel: vboxpci: IOMMU not found (not registered) --> Things go bersek right after the virtual box drivers are loaded..>>>> Apr 16 13:51:01 sandpuppy systemd[1]: Failed to get initial list of names: Connection timed out Apr 16 13:51:01 sandpuppy systemd[1]: Looping too fast. Throttling execution a little. Apr 16 13:51:01 sandpuppy systemd[1]: Looping too fast. Throttling execution a little. That could be misleading so let's rule that out first... -- You are receiving this mail because: You are on the CC list for the bug.