Xorg freeze

[Vegard Vesterheim]

Symptoms are: screen/console/keyboard non-functional. Xorg has crashed. System is up, ssh login is possible. Unable to restart display manager, unable to reboot, must powercycle machine to recover. Observing problem after being away from keyboard for some time.

Kernel call trace:
https://launchpadlibrarian.net/247894911/dmesg.xorg.freeze

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 14 15:01:49 2016
DistUpgraded: 2015-12-01 13:45:07,953 DEBUG failed to SystemUnLock() (E:Not locked)
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e5]
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:2891): WARNING **: Failed to load user image: Failed to open file '/home/vegardv/.face': No such file or directory
 init: indicator-power main process (2937) killed by TERM signal
 init: indicator-application main process (2940) killed by TERM signal
MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic root=/dev/mapper/voll2--vg-root ro splash quiet vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to xenial on 2015-12-01 (104 days ago)
dmi.bios.date: 12/17/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.21
dmi.board.asset.tag: CZC41911VB
dmi.board.name: 18E5
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC41911VB
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP EliteDesk 800 G1 USDT
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Mar 14 14:56:12 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 2095
 vendor SAM
xserver.version: 2:1.18.1-1ubuntu3

[Vegard Vesterheim (vegard-vesterheim)]

# sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
L01 v02.65
07/13/2015

The same problem occurred after BIOS upgrade. The monitors appear to be in Energy Saving mode. The Xorg server has crashed. No response from keyboard input. Dmesg output with similar content as attached previously. Machine must be powercycled to recover.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Vegard Vesterheim, 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.

Also, you don't need to apport-collect further unless specifically requested to do so.

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

Thank you for your understanding.

[Vegard Vesterheim (vegard-vesterheim)]

Installed the latest kernel package as requested. (linux-image-4.5.0-040500-generic)

An upgrade to kernel 4.5 seems to have fixed the problem. Adding tags as requested.

[penalvch (penalvch)]

Vegard Vesterheim, the next step is to fully reverse commit bisect from kernel 4.4 to 4.5 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. 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.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

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

[Vegard Vesterheim (vegard-vesterheim)]

Given the nature of this bug (sporadic, not easily reproducible),
identifying the bad commit by booting intermediate kernel commit
revisions could possibly be *very* time-consuming. This problem
affects my main desktop at work. I am not sure that I can invest that
much time to help identify this problem now.

As far as I am concerned, I am happy that my problem can be resolved
by using a more recent kernel. If it is very important for the Ubuntu
community that this problem gets fixed by backporting the good commit,
I may reconsider.

[Vegard Vesterheim (vegard-vesterheim)]

Alas, the new kernel (linux-image-4.5.0-040500-generic) exhibits another even more catastrophic behaviour!

Now the kernel crashes completely, the screen is black and now the host appears to be completely dead (no ping response, no keyboard response). Upon restart the only indication I can find is a series of ASCII NULLs in kern.log and Xorg.0.log. This problem seems to occur more seldom than the first one (every few days, as opposed to several times a day), but this also seems to be related to screensaver/power saving. I observe the problem when returning to the machine after being away for a while.

This is really strange, this machine was very stable running 14.04.

Anyway, I guess this could be an unrelated bug, so I guess it is time for yet another bug report...

As far as I am concerned, this bug can be closed.

[penalvch (penalvch)]

Perhaps 4.5 being fixed is a false positive here, given a crash happened with it.