I now did kill -ABRT as described in #2 and the result is
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1664838.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Sorry, cannot come from google chrome because I installed < 48 h ago and
the process already has 344 CPU hours.
Same strace as #14 here, and stack is sometimes
# cat /proc/1898/stack
[] 0x
sometimes
# cat /proc/1898/stack
[] retint_careful+0x14/0x32
[] 0x
Same here on Ubuntu 14.04 after installing google chrome via download
from google website and software manager (not manually adding ppa).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Ditto - Ubuntu 16.04.05
--
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/1255610
Title:
100% CPU usage with "initctl emit plymouth-ready" process
Status in upstart package
Ditto - Ubuntu 14.04.05
--
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/1255610
Title:
100% CPU usage with "initctl emit plymouth-ready" process
Status in upstart package
Same problem in Ubuntu 16.10...
--
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/1255610
Title:
100% CPU usage with "initctl emit plymouth-ready" process
Status in upstart
I experience the same issue, on Ubuntu 14.04.4
I just wanted to add that I only noticed this after I had installed
quite a few 32 bit packages on my 64 bit OS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in
Hi,
I am consistently watching this issue from my side with Ubuntu 14.04.1
LTS after 24 hours running, CPU is fully occupied by initctl emit
plymouth-ready process.
This bug seems not responsive from Canonical side, anyone can tell me
how could we WA or fix this issue.
--
You received this bug
Possibly dupe with #1173915?
I too am seeing 100% cpu on initctl, after a nearly three month uptime
on 14.04:
Linux dorset.bryceharrington.org 3.13.0-35-generic #62-Ubuntu SMP Fri
Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/1327/stack
[]
Happened again, same system. Stack is even shorter this time:
$ cat /tmp/initctl.stack
[] 0x
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
$ cat /tmp/initctl.stack
[817298bc] retint_careful+0x14/0x32
[] 0x
--
You received this bug notification
Affects also my system: laptop Acer Aspire E17 E5-771G-7868 (with a
replaced HD, by an SSD disk, in case it matters). It happens quite often
(several times a week?):
» uname -a
Linux polyphemus.wavilon.net 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13
19:36:28 UTC 2015 x86_64 x86_64 x86_64
Hi guys,
I ran into this bug on an Ubuntu 14.04.1 system (see attached
screenshot).
I ran kill -ABRT and submitted the crash report but I don't know what
happened to it? I have the files in /var/crash if you need them.
** Attachment added: Screenshot from 2014-09-04 11_30_44.png
Attaching my /var/crash files just in case...
** Attachment added: initctl_crash.tar.gz
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1255610/+attachment/4195742/+files/initctl_crash.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
14 matches
Mail list logo
