systemd-journald high CPU usage
A few days ago, I installed Ubuntu 17.04 on my Asus laptop dual-boot with Windows 10 and shortly thereafter, I noticed that the systemd-journald process was constantly using 25-35% of CPU.
I traced the process and saved part of the output is at here.
It seems that the CPU is looping, doing something that is related to a pci device.
Does anyone have any advice on the problem?
cpu systemd-journald
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
add a comment |
A few days ago, I installed Ubuntu 17.04 on my Asus laptop dual-boot with Windows 10 and shortly thereafter, I noticed that the systemd-journald process was constantly using 25-35% of CPU.
I traced the process and saved part of the output is at here.
It seems that the CPU is looping, doing something that is related to a pci device.
Does anyone have any advice on the problem?
cpu systemd-journald
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
add a comment |
A few days ago, I installed Ubuntu 17.04 on my Asus laptop dual-boot with Windows 10 and shortly thereafter, I noticed that the systemd-journald process was constantly using 25-35% of CPU.
I traced the process and saved part of the output is at here.
It seems that the CPU is looping, doing something that is related to a pci device.
Does anyone have any advice on the problem?
cpu systemd-journald
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
A few days ago, I installed Ubuntu 17.04 on my Asus laptop dual-boot with Windows 10 and shortly thereafter, I noticed that the systemd-journald process was constantly using 25-35% of CPU.
I traced the process and saved part of the output is at here.
It seems that the CPU is looping, doing something that is related to a pci device.
Does anyone have any advice on the problem?
cpu systemd-journald
cpu systemd-journald
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
edited Apr 26 '17 at 9:05
d a i s y
3,33282344
3,33282344
asked Apr 18 '17 at 14:21
S_nS_n
2614
asked Apr 18 '17 at 14:21
S_nS_n
2614
asked Apr 18 '17 at 14:21
S_nS_n
2614
2614
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
@S_n Can you please check the logs, and see whether it gives indication about the problem?
I've had the same problem and that caused to an infinite loop, and the cpu was constantly higher then 30%.
So if you run in the terminal journalctl you can check it the log in the terminal.
I fixed it by adding a pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property(you can find and edit it in: sudo vim /etc/default/grub)
After adding the parameter update the grub: sudo update-grub and then reboot.
Then run top in the terminal, and see whether that fixed it.
Note: By doing that you'll add the parameter permanently, however you can do it temporarily
If you want to add it temporarily, as following:
- Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left
Shiftkey after starting the system). - Now highlight the kernel you want to use, and press the
ekey. You should be able to see and edit the commands associated with the highlighted kernel. - Go down to the line starting with
linuxand add your parameterpci=nomsito its end. - Now press
Ctrl + xto boot.
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
3
What problem did you have withlinux_default_parameterand how did you fix it? You can't just say you have a problem and not say what the fix is.
– edwinksl
Aug 16 '17 at 20:31
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding apci=nomsiparameter to theGRUB_CMDLINE_LINUX_DEFAULTproperty, and then update the grub:sudo update-gruband the reboot. I hope that it's more clear now!
– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
|
show 1 more comment
This workaround solved the problem in my computer (Ubuntu 17.10 x64): https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/comments/11
$ sudo apt-add-repository ppa:ubuntu-desktop/gnome-software
$ sudo apt update
$ sudo apt upgrade
The problem is caused by snapd-glib, that logs hundreds / thousands of lines per minute in the /var/log/syslog like these:
Jan 29 11:12:28 hostXXX gnome-software[1723]: Ignoring unexpected response
Jan 29 11:12:28 hostXXX gnome-software[1723]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed
My /var/log/syslog got 9.5 Gb of size before update the module and purge the content.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f906251%2fsystemd-journald-high-cpu-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
@S_n Can you please check the logs, and see whether it gives indication about the problem?
I've had the same problem and that caused to an infinite loop, and the cpu was constantly higher then 30%.
So if you run in the terminal journalctl you can check it the log in the terminal.
I fixed it by adding a pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property(you can find and edit it in: sudo vim /etc/default/grub)
After adding the parameter update the grub: sudo update-grub and then reboot.
Then run top in the terminal, and see whether that fixed it.
Note: By doing that you'll add the parameter permanently, however you can do it temporarily
If you want to add it temporarily, as following:
- Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left
Shiftkey after starting the system). - Now highlight the kernel you want to use, and press the
ekey. You should be able to see and edit the commands associated with the highlighted kernel. - Go down to the line starting with
linuxand add your parameterpci=nomsito its end. - Now press
Ctrl + xto boot.
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
3
What problem did you have withlinux_default_parameterand how did you fix it? You can't just say you have a problem and not say what the fix is.
– edwinksl
Aug 16 '17 at 20:31
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding apci=nomsiparameter to theGRUB_CMDLINE_LINUX_DEFAULTproperty, and then update the grub:sudo update-gruband the reboot. I hope that it's more clear now!
– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
|
show 1 more comment
@S_n Can you please check the logs, and see whether it gives indication about the problem?
I've had the same problem and that caused to an infinite loop, and the cpu was constantly higher then 30%.
So if you run in the terminal journalctl you can check it the log in the terminal.
I fixed it by adding a pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property(you can find and edit it in: sudo vim /etc/default/grub)
After adding the parameter update the grub: sudo update-grub and then reboot.
Then run top in the terminal, and see whether that fixed it.
Note: By doing that you'll add the parameter permanently, however you can do it temporarily
If you want to add it temporarily, as following:
- Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left
Shiftkey after starting the system). - Now highlight the kernel you want to use, and press the
ekey. You should be able to see and edit the commands associated with the highlighted kernel. - Go down to the line starting with
linuxand add your parameterpci=nomsito its end. - Now press
Ctrl + xto boot.
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
3
What problem did you have withlinux_default_parameterand how did you fix it? You can't just say you have a problem and not say what the fix is.
– edwinksl
Aug 16 '17 at 20:31
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding apci=nomsiparameter to theGRUB_CMDLINE_LINUX_DEFAULTproperty, and then update the grub:sudo update-gruband the reboot. I hope that it's more clear now!
– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
|
show 1 more comment
@S_n Can you please check the logs, and see whether it gives indication about the problem?
I've had the same problem and that caused to an infinite loop, and the cpu was constantly higher then 30%.
So if you run in the terminal journalctl you can check it the log in the terminal.
I fixed it by adding a pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property(you can find and edit it in: sudo vim /etc/default/grub)
After adding the parameter update the grub: sudo update-grub and then reboot.
Then run top in the terminal, and see whether that fixed it.
Note: By doing that you'll add the parameter permanently, however you can do it temporarily
If you want to add it temporarily, as following:
- Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left
Shiftkey after starting the system). - Now highlight the kernel you want to use, and press the
ekey. You should be able to see and edit the commands associated with the highlighted kernel. - Go down to the line starting with
linuxand add your parameterpci=nomsito its end. - Now press
Ctrl + xto boot.
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
@S_n Can you please check the logs, and see whether it gives indication about the problem?
I've had the same problem and that caused to an infinite loop, and the cpu was constantly higher then 30%.
So if you run in the terminal journalctl you can check it the log in the terminal.
I fixed it by adding a pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property(you can find and edit it in: sudo vim /etc/default/grub)
After adding the parameter update the grub: sudo update-grub and then reboot.
Then run top in the terminal, and see whether that fixed it.
Note: By doing that you'll add the parameter permanently, however you can do it temporarily
If you want to add it temporarily, as following:
- Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left
Shiftkey after starting the system). - Now highlight the kernel you want to use, and press the
ekey. You should be able to see and edit the commands associated with the highlighted kernel. - Go down to the line starting with
linuxand add your parameterpci=nomsito its end. - Now press
Ctrl + xto boot.
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
edited Aug 17 '17 at 15:56
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
answered Aug 16 '17 at 20:23
Hasan ShHasan Sh
1113
1113
3
What problem did you have withlinux_default_parameterand how did you fix it? You can't just say you have a problem and not say what the fix is.
– edwinksl
Aug 16 '17 at 20:31
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding apci=nomsiparameter to theGRUB_CMDLINE_LINUX_DEFAULTproperty, and then update the grub:sudo update-gruband the reboot. I hope that it's more clear now!
– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
|
show 1 more comment
3
What problem did you have withlinux_default_parameterand how did you fix it? You can't just say you have a problem and not say what the fix is.
– edwinksl
Aug 16 '17 at 20:31
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding apci=nomsiparameter to theGRUB_CMDLINE_LINUX_DEFAULTproperty, and then update the grub:sudo update-gruband the reboot. I hope that it's more clear now!
– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
3
3
What problem did you have with
linux_default_parameter and how did you fix it? You can't just say you have a problem and not say what the fix is.– edwinksl
Aug 16 '17 at 20:31
What problem did you have with
linux_default_parameter and how did you fix it? You can't just say you have a problem and not say what the fix is.– edwinksl
Aug 16 '17 at 20:31
1
1
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
As it stands, this doesn't really seem to answer the question.
– sempaiscuba
Aug 16 '17 at 21:22
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding a
pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property, and then update the grub: sudo update-grub and the reboot. I hope that it's more clear now!– Hasan Sh
Aug 17 '17 at 8:19
My bad, sorry for not doing that. The problem was that a parameter in the grub configuration file was missing, and that caused to an infinite loop, and the cpu was constantly higher then 30%. Therefore I asked can you check what does it say in the terminal, so if you run in the terminal ` journalctl` you'll get a log, and the problem that I faced was described there, and fixed it by adding a
pci=nomsi parameter to the GRUB_CMDLINE_LINUX_DEFAULT property, and then update the grub: sudo update-grub and the reboot. I hope that it's more clear now!– Hasan Sh
Aug 17 '17 at 8:19
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@HasanSh You should add that to your answer since some people may not read comments.
– edwinksl
Aug 17 '17 at 13:31
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
@edwinksl Sure:)
– Hasan Sh
Aug 17 '17 at 15:57
|
show 1 more comment
This workaround solved the problem in my computer (Ubuntu 17.10 x64): https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/comments/11
$ sudo apt-add-repository ppa:ubuntu-desktop/gnome-software
$ sudo apt update
$ sudo apt upgrade
The problem is caused by snapd-glib, that logs hundreds / thousands of lines per minute in the /var/log/syslog like these:
Jan 29 11:12:28 hostXXX gnome-software[1723]: Ignoring unexpected response
Jan 29 11:12:28 hostXXX gnome-software[1723]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed
My /var/log/syslog got 9.5 Gb of size before update the module and purge the content.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This workaround solved the problem in my computer (Ubuntu 17.10 x64): https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/comments/11
$ sudo apt-add-repository ppa:ubuntu-desktop/gnome-software
$ sudo apt update
$ sudo apt upgrade
The problem is caused by snapd-glib, that logs hundreds / thousands of lines per minute in the /var/log/syslog like these:
Jan 29 11:12:28 hostXXX gnome-software[1723]: Ignoring unexpected response
Jan 29 11:12:28 hostXXX gnome-software[1723]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed
My /var/log/syslog got 9.5 Gb of size before update the module and purge the content.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This workaround solved the problem in my computer (Ubuntu 17.10 x64): https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/comments/11
$ sudo apt-add-repository ppa:ubuntu-desktop/gnome-software
$ sudo apt update
$ sudo apt upgrade
The problem is caused by snapd-glib, that logs hundreds / thousands of lines per minute in the /var/log/syslog like these:
Jan 29 11:12:28 hostXXX gnome-software[1723]: Ignoring unexpected response
Jan 29 11:12:28 hostXXX gnome-software[1723]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed
My /var/log/syslog got 9.5 Gb of size before update the module and purge the content.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This workaround solved the problem in my computer (Ubuntu 17.10 x64): https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/comments/11
$ sudo apt-add-repository ppa:ubuntu-desktop/gnome-software
$ sudo apt update
$ sudo apt upgrade
The problem is caused by snapd-glib, that logs hundreds / thousands of lines per minute in the /var/log/syslog like these:
Jan 29 11:12:28 hostXXX gnome-software[1723]: Ignoring unexpected response
Jan 29 11:12:28 hostXXX gnome-software[1723]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed
My /var/log/syslog got 9.5 Gb of size before update the module and purge the content.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago
answered 2 days ago
Mariano RuizMariano Ruiz
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
Mariano RuizMariano Ruiz
1013
answered 2 days ago
Mariano RuizMariano Ruiz
1013
1013
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Mariano Ruiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f906251%2fsystemd-journald-high-cpu-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
