atleast one crash fix need to be added

Keywords: (none) => feedback

crash fix added, new rpms:

SRPM:
mesa-21.3.6-2.mga8.src.rpm


i586:
libd3d1-21.3.6-2.mga8.i586.rpm
libd3d-devel-21.3.6-2.mga8.i586.rpm
libdri-drivers-21.3.6-2.mga8.i586.rpm
libgbm1-21.3.6-2.mga8.i586.rpm
libgbm-devel-21.3.6-2.mga8.i586.rpm
libglapi0-21.3.6-2.mga8.i586.rpm
libglapi-devel-21.3.6-2.mga8.i586.rpm
libmesaegl1-21.3.6-2.mga8.i586.rpm
libmesaegl-devel-21.3.6-2.mga8.i586.rpm
libmesagl1-21.3.6-2.mga8.i586.rpm
libmesagl-devel-21.3.6-2.mga8.i586.rpm
libmesaglesv1_1-21.3.6-2.mga8.i586.rpm
libmesaglesv1-devel-21.3.6-2.mga8.i586.rpm
libmesaglesv2_2-21.3.6-2.mga8.i586.rpm
libmesaglesv2-devel-21.3.6-2.mga8.i586.rpm
libmesakhr-devel-21.3.6-2.mga8.i586.rpm
libmesaopencl1-21.3.6-2.mga8.i586.rpm
libmesaopencl-devel-21.3.6-2.mga8.i586.rpm
libmesavulkan-devel-21.3.6-2.mga8.i586.rpm
libmesavulkan-drivers-21.3.6-2.mga8.i586.rpm
libosmesa8-21.3.6-2.mga8.i586.rpm
libosmesa-devel-21.3.6-2.mga8.i586.rpm
libvdpau-driver-nouveau-21.3.6-2.mga8.i586.rpm
libvdpau-driver-r300-21.3.6-2.mga8.i586.rpm
libvdpau-driver-r600-21.3.6-2.mga8.i586.rpm
libvdpau-driver-radeonsi-21.3.6-2.mga8.i586.rpm
libxatracker2-21.3.6-2.mga8.i586.rpm
libxatracker-devel-21.3.6-2.mga8.i586.rpm
mesa-21.3.6-2.mga8.i586.rpm
mesa-common-devel-21.3.6-2.mga8.i586.rpm
mesa-omx-drivers-21.3.6-2.mga8.i586.rpm


x86_64:
lib64d3d1-21.3.6-2.mga8.x86_64.rpm
lib64d3d-devel-21.3.6-2.mga8.x86_64.rpm
lib64dri-drivers-21.3.6-2.mga8.x86_64.rpm
lib64gbm1-21.3.6-2.mga8.x86_64.rpm
lib64gbm-devel-21.3.6-2.mga8.x86_64.rpm
lib64glapi0-21.3.6-2.mga8.x86_64.rpm
lib64glapi-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesaegl1-21.3.6-2.mga8.x86_64.rpm
lib64mesaegl-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesagl1-21.3.6-2.mga8.x86_64.rpm
lib64mesagl-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesaglesv1_1-21.3.6-2.mga8.x86_64.rpm
lib64mesaglesv1-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesaglesv2_2-21.3.6-2.mga8.x86_64.rpm
lib64mesaglesv2-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesakhr-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesaopencl1-21.3.6-2.mga8.x86_64.rpm
lib64mesaopencl-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesavulkan-devel-21.3.6-2.mga8.x86_64.rpm
lib64mesavulkan-drivers-21.3.6-2.mga8.x86_64.rpm
lib64openswr0-21.3.6-2.mga8.x86_64.rpm
lib64osmesa8-21.3.6-2.mga8.x86_64.rpm
lib64osmesa-devel-21.3.6-2.mga8.x86_64.rpm
lib64vdpau-driver-nouveau-21.3.6-2.mga8.x86_64.rpm
lib64vdpau-driver-r300-21.3.6-2.mga8.x86_64.rpm
lib64vdpau-driver-r600-21.3.6-2.mga8.x86_64.rpm
lib64vdpau-driver-radeonsi-21.3.6-2.mga8.x86_64.rpm
lib64xatracker2-21.3.6-2.mga8.x86_64.rpm
lib64xatracker-devel-21.3.6-2.mga8.x86_64.rpm
mesa-21.3.6-2.mga8.x86_64.rpm
mesa-common-devel-21.3.6-2.mga8.x86_64.rpm
mesa-omx-drivers-21.3.6-2.mga8.x86_64.rpm

