Fedora 31, x64 Xfce 4.14
Shutdown hangs: https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
Many thanks, -T
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64 Xfce 4.14
Shutdown hangs: https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
Many thanks, -T
Also, when this happens, backups (dump, tar) take about eight times long to complete.
And to just be clear, if no slow down is apparent, shutdown and reboot work perfectly: they do not hang
On 2020-04-23 20:06, ToddAndMargo via users wrote:
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64 Xfce 4.14
Shutdown hangs: https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
Many thanks, -T
Also, when this happens, backups (dump, tar) take about eight times long to complete.
And to just be clear, if no slow down is apparent, shutdown and reboot work perfectly: they do not hang
So, you're saying that if you see a slowdown then you'll have the issue with reboot/shutdown. That would suggest to me that determining the cause of the slowdown is most important.
When the slowdown happens, can you switch to another VT (ctrl-alt-F2) or ssh in from elsewhere and see if there is any unusual CPU or I/O activity?
It sounds as if this issue happens for you frequently? And, are you still on the kernel shown in the BZ? There have been updates to the kernel since that time.
On 2020-04-23 05:25, Ed Greshko wrote:
On 2020-04-23 20:06, ToddAndMargo via users wrote:
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64 Xfce 4.14
Shutdown hangs: https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
Many thanks, -T
Also, when this happens, backups (dump, tar) take about eight times long to complete.
And to just be clear, if no slow down is apparent, shutdown and reboot work perfectly: they do not hang
So, you're saying that if you see a slowdown then you'll have the issue with reboot/shutdown.
Yes. And time does not heal. Only the magic one fingered reset (POR -- Power On Reset) works.
That would suggest to me that determining the cause of the slowdown is most important.
I would concur
When the slowdown happens, can you switch to another VT (ctrl-alt-F2) or ssh in from elsewhere and see if there is any unusual CPU or I/O activity?
You have to be quick. As soon as "shutdown reached", everything freezes except the revolving CPU registry prints outs
It sounds as if this issue happens for you frequently? And, are you still on the kernel shown in the BZ?
What is BZ?
There have been updates to the kernel since that time.
Every day. I keep hoping a kernel update will come through and fix it
On 2020-04-23 21:03, ToddAndMargo via users wrote:
On 2020-04-23 05:25, Ed Greshko wrote:
On 2020-04-23 20:06, ToddAndMargo via users wrote:
Also, when this happens, backups (dump, tar) take about eight times long to complete.
And to just be clear, if no slow down is apparent, shutdown and reboot work perfectly: they do not hang
So, you're saying that if you see a slowdown then you'll have the issue with reboot/shutdown.
Yes. And time does not heal. Only the magic one fingered reset (POR -- Power On Reset) works.
That would suggest to me that determining the cause of the slowdown is most important.
I would concur
When the slowdown happens, can you switch to another VT (ctrl-alt-F2) or ssh in from elsewhere and see if there is any unusual CPU or I/O activity?
You have to be quick. As soon as "shutdown reached", everything freezes except the revolving CPU registry prints outs
I'm not saying you need to check during shutdown.
I'm saying do not shutdown. Determine the cause of the slowdown. Roger gave a strategy for that.
It sounds as if this issue happens for you frequently? And, are you still on the kernel shown in the BZ?
What is BZ?
Bugzilla.
There have been updates to the kernel since that time.
Every day. I keep hoping a kernel update will come through and fix it
You're on 5.5.17-200 now?
Install sysstat and the next event you should have performance data, and/or leave top running in say a window and one of the virt terminals.
The task hung is caused by 100's of different issues, the usually one I see is high swap usage slowing everything down (it typically happens at least 10x more than the real bugs, and whoever is reporting it to me typically googles and includes a bug like that stating that they have one of the many "bugs" that have those messages in it). The fact that yours shutdowns indicates it is probably swap/memory usage. When you get most of the real task hung bugs shutdown won't ever finish and you will have to force it off as the messages is reporting it hung for XX seconds, but really it will never get out the the deadlock, or whatever needs to do will never complete.
On my laptop (32gb) I only get a tiny bit slow when firefox and/or chrome uses excessive memory, on my machine with 10gb it gets unusable, and often I find one of the browsers using almost all of my ram. It seems to correlate to certain web pages, and its timing seems to be rather random and often it seems to happen unattended. On the 32gb laptop when it gets slow enough that I notice I find what is using all of the ram and kill it and that clears up the issue. Excessive swap usage will cause shutdown to be really slow.
On Thu, Apr 23, 2020 at 7:26 AM Ed Greshko ed.greshko@greshko.com wrote:
On 2020-04-23 20:06, ToddAndMargo via users wrote:
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64 Xfce 4.14
Shutdown hangs: https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
Many thanks, -T
Also, when this happens, backups (dump, tar) take about eight times long to complete.
And to just be clear, if no slow down is apparent, shutdown and reboot work perfectly: they do not hang
So, you're saying that if you see a slowdown then you'll have the issue with reboot/shutdown. That would suggest to me that determining the cause of the slowdown is most important.
When the slowdown happens, can you switch to another VT (ctrl-alt-F2) or ssh in from elsewhere and see if there is any unusual CPU or I/O activity?
It sounds as if this issue happens for you frequently? And, are you still on the kernel shown in the BZ? There have been updates to the kernel since that time.
-- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Thu, 2020-04-23 at 08:03 -0500, Roger Heflin wrote:
On my laptop (32gb) I only get a tiny bit slow when firefox and/or chrome uses excessive memory, on my machine with 10gb it gets unusable, and often I find one of the browsers using almost all of my ram. It seems to correlate to certain web pages, and its timing seems to be rather random and often it seems to happen unattended. On the 32gb laptop when it gets slow enough that I notice I find what is using all of the ram and kill it and that clears up the issue. Excessive swap usage will cause shutdown to be really slow.
Yes, this used to happen to me with Chrome, which is why I switched to Firefox about 18 months ago. I hasn't happened since (and Chrome may have improved in the interim of course). It seemed to be related to high memory usage and/or spinning Javascript.
poc
On Thu, 23 Apr 2020 03:53:07 -0700 ToddAndMargo via users users@lists.fedoraproject.org wrote:
Randomly and not associated with any particular program, my system will slow down. It becomes obvious when I can type faster than letters appear. And when this happens, a reboot will fix it.
As Roger said, this is probably a resource issue. Something is hogging the CPU or memory, and limiting the time slice for your typing interrupts. The keystroke logger on your system is misbehaving. Or maybe it is the bitcoin miner causing the problem. We'll send out new ones as soon as possible. ;-)
But the shutdown and reboot process hangs when the slowdown appears. After the shutdown/reboot sequence gets to "Target Reached Power Off" (or restart), a delay of about two minutes and then I get my CPU registries displayed over and over.
This is because a running application didn't respond to a kill -15 signal. In that case, systemd waits for a default 90 seconds before sending a kill -9. This can be changed by changing DefaultTimeoutStopSec in /etc/systemd/system.conf However, it is good to have a noticeable timeout because it brings to your attention issues like this.
Looks like this: repeating CPU registries: https://bugzilla.redhat.com/attachment.cgi?id=1672106
This is my dmesg: # journalctl -b --no-hostname -k > dmesg.tx https://bugzilla.redhat.com/attachment.cgi?id=1672107
This looks like a denial of service attack. Something is not taking no for an answer. It keeps sending invalid packets to the kernel. No wonder your responsiveness gets so bad.
This has happened three times in one day. It has also gone for days without an issue.
And again, no particular program either. I initially thought it was qemu-kvm, then VLC, but it has happened with neither running. And just sitting at the desktop with the screen saver running.
Any words of wisdom?
You should start shutting down by doing shutdown -P now in a virtual console (e.g. Ctrl-Alt-F2). Then, systemd will tell you why it is pausing before sending the kill -9 whenever it happens. Unfortunately, you have little recourse once the freeze happens, thus you are just waiting to trap the issue, and will usually shutdown without it happening.
-
Ed Greshko -
Patrick O'Callaghan -
Roger Heflin -
stan -
ToddAndMargo