Xorg freeze

Bug #1531845 reported by Xtien
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have multiple freezes per day. I can trigger this by starting Android Studio. Sometimes it happens in Gedit loading a large file, or in a shell window.

What I see is that in System Monitor, CPU2 or CPU3 (there's 12, only 2 or 3 go to 100% during freeze) goes to 100% and stays there for 5 or more minutes. All other CPUs are at less than 5%. In the "processes" tab no processes use significant CPU. But when I go to a shell (ctrl-alt-F2) and type "top", I see Xorg taking ~50% CPU and 2.4% memory.
 I tried different versions of AS, different versions of Gradle, tried Oracle Java instead of openjdk, no change. Most of the time, Firefox also freezes after a short while, then everything freezes. The freeze does stop, after a maximum of 15 minutes. Sometimes, I need to do a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.63 Sat Nov 7 21:25:42 PST 2015
 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
BootLog:

CurrentDesktop: Unity
Date: Thu Jan 7 13:12:34 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3205]
InstallationDate: Installed on 2015-12-13 (24 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: MSI MS-7881
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X99S XPOWER AC (MS-7881)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd03/20/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7881
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Jan 7 13:11:54 2016
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Logitech USB Optical Mouse MOUSE, id 8
 input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.2-1ubuntu9.1

Revision history for this message
Xtien (xtien) wrote :
Revision history for this message
Xtien (xtien) wrote :
Revision history for this message
Xtien (xtien) wrote :
Revision history for this message
Xtien (xtien) wrote :

Dmesg and xorg.log were taken during a freeze.

Revision history for this message
Xtien (xtien) wrote :
penalvch (penalvch)
tags: added: bios-outdated-1.80
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Xtien (xtien) wrote : Re: [Bug 1531845] Re: Xorg freeze

On 10-01-16 02:54, Christopher M. Penalver wrote:
> Xtien, thank you for reporting this and helping make Ubuntu better.
>
> As per http://us.msi.com/product/motherboard/support/X99S-XPOWER-AC.html
> #down-bios an update to your computer's buggy and outdated BIOS is
> available (1.8). If you update to this following
> https://help.ubuntu.com/community/BIOSUpdate does it change anything?

Christopher,

you're a darling!

I updated the bios to 1.8, and I managed to build my project in Android
Studio a number of times without any freezes. That's more than I've been
able to do in the last four or so months. As I have thought the problem
had gone before, can we keep the bug open for another few days? I'll let
you know, soon as I went through 48 hours without a "100% cpu freeze",
you can close the bug.
I'm really happy.

Where can I send the flowers? (in Amsterdam, that's what you send people
when you're grateful).

dagdag
Christine

>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> Once the BIOS is updated, if the problem is still reproducible:
> 1) Please provide the output of the following terminal command (not perform an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> 2) Please make a comment specifically advising on if there was an improvement or not.
> 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-1.80
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

--
dagdag is just a two character rotation of byebye

Revision history for this message
Xtien (xtien) wrote :

After the bios upgrade to 1.8, I have had not a single crash. I rebooted my computer, did everything I could to reproduce the crash, but it didn't happen. I can actually get some work done now. I'm a happy person.
I think it's ok to close the bug.

penalvch (penalvch)
Changed in xorg (Ubuntu):
importance: Low → Undecided
status: Incomplete → Invalid
Revision history for this message
penalvch (penalvch) wrote :

Xtien, to advise, you don't have to file new reports about this issue. Instead, this report can be re-opened.

To clarify, does this issue happen if you use nouveau instead of the nvidia proprietary drivers?

Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: Invalid → Incomplete
tags: added: latest-bios-1.80
removed: bios-outdated-1.80
description: updated
Revision history for this message
Xtien (xtien) wrote :

Oh, I'm sorry. A while ago I re-opened a bug, then I was told I should file a separate bug instead. Never mind.

I haven't tried this particular bug with nouveau. The reason I use Nvidia drivers is that I couldn't get my system to work with nouveau. I used to use nouveau until about a year ago. If you want me to try, I can try. In my experience it's a lot of work, especially if screens don't work after restart with nouveau.

Revision history for this message
Xtien (xtien) wrote :

Fyi, the bug didn't occur between the first boot with the new bios, and the first reboot after that. I rebooted just to see if that wouldn't bring back the bug. I usually don't reboot that often. I checked the overclock rate, it's at "no overclock" (i.e. 100%).

Revision history for this message
penalvch (penalvch) wrote :

Xtien, it may be more helpful for you to do initial testing of nouveau via a live environment of http://cdimage.ubuntu.com/daily-live/current/ .

Revision history for this message
Xtien (xtien) wrote :

Nouveau makes it worse. When I start Android Studio, Firefox immediately grays out, AS stops loading before it even opens a window. Then the computer remains frozen, until I stop java processes in a shell.
Also, I don't see how a graphics issue can make CPU2 or CPU3 hang, but never one of the other CPUs.

It can't be just a bug in Android Studio, because AS should not be capable of hanging up my computer. Also, it can't be just a bug in Ubuntu or in the bios or cpu, because it only happens with Android Studio (except once in gedit and once in a shell). I suspect AS does something other software doesn't do, which triggers a glitch elsewhere.

Yesterday night, I ran Prime95 software to calculate Mersenne prime numbers. This kept my cpus at 500% with low priority processes. All software would still run normally, not slower, but AS wouldn't run. It pushed prime to using over 600%, which is weird, and it wouldn't start, just hang until killed.
I tried Prime95 because they found a glitch in Intel Skylake cpus. My cpu is 5th generation, not Skylake.

Revision history for this message
penalvch (penalvch) wrote :

Xtien, to clarify https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531845/comments/14 you tested the daily x64 live environment with nouveau?

Revision history for this message
Xtien (xtien) wrote :

I tested Nouveau with the standard iso from the ubuntu site. Should I test with the daily build?

Currently, I don't have any issues, after rebooting after testing with Nouveau. I hesitate to test right now, I'd like to get some work done first, I"m afraid that rebooting will give me freezes again.
I'll see what I can do with testing nouveau from a daily build.

Revision history for this message
Xtien (xtien) wrote :

My computer hasn't frozen in over a week. I haven't rebooted, until this morning when an Ubuntu update wanted me to reboot. Now the freeze issue is back, seemingly worse than before. 3 reboots didn't change this.

I noted that in "System Monitor", CPU2 gets stuck at 100%. However, when I type "top" in a shell, total cpu use is under 3%.

Revision history for this message
Xtien (xtien) wrote :

Today I tried the daily build of Ubuntu 16.04, from a live cd usb. Nouveau worked fine, but I can't seem to run Android Studio on a live cd, so I couldn't test the freeze issue. There was a problem with java. Maybe I should create a live cd usb with a large disk space, so I can install java and as on that. I tried to run android studio from the harddisk, that I had mounted.

Revision history for this message
Xtien (xtien) wrote :

I have been working with no problems since Jan. 20. Today an Ubuntu update wanted me to reboot, then after reboot the computer froze when I started Android Studio. Rebooted again, same, and again. What seems to help is when I type

IBUS_ENABLE_SYNC_MODE=1 ibus-daemon -xrd
(from here: http://tools.android.com/knownissues/ibus)

I'm not sure if this actually works, but now I disabled ibus and I have no freeze. The issue they report is different from what I see. For now, I'll just never reboot my computer. I hope someone is working on the bug. If there's anything I can do, let me know.

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

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Xtien (xtien) wrote :

My last post was on Feb 2, that's not 60 days. The problem still exists.

Revision history for this message
penalvch (penalvch) wrote :

Xtien:
>"My last post was on Feb 2, that's not 60 days."

Feb. 2 to April 2 is clearly 60 days.

Despite this, to clarify https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531845/comments/18 , you tested the x64 version?

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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