Intermittent complete system freeze

[Andrej Prša]

This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the machine. I am attaching the trace written up in /var/log/syslog.
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: andrej 1789 F.... pulseaudio
 /dev/snd/controlC0: andrej 1789 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
InstallationDate: Installed on 2016-04-26 (358 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 8570w
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash crashkernel=384M-:128M vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/31/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IAV Ver. F.40
dmi.board.name: 176B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 50.1A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8570w
dmi.product.version: A1029D1103
dmi.sys.vendor: Hewlett-Packard

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1683865/+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.]

[Andrej Prša (andrej-prsa)]

I have several kdump crash logs that I can share. They are $100MB each so I don't know what the best way might be, and the traces are similar to the trace I already uploaded.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1683865

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Andrej Prša (andrej-prsa)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7

[Andrej Prša (andrej-prsa)]

After two days of testing, I am happy to report that the upstream rc7 version indeed fixes the freezing issue. It still hangs up on suspend/resume, but that's likely unrelated. As I am now using the upstream kernel I'm not sure whether I should report that as ubuntu bug. Any advice would be appreciated. In the mean time I will tag this bug report appropriately.

[Andrej Prša (andrej-prsa)]

Of course, seconds after I posted my previous message, the OS froze again, so the upstream does *not* fix the issue. I can't readily find how I can tag the bug as kernel-bug-exists-upstream, but I'll keep looking. The frequency of freezes seems to have reduced substantially, but since they are intermittent, it might have been a fluke that it hadn't frozen for two days.

[Andrej Prša (andrej-prsa)]

After further testing I can report that the parent issue has indeed been resolved upstream. The subsequent lockups are related to the nvidia module, not the reported issue. Thus, upgrading the kernel will solve the issue.