Any update on a fix to this problem? My work around is to kill the initctl if/when I restart; I haven't noticed any adverse effect on anything I do on a daily basis and it is running more than 2+ weeks with no sign of initctl going crazy. Since I very rarely reboot (only after any updates and such), it is not a big deal for me now but would be nice to get a fix to this problem.
Not sure the following info helps but I am sure it will give some clue. I attached gdb and dumped the stack trace after a fresh reboot (i.e. when initctl is fine) as well as the same when it goes crazy to compare. Here are the two traces. stack trace normal (siting in poll() normally) ================== (gdb) where #0 0x00007f00ff2ba0a0 in __poll_nocancel () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f00ff5ae78f in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x00007f00ff5ad3fe in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x00007f00ff596164 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x00007f00ff596c5c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x0000559a959932c9 in ?? () #6 0x00007f00ff9e9ef0 in ?? () from /lib/x86_64-linux-gnu/libnih.so.1 #7 0x00007f00ff9ea513 in nih_command_parser () from /lib/x86_64-linux-gnu/libnih.so.1 #8 0x0000559a95990699 in ?? () #9 0x00007f00ff1de3f1 in __libc_start_main (main=0x559a95990620, argc=3, argv=0x7fff0ace82d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff0ace82c8) at ../csu/libc-start.c:291 #10 0x0000559a959906ea in ?? () stack trace w/ problem (appear to read something from FD 3 (a unix socket to upstart?) ====================== (gdb) where #0 0x00007f7750af142d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #1 0x00007f7750af5f41 in dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x00007f7750aeb146 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x00007f7750aebc5c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x0000557f7db2d2c9 in ?? () #5 0x00007f7750f3eef0 in ?? () from /lib/x86_64-linux-gnu/libnih.so.1 #6 0x00007f7750f3f513 in nih_command_parser () from /lib/x86_64-linux-gnu/libnih.so.1 #7 0x0000557f7db2a699 in ?? () #8 0x00007f77507333f1 in __libc_start_main (main=0x557f7db2a620, argc=3, argv=0x7fff51adf6d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff51adf6c8) at ../csu/libc-start.c:291 #9 0x0000557f7db2a6ea in ?? () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU Status in upstart : Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Many programs are fairly slow to start on my computer, despite it being relatively new (core i5). Suspecting a heavy CPU usage, I started gnome-system-monitor: all processes were displayed at 0% CPU, but the overall load was 1.33; 1.33; 1.34. Using the "top" command, however, revealed the real CPU use, with the "initctl" process taking 100%CPU, even 1 hour after startup. I upgraded to roaring ringtail before checking this but the symptoms were the same with quantal quetzal, so there is a fair chance the causes were identical. Regards ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Sun Apr 28 13:04:05 2013 ExecutablePath: /sbin/initctl InstallationDate: Installed on 2012-12-15 (133 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UpstartBugCategory: System To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp