34604 – System crash a while after lauching adb daemon, using kernel-desktop (or linus) 6.6.101-116, but not with 6.6.93 nor server flavour of any version.

Bug 34604 - System crash a while after lauching adb daemon, using kernel-desktop (or linus) 6.6.101-116, but not with 6.6.93 nor server flavour of any version.

Summary: System crash a while after lauching adb daemon, using kernel-desktop (or linu...

Status:	NEW

Alias:	None

Product:	Mageia
Classification:	Unclassified
Component:	RPM Packages (show other bugs)
Version:	9
Hardware:	x86_64 Linux

Priority:	Normal Severity: normal
Target Milestone:	---
Assignee:	Kernel and Drivers maintainers
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2025-09-01 18:57 CEST by Pascal Drabik
Modified:	2025-11-25 10:44 CET (History)
CC List:	5 users (show)

See Also:
Source RPM:	kernel-6.6.116-1.mga9
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pascal Drabik 2025-09-01 18:57:08 CEST

I have been using adb for a long time without problem.

I recently updated mageia on a desktop computer and immediately after I started to have issues while connecting to my phone (S22-Ultra) using adb shell for instance.

After some experiments, it looks that a crash will happen sooner or later just after having started the adb daemon for instance by entering the command adb devices. There is no need to connect my phone.

The system basically shuts down without any warning and starts a full reboot.

I do not think it is relevant, but for information I am using KDE.

I was not able to identify any relevant issue in syslog or messages files. 

I run the same version of the OS on a laptop on which I do not get this issue
On both computers (desktop and laptop) the system is up to date.

Result of the uname -a command:

pascal@Andromeda ~]$ uname -a
Linux Andromeda 6.6.101-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Aug  2 22:05:21 UTC 2025 x86_64 GNU/Linux

How reproducible: The issue is reproducible.

Steps to Reproduce:
1. Starts the adb daemon, for instance by running adb devices (even without a phon connected)
2. After some time, from few seconds to several minutes (possibly up to one hour) the system will crash and reboot.

