Regression: Segfault in cso_destroy_context() regression in 20.2
Please post inxi -GSC -xx
output
System: Host: cain.armitage.org.uk Kernel: 5.9.14-200.fc33.x86_64 x86_64 bits: 64 compiler: gcc v: 2.35-15.fc33)
Console: tty 0 DM: GDM Distro: Fedora release 33 (Thirty Three)
CPU: Info: Dual Core model: AMD Turion 64 X2 Mobile TL-60 bits: 64 type: MCP arch: K8 rev.F+ rev: 1 L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 svm bogomips: 8000
Speed: 800 MHz min/max: 800/2000 MHz Core speeds (MHz): 1: 1600 2: 1600
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] vendor: Dell driver: radeon
v: kernel bus ID: 01:05.0 chip ID: 1002:5975
Display: server: X.org 1.20.10 driver: ati,radeon unloaded: fbdev,modesetting,vesa tty: 180x65
Message: Advanced graphics data unavailable in console for root.
Describe the issue
After booting the screen displays:
Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator
Regression
It used to work in 20.2.3, stopped working in 20.2.4 and still does not work in 20.2.6.
Log files as attachment
- Backtrace
[Current thread is 1 (Thread 0x7eff6bd7e740 (LWP 1111))]
Missing separate debuginfos, use: dnf debuginfo-install gnome-session-3.38.0-1.fc33.x86_64
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007eff5d4cd09b in cso_destroy_context () from /usr/lib64/dri/r300_dri.so
#2 0x00007eff5d04f034 in st_destroy_context_priv () from /usr/lib64/dri/r300_dri.so
#3 0x00007eff5d0502d4 in st_destroy_context () from /usr/lib64/dri/r300_dri.so
#4 0x00007eff5d031a82 in dri_destroy_context () from /usr/lib64/dri/r300_dri.so
#5 0x00007eff5d4cb767 in driDestroyContext () from /usr/lib64/dri/r300_dri.so
#6 0x00007eff5e81ac33 in dri2_destroy_context () from /lib64/libGLX_mesa.so.0
#7 0x00007eff5e809559 in glXDestroyContext () from /lib64/libGLX_mesa.so.0
#8 0x000055f9a9e3f93e in main ()
This is followed by two instances of
(gdb) bt
#0 0x0000000000000000 in ()
#1 0x00007f1b199e809b in cso_destroy_context () at /usr/lib64/dri/r300_dri.so
#2 0x00007f1b1956a034 in st_destroy_context_priv () at /usr/lib64/dri/r300_dri.so
#3 0x00007f1b1956b2d4 in st_destroy_context () at /usr/lib64/dri/r300_dri.so
#4 0x00007f1b1954ca82 in dri_destroy_context () at /usr/lib64/dri/r300_dri.so
#5 0x00007f1b199e6767 in driDestroyContext () at /usr/lib64/dri/r300_dri.so
#6 0x00007f1b1aa70c33 in dri2_destroy_context () at /lib64/libGLX_mesa.so.0
#7 0x00007f1b1aa5f559 in glXDestroyContext () at /lib64/libGLX_mesa.so.0
#8 0x00007f1b31da9aa2 in _cogl_winsys_display_destroy.lto_priv.0 () at /usr/lib64/mutter-7/libmutter-cogl-7.so.0
#9 0x00007f1b31d78d8d in _cogl_object_display_indirect_free () at /usr/lib64/mutter-7/libmutter-cogl-7.so.0
#10 0x00007f1b31d7b875 in cogl_renderer_check_onscreen_template () at /usr/lib64/mutter-7/libmutter-cogl-7.so.0
#11 0x00007f1b32562f24 in clutter_backend_x11_get_display () at /usr/lib64/mutter-7/libmutter-clutter-7.so.0
#12 0x00007f1b3250631e in clutter_backend_real_create_context () at /usr/lib64/mutter-7/libmutter-clutter-7.so.0
#13 0x00007f1b3252e327 in clutter_init_real () at /usr/lib64/mutter-7/libmutter-clutter-7.so.0
#14 0x00007f1b3252e6c8 in post_parse_hook () at /usr/lib64/mutter-7/libmutter-clutter-7.so.0
#15 0x00007f1b32f1c1c7 in g_option_context_parse () at /lib64/libglib-2.0.so.0
#16 0x00007f1b3252e9bd in clutter_init () at /usr/lib64/mutter-7/libmutter-clutter-7.so.0
#17 0x00007f1b32305ec3 in meta_backend_initable_init () at /lib64/libmutter-7.so.0
#18 0x00007f1b3235d04c in meta_init () at /lib64/libmutter-7.so.0
#19 0x00005568ae4529dc in main ()
- Output of
dmesg
dmesg.log
Any extra information would be greatly appreciated
This is logged as RedHat bz#1908448
When using the 20.2.4 drivers, the stack backtrace appeared to be corrupted - see RedHat BZ for more details.
Pete Walker added to the BZ report: I suspect it could be a fallout from bd32ac29 that added an assert to cso_destroy_context(). Any chance you could file this upstream and say that it's a regression in 20.2?
I have now built the RPM packages with 20.2.6 and commit bd32ac29 reverted, and I am still getting the segfault.