You are not logged in.

#1 2023-09-10 16:27:32

Zoom8160
Member
Registered: 2023-09-10
Posts: 4

thermald fails to start after system update

I updated my Arch Linux system today, restarted it and I saw that on the booting logs thermald.service was unable to start. These are the logs of the service:

sep 10 12:43:50 hum systemd[1]: Starting Thermal Daemon Service...
sep 10 12:43:50 hum thermald[4046]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:50 hum thermald[4046]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:50 hum thermald[4046]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:50 hum thermald[4046]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:50 hum thermald[4046]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:50 hum thermald[4046]: *** stack smashing detected ***: terminated
sep 10 12:43:50 hum systemd[1]: Started Thermal Daemon Service.
sep 10 12:43:50 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:50 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:51 hum systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
sep 10 12:43:51 hum systemd[1]: Starting Thermal Daemon Service...
sep 10 12:43:51 hum systemd[1]: Started Thermal Daemon Service.
sep 10 12:43:51 hum thermald[4495]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:51 hum thermald[4495]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:51 hum thermald[4495]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4495]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4495]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4495]: *** stack smashing detected ***: terminated
sep 10 12:43:51 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:51 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:51 hum systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
sep 10 12:43:51 hum systemd[1]: Starting Thermal Daemon Service...
sep 10 12:43:51 hum systemd[1]: Started Thermal Daemon Service.
sep 10 12:43:51 hum thermald[4729]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:51 hum thermald[4729]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:51 hum thermald[4729]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4729]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4729]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:51 hum thermald[4729]: *** stack smashing detected ***: terminated
sep 10 12:43:52 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:52 hum thermald[4756]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:52 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:52 hum thermald[4756]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:52 hum systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
sep 10 12:43:52 hum systemd[1]: Starting Thermal Daemon Service...
sep 10 12:43:52 hum thermald[4756]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum systemd[1]: Started Thermal Daemon Service.
sep 10 12:43:52 hum thermald[4756]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum thermald[4756]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum thermald[4756]: *** stack smashing detected ***: terminated
sep 10 12:43:52 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:52 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:52 hum systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
sep 10 12:43:52 hum systemd[1]: Starting Thermal Daemon Service...
sep 10 12:43:52 hum systemd[1]: Started Thermal Daemon Service.
sep 10 12:43:52 hum thermald[4779]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:52 hum thermald[4779]: 22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9)
sep 10 12:43:52 hum thermald[4779]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum thermald[4779]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum thermald[4779]: sensor id 12 : No temp sysfs for reading raw temp
sep 10 12:43:52 hum thermald[4779]: *** stack smashing detected ***: terminated
sep 10 12:43:53 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:53 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:53 hum systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
sep 10 12:43:53 hum systemd[1]: thermald.service: Start request repeated too quickly.
sep 10 12:43:53 hum systemd[1]: thermald.service: Failed with result 'core-dump'.
sep 10 12:43:53 hum systemd[1]: Failed to start Thermal Daemon Service.

El Psy Congroo

Offline

#2 2023-09-10 19:32:34

seth
Member
Registered: 2012-09-03
Posts: 52,262

Re: thermald fails to start after system update

sep 10 12:43:53 hum systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
sep 10 12:43:53 hum systemd[1]: thermald.service: Failed with result 'core-dump'

https://wiki.archlinux.org/title/Core_d … _core_dump

Offline

#3 2023-09-10 21:34:04

Zoom8160
Member
Registered: 2023-09-10
Posts: 4

Re: thermald fails to start after system update

I followed the "Analyzing a core dump" and "Debugging/Getting traces" guides and all I could get was "Signal: 6 (ABRT)", some lines that mentioned "/usr/lib/libc.so.6" and an empty gdb.txt file. I think I did everything right, is there something I'm missing?

Last edited by Zoom8160 (2023-09-10 21:35:44)


El Psy Congroo

Offline

#4 2023-09-10 21:43:03

seth
Member
Registered: 2012-09-03
Posts: 52,262

Re: thermald fails to start after system update

No idea, because you're not actually saying what you did.
What's the output of "coredumpctl list"? And what exactly did you do with it?

The stack might be corrupted to the point where it's indeed unusable, but that's hard to say from some generic "I followed generic wiki instructions" assertion.

Offline

#5 2023-09-10 22:52:50

Zoom8160
Member
Registered: 2023-09-10
Posts: 4

Re: thermald fails to start after system update

Sorry about that, here's the output of "sudo coredumpctl list":

