*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a mem
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
Will be fixed in next upload, in 246.6-1ubuntu1
https://github.com/systemd/systemd/issues/16669
** Bug watch added: github.com/systemd/systemd/issues #16669
https://github.com/systemd/systemd/issues/1666
Same here BUT ... I have delete the /var/crash/* and init splash stop to
consume 100% cpu.
This is the clue :
```
sept. 18 15:15:26 rige systemd[1]: apport-autoreport.service: Succeeded.
sept. 18 15:15:26 rige systemd[1]: Finished Process error reports when
automatic reporting is enabled.
sept.
I am experiencing this same problem and I can confirm that when I mask the
apport-autoreport.service the problem stops.
I am on Ubuntu 20.10 with Kernel 5.8.0-18-generic. I also have Ubuntu 20.04
with Kernel 5.8.0-05-generic and
can confirm the problem does not happen there
John
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890913
** No longer affects: apport (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890913
Title:
init is using 100% of processor
Status in linux package in Ubuntu:
Confirmed
Status
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890913
Title:
init is using 100% of processor
Status in apport packa
These messages show up repeatedly in the journal:
Aug 19 21:33:11 ubuntu-x1 systemd[1]: Failed to start Process error reports
when automatic reporting is enabled.
Aug 19 21:33:11 ubuntu-x1 systemd[1]: apport-autoreport.service: Start request
repeated too quickly.
Aug 19 21:33:11 ubuntu-x1 system
I hadn't seen this bug before today when I noticed that it's blocking my
kernel in groovy-proposed. I upgraded systemd, and I am seeing this
issue. But when I boot back to 5.4.0-37 the problem persists, so it
doesn't seem to have anything to do with the 5.8 kernel.
It seems like a problem with app
I should note, I did not update systemd in isolation. I can provide a
complete list of packages installed/upgrade at the same time if that is
helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Systemd since then migrated and probably we don't want to have the
kernel migrated as well to trigger the issue, thus I've added the block-
proposed tag.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
1. It was not set by me manually
2. After removing the corresponding line from `/etc/default/grub` and updating
grub and initramfs, the problem is still there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
1. It was not set by me manually
2. After removing the corresponding line from `/etc/default/grub` and updating
grub and initramfs, the problem is still there.
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Pa
Fastboot is known to cause issues on older CPUs:
https://wiki.archlinux.org/index.php/intel_graphics#Fastboot
If the i915.fastboot=1 option was _not_ set by you manually then please
reopen the bug by settint status to New.
** Changed in: systemd (Ubuntu)
Importance: High => Undecided
** Chang
15 matches
Mail list logo
