Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1822835 - 0ad won't start on Ryzen 3xxx CPU
Summary: 0ad won't start on Ryzen 3xxx CPU
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: 0ad
Version: 31
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Paulo Andrade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-10 03:39 UTC by Trevor Cordes
Modified: 2020-05-28 02:00 UTC (History)
6 users (show)

Fixed In Version: 0ad-master-3220200523074436.1 0ad-0.0.23b-15.fc32 0ad-0.0.23b-15.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-27 00:47:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Trevor Cordes 2020-04-10 03:39:14 UTC 
Description of problem:
0ad worked fine until I upgraded box to Ryzen 3900X CPU.  Now it won't start, instead gives error:
cache.cpp(43): Assertion failed: "cache.Validate()"

Known problem has been fixed upstream.  Can we get a new version build for F30?
https://trac.wildfiregames.com/ticket/4360
See patch in comment 23


Version-Release number of selected component (if applicable):
0ad-0.0.23b-6.fc30.x86_64


How reproducible:
always


Steps to Reproduce:
1. Put 0ad on a Ryzen 3xxx CPU
2. type 0ad at the command line
3.

Actual results:
cache.cpp(43): Assertion failed: "cache.Validate()"
Assertion failed: "cache.Validate()"
Location: cache.cpp:43 (AddCache)

Call stack:

(0x989aa5) /bin/pyrogenesis() [0x989aa5]
(0x93f8e1) /bin/pyrogenesis() [0x93f8e1]
(0x940c47) /bin/pyrogenesis() [0x940c47]
(0x9413f9) /bin/pyrogenesis() [0x9413f9]
(0x9816ae) /bin/pyrogenesis() [0x9816ae]
(0x981cb8) /bin/pyrogenesis() [0x981cb8]
(0x98205d) /bin/pyrogenesis() [0x98205d]
(0x9b8203) /bin/pyrogenesis() [0x9b8203]
(0x981db2) /bin/pyrogenesis() [0x981db2]
(0x983b0a) /bin/pyrogenesis() [0x983b0a]
(0x9b8203) /bin/pyrogenesis() [0x9b8203]
(0x9838de) /bin/pyrogenesis() [0x9838de]
(0x670bba) /bin/pyrogenesis() [0x670bba]
(0x6666f8) /bin/pyrogenesis() [0x6666f8]
(0x47a753) /bin/pyrogenesis() [0x47a753]
(0x46983e) /bin/pyrogenesis() [0x46983e]

errno = 0 (Error during IO)
OS error = ?

** no graphical screen is shown **


Expected results:
should start the game and show initial screen


Additional info:
Looks like the new Ryzens do something weird with the L3 cache that 0ad isn't expecting.
Comment 1 Ben Cotton 2020-04-30 20:15:34 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Trevor Cordes 2020-05-23 06:21:22 UTC 
Bug persists in F31: 0ad-0.0.23b-9.fc31.x86_64

The patch I provide in original post completely fixes the problem with just one line changed.  Here's a more direct link to the patch:

https://trac.wildfiregames.com/changeset/23262

It is patched upstream, but no idea when that newer version is going to be released to the point Fedora has it.
Comment 3 Kalev Lember 2020-05-23 06:52:29 UTC 
Thanks! I went ahead and backported this in https://src.fedoraproject.org/rpms/0ad/c/67e2fa2f0b66e9aeb6256fe22df151efde41de8f?branch=master
Comment 4 Fedora Update System 2020-05-23 10:39:59 UTC 
FEDORA-2020-fbc02b5d11 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbc02b5d11
Comment 5 Fedora Update System 2020-05-23 10:40:00 UTC 
FEDORA-2020-14ac92302f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-14ac92302f
Comment 6 Fedora Update System 2020-05-23 10:40:01 UTC 
FEDORA-FLATPAK-2020-6c920b415d has been submitted as an update to Fedora 32 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-6c920b415d
Comment 7 Fedora Update System 2020-05-24 04:49:10 UTC 
FEDORA-2020-14ac92302f has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-14ac92302f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-14ac92302f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2020-05-24 05:02:34 UTC 
FEDORA-2020-fbc02b5d11 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fbc02b5d11`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbc02b5d11

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2020-05-24 05:03:58 UTC 
FEDORA-FLATPAK-2020-6c920b415d has been pushed to the Fedora 32 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-6c920b415d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 10 Fedora Update System 2020-05-27 00:47:49 UTC 
FEDORA-FLATPAK-2020-6c920b415d has been pushed to the Fedora 32 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.
Comment 11 Fedora Update System 2020-05-27 04:11:45 UTC 
FEDORA-2020-14ac92302f has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 12 Trevor Cordes 2020-05-27 08:55:48 UTC 
That fixed it!  I left karma
Comment 13 Kalev Lember 2020-05-27 09:16:58 UTC 
Great! Thanks, Trevor.
Comment 14 Fedora Update System 2020-05-28 02:00:06 UTC 
FEDORA-2020-fbc02b5d11 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.