TIME                          PID UID GID SIG     COREFILE EXE                 SIZE
Sun 2023-09-10 12:43:50 -03  4046   0   0 SIGABRT present  /usr/bin/thermald 231.6K
Sun 2023-09-10 12:43:51 -03  4495   0   0 SIGABRT present  /usr/bin/thermald 231.7K
Sun 2023-09-10 12:43:52 -03  4729   0   0 SIGABRT present  /usr/bin/thermald 231.3K
Sun 2023-09-10 12:43:52 -03  4756   0   0 SIGABRT present  /usr/bin/thermald 231.3K
Sun 2023-09-10 12:43:53 -03  4779   0   0 SIGABRT present  /usr/bin/thermald 231.6K
Sun 2023-09-10 12:54:40 -03  6195   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 12:54:40 -03  6207   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 12:54:40 -03  6218   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 12:54:41 -03  6230   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 12:54:41 -03  6241   0   0 SIGABRT present  /usr/bin/thermald 231.4K
Sun 2023-09-10 13:32:13 -03  2375   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 13:32:14 -03  2868   0   0 SIGABRT present  /usr/bin/thermald 231.9K
Sun 2023-09-10 13:32:15 -03  3023   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 13:32:15 -03  3148   0   0 SIGABRT present  /usr/bin/thermald 231.4K
Sun 2023-09-10 13:32:16 -03  3159   0   0 SIGABRT present  /usr/bin/thermald 231.9K
Sun 2023-09-10 17:09:16 -03  2299   0   0 SIGABRT present  /usr/bin/thermald 231.3K
Sun 2023-09-10 17:09:17 -03  2845   0   0 SIGABRT present  /usr/bin/thermald 231.7K
Sun 2023-09-10 17:09:17 -03  2943   0   0 SIGABRT present  /usr/bin/thermald 231.8K
Sun 2023-09-10 17:09:18 -03  2968   0   0 SIGABRT present  /usr/bin/thermald 231.7K
Sun 2023-09-10 17:09:18 -03  2985   0   0 SIGABRT present  /usr/bin/thermald 231.4K
Sun 2023-09-10 18:12:39 -03 11707   0   0 SIGABRT none     /usr/bin/thermald      -
Sun 2023-09-10 18:20:52 -03  2932   0   0 SIGABRT present  /usr/bin/thermald 231.5K
Sun 2023-09-10 18:20:53 -03  3520   0   0 SIGABRT present  /usr/bin/thermald 231.6K
Sun 2023-09-10 18:20:53 -03  3545   0   0 SIGABRT present  /usr/bin/thermald 231.8K
Sun 2023-09-10 18:20:54 -03  3556   0   0 SIGABRT present  /usr/bin/thermald 232.0K
Sun 2023-09-10 18:20:54 -03  3570   0   0 SIGABRT present  /usr/bin/thermald 232.2K
Sun 2023-09-10 18:25:11 -03  4589   0   0 SIGABRT none     /usr/bin/thermald      -

I didn't do anything with this really. Then I executed "sudo coredumpctl info /usr/bin/thermald":

