Ubuntu
linux package

System hang when utilising OpenGL 4.5 features

Bug #1689408 reported by Paul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mesa
Fix Released
Medium
linux (Ubuntu)
Triaged
Low
Unassigned
mesa (Ubuntu)
New
Low
Unassigned

Bug Description

I've found this to be easily reproducible via unigine's heaven benchmark, which uses tessellation and other features extensively. Simply creating a OpenGL 4.5 context will not trigger the hang, and you must explicitly request an OGL 4+ context as the default will only be 3.0.

On a successful trigger, the screen may flicker on and off a few times and eventually hang completely on a black screen, there's no way to recover the system from this state bar a power cycle (ie hold the power button).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: paulh 1405 F.... pulseaudio
 /dev/snd/controlC0: paulh 1405 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue May 9 09:14:09 2017
InstallationDate: Installed on 2017-01-05 (123 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: HP HP Notebook
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.1C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8133
dmi.board.vendor: HP
dmi.board.version: KBC Version 98.0E
dmi.chassis.asset.tag: 5CG6124XBK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

Revision history for this message
Paul (paul17041993) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

since the default is safe I'll lower the importance

do file this upstream too, thanks

Changed in mesa (Ubuntu):
importance: Undecided → Low
Revision history for this message
Paul (paul17041993) wrote :

The default is ignored however if the game requires tessellation or other 4+ features, which is pretty much every big game released in the past few years...

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

so file it upstream

Revision history for this message
In , Paul (paul17041993) wrote :

This is easily reproducible via unigine's heaven benchmark, simply running it with normal tessellation settings results in the screen flashing black a few times and then an eventual system hang before anything even starts to render. A power cycle is the only way out.

Simply creating a 4.5 context will not trigger the bug, haven't been able to fully test what causes the hang specifically as accessible tools I've found are not compatible with mesa due to only creating a default context (which is currently 3.0), thus crashing on init.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408

Revision history for this message
Paul (paul17041993) wrote :

https://bugs.freedesktop.org/show_bug.cgi?id=100995

Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

Please attach the output of glxinfo and dmesg and the Xorg log file.

Revision history for this message
In , Paul (paul17041993) wrote :

Created attachment 131303
errors that appear to be related to the hang

errors that appear to be related to the hang

Revision history for this message
In , Paul (paul17041993) wrote :

Created attachment 131304
glxinfo, should contain all the hardware and package info needed

glxinfo, should contain all the hardware and package info needed

Revision history for this message
In , Paul (paul17041993) wrote :

Created attachment 131305
dmesg

dmesg

(In reply to Michel Dänzer from comment #1)
> Please attach the output of glxinfo and dmesg and the Xorg log file.

Already in the process of dumping files...

Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

Is this a regression from an older version of Mesa? If so, can you bisect?

Revision history for this message
In , Paul (paul17041993) wrote :

Created attachment 131306
post-hang xorg log, may not be relevant

post-hang xorg log, may not be relevant

Xorg doesn't appear to keep old log files, or the log may have been lost as a result of the hang, not exactly willing to trigger the hang again at this particular time...

Revision history for this message
In , Paul (paul17041993) wrote :

(In reply to Michel Dänzer from comment #5)
> Is this a regression from an older version of Mesa? If so, can you bisect?

Don't know, never had any working previous versions due to outdated kernel and drivers (kubuntu 16.10). This is as close as I've gotten > 3.0 to work on this machine by upgrading to 17.04 (4.10 kernel).

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

great, thanks

Bug Watch Updater (bug-watch-updater)
Changed in mesa:
importance: Unknown → Medium
status: Unknown → Confirmed
Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Revision history for this message
In , Timothy Arceri (t-fridey) wrote :

Is this working for you now?

Unigine heaven is used regularly for benchmarking and there are no other reports of this type as far as I'm aware.

Bug Watch Updater (bug-watch-updater)
Changed in mesa:
status: Confirmed → Incomplete
Revision history for this message
In , Paul (paul17041993) wrote :

(In reply to Timothy Arceri from comment #8)
> Is this working for you now?

I've since removed linux from the system and handed it down to a family member, so it's not possible for me to test anymore. However I would expect the bug would have been fixed by now, according to the current RadeonFeature support table.

Bug Watch Updater (bug-watch-updater)
Changed in mesa:
status: Incomplete → Fix Released
Revision history for this message
Paul (paul17041993) wrote :

Fix status is unknown and untested, it may not be fixed at all, I simply lack the hardware to actually test it.

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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