System freezes randomly after upgrading to ubuntu 17.04

Bug #1686329 reported by Luke picciau
84
This bug affects 17 people
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

Since upgrading to ubuntu 17.04 from 16.10 my system will randomly freeze after a few hours. Initially the display will stop updating then audio will stop playing. Nothing but a hard reset can fix it. I have attempted to switch TTY and use alt+sysreq+1 then alt+sysreq+t still nothing.

I can't work out how to reproduce this issue but it happens seemingly randomly fairly often sometimes while the computer is not in use and locked. I tried switching from unity to gnome to solve the issue but I have the same problem.

Here are the lines in syslog right before the crash

Apr 26 14:55:01 desktop CRON[14753]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 14:58:27 desktop kernel: [17152.145453] usb 3-1: USB disconnect, device number 6
Apr 26 14:58:27 desktop gvfsd[2309]: PTP: reading event an error 0x05 occurred
Apr 26 14:58:28 desktop gvfsd[2309]: Android device detected, assigning default bug flags
Apr 26 14:58:28 desktop gvfsd[2309]: Received event PTP_EC_DevicePropChanged in session 1
Apr 26 14:58:28 desktop gvfsd[2309]: message repeated 10 times: [ Received event PTP_EC_DevicePropChanged in session 1]
Apr 26 15:05:01 desktop CRON[14850]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:15:01 desktop CRON[14924]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:17:01 desktop CRON[14945]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 26 15:25:01 desktop CRON[14994]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:35:01 desktop CRON[15087]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:45:01 desktop CRON[15156]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 15:55:01 desktop CRON[15255]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:05:01 desktop CRON[15347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:15:01 desktop CRON[15440]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:17:01 desktop CRON[15457]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 26 16:25:01 desktop CRON[15532]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:35:01 desktop CRON[15612]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 26 16:45:01 desktop CRON[15689]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

I will also attach the output from lspci

Tags: bot-comment
Revision history for this message
Luke picciau (luke-b-picciau) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1686329/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Luke picciau (luke-b-picciau) wrote :

Had another freeze but while it was stuck I got a notification so the display isn't stuck. The mouse and keyboard don't work anymore but remain lit up. The power button also doesn't work even though it is set to suspend the system.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Renardo (renardo) wrote :

I have the same behaviour except that I usually can move the mouse within one screen (dual-screen system). No reactions on mouse clicks or keyboard input. Ctrl-Alt-F1 does not work. REISUB works and can power down the system! So the keyboard is not really dead.

Suspicious lines from syslog:
 * NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [thunderbird:2634]
 * CPU: 0 PID: 2634 Comm: thunderbird Tainted: G D L 4.10.0-20-generic #22-Ubuntu

I have no idea whether they are related.

uname -a says "4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux".

Revision history for this message
Mario (mario-gleirscher) wrote :

Hope the following description belongs to this bug, couldn't easily find something more similar:

After a fresh install of 17.04 (with standard packages) on my Dell Latitude E7240 some 10 days ago, my system seems to show similar phenomena, however, I could recognise that the final freeze is a consequence of a staged process happening beforehand:

1. E.g. (T)hunderbird or (F)irefox is getting what is (afaik) called a Zombie process, however, instead of "Z", T/F are marked with "D" (for disk) in top, running at 100% and not killable via top or kill -9/-15.

2. Machine load is slowly going upwards (within 4-5 min or so) until I can't switch windows or desktops anymore, neither can I switch to the text console to initiate an ordinary "shutdown (-R) now".

3. I have to perform a hard ACPI reset per button.

This happened already 4 times since I have installed 17.04.

According to what I found on the web,
https://unix.stackexchange.com/questions/5642/what-if-kill-9-does-not-work
it seems to be a peripheral/driver/filesystem/interrupt related problem. However, this exceeds my knowledge.

Hope to get some help, or hope to have contributed worthy information.

Revision history for this message
pmow (pmow) wrote :

This seems to be a duplicate of bug 1674838 (but since it doesn't contain the dmesg or kern.log info about the kernel panic, I'm not sure if this happens at swapops.h:129 as well).

Changed in ubuntu:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
Revision history for this message
Blaha (nelson-blaha) wrote :

I have this problem under Ubuntu 17.10, with the same line right before a total freeze and audio loop:

Mar 21 18:35:01 bigbaby-ubuntu CRON[8572]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.