Keywords: feedback => (none)

Tested with Foolishness, my Dell Inspiron 5100, 32-bit P4, Radeon RV200 graphics, 32-bit Xfce system using kernel-desktop.

No installation issues. Did a reboot, looked at a few things, then used qarepo to download packages to test a kernel update. Rebooted into the new kernel, tried this and that, no issues noted.

CC: (none) => andrewsfarm

mga8, x64, Intel/nvidia system
Installed any missing packages then updated using qarepo.
Everything running after reboot.  Tried a few of the mesademos like reflect, gears, bounce...  All good.

CC: (none) => tarazed25

MGA8 64 Intel Core I3, Nvidia Geforce 520M

Updated with QA repo.
No issues after reboot

CC: (none) => guillaume.royer

MGA8-64 Plasma on Lenovo B50 (all Intel HW) in Dutch
No installation issues.
Rebooted fine, no ill effects.

CC: (none) => herman.viaene

MGA8-64 Plasma on a HP Probook 6550b, i3, Intel i915 graphics.

No installation issues. Checked both before and after getting the proposed kernel update. No new issues noted.

I had a small hope that the "crash fix" might solve problems with this hardware and glmark2 (Bug 25204), but it didn't happen. Glmark2 still crashes with a segmentation fault partway through the test. However, as this is an ongoing problem carried over from Mageia 7, and is probably a glmark2 problem anyway, it doesn't count as a new issue.

re comment 7.
I have tried to recreate this, in vain.  Ran glmark2 in debug mode before and after the mesa update, on Intel i7 hardware with the i915 driver, and saved the terminal logs.  Diffing those showed nothing exceptional.  The main differences between TJ's system and this one is i3/i7 and the relative ages of the hardware.
Different desktops as well but all these things should be irrelevant.

It seems to be connected to which "GL Version" glmark2 reports that the video hardware is using. I too have another Intel-based machine where glmark2 works just fine. That one has a i5-2500 and integrated graphics, but glmark2 reports a "GL Version" of 3.0 on that machine, where it says the 6550b uses the 2.1 version. 

And here's an odd-seeming one... On the same real 6550b hardware, glmark2 works just fine in a VirtualBox guest - but there it reports a GL Version of 3.1. Apparently, VirtualBox is capable of simulating hardware that's better than the hardware it's running on.

All this was reported in Bug 25204 in October, but nothing has happened with that bug since I did so.

MGA8-64 Plasma VirtualBox guest on a MGA8-64 Plasma host. (Probook 6550b)

No installation issues. Rebooted, then ran glmark2, which completed with the dismal score of 54 - but it did complete. GL Version being reported is now 4.5.

Ran a few things, no issues noted.

Gonna get this in, anyway...

Dell Dimension e520, Core2Quad, Radeon HD 8570 graphics (amdcpu driver).

No installation issues. Ran glmark2, receiving a score of 1325. Looks good.

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0025.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED

This went through quicker than I thought :)
Reporting in short

64 bit OK - No regressions noted on 4 systems user more or less hours
Tested together with kernel-desktop, mesa, microcode, nonfree firmwares


§ Workstation "svarten": plasma, nvidia-current, ...
Details: https://bugs.mageia.org/show_bug.cgi?id=30030#c18


§ Virtual box guest mga 8, details noted in same kernel bug comment.


§ Laptop Asus A717
i5-7300HQ, integrated HD Graphics 630, using "Intel 810 and later" (GPU 2 not configured), wifi Atheros QCA6174 using ath10k_pci


§ Laptop Thinkpad T510
GPU i5-M540, 4 core
GPU: GT218M[NVS 3100M] using NVIDIA GeForce 8100 to GeForce 415
wifi: Centrino Advanced N 6200, using iwlwifi


§ Laptop Dell Dimension M63000
CPU: Core2 Duo T7500
GPU: G84GLM [Quadro FX 1600M] using NVIDIA GeForce 8100 to GeForce 415
wifi: PRO/Wireless 3945ABG using iwl3945

CC: (none) => fri