Hi all,

please check and save what packages you have installed BEFORE performing
the current "update"!

I "updated", and now when setting the graphics system under load, the box completely crashes. Tested on two machines with same HW and SW / OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16 CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024 14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST pulseaudio-module-zeroconf-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST
pulseaudio-module-jack-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST
pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST
net-snmp-mibs-5.9.3-2.1.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST lib64osmesa8-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:15 CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST pulseaudio-client-config-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST pipewire-0.3.85-5.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:14 CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:14 CEST lib64camera0.2-0.2.0-1.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:13 CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:11 CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:11 CEST
vim-common-9.1.411-1.1.mga9.x86_64 So 04 Aug 2024 14:43:10 CEST lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64 So 04 Aug 2024 14:43:09
CEST
lib64pulsecore16.1-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:09 CEST lib64pulsecommon16.1-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:09 CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did not occur (!). -- Hence, there has been some component installed, see above,
that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a "no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Hello Markus!

Monday August 05 2024 12:20, Markus Robert Kessler wrote to All:

Interesting - I have been getting occasional crash for a month or so and
just 'assumed' it was my kit.

May be similar reason as I use 6.6.37 for at least 14 days (since last
reboot any way).

In which case I will keep the previous 6.6.28 - JIC.

Vince

Hi all,

please check and save what packages you have installed BEFORE
performing the current "update"!

I "updated", and now when setting the graphics system under load, the
box completely crashes. Tested on two machines with same HW and SW /
OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile
GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16
CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024
14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64
So 04 Aug 2024 14:43:15
CEST pulseaudio-module-zeroconf-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:15 CEST pulseaudio-module-jack-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So
04 Aug 2024 14:43:15
CEST pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST net-snmp-mibs-5.9.3-2.1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST lib64osmesa8-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64
So 04 Aug 2024 14:43:15
CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:14 CEST pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:14 CEST pulseaudio-client-config-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST pipewire-0.3.85-5.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64camera0.2-0.2.0-1.mga9.x86_64
So 04 Aug 2024 14:43:14
CEST lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:13 CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug
2024 14:43:11
CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug
2024
14:43:11 CEST
vim-common-9.1.411-1.1.mga9.x86_64 So 04 Aug 2024 14:43:10
CEST lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64 So 04 Aug 2024 14:43:09 CEST lib64pulsecore16.1-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:09 CEST lib64pulsecommon16.1-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:09 CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did
not occur (!). -- Hence, there has been some component installed, see
above, that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a
"no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

Vincent


SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 263/0 362/6 467/4 712/1321

Subject: RPM list from backup? ./. Was: Warning: Yesterday's update makes
MGA9-64 crash

Forgot to mention:

Luckily, I made a whole-backup from the machine before I (stupidely)
started the "update".

So, I could throw down everything and restore from backup. What I don`t
really want to. Or:

if there is a way to create the RPM list out of the whole-backup tgz file?
I have everything on /dev/sda1 as archive file.

Maybe someone known how to "extract" the RPM list out of /var, /usr or somewhere else?

Would appreciate to hear. Thanks!

Best regards,

Markus






On Mon, 5 Aug 2024 11:20:29 -0000 (UTC) Markus Robert Kessler wrote:

Hi all,

please check and save what packages you have installed BEFORE performing
the current "update"!

I "updated", and now when setting the graphics system under load, the
box completely crashes. Tested on two machines with same HW and SW / OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile
GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16
CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024
14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64 So
04 Aug 2024 14:43:15 CEST pulseaudio-module-zeroconf-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-module-jack-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:15 CEST net-snmp-mibs-5.9.3-2.1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST lib64osmesa8-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:15 CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST
pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14
CEST pulseaudio-client-config-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:14 CEST pipewire-0.3.85-5.mga9.x86_64 So 04
Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64 So
04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64camera0.2-0.2.0-1.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:13
CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:11 CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So 04
Aug 2024 14:43:11 CEST vim-common-9.1.411-1.1.mga9.x86_64 So
04 Aug 2024 14:43:10 CEST
lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64 So 04 Aug 2024
14:43:09 CEST lib64pulsecore16.1-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:09 CEST lib64pulsecommon16.1-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:09 CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did
not occur (!). -- Hence, there has been some component installed, see
above, that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a
"no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Subject: Re: RPM list from backup? ./. Was: Warning: Yesterday's update makes
MGA9-64 crash

The rpm database seems to be located in /var/lib/rpm.

So, when extracting this path out of the working backup to let's say /tmp,
one could try to export the rpm list from there.

Therefore it should be possible to tell rpmdb or some other tool to
extract the rpm list from exactly this /tmp/rpmbd.sqlite, and not the db
from the host system.

Someone already facing this problem and know how to proceed?

Markus




On Mon, 5 Aug 2024 13:26:42 -0000 (UTC) Markus Robert Kessler wrote:

Forgot to mention:

Luckily, I made a whole-backup from the machine before I (stupidely)
started the "update".

So, I could throw down everything and restore from backup. What I don`t really want to. Or:

if there is a way to create the RPM list out of the whole-backup tgz
file?
I have everything on /dev/sda1 as archive file.

Maybe someone known how to "extract" the RPM list out of /var, /usr or somewhere else?

Would appreciate to hear. Thanks!

Best regards,

Markus

On Mon, 5 Aug 2024 11:20:29 -0000 (UTC) Markus Robert Kessler wrote:

Hi all,

please check and save what packages you have installed BEFORE
performing the current "update"!

I "updated", and now when setting the graphics system under load, the
box completely crashes. Tested on two machines with same HW and SW /
OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile
GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16
CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024
14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64 So
04 Aug 2024 14:43:15 CEST
pulseaudio-module-zeroconf-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-jack-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST
pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:15 CEST net-snmp-mibs-5.9.3-2.1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST lib64osmesa8-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:15 CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST
pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14
CEST pulseaudio-client-config-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:14 CEST pipewire-0.3.85-5.mga9.x86_64 So 04
Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64 So
04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64 So 04
Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64camera0.2-0.2.0-1.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST
lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:13
CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:11 CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:11 CEST vim-common-9.1.411-1.1.mga9.x86_64
So 04 Aug 2024 14:43:10 CEST
lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64 So 04 Aug 2024
14:43:09 CEST lib64pulsecore16.1-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:09 CEST lib64pulsecommon16.1-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:09 CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did
not occur (!). -- Hence, there has been some component installed, see
above, that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a
"no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Subject: Re: RPM list from backup? ./. Was: Warning: Yesterday's update makes
MGA9-64 crash

Gotit!

Maybe this is helpful for others:

I did the following --

- extract /var/lib/rpm from backup
- mv /var/lib/rpm on the damaged system to rpm_damaged
- mv restored dir to /var/lib/rpm_working
- in /var/lib set symlinks, ln -s rpm_working rpm
- extract rpm list, rpm -qa --last > rpmlist_working
- do exactly the same for damaged state
- compare

BR,

Markus




On Mon, 5 Aug 2024 14:23:54 -0000 (UTC) Markus Robert Kessler wrote:

The rpm database seems to be located in /var/lib/rpm.

So, when extracting this path out of the working backup to let's say
/tmp,
one could try to export the rpm list from there.

Therefore it should be possible to tell rpmdb or some other tool to
extract the rpm list from exactly this /tmp/rpmbd.sqlite, and not the db
from the host system.

Someone already facing this problem and know how to proceed?

Markus

On Mon, 5 Aug 2024 13:26:42 -0000 (UTC) Markus Robert Kessler wrote:

Forgot to mention:

Luckily, I made a whole-backup from the machine before I (stupidely)
started the "update".