If it can help, here is the content of a syslog file just before the crash:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Aug 28 10:48:51 Andromeda mgaapplet[10206]: trying distributions list from https://releases.mageia.org/api/b/x86_64?product=Default&version=9&mgaonline_version=3.33
Aug 28 10:48:52 Andromeda mgaapplet[10206]: Computing new updates...
Aug 28 10:48:52 Andromeda mgaapplet[10206]: running: mgaapplet-update-checker 
Aug 28 10:48:52 Andromeda mgaapplet-update-checker[51927]: ### Program is starting ###
Aug 28 10:48:52 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update --update
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: updating inactive backport media Core Backports, Nonfree Backports, Tainted Backports, Core 32bit Backports, Nonfree 32bit Backports, Tainted 32bit Backports, MLO_backport
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Core Backports
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Nonfree Backports
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Tainted Backports
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Core 32bit Backports
Aug 28 10:48:53 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Nonfree 32bit Backports
Aug 28 10:48:54 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update Tainted 32bit Backports
Aug 28 10:48:54 Andromeda mgaapplet-update-checker[51927]: running: /usr/bin/urpmi.update MLO_backport
Aug 28 10:48:55 Andromeda mgaapplet[10206]: Packages are up to date
Aug 28 10:50:01 Andromeda CROND[60082]: (root) CMD (/usr/share/sshd-monitor/sshd-restarter)
Aug 28 10:50:01 Andromeda CROND[60081]: (root) CMDEND (/usr/share/sshd-monitor/sshd-restarter)
Aug 28 10:50:41 Andromeda kernel: [  497.226845] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 28 10:52:40 Andromeda kernel: [  616.453167] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 28 10:54:33 Andromeda kernel: [  728.665337] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 28 10:55:01 Andromeda CROND[100251]: (root) CMD (/usr/share/sshd-monitor/sshd-restarter)
Aug 28 10:55:01 Andromeda CROND[100250]: (root) CMDEND (/usr/share/sshd-monitor/sshd-restarter)
Aug 28 10:56:24 Andromeda kernel: [  840.602820] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 28 10:56:36 Andromeda kernel: [  852.056360] usb 4-1.1: new SuperSpeed USB device number 3 using xhci_hcd
Aug 28 10:56:36 Andromeda kernel: [  852.072951] usb 4-1.1: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 5.04
Aug 28 10:56:36 Andromeda kernel: [  852.072954] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 28 10:56:36 Andromeda kernel: [  852.072955] usb 4-1.1: Product: SAMSUNG_Android
Aug 28 10:56:36 Andromeda kernel: [  852.072957] usb 4-1.1: Manufacturer: SAMSUNG
Aug 28 10:56:36 Andromeda kernel: [  852.072958] usb 4-1.1: SerialNumber: R3CT400H7SM
Aug 28 10:56:36 Andromeda kernel: [  852.142818] cdc_acm 4-1.1:1.1: ttyACM0: USB ACM device
Aug 28 10:56:36 Andromeda kernel: [  852.142838] usbcore: registered new interface driver cdc_acm
Aug 28 10:56:36 Andromeda kernel: [  852.142839] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Aug 28 10:56:36 Andromeda kernel: [  852.538899] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:a8:a7:95:66:c1:bc:08:00 SRC=192.168.1.171 DST=192.168.1.141 LEN=2506 TOS=0x00 PREC=0x00 TTL=64 ID=60028 PROTO=UDP SPT=3702 DPT=44325 LEN=2486 
Aug 28 10:56:39 Andromeda ModemManager[2142]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:08.0/0000:09:00.0/0000:0a:0c.0/0000:10:00.0/usb4/4-1/4-1.1': not supported by any plugin
Aug 28 10:56:41 Andromeda kernel: [  857.022790] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:a8:a7:95:66:c1:bc:08:00 SRC=192.168.1.171 DST=192.168.1.141 LEN=2506 TOS=0x00 PREC=0x00 TTL=64 ID=60422 PROTO=UDP SPT=3702 DPT=44325 LEN=2486 
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0Aug 28 10:59:54 Andromeda kernel: [    0.000000] Linux version 6.6.101-desktop-1.mga9 (iurt@ecosse.mageia.org) (gcc (Mageia 12.3.0-3.mga9) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Sat Aug  2 22:05:21 UTC 2025
Aug 28 10:59:54 Andromeda kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.6.101-desktop-1.mga9 root=UUID=8d8b7953-deed-43f8-90e4-f6151ce93f4c ro splash quiet noiswmd resume=UUID=a9ece2a9-5fd6-4634-bdf2-1b0d753ea48e audit=0 vga=798

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Comment 1 Lewis Smith 2025-09-03 20:27:11 CEST

Thank you for the report.

(In reply to Pascal Drabik from comment #0)
> I have been using adb for a long time without problem.
> I recently updated mageia on a desktop computer and immediately after I
> started to have issues while connecting to my phone (S22-Ultra) using adb
> shell for instance.
Are you able to say *when* (what date) you did the updates which started the problem?
If you can, this command will enable you to look at what packages were updated on that date (packages listed in reverse date order):
 $ rpm -qa --last | less
A kernel update is the most likely suspect, unless 'android-tools' itself was updated. Please have a look.
If it was 'android-tools', you can downgrade that.
If it was a kernel, you can try booting the previous one.

CC: (none) => lewyssmith

Comment 2 Pascal Drabik 2025-09-05 12:03:44 CEST

Dear Lewis,
Thank you very much for your reaction. Sorry for my late reply, being afraid of possible corruption of remotely mounted disks, I avoid these days to use my main desktop. But today, I have some time and I was able to investigate a bit more.

So, indeed the update that started the issue took place on August 28th. I do remember that just after the update I had to download pictures from my phone (more or less as usual) using adb. Unfortunately few seconds after I started the download, the system rebooted without any warning.
After some investigation, it seems that the system crshes just by starting the adb daemoon.

Using "rpm -qa --last" tells me that I updated the system on August 3rd (no problem), then August 28th (triggering the crash) and today September 5th, as you can see in the listing at the end of my message.

"android-tools" has not been updated. The entry in the listing on August 31st comes me trying to de-install and install again "android-tools".

The kernel seems to have been updated on August 28th:-(

After the latest update (today), it looks that I still have the issue while using adb.

So I understand that going back to a previous version of the kernel might provide a temporary solution. I would need some help to do it. 

But this means that I would be unable to update the system in the future, which does not look like a good idea. I would by far much prefer to solve the problem 

Is there a way for me to try to investigate better the origin of the problem?

In the mean time, I will have a closer look to the android-tools...

Here is the list of update since the beginning of August:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

vim-minimal-9.1.1552-1.mga9.x86_64            Fri 05 Sep 2025 10:58:00
vim-enhanced-9.1.1552-1.mga9.x86_64           Fri 05 Sep 2025 10:58:00
vim-common-9.1.1552-1.mga9.x86_64             Fri 05 Sep 2025 10:58:00
lib64gnutlsxx30-3.8.4-1.2.mga9.x86_64         Fri 05 Sep 2025 10:58:00
lib64gnutls-devel-3.8.4-1.2.mga9.x86_64       Fri 05 Sep 2025 10:58:00
lib64gnutls-dane0-3.8.4-1.2.mga9.x86_64       Fri 05 Sep 2025 10:58:00
lib64gnutls30-3.8.4-1.2.mga9.x86_64           Fri 05 Sep 2025 10:58:00
gnutls-3.8.4-1.2.mga9.x86_64                  Fri 05 Sep 2025 10:58:00
glibc-devel-2.36-57.mga9.x86_64               Fri 05 Sep 2025 10:57:49
glibc-2.36-57.mga9.x86_64                     Fri 05 Sep 2025 10:57:49

android-tools-34.0.0-5.mga9.x86_64            Sun 31 Aug 2025 17:37:54

wireless-regdb-20250710-1.mga9.noarch         Thu 28 Aug 2025 10:39:33
pdfarranger-1.12.1-1.mga9.noarch              Thu 28 Aug 2025 10:39:33
opencpn-radar-plugin-5.5.4-3.mga9.x86_64      Thu 28 Aug 2025 10:39:33
lib64bpf1-6.6.101-1.mga9.x86_64               Thu 28 Aug 2025 10:39:33
kernel-userspace-headers-6.6.101-1.mga9.x86_64 Thu 28 Aug 2025 10:39:33
kernel-desktop-latest-6.6.101-1.mga9.x86_64   Thu 28 Aug 2025 10:39:33
kernel-desktop-6.6.101-1.mga9.x86_64          Thu 28 Aug 2025 10:39:32
cpupower-6.6.101-1.mga9.x86_64                Thu 28 Aug 2025 10:39:32

poppler-23.02.0-1.7.mga9.x86_64               Sun 03 Aug 2025 10:47:27
mc-4.8.33-1.3.mga9.x86_64                     Sun 03 Aug 2025 10:47:27
lib64poppler-qt6_3-23.02.0-1.7.mga9.x86_64    Sun 03 Aug 2025 10:47:27
wxgtk3.2-3.2.8.1-1.mga9.x86_64                Sun 03 Aug 2025 10:47:26
sudo-1.9.15p5-1.1.mga9.x86_64                 Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_webview3.2_0-3.2.8.1-1.mga9.x86_64 Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_stc3.2_0-3.2.8.1-1.mga9.x86_64  Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_richtext3.2_0-3.2.8.1-1.mga9.x86_64 Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_qa3.2_0-3.2.8.1-1.mga9.x86_64   Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_html3.2_0-3.2.8.1-1.mga9.x86_64 Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_gl3.2_0-3.2.8.1-1.mga9.x86_64   Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_core3.2_0-3.2.8.1-1.mga9.x86_64 Sun 03 Aug 2025 10:47:26
lib64wx_gtk3u_aui3.2_0-3.2.8.1-1.mga9.x86_64  Sun 03 Aug 2025 10:47:26
lib64wx_baseu_xml3.2_0-3.2.8.1-1.mga9.x86_64  Sun 03 Aug 2025 10:47:26
lib64wx_baseu_net3.2_0-3.2.8.1-1.mga9.x86_64  Sun 03 Aug 2025 10:47:26
lib64wx_baseu3.2_0-3.2.8.1-1.mga9.x86_64      Sun 03 Aug 2025 10:47:26
lib64poppler-qt5_1-23.02.0-1.7.mga9.x86_64    Sun 03 Aug 2025 10:47:26
lib64poppler-glib8-23.02.0-1.7.mga9.x86_64    Sun 03 Aug 2025 10:47:26
lib64poppler-gir0.18-23.02.0-1.7.mga9.x86_64  Sun 03 Aug 2025 10:47:26
lib64kwinglutils14-5.27.10-1.2.mga9.x86_64    Sun 03 Aug 2025 10:47:26
lib64kwineffects14-5.27.10-1.2.mga9.x86_64    Sun 03 Aug 2025 10:47:26
lib64kwin5-5.27.10-1.2.mga9.x86_64            Sun 03 Aug 2025 10:47:26
lib64kcmkwincommon5-5.27.10-1.2.mga9.x86_64   Sun 03 Aug 2025 10:47:26
lib64glib2.0-devel-2.76.3-1.5.mga9.x86_64     Sun 03 Aug 2025 10:47:26
kwin-common-5.27.10-1.2.mga9.x86_64           Sun 03 Aug 2025 10:47:26
kwin-5.27.10-1.2.mga9.x86_64                  Sun 03 Aug 2025 10:47:26
glib-gettextize-2.76.3-1.5.mga9.x86_64        Sun 03 Aug 2025 10:47:26
glib2.0-common-2.76.3-1.5.mga9.x86_64         Sun 03 Aug 2025 10:47:26
lha-1.14i-20230328.1.mga9.x86_64              Sun 03 Aug 2025 10:47:16
ldetect-lst-0.6.61-1.mga9.x86_64              Sun 03 Aug 2025 10:47:16
virtualbox-guest-additions-7.1.10-1.mga9.x86_64 Sun 03 Aug 2025 10:47:15
qtbase6-common-6.4.1-5.2.mga9.x86_64          Sun 03 Aug 2025 10:47:15
qtbase5-common-5.15.7-6.2.mga9.x86_64         Sun 03 Aug 2025 10:47:15
python3-s3transfer-0.6.0-1.mga9.noarch        Sun 03 Aug 2025 10:47:15
python3-jmespath-1.0.1-1.mga9.noarch          Sun 03 Aug 2025 10:47:15
python3-botocore-1.29.157-1.mga9.noarch       Sun 03 Aug 2025 10:47:15
python3-boto3-1.26.157-1.mga9.noarch          Sun 03 Aug 2025 10:47:15
mesa-demos-9.0.0-1.mga9.x86_64                Sun 03 Aug 2025 10:47:15
libdecor-0.2.3-1.mga9.x86_64                  Sun 03 Aug 2025 10:47:15
lib64qt6xml6-6.4.1-5.2.mga9.x86_64            Sun 03 Aug 2025 10:47:15
lib64qt6xcbqpa6-6.4.1-5.2.mga9.x86_64         Sun 03 Aug 2025 10:47:15
lib64qt6widgets6-6.4.1-5.2.mga9.x86_64        Sun 03 Aug 2025 10:47:15
lib64qt6test6-6.4.1-5.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt6sql6-6.4.1-5.2.mga9.x86_64            Sun 03 Aug 2025 10:47:15
lib64qt6printsupport6-6.4.1-5.2.mga9.x86_64   Sun 03 Aug 2025 10:47:15
lib64qt6openglwidgets6-6.4.1-5.2.mga9.x86_64  Sun 03 Aug 2025 10:47:15
lib64qt6opengl6-6.4.1-5.2.mga9.x86_64         Sun 03 Aug 2025 10:47:15
lib64qt6network6-6.4.1-5.2.mga9.x86_64        Sun 03 Aug 2025 10:47:15
lib64qt6gui6-6.4.1-5.2.mga9.x86_64            Sun 03 Aug 2025 10:47:15
lib64qt6eglfskmssupport6-6.4.1-5.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt6eglfskmsgbmsupport6-6.4.1-5.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt6eglfsdeviceintegration6-6.4.1-5.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt6dbus6-6.4.1-5.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt6-database-plugin-sqlite-6.4.1-5.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt6-database-plugin-ibase-6.4.1-5.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt6core6-6.4.1-5.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt6concurrent6-6.4.1-5.2.mga9.x86_64     Sun 03 Aug 2025 10:47:15
lib64qt5xml5-5.15.7-6.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt5xcbqpa5-5.15.7-6.2.mga9.x86_64        Sun 03 Aug 2025 10:47:15
lib64qt5widgets5-5.15.7-6.2.mga9.x86_64       Sun 03 Aug 2025 10:47:15
lib64qt5test5-5.15.7-6.2.mga9.x86_64          Sun 03 Aug 2025 10:47:15
lib64qt5sql5-5.15.7-6.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt5printsupport5-5.15.7-6.2.mga9.x86_64  Sun 03 Aug 2025 10:47:15
lib64qt5opengl5-5.15.7-6.2.mga9.x86_64        Sun 03 Aug 2025 10:47:15
lib64qt5network5-5.15.7-6.2.mga9.x86_64       Sun 03 Aug 2025 10:47:15
lib64qt5gui5-5.15.7-6.2.mga9.x86_64           Sun 03 Aug 2025 10:47:15
lib64qt5eglfskmssupport5-5.15.7-6.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt5eglfsdeviceintegration5-5.15.7-6.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt5dbus5-5.15.7-6.2.mga9.x86_64          Sun 03 Aug 2025 10:47:15
lib64qt5-database-plugin-sqlite-5.15.7-6.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt5-database-plugin-mysql-5.15.7-6.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt5-database-plugin-ibase-5.15.7-6.2.mga9.x86_64 Sun 03 Aug 2025 10:47:15
lib64qt5core5-5.15.7-6.2.mga9.x86_64          Sun 03 Aug 2025 10:47:15
lib64qt5concurrent5-5.15.7-6.2.mga9.x86_64    Sun 03 Aug 2025 10:47:15
lib64poppler-cpp0-23.02.0-1.7.mga9.x86_64     Sun 03 Aug 2025 10:47:15
lib64poppler126-23.02.0-1.7.mga9.x86_64       Sun 03 Aug 2025 10:47:15
lib64glib2.0_0-2.76.3-1.5.mga9.x86_64         Sun 03 Aug 2025 10:47:15
lib64gio2.0_0-2.76.3-1.5.mga9.x86_64          Sun 03 Aug 2025 10:47:15
lib64djvulibre21-3.5.29-1.mga9.x86_64         Sun 03 Aug 2025 10:47:15
lib64decor0-0.2.3-1.mga9.x86_64               Sun 03 Aug 2025 10:47:15
glxinfo-9.0.0-1.mga9.x86_64                   Sun 03 Aug 2025 10:47:15
eglinfo-9.0.0-1.mga9.x86_64                   Sun 03 Aug 2025 10:47:15

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Comment 3 Morgan Leijström 2025-09-05 17:59:32 CEST

Thank you for reporting.
This is probably hard to track down.

You might have luck with the backport kernel
https://wiki.mageia.org/en/Kernel_flavours#Backport_kernels

For some it works better, while a few have problems with it.

---

For just picture/file access you probably know already there are other ways
https://wiki.mageia.org/en/File_transfer_with_Android_devices

CC: (none) => fri

Comment 4 Pascal Drabik 2025-09-05 18:32:38 CEST

No luck so far...

If it can help, the same version of the kernel and of anfroid-tools does not generate reboot on my laptop.

I removed a PCI card that generates some errors according syslog. But this had no effect (more or less expected).

I looked more carefully at the time of the crash (I used a script recording the time every second in a file). So, just before the crash, there is no indication in syslog.

So, I will try to go backward, using I guess the previous kernel (version 6.6.93, I think) which did work well for me.

In the directory /boot, I currently have:

lrwxrwxrwx 1 root root       30 Aug 28 10:39 vmlinuz-desktop -> vmlinuz-6.6.101-desktop-1.mga9
lrwxrwxrwx 1 root root       30 Aug 28 10:39 vmlinuz ->         vmlinuz-6.6.101-desktop-1.mga9
lrwxrwxrwx 1 root root       33 Aug 28 10:39 initrd.img ->         initrd-6.6.101-desktop-1.mga9.img
lrwxrwxrwx 1 root root       33 Aug 28 10:39 initrd-desktop.img -> initrd-6.6.101-desktop-1.mga9.img

Could it be sufficient just to link the files 

   - initrd-6.6.93-desktop-1.mga9.img to  initrd.img and to initrd-desktop.img
and
   - vmlinuz-6.6.93-desktop-1.mga9 to vmlinuz and to vmlinuz-desktop

My current grub menu does not offer the possibility to choose other kernel.

I must say I am not really used to this kind of manipulation.

Even if I go back to a previous version of the kernel, how will I be able to install future updates?

Thanks in advance for any support.

Comment 5 Morgan Leijström 2025-09-05 19:19:56 CEST

There should always be at least an extra kernel to fall back to.
Our tool remove-old-kernels by default keep three latest installed kernels of each flavour used.
https://wiki.mageia.org/en/Mageia_9_Release_Notes#remove-old-kernels



It should be easy to select any installed kernel from the boot menu.

On the first showing boot menu
 (Example https://wiki.mageia.org/en/File:Grub2-sc1.png)
you should be able to select "Advanced options for Mageia",
and then select any of installed kernels.

(and for each able to select normal boot or boot to command line for manitenance.)

Does not that work for you, we will first help you to get that working.



What is the output from 

$ rpm -qa | grep ^kernel

Comment 6 Pascal Drabik 2025-09-06 09:07:32 CEST

Hi Morgan,

Thanks for your support and reaction. Actually thanks to Mageia for the great job it is doing:-)

Actually I forgot to look at advanced option... I will try it as soon as I can.

I did see 3 versions of vmlinuz in /boot (6.6.88, 6.693 and 6.6.101). But I failed to see them at the boot phase (grub menu). I have to look at the advance options...

The result of the rpm query for kernel is:

[pascal@Andromeda ~]$ rpm -qa | grep ^kernel
kernel-desktop-6.6.88-3.mga9
kernel-firmware-nonfree-20250509-1.mga9.nonfree
kernel-firmware-20250509-1.mga9
kernel-desktop-6.6.93-1.mga9
kernel-desktop-6.6.101-1.mga9
kernel-desktop-latest-6.6.101-1.mga9
kernel-userspace-headers-6.6.101-1.mga9

I will investigate further, but probably not before next Wednesday. I will keep you informed in any case.

Thanks again Mageia. Your work is exceptional.

Comment 7 Morgan Leijström 2025-09-06 10:30:33 CEST

Thank you Pascal :)
We are all volunteers, building Mageia.
You too, by testing and reporting like this.

You can probably conveniently choose any of the three installed kernels under boot menu advanced options.


Sidenote: Regarding connecting with phone (Android and derivative (I use Murena)), I find Syncthing to be fantastic for continuous sync, and KDEConnect for casual file access, as well as sharing text clips and other functions.  If you want to discuss that further do not use this bug, but use forum.

This bug is for tracking down why your system crash.

Comment 8 Pascal Drabik 2025-09-06 10:59:25 CEST

Hi Morgan,

I feel more lke a user than a tester;-) But anyway...

Ok, I did boot the system with the previous version of the kernel that I have (6.6.93) and it looks that the adb daemon can run without trouble.

I wish this can help you to possibly detect what could be the issue with the version 6.6.101.

I will keep you informed in case I discover something else.

And, indeed, I will have a look to Murena and use the forum.

Thanks again...

Comment 9 Morgan Leijström 2025-09-06 11:47:02 CEST

Glad it works for now to downgrade.

It may also be interesting to see if the linus flavour of 6.6.101 works, because the linus kernels are less patched by us.
To install, in package manager select kernel-linus-6.6.101

You could try if kernel-desktop-6.6.103 in testing works, Bug 34595.
For package manager to see it, enable vcore updates testing repository.
If -desktop-6.6.103 fail, try linus flavour of it.

Also test of the backport kernel as I mentioned and linked in comment 5, could be helpful.

Setting this to kernel maintainer for ideas what to check/test.
Giuseppe is currently taking a break.

---
For clarity previous comment: Murena is a de-googled Android OS. It use standard Android apps for Syncthing and KDEConnect.

Assignee: bugsquad => kernel
Source RPM: android-tools-34.0.0-5.mga9.src.rpm => kernel-6.6.101-1.mga9

Comment 10 Morgan Leijström 2025-09-06 11:58:16 CEST

Another bug: do you too see this problem with the displaying of this bug report, that the comments are so wide you need to scroll to see the long text lines?

Please comment there weather you see it or not, at:
Bug 34614 - Sometimes, comments section go very wide

Comment 11 Morgan Leijström 2025-09-06 12:01:37 CEST

Due to the system crash the bug severity may be set as critical or at least high, but this is the only report so far, and few people use adb, so I keep it as normal for now.

Summary: Crash of the system after lauching adb daemon; This happens since my very recent update of mageia. => System crash a while after lauching adb daemon, using kernel-desktop 6.6.101, but not with 6.6.93

Comment 12 Morgan Leijström 2025-09-07 15:56:50 CEST

Try 6.6.104, now building, instead of 6.6.103

Comment 13 Pascal Drabik 2025-09-10 16:56:34 CEST

Hi Morgan

I am now back to my desktop...

So, I tried to install kernel-linus-6.6.101. But I get an error in the process:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

1 installation transactions failed
There was a problem during the installation:
...retrieving failed: aria2 failed: exited with 3
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

I will try now to use 6..104...

Comment 14 Morgan Leijström 2025-09-10 19:35:55 CEST

(In reply to Pascal Drabik from comment #13)

> ...retrieving failed: aria2 failed: exited with 3

Probably transisent,
I read we had some problems with bots hammering the mirrors
 
> I will try now to use 6..104...

Please instead try 6.6.105, building right now - ready in a few hours.
Bug 34594 - Update request: kernel-6.6.105-1.mga9

Comment 15 Pascal Drabik 2025-09-11 09:20:33 CEST

(In reply to Morgan Leijström from comment #14)

> > ...retrieving failed: aria2 failed: exited with 3
> 
> Probably transisent,
> I read we had some problems with bots hammering the mirrors

   Perhaps I can try a bit later?

> > I will try now to use 6..104...
> 
> Please instead try 6.6.105, building right now - ready in a few hours.
> Bug 34594 - Update request: kernel-6.6.105-1.mga9

   For information I tried yesterday evening 6.6.104 and got the same crash. I did not notice anything interesting in syslog.

   I will try a bit later 6.6.105.

   I will also try to investgate adb itself, find if there is any option that could provide information.

   In any case, thanks a lot for your support.

Comment 16 Morgan Leijström 2025-09-11 11:08:45 CEST

Please also try the linus 6.6.105
(note linus optimally need cpupower and lib64bpf1 packages of same version from desktop/server kernel bug to be installed)

Summary: System crash a while after lauching adb daemon, using kernel-desktop 6.6.101, but not with 6.6.93 => System crash a while after lauching adb daemon, using kernel-desktop 6.6.101-105, but not with 6.6.93

Comment 17 i mek 2025-09-11 22:36:00 CEST

@Pascal Drabik

Do You experience the same problem with 6.12.x (available from core/backports_testing; nb. rok (remove-old-kernels) seems not to count these kernels yet)?

CC: (none) => imek5

Comment 18 Pascal Drabik 2025-09-12 10:33:50 CEST

(In reply to Morgan Leijström from comment #16)
> Please also try the linus 6.6.105
> (note linus optimally need cpupower and lib64bpf1 packages of same version
> from desktop/server kernel bug to be installed)

Hi,
Yesterday, I got some hope... The system has been running Kernel-linus_6.6.105 for more time than before. I also started adb via a remote connection, I naively thought that there was something new. But no. The system crashed again:-(

I also tried to get information from the adb server using "ADB_TRACE=all" with the hope that the server could dump something just before the crash. But no:-(

Comment 19 Pascal Drabik 2025-09-12 10:35:54 CEST

(In reply to i mek from comment #17)
> @Pascal Drabik
> 
> Do You experience the same problem with 6.12.x (available from
> core/backports_testing; nb. rok (remove-old-kernels) seems not to count
> these kernels yet)?

I did not know the existence of 6.12.x yet.

I will try it and give you the feedback.

Comment 20 Morgan Leijström 2025-09-12 11:21:20 CEST

> (In reply to i mek from comment #17)
> 6.12.x (available from core/backports_testing;
> nb. rok (remove-old-kernels) seems not to count these kernels yet)?

Please read https://wiki.mageia.org/en/Kernel_flavours#Backport_kernels
There, also a fix for rok is described.

Comment 21 Pascal Drabik 2025-09-12 13:43:43 CEST

(In reply to i mek from comment #17)
> @Pascal Drabik
> 
> Do You experience the same problem with 6.12.x (available from
> core/backports_testing; nb. rok (remove-old-kernels) seems not to count
> these kernels yet)?

Hi,
I did try 6.12.44. But I get the same issue:-(

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-bash-5.2$ uname -a
Linux Andromeda 6.12.44-desktop-1.stable.mga9 #1 SMP PREEMPT_DYNAMIC Thu Aug 28 21:34:30 UTC 2025 x86_64 GNU/Linux
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Comment 22 Pascal Drabik 2025-09-12 16:44:09 CEST

I had a look to previous syslog files and it might be that I got already a similar problem on August 13 using then kernel 6.6.93-desktop-1.mga9. There were activities involving my phone (perhaps via bluetooth) just before what looks like a crash.

But I cannot say for sure. Below, I insert an extract from the syslog file (I removed sensord messages...)

I will try to boot my desktop from an image on a USB drive using the 6.6.101 kernel and report what will be the result. If it works, that would mean perhaps a wrong configuration of my system.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Aug 13 17:29:00 Andromeda kernel: [891540.368529] usb 3-1.2: reset high-speed USB device number 3 using xhci_hcd
Aug 13 17:29:23 Andromeda dbus-daemon[41310]: [session uid=1000 pid=41310] Activating via systemd: service name='org.kde.kscreen.osdService' unit='plasma-kscreen-osd.service' requested by ':1.10' (uid=1000 pid=41393 comm="/usr/bin/kded5")
Aug 13 17:29:23 Andromeda dbus-daemon[41310]: [session uid=1000 pid=41310] Successfully activated service 'org.kde.kscreen.osdService'
Aug 13 17:29:23 Andromeda kernel: [891562.784136] [drm] REG_WAIT timeout 1us * 100000 tries - optc1_wait_for_state line:839
Aug 13 17:29:23 Andromeda kernel: [891562.943557] [drm] REG_WAIT timeout 1us * 100000 tries - optc1_wait_for_state line:839
Aug 13 17:29:23 Andromeda kernel: [891563.102991] [drm] REG_WAIT timeout 1us * 100000 tries - optc1_wait_for_state line:839
Aug 13 17:29:23 Andromeda kernel: [891563.149883] pcieport 0000:00:02.1: PME: Spurious native interrupt!
Aug 13 17:29:24 Andromeda kernel: [891563.615935] usb 3-1.2: reset high-speed USB device number 3 using xhci_hcd
Aug 13 17:29:51 Andromeda kernel: [891590.731200] Bluetooth: hci0: ACL packet for unknown connection handle 3837
Aug 13 17:29:51 Andromeda bluetoothd[1927]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 60:AB:D2:23:E5:96: Connection refused (111)
Aug 13 17:29:51 Andromeda kernel: [891591.043181] Bluetooth: hci0: ACL packet for unknown connection handle 3837
Aug 13 17:29:51 Andromeda bluetoothd[1927]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 60:AB:D2:23:E5:96: Connection refused (111)
Aug 13 17:29:51 Andromeda bluetoothd[1927]: src/service.c:btd_service_connect() a2dp-source profile connect failed for 60:AB:D2:23:E5:96: Device or resource busy
Aug 13 17:30:01 Andromeda CROND[3021526]: (root) CMD (/usr/share/sshd-monitor/sshd-restarter)
Aug 13 17:30:01 Andromeda CROND[3021525]: (root) CMDEND (/usr/share/sshd-monitor/sshd-restarter)
Aug 13 17:30:04 Andromeda kernel: [891603.448871] Bluetooth: hci0: ACL packet for unknown connection handle 3837
Aug 13 17:30:04 Andromeda bluetoothd[1927]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 60:AB:D2:23:E5:96: Connection refused (111)
Aug 13 17:30:04 Andromeda kernel: [891603.740866] Bluetooth: hci0: ACL packet for unknown connection handle 3837
Aug 13 17:30:04 Andromeda bluetoothd[1927]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 60:AB:D2:23:E5:96: Connection refused (111)
Aug 13 17:30:04 Andromeda bluetoothd[1927]: src/service.c:btd_service_connect() a2dp-source profile connect failed for 60:AB:D2:23:E5:96: Device or resource busy
Aug 13 17:30:47 Andromeda kernel: [891646.753074] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 13 17:32:35 Andromeda kernel: [891755.186594] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 13 17:34:28 Andromeda kernel: [891867.653175] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
Aug 13 17:35:01 Andromeda CROND[3022246]: (root) CMD (/usr/share/sshd-monitor/sshd-restarter)
Aug 13 17:35:01 Andromeda CROND[3022245]: (root) CMDEND (/usr/share/sshd-monitor/sshd-restarter)
.
.
.
Aug 13 17:36:13 Andromeda kernel: [891972.993492] input: Pascal's S22 Ultra (AVRCP) as /devices/virtual/input/input170
Aug 13 17:36:18 Andromeda kernel: [891977.534981] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=82 
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
Aug 13 17:44:20 Andromeda kernel: [    0.000000] Linux version 6.6.93-desktop-1.mga9 (iurt@ecosse.mageia.org) (gcc (Mageia 12.3.0-3.mga9) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Wed Jun  4 15:23:13 UTC 2025
Aug 13 17:44:20 Andromeda kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.6.93-desktop-1.mga9 root=UUID=8d8b7953-deed-43f8-90e4-f6151ce93f4c ro splash quiet noiswmd resume=UUID=a9ece2a9-5fd6-4634-bdf2-1b0d753ea48e audit=0 vga=798
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-provided physical RAM map:
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009afefff] usable
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x0000000009aff000-0x0000000009ffffff] reserved
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000000a210000-0x000000000affffff] usable
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000000b000000-0x000000000b020fff] reserved
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000000b021000-0x000000006fe7afff] usable
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x000000006fe7b000-0x0000000075e7afff] reserved
Aug 13 17:44:20 Andromeda kernel: [    0.000000] BIOS-e820: [mem 0x0000000075e7b000-0x000000007607dfff] ACPI data

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Comment 23 i mek 2025-09-12 20:27:30 CEST

I'm sorry, I was probably wrong saying (in comment #17)
> nb. rok (remove-old-kernels) seems not to count these kernels yet
In reality it seems to be the way described by Morgan Leijström in comment #5

> Our tool remove-old-kernels by default keep three latest installed kernels
> of each flavour used.
> https://wiki.mageia.org/en/Mageia_9_Release_Notes#remove-old-kernels

Comment 24 Giuseppe Ghibò 2025-09-14 22:17:12 CEST

According to comment #28, the issue seems started prior than 6.6.101.

Check also your USB cables.

Can you try whether disabling USB3.0 at boot, and rely only on USB2.0 the same issue occurs.

Maybe we could push also newer (35.0.2) android-tools, if current go stack would allow building without issues or missed deps.

CC: (none) => ghibomgx

Comment 25 PC LX 2025-09-15 00:19:36 CEST

I use adb practically every day, and connect by USB or TCP/IP to several phones without any issues.

I'm currently testing kernel 6.6.105-desktop-1.mga9, and also tested all the previous version (e.g. 104,103,101,93). None had problems with adb.

One way to get the last messages from the kernel/system is to connect to the system with a serial cable and setup a serial console. For that you will need a serial cable and two computer with serial ports (or an USB adapter). Another way, but less reliable, is to use a ssh.

Connect to the problematic system (either with a serial connection, or ssh), and run "dmesg --follow-new". This will show all kernel messages, and if the system doesn't just hard reboot, it may give some clues has to what the issue is.

CC: (none) => mageia

Comment 26 Pascal Drabik 2025-09-15 11:13:30 CEST

Dear All,
Thank you really a lot for your interest.
I am currently away from my desktop and I can not do much until next Thursday.

@Giuseppe Ghibò: I do not need to connect a Smartphone to get a system crash. It is sufficient to start the adb server (for instance by running the command adb devices or more "elegant" adb server) and wait a little bit, doing nothing in front of screen (I mean, I do not start any other specific application, except running a script that records the time every second, in order to get an idea of the time of the crash) and at some point the system will crash.

Just after the reboot I check the syslog file but see no clear information that could explain the crash.

I also started the adb server with the environment variable ADB_TRACE=all to get possible information from adb itself. But there is nothing abnormal.

Regarding the possible occurrence of this issue prior to 6.6.101 (i.e. 6.6.93), I am really not sure. But the adb server was running always and I was using it to download pictures from my phone. It is only when I moved to 6.6.101 that the issue appeared immediately and can be reproduced at will.

@PC LX: I do use still adb with my laptop, that is up to date, i.e. it runs the same current Mageia official 6.6.101-desktop kernel. And I have no problem. As far as I am concerned this is a backup solution, but not really convenient since my main computer is my desktop on which many scripts are running to periodically manage backups and photos processing.

Next Thursday, I will try to monitor the desktop through an ssh connection from my laptop using "dmesg --follow-new". But I am afraid this will not show much. I think the computer does indeed what you call a "hard reboot¨.

In any case, I will report by then.

I want also to test the desktop with a current official system (i.e. with 6.6.101-desktop) installed on a fresh installation on a USB stick. I did prepare the USB stick yesterday and will try it next Thursday.

With this test, I would like to see whether the current configuration of my desktop might have some problem. I can not remember the details, but I did a fresh Mageia installation many, many years ago and made the updates each time it was necessary. I could imagine that some configuration file might trigger some problem.

A possible alternative to investigate could be the hardware. So far I just checked removing a PCIe card (to bring more internal and external USB 3 ports) that was suspicious from the syslog files. But it did not solve the problem. Beside this board, I do not know how to check the other hardware parts.

Comment 27 Pascal Drabik 2025-10-15 13:28:52 CEST

Dear All,

Already one month went away... I would like to summarize the various tests I made in order to try to understand and hopefully to find a solution to my problem about the system crash when I start the ADB server.

So, I used the Mageia live version from a USB key, based on "6.4.6-desktop-4", updated to the status of Mageia one month ago.

While running this updated version live version, I tried the following kernels. I started the adb server and include the result of the test:

    1- 6.12.44-desktop-1.stable.mga9: Crash after 18 mn
    2- 6.6.105-server-1.mga9:         Still running after 19 hours
    3- 6.6.105-desktop-1.mga9:        Crash after 1 mn
    4- 6.6.105-1.mga9 (Linus):        Crash after 13 mn
    5- 6.6.88-desktop-2.mga9:         Still running after 20 hours

As you can see, it looks I got no trouble with "6.6.88-desktop-2.mga9" which was expected.

What might be interesting is that, while using "6.6.105", the system crashed with the "Linus" and "desktop" flavors, but seemed to work with the "server" flavor.

Could this result help someone to undertand the issue? What are the differences between "server" and "desktop" flavors? Keeping in mind that my system is a desktop and not really a server, would it matter if I switch the the server flavor? This might be a solution, but it would leav us without knowing the cause of the crash anyway, which I find a bit frustrating.

Following the advice from @PC LX, I did run the command "dmesg --follow-new" in an ssh shell from my laptop and got some more information just before the crash occurs:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

[207563.272259] net-fw DROP IN=enp13s0 OUT= MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0
000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=U
DP SPT=547 DPT=546 LEN=82 
[207587.740372] xhci_hcd 0000:14:00.3: Controller not ready at resume -19
[207587.740391] xhci_hcd 0000:14:00.3: PCI post-resume error -19!
[207587.740394] xhci_hcd 0000:14:00.3: HC died; cleaning up
client_loop: send disconnect: Broken pipe


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Could this new message help to track the cause of the crash?

Thanks in advance anyway for your comments, and perhaps a solution.

In the mean time, could I continue to update the system when I get the usual Mageia notification.

Best regards,

Pascal.

Comment 28 PC LX 2025-10-19 16:45:04 CEST

(In reply to Pascal Drabik from comment #27)
> Could this result help someone to undertand the issue? What are the
> differences between "server" and "desktop" flavors?

I think the main differences are the scheduler and power saving.

> Keeping in mind that my system is a desktop and not really a server,
> would it matter if I switch the the server flavor?

The server kernel will work for desktop usage but the GUI may feel less
responsive when under load, due to scheduler priorities.

> Following the advice from @PC LX, I did run the command "dmesg --follow-new"
> in an ssh shell from my laptop and got some more information just before the
> crash occurs:
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> [207563.272259] net-fw DROP IN=enp13s0 OUT=
> MAC=d8:5e:d3:e5:54:85:f0:4d:d4:14:2f:82:86:dd SRC=fe80:0000:0000:0
> 000:f24d:d4ff:fe14:2f82 DST=fe80:0000:0000:0000:da5e:d3ff:fee5:5485 LEN=122
> TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=U
> DP SPT=547 DPT=546 LEN=82 
> [207587.740372] xhci_hcd 0000:14:00.3: Controller not ready at resume -19
> [207587.740391] xhci_hcd 0000:14:00.3: PCI post-resume error -19!
> [207587.740394] xhci_hcd 0000:14:00.3: HC died; cleaning up
> client_loop: send disconnect: Broken pipe
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> Could this new message help to track the cause of the crash?

xhci_hcd is a USB kernel driver and after a quick search those errors may be
related to power saving features and auto suspend. To test this hypothesis I
suggest disabling USB auto suspend.

Boot in to a kernel that has issues then BEFORE using adb run the following
command as root:
"""
echo -1 > /sys/module/usbcore/parameters/autosuspend
"""

If this works, the permanently disable USB auto suspend by adding
"usbcore.autosuspend=-1" to the kernel boot options.

As root, edit the file /etc/default/grub and append "usbcore.autosuspend=-1" to the
variable GRUB_CMDLINE_LINUX. It should look something like this:
"""
GRUB_CMDLINE_LINUX="<KEEP WHATEVER WAS HERE> usbcore.autosuspend=-1".
"""

Hope this helps.

Comment 29 Pascal Drabik 2025-10-30 10:17:51 CET

   Hi PC_LX,

   Thanks again for your reaction.

> > Could this result help someone to undertand the issue? What are the
> > differences between "server" and "desktop" flavors?
> 
> I think the main differences are the scheduler and power saving.
> .
> .
> .
> The server kernel will work for desktop usage but the GUI may feel less
> responsive when under load, due to scheduler priorities.

   Thanks. I started yesterday the 6.6.105-server kernel, without the adb server. I do not think having detected real differences compared to the desktop flavor. Today I started the adb server with the hope it can bring informaton on the iissue.

> The server kernel will work for desktop usage but the GUI may feel less
> responsive when under load, due to scheduler priorities.
> 
> > Following the advice from @PC LX, I did run the command "dmesg --follow-new"
> > in an ssh shell from my laptop and got some more information just before the
> > crash occurs:
> .
> .
> .
> xhci_hcd is a USB kernel driver and after a quick search those errors may be
> related to power saving features and auto suspend. To test this hypothesis I
> suggest disabling USB auto suspend.
> 
> Boot in to a kernel that has issues then BEFORE using adb run the following
> command as root:
> """
> echo -1 > /sys/module/usbcore/parameters/autosuspend
> """

   I tried it using the 6.6.105-desktop kernel, the adb server not running, I wrote -1 to /sys/module/usbcore/parameters/autosuspend, I did check that the value was changed from the intial 2 to the suggested one -1 and then I started the adb server. Few minutes later the system crashed and rebooted.

   So, now I mainly expect that the adb server will not trigger a crash of the system while using the 6.6.105-server.

   If so, this will mean that some difference between the desktop and server flavors are responsible for the crash.

   I will keep you informed about the status after one full day of testing, or earlier if there is a problem, and then somewhere nexr week.

   Thanks anyway for your support about this strange case.

Comment 30 Lewis Smith 2025-10-31 21:50:34 CET

Thank you for your trials.

Comment 31 Morgan Leijström 2025-11-04 00:22:52 CET

New kernels in testing: 6.6.116-1

Comment 32 Pascal Drabik 2025-11-04 09:56:41 CET

Hi,

So 5 days after having started the adb server, using the 6.6.105-server kernel, my desktop is still running well.

A bit later today, I will try another step which is to connect my phone and to use it to transfer files between the desktop and the phone. 

I do not expect any problem. But, I need to test the real use I have for adb. And I have to admit I feel a bit anxious about it:-(

If things are going well, this would mean indeed that there are some differences between the desktop and server flavors of the 6.6.105 version that trigger the crash of the system while using the desktop flavor.

I will report the result of the test tomorrow.

@Morgan Leijström: Thanks for the information about the new version 6.6.106. I will investigate this new version after the test I plan to do later today, which means probably tomorrow afternoon. I will of course about the result.

Comment 33 Pascal Drabik 2025-11-05 15:59:08 CET

Hi,

As I said yesterday, I did test file transferring from my phone to my desktop using adb on 6.6.105-server, perhaps 100 GB. 

No problem. My system is still running:-)

This caonfirms that some differences between the server and desktop flavor on 6.6.105 trigger a crash and reboor of the desktop flavor.

I will now experient with 6.6.106-1...

Comment 34 Pascal Drabik 2025-11-06 09:49:16 CET

Hi,

I have used actually 6.6.116-desktop-1 (I did not find 6.6.106). I started the adb server and my desktop crashed after more or less one hour.

Later today, I will make some more tests, with the hope that at least 6.6.116-server-1 will be usable.

And of course I will report the result...

Comment 35 Morgan Leijström 2025-11-06 10:22:47 CET

Thank you for your continued testing!
Well I did write "116"... ;-)

@Giuseppe, any idea?

Comment 36 Pascal Drabik 2025-11-06 12:27:48 CET

(In reply to Morgan Leijström from comment #35)
> Thank you for your continued testing!
> Well I did write "116"... ;-)

   oupsss.... Sorry.

   My eyes are not as good as they have some time ago:-(

Comment 37 Pascal Drabik 2025-11-07 15:03:37 CET

Hi,

So, I tried again 6.6.116-desktop and few minutes after the start of the adb server, the system did crash and rebooted:-(

After that, I started with 6.6.116-server, I started adb server and the system is still running after almost 4 hours.

I think I can make the same conclusion as for 6.6.105. The desktop flavor generates quickly a crash and a reboot while the server flavor behaves correctly.

I am not sure whether it could help someone to understand the issue, but while making the tests, I was running the "top" command in a remote shell on my laptop.. Here is the "snapshot" before the crash (well the data are refreshed every 3 seconds if I understood correctly):

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

top - 11:04:09 up 12 min,  4 users,  load average: 0.86, 0.81, 0.49
Tasks: 374 total,   1 running, 373 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.1 sy,  0.0 ni, 99.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  31225.7 total,  27193.9 free,   2634.3 used,   1397.4 buff/cache
MiB Swap:  65535.0 total,  65535.0 free,      0.0 used.  28152.9 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    661 root      20   0       0      0      0 I   0.3   0.0   0:00.10 kworker/8:2-events_freezable_power_
  26636 pascal    20   0  243064   7936   7452 S   0.3   0.0   0:02.37 adb
  65925 pascal    20   0 1985304 193056 119996 S   0.3   0.6   0:00.54 kscreenlocker_g
  68736 pascal    20   0  183484   4284   3296 R   0.3   0.0   0:00.52 top
      1 root      20   0  175168  13868   8876 S   0.0   0.0   0:00.79 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.00 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_workqueue_release
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-rcu_g
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-slub_
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-netns
      9 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/0:0H-events_highpri
     11 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-mm_pe
     12 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_kthread
     13 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_rude_kthread
     14 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_trace_kthread
     15 root      20   0       0      0      0 S   0.0   0.0   0:00.00 ksoftirqd/0
     16 root      -2   0       0      0      0 I   0.0   0.0   0:00.16 rcu_preempt
     17 root      -2   0       0      0      0 S   0.0   0.0   0:00.00 rcub/0
     18 root      -2   0       0      0      0 S   0.0   0.0   0:00.00 rcu_exp_gp_kthread_worker
     19 root      -2   0       0      0      0 S   0.0   0.0   0:00.00 rcu_exp_par_gp_kthread_worker
     20 root      rt   0       0      0      0 S   0.0   0.0   0:00.00 migration/0
     21 root     -51   0       0      0      0 S   0.0   0.0   0:00.00 idle_inject/0
     22 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/0
     23 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/1
     24 root     -51   0       0      0      0 S   0.0   0.0   0:00.00 idle_inject/1
     25 root      rt   0       0      0      0 S   0.0   0.0   0:00.19 migration/1
     26 root      20   0       0      0      0 S   0.0   0.0   0:00.00 ksoftirqd/1
     

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Unfortunately, I will probably have no direct access to my desktop up to November 17th and won't be able to testing anything.

In the mean time I will go back to 6.6.105-server, since it looks quite reliable.

Thanks again for your patience and support.

Comment 38 Giuseppe Ghibò 2025-11-07 16:04:35 CET

(In reply to Morgan Leijström from comment #35)

> Thank you for your continued testing!
> Well I did write "116"... ;-)
> 
> @Giuseppe, any idea?

It was already reported failing also with kernel-linus, which is substantially vanilla and doesn't include any extra patchset, as well as with 6.12.x.

It could some hardware instability at higher tick rate or some bug in USB hardware or firmware. An alternative could be to try booting with an alternative clocksource like adding at boot "clocksource=hpet hpet=force".

Comment 39 Morgan Leijström 2025-11-07 17:01:25 CET

May be interesting to try backport kernel when we get a new 6.12 version there.

Source RPM: kernel-6.6.101-1.mga9 => kernel-6.6.116-1.mga9
Summary: System crash a while after lauching adb daemon, using kernel-desktop 6.6.101-105, but not with 6.6.93 => System crash a while after lauching adb daemon, using kernel-desktop (or linus) 6.6.101-116, but not with 6.6.93 nor server flavour of any version.

Comment 40 Pascal Drabik 2025-11-25 10:44:34 CET

(In reply to Giuseppe Ghibò from comment #38)
> (In reply to Morgan Leijström from comment #35)
> 
> > Thank you for your continued testing!
> > Well I did write "116"... ;-)
> > 
> > @Giuseppe, any idea?
> 
> It was already reported failing also with kernel-linus, which is
> substantially vanilla and doesn't include any extra patchset, as well as
> with 6.12.x.
> 
> It could some hardware instability at higher tick rate or some bug in USB
> hardware or firmware. An alternative could be to try booting with an
> alternative clocksource like adding at boot "clocksource=hpet hpet=force".

Hi, I am finally back to my desktop, but not for too long.

@Giuseppe: I will try a bit later today your suggestion. But, even if it works, it would not explain why the system started to crash immediately after the upgrade from 6.6.93-desktop to 6.6.101-desktop.

Now I do not dare much to use any "6.*.*-desktop" flavor. I currently use 6.6.105-server which does not crash while using adb. I had to move several GB of files across my filesystems and I do experiment slow reaction from my desktop.

Is this related to the server flavor of the kernel?

Note You need to log in before you can comment on or make changes to this bug.