Slackwarearm -current updates batch Wed Apr 29 2015 reports

drmozes · 05-20-2015, 03:19 AM

Quote:

Originally Posted by Linux.tar.gz

Slackware-14.1 with or without fbturbo : Xorg.bin at 0% cpu usage when idle, fluid.

How can I debug the 20% cpu usage on -current ?

Have you tried strace?

I have swapped out the fbdev package with fbturbo. I contemplated keeping the two packages but since fbturbo lists itself as a drop-in replacement (although that's not quite true since the driver name is different which requires a change to the X11 config) it doesn't really make sense.

Linux.tar.gz · 05-24-2015, 06:38 AM

I was using Xfce.
CPU usage is normal with Blackbox.

I'm not a strace pro, I did on Xorg.bin's PID :
strace -p1691 -s1024 > pid.strace 2>&1

I see tons of clock_gettime(CLOCK_MONOTONIC, {476, 813932998}) = 0

Linux.tar.gz · 05-24-2015, 12:14 PM

Ok, found out.
Xfce display compositor is enabled by default and eat some CPU.

Patch :
sed -i -e "s/use_compositing=true/use_compositing=false" /usr/share/xfwm4/defaults

drmozes · 05-25-2015, 03:12 AM

Quote:

Originally Posted by Linux.tar.gz

Ok, found out.
Xfce display compositor is enabled by default and eat some CPU.

Patch :
sed -i -e "s/use_compositing=true/use_compositing=false" /usr/share/xfwm4/defaults

What hardware are you using to test on? I was going to load up XFCE on my OpenRD client until I discovered that the frame buffer isn't working any more (something new to hack on for a few hours!).

Linux.tar.gz · 05-25-2015, 12:42 PM

IGEPv5 OMAP5432.

lems · 05-27-2015, 11:31 AM

Hello,

is there a reason I'm seeing messages like these:

Code:

[...]
ldconfig: libraries libnss_nis-2.17.so and libnss_nis-2.21.so in directory /lib have same soname but different type.
ldconfig: libraries libcidn-2.17.so and libcidn-2.21.so in directory /lib have same soname but different type.
[...]

when running ldconfig after upgrading from 14.1 to current on my Raspberry Pi, while I don't see this on my desktop (x86_64) or laptop (x86)? What is the preferred way to get rid of this? Deleting those old .so's? I did upgrade aaa_elflibs first, then glibc-solibs, followed by everything else. I understand this is a harmless but rather annoying message.

drmozes · 05-27-2015, 03:18 PM

Quote:

Originally Posted by lems

Hello,

is there a reason I'm seeing messages like these:

Code:

[...]
ldconfig: libraries libnss_nis-2.17.so and libnss_nis-2.21.so in directory /lib have same soname but different type.
ldconfig: libraries libcidn-2.17.so and libcidn-2.21.so in directory /lib have same soname but different type.
[...]

when running ldconfig after upgrading from 14.1 to current on my Raspberry Pi, while I don't see this on my desktop (x86_64) or laptop (x86)? What is the preferred way to get rid of this? Deleting those old .so's? I did upgrade aaa_elflibs first, then glibc-solibs, followed by everything else. I understand this is a harmless but rather annoying message.

It's because the libraries for glibc are placed in to a staging directory, lib/incoming which isn't tracked by pkgtools. The only way to clean it up is manually - so yes, delete them: if you've upgraded everything then those libraries from the glibc-2.17 will be superfluous to requirements.

lems · 05-28-2015, 01:12 AM

Quote:

Originally Posted by drmozes

It's because the libraries for glibc are placed in to a staging directory, lib/incoming which isn't tracked by pkgtools. The only way to clean it up is manually - so yes, delete them: if you've upgraded everything then those libraries from the glibc-2.17 will be superfluous to requirements.

Thank you for the explanation, Stuart. I've moved the .so's in question to another location for now and the messages are gone.