PID: 4046 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2023-09-10 12:43:50 -03 (6h ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: idk if I should share this
    Machine ID: idk if I should share this
      Hostname: hum
       Storage: /var/lib/systemd/coredump/core.thermald.idk if I should share this.zst (present)
  Size on Disk: 231.6K
       Message: Process 4046 (thermald) of user 0 dumped core.
                
                Stack trace of thread 4046:
                #0  idk if I should share this n/a (libc.so.6 + idk if I should share this)
                #1  idk if I should share this raise (libc.so.6 + idk if I should share this)
                #2  idk if I should share this abort (libc.so.6 + idk if I should share this)
                #3  idk if I should share this n/a (libc.so.6 + idk if I should share this)
                #4  idk if I should share this __fortify_fail (libc.so.6 + idk if I should share this)
                #5  idk if I should share this __stack_chk_fail (libc.so.6 + idk if I should share this)
                #6  idk if I should share this _ZN13cthd_acpi_rel9read_psvtEv (thermald + idk if I should share this)
                #7  idk if I should share this n/a (n/a + idk if I should share this)
                ELF object binary architecture: AMD x86-64

Sorry about the "idk if I should share this", but I really don't know if it's safe to share that data (I'm a noob sorry).

Then I did "sudo coredumpctl debug /usr/bin/thermald" and on gdb I did "bt" which gives similar "0x000..." data, which I don't know if I should sare again, sorry.

Then I followed the "Debugging/Getting traces" guide, executing the command "gdb /usr/bin/thermald", which enabled "Debuginfod":

GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/thermald...

This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.archlinux.org>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from /home/hum/.cache/debuginfod_client/idk if I should share this/debuginfo...                                                                                     
(gdb) q

After that I did "sudo gdb /usr/bin/thermald" which shows:

GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/thermald...
(No debugging symbols found in /usr/bin/thermald)
(gdb) 

Then I did "run" with no arguments:

(gdb) run
Starting program: /usr/bin/thermald 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ready to serve requests: Daemonizing.. 1
[Detaching after fork from child process 8013]
[Inferior 1 (process 8010) exited normally]
(gdb) 

Now the guide says "Now do whatever is necessary to evoke the bug", but I don't know what to do to evoke the bug since I think it already crashed, so I do "set logging enabled on":

(gdb) set logging enabled on
Copying output to gdb.txt.
Copying debug output to gdb.txt.
(gdb) 

And "thread apply all backtrace full":

(gdb) thread apply all backtrace full
(gdb) 

Which gives me a "gdb.txt" file that is empty.

Last edited by Zoom8160 (2023-09-10 22:55:39)


El Psy Congroo

Offline

#6 2023-09-10 23:18:34

espritlibre
Member
Registered: 2022-12-15
Posts: 129

Re: thermald fails to start after system update

Now the guide says "Now do whatever is necessary to evoke the bug", but I don't know what to do to evoke the bug since I think it already crashed, so I do "set logging enabled on":

trigger the thermald crash with:

sudo systemctl restart thermald.service

Offline

#7 2023-09-11 01:49:30

Zoom8160
Member
Registered: 2023-09-10
Posts: 4

Re: thermald fails to start after system update

I did what you said both on a different terminal:

sudo gdb /usr/bin/thermald
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/thermald...
(No debugging symbols found in /usr/bin/thermald)
(gdb) run
Starting program: /usr/bin/thermald 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ready to serve requests: Daemonizing.. 1
[Detaching after fork from child process 9319]
[Inferior 1 (process 9316) exited normally] 

On the other terminal:

sudo systemctl restart thermald.service

Back to the first terminal:

(gdb) set logging enabled on
Copying output to gdb.txt.
Copying debug output to gdb.txt.
(gdb) thread apply all backtrace full
(gdb) 

And on the same one:

sudo gdb /usr/bin/thermald
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/thermald...
(No debugging symbols found in /usr/bin/thermald)
(gdb) run
Starting program: /usr/bin/thermald 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ready to serve requests: Daemonizing.. 1
[Detaching after fork from child process 9319]
[Inferior 1 (process 9316) exited normally]
(gdb) q
$ sudo systemctl restart thermald.service
$ sudo gdb
(gdb) set logging enabled on
Copying output to gdb.txt.
Copying debug output to gdb.txt.
(gdb) thread apply all backtrace full
(gdb) 

And I still got an empty "gdb.txt" file on both cases, did I do something wrong?


El Psy Congroo

Offline

#8 2023-09-11 06:02:37

seth
Member
Registered: 2012-09-03
Posts: 52,262

Re: thermald fails to start after system update

The "Stack trace of thread 4046:" stuff is the relevant part, please also look into the other dumps (at least a handful) to see whether they all go down in the same position and you can and should share all of that - those are stack positions, coredumps are kinda meant to be shared and - generally - don't contain sensitive information.
And, frankly, what kind of sensitive information do you expect thermald might hold itfp?

Offline

#9 2023-09-13 08:45:09

olivierguillon
Member
Registered: 2019-03-11
Posts: 6

Re: thermald fails to start after system update

Hello
Same problem here since kernel update (linux 6.5.2). Loading thermald.service fails systematically.
here is the output of `sudo coredumpctl info /usr/bin/thermald`:

           PID: 438 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2023-09-13 09:48:21 CEST (38min ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: 854f6e597ac74c0792a40d9cc9184f39
    Machine ID: 73e76549fa5245cda4488f1b00f705b3
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.thermald.0.854f6e597ac74c0792a40d9cc9184f39.438.1694591301000000.zst (present)
  Size on Disk: 231.9K
       Message: Process 438 (thermald) of user 0 dumped core.

                Stack trace of thread 438:
                #0  0x00007ff22f88e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007ff22f83e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007ff22f8264b8 abort (libc.so.6 + 0x264b8)
                #3  0x00007ff22f827390 n/a (libc.so.6 + 0x27390)
                #4  0x00007ff22f91f17b __fortify_fail (libc.so.6 + 0x11f17b)
                #5  0x00007ff22f920486 __stack_chk_fail (libc.so.6 + 0x120486)
                #6  0x000055d83c44ee55 _ZN13cthd_acpi_rel9read_psvtEv (thermald + 0x48e55)
                #7  0x0000000000010000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

           PID: 510 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2023-09-13 09:48:22 CEST (38min ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: 854f6e597ac74c0792a40d9cc9184f39
    Machine ID: 73e76549fa5245cda4488f1b00f705b3
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.thermald.0.854f6e597ac74c0792a40d9cc9184f39.510.1694591302000000.zst (present)
  Size on Disk: 232.1K
       Message: Process 510 (thermald) of user 0 dumped core.

                Stack trace of thread 510:
                #0  0x00007fc76a68e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007fc76a63e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007fc76a6264b8 abort (libc.so.6 + 0x264b8)
                #3  0x00007fc76a627390 n/a (libc.so.6 + 0x27390)
                #4  0x00007fc76a71f17b __fortify_fail (libc.so.6 + 0x11f17b)
                #5  0x00007fc76a720486 __stack_chk_fail (libc.so.6 + 0x120486)
                #6  0x00005591c8ac6e55 _ZN13cthd_acpi_rel9read_psvtEv (thermald + 0x48e55)
                #7  0x0000000000010000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

           PID: 527 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2023-09-13 09:48:23 CEST (38min ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: 854f6e597ac74c0792a40d9cc9184f39
    Machine ID: 73e76549fa5245cda4488f1b00f705b3
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.thermald.0.854f6e597ac74c0792a40d9cc9184f39.527.1694591303000000.zst (present)
  Size on Disk: 232.1K
       Message: Process 527 (thermald) of user 0 dumped core.

                Stack trace of thread 527:
                #0  0x00007f64a5e8e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007f64a5e3e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007f64a5e264b8 abort (libc.so.6 + 0x264b8)
                #3  0x00007f64a5e27390 n/a (libc.so.6 + 0x27390)
                #4  0x00007f64a5f1f17b __fortify_fail (libc.so.6 + 0x11f17b)
                #5  0x00007f64a5f20486 __stack_chk_fail (libc.so.6 + 0x120486)
                #6  0x0000559dc30d1e55 _ZN13cthd_acpi_rel9read_psvtEv (thermald + 0x48e55)
                #7  0x0000000000010000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

           PID: 543 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2023-09-13 09:48:23 CEST (38min ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: 854f6e597ac74c0792a40d9cc9184f39
    Machine ID: 73e76549fa5245cda4488f1b00f705b3
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.thermald.0.854f6e597ac74c0792a40d9cc9184f39.543.1694591303000000.zst (present)
  Size on Disk: 231.9K
       Message: Process 543 (thermald) of user 0 dumped core.

                Stack trace of thread 543:
                #0  0x00007f89fd28e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007f89fd23e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007f89fd2264b8 abort (libc.so.6 + 0x264b8)
                #3  0x00007f89fd227390 n/a (libc.so.6 + 0x27390)
                #4  0x00007f89fd31f17b __fortify_fail (libc.so.6 + 0x11f17b)
                #5  0x00007f89fd320486 __stack_chk_fail (libc.so.6 + 0x120486)
                #6  0x0000559e9ef41e55 _ZN13cthd_acpi_rel9read_psvtEv (thermald + 0x48e55)
                #7  0x0000000000010000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

           PID: 554 (thermald)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2023-09-13 09:48:24 CEST (38min ago)
  Command Line: /usr/bin/thermald --systemd --dbus-enable --adaptive
    Executable: /usr/bin/thermald
 Control Group: /system.slice/thermald.service
          Unit: thermald.service
         Slice: system.slice
       Boot ID: 854f6e597ac74c0792a40d9cc9184f39
    Machine ID: 73e76549fa5245cda4488f1b00f705b3
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.thermald.0.854f6e597ac74c0792a40d9cc9184f39.554.1694591304000000.zst (present)
  Size on Disk: 232.1K
       Message: Process 554 (thermald) of user 0 dumped core.

                Stack trace of thread 554:
                #0  0x00007fc18a48e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007fc18a43e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007fc18a4264b8 abort (libc.so.6 + 0x264b8)
                #3  0x00007fc18a427390 n/a (libc.so.6 + 0x27390)
                #4  0x00007fc18a51f17b __fortify_fail (libc.so.6 + 0x11f17b)
                #5  0x00007fc18a520486 __stack_chk_fail (libc.so.6 + 0x120486)
                #6  0x000055ad55c05e55 _ZN13cthd_acpi_rel9read_psvtEv (thermald + 0x48e55)
                #7  0x0000000000010000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

I'm at work and don't have time to investigate any longer for now.
I switched to linux-lts and thermald works fine again.

Last edited by olivierguillon (2023-09-13 08:53:25)

Offline

#10 2023-09-13 09:52:40

seth
Member
Registered: 2012-09-03
Posts: 52,262

Re: thermald fails to start after system update

https://github.com/intel/thermal_daemon/issues
Looks like a stack corruption, the general vicinity has previously shown up in https://github.com/intel/thermal_daemon/issues/193
Stracing it might reveal the input file that triggers this.

Offline

#11 2023-09-13 22:40:32

olivierguillon
Member
Registered: 2019-03-11
Posts: 6

Re: thermald fails to start after system update

Hi
As a workaround I ran `# dptfxtract`, which seems to solve the problem for me (... maybe missing config files in /etc/thermald/ ?? ). Now thermald service starts on boot without issue on linux 6.5.3.
Just got the idea reading through the intel/thermal_daemon github page, particularly issue #211.

Offline

Board footer

Powered by FluxBB