So, I could throw down everything and restore from backup. What I don`t
really want to. Or:

if there is a way to create the RPM list out of the whole-backup tgz
file?
I have everything on /dev/sda1 as archive file.

Maybe someone known how to "extract" the RPM list out of /var, /usr or
somewhere else?

Would appreciate to hear. Thanks!

Best regards,

Markus






On Mon, 5 Aug 2024 11:20:29 -0000 (UTC) Markus Robert Kessler wrote:

Hi all,

please check and save what packages you have installed BEFORE
performing the current "update"!

I "updated", and now when setting the graphics system under load, the
box completely crashes. Tested on two machines with same HW and SW /
OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile
GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16
CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024
14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST
pulseaudio-module-zeroconf-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-jack-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST
pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:15 CEST pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST net-snmp-mibs-5.9.3-2.1.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST
lib64osmesa8-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:15
CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST
pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14
CEST pulseaudio-client-config-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:14 CEST pipewire-0.3.85-5.mga9.x86_64 So 04
Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:14 CEST lib64camera0.2-0.2.0-1.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST
lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:13
CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:11 CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:11 CEST vim-common-9.1.411-1.1.mga9.x86_64 So 04 Aug
2024 14:43:10 CEST lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64
So 04 Aug 2024 14:43:09 CEST lib64pulsecore16.1-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:09 CEST
lib64pulsecommon16.1-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:09
CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did
not occur (!). -- Hence, there has been some component installed, see
above, that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a
"no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Hello Vince!

Well, first I have to add a word to what I wrote:
Even loading the previous kernel did not permanently prevent the OS from crashing. It's clear, that there's something heavily messed up with the graphics drivers.

I doubt that Mageia's packagers have something to do with it. It rather
looks like "upstream" once more released untested stuff.

What made me nervous is, that I need these machines for working for my employer. So, it must not, never ever, happen, that a crash occures during
an important video conference etc.

So, I knew I have to roll back to the status before the "update".

As I wrote before, I had a version of /var/lib/rpm in a backup directly
before the "update" and I was able to reproduce the rpm -qa --last list.

So I compared the previous one with the newest, and so I got one list with rpms to "rpm --nodeps -e", and one list with "rpm --nodeps -i".

The pool of rpms to install can be easily downloaded automatically. This afternoon I wrote a script therefore,

https://www.dipl-ing-kessler.de/tmp/rpmdl.sh

It is trivial and can be modified, of course. I was glad to have it!

After all, lessons learned:

- always have / make a backup of your rpm list or directory, see above, at least before any "update"

- always mistrust must-have updates. Better wait some days and watch if someone shouts for help

- if you have more than one machine, then never update all of them at the
same time. Update one, then wait. See above

The latter item was my mistake...

Well, everything on all my machines works again perfectly, now.

I am not angry, I learned a lot!

Best regards,

Markus




On Mon, 05 Aug 2024 18:26:44 +0100 Vincent Coen wrote:

Hello Markus!

Monday August 05 2024 12:20, Markus Robert Kessler wrote to All:

Interesting - I have been getting occasional crash for a month or so and
just 'assumed' it was my kit.

May be similar reason as I use 6.6.37 for at least 14 days (since last
reboot any way).

In which case I will keep the previous 6.6.28 - JIC.

Vince

Hi all,

please check and save what packages you have installed BEFORE
performing the current "update"!

I "updated", and now when setting the graphics system under load, the
box completely crashes. Tested on two machines with same HW and SW /
OS.

CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz, GPU: Intel Mobile
GM965/GL960.

I got the following packages updated yesterday:

######################################################################

lib64xatracker2-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:16
CEST gnupg2-2.3.8-1.2.mga9.x86_64 So 04 Aug 2024
14:43:16 CEST xfce4-weather-plugin-0.11.2-1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST vim-minimal-9.1.411-1.1.mga9.x86_64 So
04 Aug 2024 14:43:15 CEST vim-enhanced-9.1.411-1.1.mga9.x86_64 So 04
Aug 2024 14:43:15 CEST pulseaudio-module-zeroconf-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:15 CEST
pulseaudio-module-jack-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-gsettings-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15
CEST pulseaudio-module-bluetooth-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:15 CEST net-snmp-mibs-5.9.3-2.1.mga9.x86_64 So 04 Aug
2024 14:43:15 CEST lib64pulseglib20-16.1-17.mga9.x86_64 So
04 Aug 2024 14:43:15 CEST lib64osmesa8-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST lib64net-snmp40-5.9.3-2.1.mga9.x86_64 So
04 Aug 2024 14:43:15 CEST lib64mesaegl1-24.1.4-2.mga9.tainted.x86_64
So 04 Aug 2024 14:43:15 CEST pulseaudio-utils-16.1-17.mga9.x86_64
So 04 Aug 2024 14:43:14 CEST pulseaudio-module-x11-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14
CEST pulseaudio-client-config-16.1-17.mga9.x86_64 So 04 Aug 2024
14:43:14 CEST pulseaudio-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14
CEST pipewire-0.3.85-5.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64pulseaudio0-16.1-17.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64pipewire0.3_0-0.3.85-5.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64mesagl1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:14
CEST lib64gbm1-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:14
CEST lib64camera0.2-0.2.0-1.mga9.x86_64 So 04 Aug 2024 14:43:14 CEST lib64dri-drivers-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024 14:43:13
CEST mesa-24.1.4-2.mga9.tainted.x86_64 So 04 Aug 2024
14:43:11 CEST lib64mesavulkan-drivers-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:11 CEST vim-common-9.1.411-1.1.mga9.x86_64
So 04 Aug 2024 14:43:10 CEST lib64webrtc-audio-processing1_3-1.3-1.mga9.x86_64 So 04 Aug 2024
14:43:09 CEST lib64pulsecore16.1-16.1-17.mga9.x86_64 So 04 Aug
2024 14:43:09 CEST lib64pulsecommon16.1-16.1-17.mga9.x86_64 So
04 Aug 2024 14:43:09 CEST lib64glapi0-24.1.4-2.mga9.tainted.x86_64 So
04 Aug 2024 14:43:09 CEST

######################################################################

This shows that there was no kernel update now.
Newest default kernel is kernel-desktop-6.6.37-1.mga9

So, the crashes seem to be caused by other reason.

Nevertheless, I now booted the former kernel 6.6.28 and the crash did
not occur (!). -- Hence, there has been some component installed, see above, that does not fit to the current kernel.

I need the box for daily work. So, the risk of crashes is just a
"no-go".

Any idea, how to roll back to the former state?
At least suspicious components like graphics drivers.

Best regards,

Markus

Vincent

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2024-08-05 15:34, Markus Robert Kessler wrote:

Hello Vince!

Well, first I have to add a word to what I wrote:
Even loading the previous kernel did not permanently prevent the OS from crashing. It's clear, that there's something heavily messed up with the graphics drivers.

I doubt that Mageia's packagers have something to do with it. It rather
looks like "upstream" once more released untested stuff.

What made me nervous is, that I need these machines for working for my employer. So, it must not, never ever, happen, that a crash occures during
an important video conference etc.

So, I knew I have to roll back to the status before the "update".

As I wrote before, I had a version of /var/lib/rpm in a backup directly before the "update" and I was able to reproduce the rpm -qa --last list.

So I compared the previous one with the newest, and so I got one list with rpms to "rpm --nodeps -e", and one list with "rpm --nodeps -i".

The pool of rpms to install can be easily downloaded automatically. This afternoon I wrote a script therefore,

https://www.dipl-ing-kessler.de/tmp/rpmdl.sh

It is trivial and can be modified, of course. I was glad to have it!

After all, lessons learned:

- always have / make a backup of your rpm list or directory, see above, at least before any "update"

- always mistrust must-have updates. Better wait some days and watch if someone shouts for help

- if you have more than one machine, then never update all of them at the same time. Update one, then wait. See above

The latter item was my mistake...

Well, everything on all my machines works again perfectly, now.

I am not angry, I learned a lot!

I'm glad you got things worked out. However, you should be aware that
when you start using the "nodeps" option, you venture into territory
that is not tested by QA.

It is impossible for us to test every possible combination of hardware
and software that could exist. So you may be on your own.

BTW, there is a new kernel coming, very soon. Should be within a couple
of days...

TJ

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 6 Aug 2024 10:38:27 -0400 TJ wrote:

On 2024-08-05 15:34, Markus Robert Kessler wrote:

Hello Vince!

Well, first I have to add a word to what I wrote:
Even loading the previous kernel did not permanently prevent the OS
from crashing. It's clear, that there's something heavily messed up
with the graphics drivers.

I doubt that Mageia's packagers have something to do with it. It rather
looks like "upstream" once more released untested stuff.

What made me nervous is, that I need these machines for working for my
employer. So, it must not, never ever, happen, that a crash occures
during an important video conference etc.

So, I knew I have to roll back to the status before the "update".

As I wrote before, I had a version of /var/lib/rpm in a backup directly
before the "update" and I was able to reproduce the rpm -qa --last
list.

So I compared the previous one with the newest, and so I got one list
with rpms to "rpm --nodeps -e", and one list with "rpm --nodeps -i".

The pool of rpms to install can be easily downloaded automatically.
This afternoon I wrote a script therefore,

https://www.dipl-ing-kessler.de/tmp/rpmdl.sh

It is trivial and can be modified, of course. I was glad to have it!

After all, lessons learned:

- always have / make a backup of your rpm list or directory, see above,
at least before any "update"

- always mistrust must-have updates. Better wait some days and watch if
someone shouts for help

- if you have more than one machine, then never update all of them at
the same time. Update one, then wait. See above

The latter item was my mistake...

Well, everything on all my machines works again perfectly, now.

I am not angry, I learned a lot!

I'm glad you got things worked out. However, you should be aware that
when you start using the "nodeps" option, you venture into territory
that is not tested by QA.

It is impossible for us to test every possible combination of hardware
and software that could exist. So you may be on your own.

BTW, there is a new kernel coming, very soon. Should be within a couple
of days...

TJ

Hi!

Thanks for commenting. Well, it was not my intention to test "fancy" combinations. I just needed to find a way back to my formerly working OS.

This was the reason for rebuilding everything exactly according to the
former rpm-list, when the system worked reliably.

Can you recommend a tool (builtin or external) which can be used to fall
back to a certain timestamp / backup point?

In Windows(TM) there is such a feature to fall back to the time, let's
say, two "updates" before. Would be nice to have such here too.

Best regards,

Markus

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)