Random freeze of UI and input for ~30s

[Andrew Hayzen]

Description: Ubuntu 14.10
Release: 14.10
Linux andy-Pangolin-Performance 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

This has happened a few times, the UI freezes and no input works for ~30s and then something resets/releases, all the inputs are then run and everything appears to be normal again.

Note I did have Firefox nightly and icedtea-7-plugin installed (not sure if related to the freezes but these are the only things I have installed recently since the freezes have been occurring)

The output of dmesg [0] also suggests a similar/or the same issue as [1]

0 - http://pastebin.ubuntu.com/9358472/
1 - https://bugzilla.kernel.org/show_bug.cgi?id=64431

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andy 2398 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Dec 3 22:53:31 2014
HibernationDevice: RESUME=UUID=c5bf783f-d936-4a4c-9469-9c4a9685ca92
InstallationDate: Installed on 2014-11-03 (30 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System76, Inc. Pangolin Performance
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=589d892c-e903-4e66-8aa4-a457b38cc391 ro acpi_os_name=Linux acpi_osi= quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.138
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Pangolin Performance
dmi.board.vendor: System76, Inc.
dmi.board.version: panp9
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: Pangolin Performance
dmi.product.version: panp9
dmi.sys.vendor: System76, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[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 v3.18 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.18-rc7-vivid/

[Andrew Hayzen (ahayzen)]

Thanks for the instructions, I have managed to install the later kernel version and will report back if I have any freezes on this as well.

Linux andy-Pangolin-Performance 3.18.0-031800rc7-generic #201411302035 SMP Mon Dec 1 01:36:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[Andrew Hayzen (ahayzen)]

I have been using the kernel stated in the previous comment for 9 days now and have not had the same freeze and resume (note this doesn't mean it has totally gone as it was random before but I am quite confident it has), therefore I am tagging this bug with 'kernel-fixed-upstream'.

However while testing the new kernel I noted that when playing Metro: Last Light the machine locks and never recovers after ~20-30 seconds of playback, I assume this is a separate bug as nothing appears in the logs and it is non recoverable? Should I report a separate bug and how would I go about debugging this issue?

[Christopher M. Penalver (penalvch)]

Andrew Hayzen, the next step is to fully reverse commit bisect from kernel 3.16 to 3.18-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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