I also had a similar, but maybe not identical issue today. First, several application windows grayed out, one after another. Then my system slowed down and after a few seconds became completely unresponsive. Of course, I couldn't switch to VT1 too. I waited for more than 10 minutes, but nothing changed, so I restarted the laptop.
What is unusual about the situation is that during the freeze there was no HDD activity (the blinkenlight didn't blink even once and I didn't hear my HDD) and the CPU apparently did almost nothing too (my laptop's fan was completely silent). Unfortunately, there was nothing interesting in syslog when I checked it after the restart, and checking out dmesg after a restart wouldn't help much too. I never experienced anything like this when I was on xenial. On xenial, usually, when I was running out of memory and swap, my system would become very, but not completely unresponsive, the fan would spin like crazy, the blinkenlight responsible for HDD activity would blink like crazy, and of course I would be able to hear the HDD too. I would usually switch to VT1, patiently wait until the switch actually happened, then type a command to kill the offending process. The 2 incidents that happened to me today (after I had upgraded to zesty) were nothing like this. -- 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/1683091 Title: The whole system froze for something like 30 seconds, then a process got killed Status in linux package in Ubuntu: Incomplete Bug description: Upgraded from xenial to zesty recently. I was using a Firefox instance, one which is a part of Tor Browser Bundled. First, the application window grayed out, then the whole system froze for something like 30 seconds (I tried to switch to VT1 to no avail), then the process got killed. Well, not exactly killed. The grayed-out window is still there, `xprop | grep PID` and clicking on it gives: ``` _NET_WM_PID(CARDINAL) = 13 ``` PID 13 is a child of kthreadd: ``` $ ps -A | awk '$1 == "13" { print }' 13 ? 00:00:00 cpuhp/1 ``` And this is how the relevant part of `ps -AH` with the "killed" process looks like: ``` 5709 pts/11 00:00:00 firejail 5710 pts/11 00:00:00 firejail 5725 pts/11 00:00:00 bash 5736 pts/11 00:56:49 firefox <defunct> 5769 pts/11 00:00:24 tor ``` EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding the output above as ps.log. I checked syslog and dmesg. Both of them have an interesting and identical message, which I add as dmesg.log. I also add the output of `cat /proc/version_signature` as version.log. I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna share it unless absolutely necessary. The crashed process will be there for something like 2 or 3 days at least (I don't restart my laptop often), so feel free to ask me to manipulate or query it somehow, if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
