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 1906165 - After upgrade mesa from 20.3.0-1 to 20.3.0-2 version on computer with Radeon GPU gnome-shell become crashing
Summary: After upgrade mesa from 20.3.0-1 to 20.3.0-2 version on computer with Radeon ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34BetaBlocker F34BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2020-12-09 19:43 UTC by Mikhail
Modified: 2021-01-02 22:58 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-02 22:58:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
gnome-shell backtrace (351.71 KB, text/plain)
2020-12-09 19:43 UTC, Mikhail 		no flags Details
system log (663.63 KB, text/plain)
2020-12-09 19:45 UTC, Mikhail 		no flags Details
valgrind report for glxgears (727.22 KB, text/plain)
2020-12-10 07:47 UTC, Mikhail 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab mesa/mesa - issues 3974 0 None None None 2020-12-14 05:44:14 UTC

Description Mikhail 2020-12-09 19:43:33 UTC 
Created attachment 1737988 [details]
gnome-shell backtrace

Description of problem:
After upgrade mesa from 20.3.0-1 to 20.3.0-2 version gnome-shell become crashing

Version-Release number of selected component (if applicable):
Last good version: 20.3.0-1

How reproducible:
Update Mesa on computer with Radeon GPU and try reboot.


$ inxi -bM
System:    Host: fedora Kernel: 5.10.0-0.rc6.20201204git34816d20f173.92.fc34.x86_64 x86_64 bits: 64 Desktop: GNOME 40.alpha 
           Distro: Fedora release 34 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-I GAMING v: Rev X.0x serial: <superuser/root required> 
           UEFI: American Megatrends v: 2802 date: 10/21/2020 
Battery:   ID-1: hidpp_battery_0 charge: N/A condition: N/A 
CPU:       Info: 16-Core (2-Die) AMD Ryzen 9 3950X [MT MCP MCM] speed: 3528 MHz min/max: 2200/3500 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.10 driver: ati,modesetting unloaded: fbdev,radeon,vesa 
           resolution: 3840x2160~60Hz 
           OpenGL: 
           renderer: AMD Radeon VII (VEGA20 DRM 3.40.0 5.10.0-0.rc6.20201204git34816d20f173.92.fc34.x86_64 LLVM 11.0.0) 
           v: 4.6 Mesa 20.3.0 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
           Device-2: Intel I211 Gigabit Network driver: igb 
Drives:    Local Storage: total: 11.35 TiB used: 10.25 TiB (90.3%) 
Info:      Processes: 685 Uptime: 1h 19m Memory: 31.18 GiB used: 18.64 GiB (59.8%) Shell: Bash inxi: 3.1.08
Comment 1 Mikhail 2020-12-09 19:45:03 UTC 
Created attachment 1737989 [details]
system log
Comment 2 Mikhail 2020-12-09 19:52:11 UTC 
Yes I know that this commit https://src.fedoraproject.org/rpms/mesa/c/709d0a2cd134072cc32bf5372e20176bf533acd3?branch=master is not culprit here. I suppose here is blame new GCC 11. I am every day compile mesa git and after the GCC 11 was came to my computer then all graphical application started crashing too with fresh builded mesa.
Comment 3 Mikhail 2020-12-10 07:47:57 UTC 
Created attachment 1738133 [details]
valgrind report for glxgears

==204183== LEAK SUMMARY:
==204183==    definitely lost: 32 bytes in 1 blocks
==204183==    indirectly lost: 0 bytes in 0 blocks
==204183==      possibly lost: 154,806 bytes in 670 blocks
==204183==    still reachable: 13,340,749 bytes in 19,671 blocks
==204183==                       of which reachable via heuristic:
==204183==                         newarray           : 2,555,360 bytes in 40 blocks
==204183==                         multipleinheritance: 43,488 bytes in 63 blocks
==204183==         suppressed: 0 bytes in 0 blocks
==204183== Reachable blocks (those to which a pointer was found) are not shown.
==204183== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==204183== 
==204183== ERROR SUMMARY: 557 errors from 557 contexts (suppressed: 0 from 0)
Comment 4 Chad King 2020-12-14 02:27:45 UTC 
Hi, ran into this as well on my RX 6800. Ended up downgrading to mesa 20.3.0-1, thanks for the info.
Comment 5 Fedora Blocker Bugs Application 2020-12-20 21:13:25 UTC 
Proposed as a Blocker and Freeze Exception for 34-beta by Fedora user mikhail using the blocker tracking app because:

 Because gnome-shell will not run on computers with Radeon GPU (checked on Radeon VII and 6800) after users upgraded to Fedora 34.
Comment 6 Mikhail 2020-12-29 20:40:16 UTC 
The problem will gone if mesa would compiled with gcc-11.0.0-0.11.fc34.
So please rebuild mesa and put new build in repo.
Comment 7 Adam Williamson 2021-01-02 19:59:39 UTC 
There was a build on Dec 31:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1663455

so is the bug fixed now?

(I thought we built mesa with llvm not gcc...)
Comment 8 Mikhail 2021-01-02 22:58:04 UTC 
> There was a build on Dec 31:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1663455
> 
> so is the bug fixed now?

Yes, the build 20.3.2-1.fc34  working well as expected on Radeon GPUs.

> (I thought we built mesa with llvm not gcc...)

This is isn't it.
You can to sure here:
https://kojipkgs.fedoraproject.org//work/tasks/7629/58657629/build.log

> C++ compiler for the host machine: g++ (gcc 11.0.0 "g++ (GCC) 11.0.0 20201223 (Red Hat 11.0.0-0)")
> C++ linker for the host machine: g++ ld.bfd 2.35.1-16
> Using 'CC' from environment with value: 'gcc'
Note You need to log in before you can comment on or make changes to this bug.