Summary: | Time-out problems during boot with systemd | ||
---|---|---|---|
Product: | dbus | Reporter: | Paul Menzel <paulepanter> |
Component: | core | Assignee: | D-Bus Maintainers <dbus> |
Status: | RESOLVED NOTOURBUG | QA Contact: | D-Bus Maintainers <dbus> |
Severity: | critical | ||
Priority: | medium | CC: | paulepanter |
Version: | 1.8 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Output of `sudo journalctl -l -b -3` |
Description
Paul Menzel
2014-12-17 21:40:43 UTC
Created attachment 111079 [details] Output of `sudo journalctl -l -b -3` As asked by smcv in #dbus@irc.freennode.net I am attaching the log. Last time when `binfmt-support.service` did not start and the boot hung, running `htop` in the debug shell, it should that `/sbin/init` used around 40 % of the CPU. Attaching with GDB there is the backtrace below. No idea if that can be explained by the fact that systemd is waiting for D-Bus or something else. Thread 1 (Thread 0xb72a77c0 (LWP 1)): #0 0xb75b6d3c in __kernel_vsyscall () No symbol table info available. #1 0xb749aebe in timerfd_settime () at ../sysdeps/unix/syscall-template.S:81 No locals. #2 0xb761b49d in event_arm_timer.lto_priv.605 (e=e@entry=0xb85c8e90, d=d@entry=0xb85c8ed0) at ../src/libsystemd/sd-event/sd-event.c:1781 its = {it_interval = {tv_sec = 0, tv_nsec = 0}, it_value = {tv_sec = 0, tv_nsec = 1}} a = <optimized out> b = <optimized out> t = 0 r = <optimized out> __PRETTY_FUNCTION__ = "event_arm_timer" #3 0xb760c78e in sd_event_run (e=<optimized out>, timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2225 ev_queue = <optimized out> ev_queue_max = <optimized out> p = <optimized out> r = <optimized out> i = <optimized out> m = <optimized out> timedout = <optimized out> __PRETTY_FUNCTION__ = "sd_event_run" #4 0xb7697f13 in manager_loop (m=0xb85c8bd0) at ../src/core/manager.c:1912 wait_usec = 18446744073709551615 rl = {interval = 1000000, begin = 1278764232, burst = 50000, num = 43622} __PRETTY_FUNCTION__ = "manager_loop" __func__ = "manager_loop" #5 0xb75eb062 in main (argc=1, argv=0xbf8b1c64) at ../src/core/main.c:1743 m = <optimized out> r = <optimized out> retval = 1 before_startup = <optimized out> after_startup = <optimized out> timespan = " \201*\267@[[\267\234\325U\267\070\324;\267\364\276U\267\001\000\000\000\000\000\000\000 T\\\267\330\032\213\277\000\220]\267\264\030\213\277 Z[\267p\030\213\277\352\"\\\267 \030\213\277\364\276U\267" fds = 0x0 reexecute = false shutdown_verb = 0x0 initrd_timestamp = <optimized out> userspace_timestamp = {realtime = 1419759906775553, monotonic = 44872499} kernel_timestamp = {realtime = <optimized out>, monotonic = 0} security_start_timestamp = {realtime = 1419759906824087, monotonic = 44921034} security_finish_timestamp = {realtime = 1419759906857197, monotonic = 44954144} systemd = "systemd" skip_setup = <optimized out> j = <optimized out> loaded_policy = false arm_reboot_watchdog = false queue_default_job = <optimized out> empty_etc = <optimized out> switch_root_dir = 0x0 switch_root_init = 0x0 saved_rlimit_nofile = {rlim_cur = 1024, rlim_max = 4096} __func__ = "main" __PRETTY_FUNCTION__ = "main" (In reply to Paul Menzel from comment #2) > Last time when `binfmt-support.service` did not start and the boot hung, > running `htop` in the debug shell, it should that `/sbin/init` used around > 40 % of the CPU. Sorry, I think you'll need to talk to the systemd maintainers about this. (In reply to Simon McVittie from comment #3) > (In reply to Paul Menzel from comment #2) > > Last time when `binfmt-support.service` did not start and the boot hung, > > running `htop` in the debug shell, it should that `/sbin/init` used around > > 40 % of the CPU. > > Sorry, I think you'll need to talk to the systemd maintainers about this. No problem. What do you mean by “this” though? The whole issue or the `binfmt-support.service` issue? (In reply to Paul Menzel from comment #4) > No problem. What do you mean by “this” though? The whole issue or the > `binfmt-support.service` issue? The whole issue: > `/sbin/init` used around 40 % of the CPU This seems like something that shouldn't happen. > Dez 17 21:41:25 my-asrock-e350m1 systemd[1]: Looping too fast. Throttling execution a little. So does this. Sorry, I don't think dbus maintainers can help you with this. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789796 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.