Ubuntu freezes when playing multimedia, VLC, totem

[Javier Antonio Nisa Avila]

When playing multimedia, mkv, avi, mp4 files, edit PowerPoint transitions or any similarly required to reproduce an image. Randomly, it freezes everything and must be reset with a hard reset. mouse, screen and everything is frozen and can not do anything.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-27-generic 4.2.0-27.32
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nebrit 1545 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Feb 4 18:15:19 2016
HibernationDevice: RESUME=UUID=d9094006-443f-43e3-9c8d-09537e4c2289
InstallationDate: Installed on 2016-01-14 (20 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20D9S00D00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed root=UUID=3e293fa3-ec43-4f0a-a925-562901db8088 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-27-generic N/A
 linux-backports-modules-4.2.0-27-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N15ET54W (1.14)
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0G00622 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrN15ET54W(1.14):bd01/05/2015:svnLENOVO:pn20D9S00D00:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0G00622WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20D9S00D00
dmi.product.version: ThinkPad 11e
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Javier Antonio Nisa Avila (javiernisa)]

I have just ubuntuI do not have windows installed. I do not know how to upgrade. Please help me. Tell me how to update the BIOS

[Javier Antonio Nisa Avila (javiernisa)]

same problem, same conditions, all same. I attach dates of step 1

nebrit@Nebrit-Thinkpad11e:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for nebrit:
N15ET66W (1.26)
12/17/2015
nebrit@Nebrit-Thinkpad11e:~$

[penalvch (penalvch)]

Javier Antonio Nisa Avila, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Javier Antonio Nisa Avila (javiernisa)]

I still have the same problem, nothing changes. I added the labels indicating that it has not been solved. I hope to settle it soon. You can not watch videos or anything similar, for fear of freezing.

[penalvch (penalvch)]

Javier Antonio Nisa Avila, could you please capture the kernel call trace or xorg back trace following https://help.ubuntu.com/community/DebuggingSystemCrash ?

[Javier Antonio Nisa Avila (javiernisa)]

Attach.

[penalvch (penalvch)]

Javier Antonio Nisa Avila:
https://launchpadlibrarian.net/236884982/kern.log
Feb 7 16:22:21 Nebrit-Thinkpad11e kernel: [ 634.289811] perf interrupt took too long (2620 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Feb 7 16:34:05 Nebrit-Thinkpad11e kernel: [ 1338.144714] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Feb 7 16:44:34 Nebrit-Thinkpad11e kernel: [ 1967.907654] do_general_protection: 39 callbacks suppressed
Feb 7 16:44:34 Nebrit-Thinkpad11e kernel: [ 1967.907662] traps: vlc[3369] general protection ip:7f0f45685c7d sp:7f0eec1a7770 error:0 in libc-2.21.so[7f0f4564c000+1c0000]

To clarify, after you reboot from this, is there a crash file in /var/crash?

[Javier Antonio Nisa Avila (javiernisa)]

Attach files of var/crash (4 files)

[penalvch (penalvch)]

Javier Antonio Nisa Avila, thank you for reporting this and helping make Ubuntu better. However, your crash reports are manually attached.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

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

[Javier Antonio Nisa Avila (javiernisa)]

I running stable release. So, the steps are:

Step 1: cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

Step 2: sudo ubuntu-bug /var/crash/_my_crash_report.crash

The two steps or one step 2.
That is what makes the step 1?

[Javier Antonio Nisa Avila (javiernisa)]

Reports!!! Thanks.