Comment # 4 on bug 1204607 from
Request 1:

Since I have the old rpm, I diffed the outputs for brevity.

Old version:
# zypper -q se -sx irqbalance.x86_64

S  | Name       | Type    | Version   | Arch   | Repository
---+------------+---------+-----------+--------+----------------------
i+ | irqbalance | package | 1.9.1-1.1 | x86_64 | (System Packages)
v  | irqbalance | package | 1.9.1-2.1 | x86_64 | Main Repository (OSS)

# irqbalance -d --foreground > irqbalance.old

New version:
# zypper -q se -sx irqbalance.x86_64

S  | Name       | Type    | Version   | Arch   | Repository
---+------------+---------+-----------+--------+----------------------
i+ | irqbalance | package | 1.9.1-2.1 | x86_64 | Main Repository (OSS)

# irqbalance -d --foreground > irqbalance.new

Differences:
# diff -s irqbalance.old irqbalance.new

2a3
> Prevent irq assignment to these thermal-banned CPUs: 00000000
94a96
> thermal: received group id (3).

The first message looks reasonable for a CPU that doesn't support thermald, I'm
not sure about the second message.  However, the message in the journal is
confusing.  

Oct 24 08:35:16 Mobile-PC /usr/sbin/irqbalance[3546]: thermal: socket bind
failed.

It sounds like something went wrong, when in fact, the action was normal for a
non-Intel CPU.

Request 2:
Results of gdb backtrace for the irqbalance coredump:

# coredumpctl -1 debug
           PID: 943 (irqbalance)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Mon 2022-10-24 08:49:03 PDT (1h 33min ago)
  Command Line: /usr/sbin/irqbalance --foreground
    Executable: /usr/sbin/irqbalance
 Control Group: /system.slice/irqbalance.service
          Unit: irqbalance.service
         Slice: system.slice
       Boot ID: 1fe3c0c81e464baab607f078ceddadd1
    Machine ID: 67007840ea464a92b139e093c5491dfd
      Hostname: Mobile-PC
       Storage:
/var/lib/systemd/coredump/core.irqbalance.0.1fe3c0c81e464baab607f078ceddadd1.943.1666626543000000.zst
(present)
     Disk Size: 58.6K
       Message: Process 943 (irqbalance) of user 0 dumped core.
#0  0x00007f9d49c3980c in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f9d49af2780 (LWP 943))]
Missing separate debuginfos, use: zypper install
irqbalance-debuginfo-1.9.1-2.1.x86_64

...

(gdb) bt
#0  0x00007f9d49c3980c in __pthread_kill_implementation () from
/lib64/libc.so.6
#1  0x00007f9d49be6846 in raise () from /lib64/libc.so.6
#2  0x00007f9d49bcf81c in abort () from /lib64/libc.so.6
#3  0x00007f9d49c2c9ae in __libc_message () from /lib64/libc.so.6
#4  0x00007f9d49c4414c in malloc_printerr () from /lib64/libc.so.6
#5  0x00007f9d49c46626 in _int_free () from /lib64/libc.so.6
#6  0x00007f9d49c48b13 in free () from /lib64/libc.so.6
#7  0x0000564f3cfa6f41 in ?? ()
#8  0x00007f9d49bd05b0 in __libc_start_call_main () from /lib64/libc.so.6
#9  0x00007f9d49bd0679 in __libc_start_main_impl () from /lib64/libc.so.6
#10 0x0000564f3cfa81a5 in ?? ()
(gdb)


You are receiving this mail because: