Bug 204345 - Unigine Superposition hard locks the PC since 5.1.18 (and possibly before)
Summary: Unigine Superposition hard locks the PC since 5.1.18 (and possibly before)
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-28 02:08 UTC by Joaquin Otsoa
Modified: 2019-08-21 20:55 UTC (History)
0 users

See Also:
Kernel Version: 5.1.20
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Joaquin Otsoa 2019-07-28 02:08:58 UTC
At first glance I though it was an Overclocking problem because I oc my hardware just slightly. But no even with no OCing, zero, nada... since 5.1.18 Unigine benchmark crashes. It is really unstable 90% of the times it will crash when it's about to display the final results, on 5.1.20 is even worse and it gets crazy because fps drop really hard. If you are really luck it will finish. I have tried 5.1.18/19 and 20. 5.0.20 doesn't not have this bug. I will try to investigate further to at least know which is the precise point release when this bug was introduced.
Comment 1 Joaquin Otsoa 2019-07-28 02:11:23 UTC
This is with Linux Mint (Ubuntu 18.04.2 LTS really) I forgot to mention that this is with the liquorix kernel, maybe I should try with vanilla kernel first.
Comment 2 Joaquin Otsoa 2019-07-28 02:34:22 UTC
With ubuntu ppa vanilla kernel this happens as well.
Comment 3 Joaquin Otsoa 2019-07-28 02:46:08 UTC
I should be more precise it doesn't crash really it hard locks the pc completely only the reset button will fix the problem.
Comment 4 Joaquin Otsoa 2019-07-28 03:21:57 UTC
interesting, kernel 5.2.3 doesn't hard lock the PC, but fps drop, abnormally (like with 5.1.20) but when looking at the final results, it's not that bad, about 5% performance hit.
Comment 5 Joaquin Otsoa 2019-07-28 04:04:01 UTC
unfortunately the bug was introduced in 5.1.0 so this is going to take thousands of commits, I'll do my best.
Comment 6 Joaquin Otsoa 2019-07-28 04:50:56 UTC
it doesn't happen with 4.19.61 lts. I think it will be easier to check all the 5.1 rc and check when this was introduced.
Comment 7 Jani Nikula 2019-08-21 09:47:15 UTC
What hardware?
Comment 8 Joaquin Otsoa 2019-08-21 20:55:13 UTC
I'm gonna close this because the regression on the 5.2 are fixed now performs even better than the 5.1 branch. And fixing the 5.1 branch makes no sense because it has reached EOL.

Note You need to log in before you can comment on or make changes to this bug.