You are not logged in.
ever since massive update this morning, kde ksysguard failed miserably.
here's the journalctl
Feb 12 14:02:28 ARCHHOME krunner[628]: Reusing existing ksycoca
Feb 12 14:02:28 ARCHHOME krunner[628]: Recreating ksycoca file ("/home/boes/.cache/ksycoca5_en_nl59BFuBDu32TCGAFnIxrF_yxAY=", version 303)
Feb 12 14:02:28 ARCHHOME krunner[628]: Waiting for already running kbuildsycoca5 to finish.
Feb 12 14:02:28 ARCHHOME krunner[628]: Still in the time dict (i.e. deleted files) ("apps")
Feb 12 14:02:28 ARCHHOME krunner[628]: Menu "applications-kmenuedit.menu" not found.
Feb 12 14:02:28 ARCHHOME krunner[628]: Saving
Feb 12 14:02:30 ARCHHOME plasmashell[629]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:44:32: Unable to assign [undefined] to int
Feb 12 14:02:30 ARCHHOME systemd-coredump[32142]: Process 32140 (ksysguardd) of user 1000 dumped core.
Stack trace of thread 32140:
#0 0x00007f37a104404f raise (libc.so.6)
#1 0x00007f37a104547a abort (libc.so.6)
#2 0x00007f37a1081c50 __libc_message (libc.so.6)
#3 0x00007f37a1087fe6 malloc_printerr (libc.so.6)
#4 0x00007f37a10887de _int_free (libc.so.6)
#5 0x00007f37a1077c92 fclose@@GLIBC_2.2.5 (libc.so.6)
#6 0x0000000000416365 n/a (ksysguardd)
#7 0x0000000000417c7a n/a (ksysguardd)
#8 0x00000000004027c9 n/a (ksysguardd)
#9 0x00007f37a1031291 __libc_start_main (libc.so.6)
#10 0x0000000000402efa _start (ksysguardd)
Feb 12 14:02:30 ARCHHOME ksysguard[32137]: libksysguard: SensorShellAgent: Warning, received text over stderr!
""
Feb 12 14:02:30 ARCHHOME ksysguard[32137]: libksysguard: Error received "The daemon program 'ksysguardd' failed." ( QProcess::ProcessError(Crashed) )
Feb 12 14:02:30 ARCHHOME ksysguard[32137]: libksysguard: daemon exited, exit status QProcess::ExitStatus(CrashExit)
and most of my monitoring widgets also failed
Feb 12 14:07:00 ARCHHOME plasmashell[629]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:68: ReferenceError: batteryLabel is not defined
Feb 12 14:07:02 ARCHHOME kwin_x11[627]: QXcbWindow: Unhandled client message: "_NET_SHOWING_DESKTOP"
Feb 12 14:07:02 ARCHHOME plasmashell[629]: Arrived mimeData () ("text/x-plasmoidservicename") at 581 , 633
Feb 12 14:07:02 ARCHHOME plasmashell[629]: adding "org.kde.plasma.systemmonitor.cpu"
Feb 12 14:07:03 ARCHHOME systemd-coredump[32477]: Process 32475 (ksysguardd) of user 1000 dumped core.
Stack trace of thread 32475:
#0 0x00007f728109404f raise (libc.so.6)
#1 0x00007f728109547a abort (libc.so.6)
#2 0x00007f72810d1c50 __libc_message (libc.so.6)
#3 0x00007f72810d7fe6 malloc_printerr (libc.so.6)
#4 0x00007f72810d87de _int_free (libc.so.6)
#5 0x00007f72810c7c92 fclose@@GLIBC_2.2.5 (libc.so.6)
#6 0x0000000000416365 n/a (ksysguardd)
#7 0x0000000000417c7a n/a (ksysguardd)
#8 0x00000000004027c9 n/a (ksysguardd)
#9 0x00007f7281081291 __libc_start_main (libc.so.6)
#10 0x0000000000402efa _start (ksysguardd)
Feb 12 14:07:03 ARCHHOME plasmashell[629]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/BusyOverlay.qml:29: TypeError: Cannot read property 'busy' of null
Feb 12 14:07:03 ARCHHOME plasmashell[629]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/AppletAppearance.qml:331: TypeError: Cannot read property 'busy' of null
Feb 12 14:07:03 ARCHHOME plasmashell[629]: libksysguard: SensorShellAgent: Warning, received text over stderr!
""
Feb 12 14:07:03 ARCHHOME plasmashell[629]: libksysguard: Error received "The daemon program 'ksysguardd' failed." ( QProcess::ProcessError(Crashed) )
Feb 12 14:07:03 ARCHHOME plasmashell[629]: libksysguard: daemon exited, exit status QProcess::ExitStatus(CrashExit)
Feb 12 14:07:03 ARCHHOME systemd-coredump[32485]: Process 32483 (ksysguardd) of user 1000 dumped core.
Stack trace of thread 32483:
#0 0x00007f9c24f8404f raise (libc.so.6)
#1 0x00007f9c24f8547a abort (libc.so.6)
#2 0x00007f9c24fc1c50 __libc_message (libc.so.6)
#3 0x00007f9c24fc7fe6 malloc_printerr (libc.so.6)
#4 0x00007f9c24fc87de _int_free (libc.so.6)
#5 0x00007f9c24fb7c92 fclose@@GLIBC_2.2.5 (libc.so.6)
#6 0x0000000000416365 n/a (ksysguardd)
#7 0x0000000000417c7a n/a (ksysguardd)
#8 0x00000000004027c9 n/a (ksysguardd)
#9 0x00007f9c24f71291 __libc_start_main (libc.so.6)
#10 0x0000000000402efa _start (ksysguardd)
Feb 12 14:07:09 ARCHHOME plasmashell[629]: Couldn't find node mouseover-arrow-up. Skipping rendering.
Feb 12 14:07:11 ARCHHOME kwin_x11[627]: QXcbWindow: Unhandled client message: "_NET_SHOWING_DESKTOP"
Feb 12 14:07:11 ARCHHOME kwin_x11[627]: QXcbWindow: Unhandled client message: "_NET_SHOWING_DESKTOP"
Feb 12 14:07:11 ARCHHOME plasmashell[629]: QXcbConnection: XCB error: 2 (BadValue), sequence: 13177, resource id: 35651585, major code: 142 (Unknown), minor code: 3
Feb 12 14:07:12 ARCHHOME plasmashell[629]: QXcbConnection: XCB error: 2 (BadValue), sequence: 13732, resource id: 54526017, major code: 142 (Unknown), minor code: 3
any idea?
Last edited by boes (2017-02-21 17:30:21)
Offline
massive update this morning
Some dated library/plugin, maybe from an AUR package (style plugin or so)?
Also ensure there're no pending updates. Did you force update anything?
Offline
no, i use pacman -Syu to update systems. no force update committed.
and i rarely install from aur.
Offline
Ok, just looked like "I accessed random memory" - since there're no debug symbols you might ltrace or strace ksysguardd to get more details on what's going on when it aborts.
Offline
here's the ltrace
[boes@ARCHHOME ~]$ ltrace ksysguard
kdemain(1, 0x7ffcb87a6f88, 0x7ffcb87a6f98, 864*** Error in `ksysguardd': double free or corruption (out): 0x00000000023f9ef0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x70c4b)[0x7f4b05009c4b]
/usr/lib/libc.so.6(+0x76fe6)[0x7f4b0500ffe6]
/usr/lib/libc.so.6(+0x777de)[0x7f4b050107de]
/usr/lib/libc.so.6(fclose+0x132)[0x7f4b04fffc92]
ksysguardd[0x416365]
ksysguardd[0x417c7a]
ksysguardd[0x4027c9]
/usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7f4b04fb9291]
ksysguardd(_start+0x2a)[0x402efa]
======= Memory map: ========
00400000-00422000 r-xp 00000000 08:13 13926551 /usr/bin/ksysguardd
00621000-00622000 r--p 00021000 08:13 13926551 /usr/bin/ksysguardd
00622000-00623000 rw-p 00022000 08:13 13926551 /usr/bin/ksysguardd
00623000-0063a000 rw-p 00000000 00:00 0
023bf000-02400000 rw-p 00000000 00:00 0 [heap]
7f4b00000000-7f4b00021000 rw-p 00000000 00:00 0
7f4b00021000-7f4b04000000 ---p 00000000 00:00 0
7f4b04a79000-7f4b04a8f000 r-xp 00000000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f4b04a8f000-7f4b04c8e000 ---p 00016000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f4b04c8e000-7f4b04c8f000 r--p 00015000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f4b04c8f000-7f4b04c90000 rw-p 00016000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f4b04c91000-7f4b04d94000 r-xp 00000000 08:13 13896928 /usr/lib/libm-2.24.so
7f4b04d94000-7f4b04f93000 ---p 00103000 08:13 13896928 /usr/lib/libm-2.24.so
7f4b04f93000-7f4b04f94000 r--p 00102000 08:13 13896928 /usr/lib/libm-2.24.so
7f4b04f94000-7f4b04f95000 rw-p 00103000 08:13 13896928 /usr/lib/libm-2.24.so
7f4b04f99000-7f4b0512e000 r-xp 00000000 08:13 13896870 /usr/lib/libc-2.24.so
7f4b0512e000-7f4b0532d000 ---p 00195000 08:13 13896870 /usr/lib/libc-2.24.so
7f4b0532d000-7f4b05331000 r--p 00194000 08:13 13896870 /usr/lib/libc-2.24.so
7f4b05331000-7f4b05333000 rw-p 00198000 08:13 13896870 /usr/lib/libc-2.24.so
7f4b05333000-7f4b05337000 rw-p 00000000 00:00 0
7f4b05339000-7f4b05347000 r-xp 00000000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f4b05347000-7f4b05546000 ---p 0000e000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f4b05546000-7f4b05547000 r--p 0000d000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f4b05547000-7f4b05548000 rw-p 0000e000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f4b05549000-7f4b0556c000 r-xp 00000000 08:13 13896869 /usr/lib/ld-2.24.so
7f4b0572f000-7f4b05731000 rw-p 00000000 00:00 0
7f4b0576a000-7f4b0576b000 rw-p 00000000 00:00 0
7f4b0576b000-7f4b0576c000 r--p 00022000 08:13 13896869 /usr/lib/ld-2.24.so
7f4b0576c000-7f4b0576d000 rw-p 00023000 08:13 13896869 /usr/lib/ld-2.24.so
7f4b0576d000-7f4b05770000 rw-p 00000000 00:00 0
7ffd30f05000-7ffd30f26000 rw-p 00000000 00:00 0 [stack]
7ffd30f49000-7ffd30f4b000 r--p 00000000 00:00 0 [vvar]
7ffd30f4b000-7ffd30f4d000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
<no return ...>
--- SIGCHLD (Child exited) ---
libksysguard: Error received "The daemon program 'ksysguardd' failed." ( QProcess::ProcessError(Crashed) )
libksysguard: daemon exited, exit status QProcess::ExitStatus(CrashExit)
*** Error in `ksysguardd': double free or corruption (out): 0x0000000000f77ef0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x70c4b)[0x7f11997e1c4b]
/usr/lib/libc.so.6(+0x76fe6)[0x7f11997e7fe6]
/usr/lib/libc.so.6(+0x777de)[0x7f11997e87de]
/usr/lib/libc.so.6(fclose+0x132)[0x7f11997d7c92]
ksysguardd[0x416365]
ksysguardd[0x417c7a]
ksysguardd[0x4027c9]
/usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7f1199791291]
ksysguardd(_start+0x2a)[0x402efa]
======= Memory map: ========
00400000-00422000 r-xp 00000000 08:13 13926551 /usr/bin/ksysguardd
00621000-00622000 r--p 00021000 08:13 13926551 /usr/bin/ksysguardd
00622000-00623000 rw-p 00022000 08:13 13926551 /usr/bin/ksysguardd
00623000-0063a000 rw-p 00000000 00:00 0
00f3d000-00f7e000 rw-p 00000000 00:00 0 [heap]
7f1194000000-7f1194021000 rw-p 00000000 00:00 0
7f1194021000-7f1198000000 ---p 00000000 00:00 0
7f1199251000-7f1199267000 r-xp 00000000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f1199267000-7f1199466000 ---p 00016000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f1199466000-7f1199467000 r--p 00015000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f1199467000-7f1199468000 rw-p 00016000 08:13 13897246 /usr/lib/libgcc_s.so.1
7f1199469000-7f119956c000 r-xp 00000000 08:13 13896928 /usr/lib/libm-2.24.so
7f119956c000-7f119976b000 ---p 00103000 08:13 13896928 /usr/lib/libm-2.24.so
7f119976b000-7f119976c000 r--p 00102000 08:13 13896928 /usr/lib/libm-2.24.so
7f119976c000-7f119976d000 rw-p 00103000 08:13 13896928 /usr/lib/libm-2.24.so
7f1199771000-7f1199906000 r-xp 00000000 08:13 13896870 /usr/lib/libc-2.24.so
7f1199906000-7f1199b05000 ---p 00195000 08:13 13896870 /usr/lib/libc-2.24.so
7f1199b05000-7f1199b09000 r--p 00194000 08:13 13896870 /usr/lib/libc-2.24.so
7f1199b09000-7f1199b0b000 rw-p 00198000 08:13 13896870 /usr/lib/libc-2.24.so
7f1199b0b000-7f1199b0f000 rw-p 00000000 00:00 0
7f1199b11000-7f1199b1f000 r-xp 00000000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f1199b1f000-7f1199d1e000 ---p 0000e000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f1199d1e000-7f1199d1f000 r--p 0000d000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f1199d1f000-7f1199d20000 rw-p 0000e000 08:13 13926505 /usr/lib/libsensors.so.4.4.0
7f1199d21000-7f1199d44000 r-xp 00000000 08:13 13896869 /usr/lib/ld-2.24.so
7f1199f05000-7f1199f09000 rw-p 00000000 00:00 0
7f1199f43000-7f1199f44000 r--p 00022000 08:13 13896869 /usr/lib/ld-2.24.so
7f1199f44000-7f1199f45000 rw-p 00023000 08:13 13896869 /usr/lib/ld-2.24.so
7f1199f45000-7f1199f47000 rw-p 00000000 00:00 0
7ffd8d8e7000-7ffd8d908000 rw-p 00000000 00:00 0 [stack]
7ffd8d941000-7ffd8d943000 r--p 00000000 00:00 0 [vvar]
7ffd8d943000-7ffd8d945000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
btw, ksysguard is running, but some functionalities not working: avg cpu usage, system load tab, etc.
Last edited by boes (2017-02-12 10:46:01)
Offline
ksysguard ./. ksysguardd ! - latter aborts, so please ltrace/strace that, not ksysguard.
Offline
oh my bad. ltrace ksysguardd produce 1mb of file https://drive.google.com/file/d/0B6RaWo … sp=sharing
Offline
This seems to abort on freeing the file handle for /proc/stat, but I don't understand why. The address looks ok though and is not freed twice either.
The previous handle address (stat is opened/closed twice, first time no troubles) is re-used twice (vstat and soem calloc), but doesn't seem to be the problem.
=> try to "valgrind ksysguardd"
Offline
i'm at work now, i'll use valgrind on my problematic pc after home.
thanks
Offline
and here's the valgrind output
[boes@ARCHHOME ~]$ valgrind ksysguardd
==1354== Memcheck, a memory error detector
==1354== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1354== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==1354== Command: ksysguardd
==1354==
ksysguardd 4
(c) 1999, 2000, 2001, 2002 Chris Schlaeger <cs@kde.org>
(c) 2001 Tobias Koenig <tokoe@kde.org>
(c) 2006-2008 Greg Martyn <greg.martyn@gmail.com>
This program is part of the KDE Project and licensed under
the GNU GPL version 2. See http://www.kde.org for details.
==1354== Invalid read of size 8
==1354== at 0x4150FE: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e18 is 24 bytes after a block of size 384 in arena "client"
==1354==
==1354== Invalid read of size 8
==1354== at 0x415102: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e28 is 24 bytes before a block of size 552 alloc'd
==1354== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x50AD5AC: __fopen_internal (in /usr/lib/libc-2.24.so)
==1354== by 0x4160AB: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid read of size 8
==1354== at 0x415109: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e20 is 32 bytes before a block of size 560 in arena "client"
==1354==
==1354== Invalid read of size 8
==1354== at 0x415110: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e30 is 16 bytes before a block of size 552 alloc'd
==1354== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x50AD5AC: __fopen_internal (in /usr/lib/libc-2.24.so)
==1354== by 0x4160AB: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid read of size 8
==1354== at 0x415117: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e38 is 8 bytes before a block of size 552 alloc'd
==1354== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x50AD5AC: __fopen_internal (in /usr/lib/libc-2.24.so)
==1354== by 0x4160AB: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 4
==1354== at 0x415171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e00 is 0 bytes after a block of size 384 alloc'd
==1354== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x417CAA: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 4
==1354== at 0x415197: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e08 is 8 bytes after a block of size 384 alloc'd
==1354== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x417CAA: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 4
==1354== at 0x4151BE: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e04 is 4 bytes after a block of size 384 alloc'd
==1354== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x417CAA: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 4
==1354== at 0x4151E5: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e0c is 12 bytes after a block of size 384 alloc'd
==1354== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x417CAA: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 4
==1354== at 0x415209: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e10 is 16 bytes after a block of size 384 alloc'd
==1354== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x417CAA: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
==1354== Invalid write of size 8
==1354== at 0x41522C: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e18 is 24 bytes after a block of size 384 in arena "client"
==1354==
==1354== Invalid write of size 8
==1354== at 0x415230: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354== Address 0x57c2e28 is 24 bytes before a block of size 552 alloc'd
==1354== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1354== by 0x50AD5AC: __fopen_internal (in /usr/lib/libc-2.24.so)
==1354== by 0x4160AB: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
==1354==
valgrind: m_mallocfree.c:303 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 448, hi = 1317.
This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata. If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away. Please try that before reporting this as a bug.
host stacktrace:
==1354== at 0x38085208: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x38085324: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x380854B1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x38092F44: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x3807E773: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x3807CFF3: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x3808124A: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x3807C36B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==1354== by 0x802D49778: ???
==1354== by 0x802BADF2F: ???
==1354== by 0x8020082CF: ???
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x8020082CF: ???
==1354== by 0x1BFF: ???
==1354== by 0x804BDCFFF: ???
==1354== by 0x802BADDBF: ???
==1354== by 0x141A5: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 1354)
==1354== at 0x415234: ??? (in /usr/bin/ksysguardd)
==1354== by 0x416171: ??? (in /usr/bin/ksysguardd)
==1354== by 0x417C79: ??? (in /usr/bin/ksysguardd)
==1354== by 0x4027C8: ??? (in /usr/bin/ksysguardd)
==1354== by 0x5066290: (below main) (in /usr/lib/libc-2.24.so)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
Offline
i tried downgrading the kernel, which also downgraded several dependencies from previous system update
linux (4.8.13-1 <- 4.9.8-1)
upgraded nvidia (375.26-1 <- 375.26-6)
upgraded virtualbox-host-modules-arch (5.1.12-1 <- 5.1.14-3)
ksysguard and monitoring widgets are working fine now, and no more error in journalctl.
perhaps the nvudia gpu driver problem?
Offline
Not necessarily, but supports my suspicion (sorry for being late) - it smells like there's an "unexpectedly" long entry in /proc/stat - compare the output for the broken and the working (or linux-lts) kernel.
Offline
here's the procstat for working kernel (4.8.13-1)
[boes@ARCHHOME ~]$ cat /proc/stat
cpu 49600 29 20009 941030 33934 0 626 0 0 0
cpu0 9628 2 3430 152381 7941 0 248 0 0 0
cpu1 7581 3 2603 159114 5112 0 56 0 0 0
cpu2 9417 2 3368 156243 5064 0 90 0 0 0
cpu3 7337 6 2569 159691 4801 0 59 0 0 0
cpu4 8854 5 4341 155668 5241 0 83 0 0 0
cpu5 6778 9 3694 157930 5772 0 86 0 0 0
intr 6159969 50 2 0 0 0 0 0 0 1 0 0 0 4 0 134 0 1614 506974 120491 52622 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 306 0 287826 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 9510010
btime 1487154362
processes 3757
procs_running 1
procs_blocked 0
softirq 2252506 345592 608851 2668 1027 52889 0 330287 456320 0 454872
i'll post the output for updated kernel a moment later, need to reboot
Last edited by boes (2017-02-15 10:58:36)
Offline
dude, u're right
the output is very different on cpu indexing, jumping from cpu0 directly to cpu3
i'm currently using amd fx-6100
[boes@ARCHHOME ~]$ uname -a
Linux ARCHHOME 4.9.8-1-ARCH #1 SMP PREEMPT Mon Feb 6 12:59:40 CET 2017 x86_64 GNU/Linux
[boes@ARCHHOME ~]$ cat /proc/stat
cpu 2388 3 1916 41568 20533 0 39 0 0 0
cpu0 453 0 476 5343 4789 0 16 0 0 0
cpu3 325 0 304 7276 3115 0 4 0 0 0
cpu4 387 0 241 7540 2916 0 6 0 0 0
cpu5 411 1 360 6872 3446 0 4 0 0 0
cpu6 376 0 201 7305 3197 0 1 0 0 0
cpu7 433 0 331 7229 3066 0 4 0 0 0
intr 231032 50 3 0 0 0 0 0 0 1 0 0 0 4 0 134 0 1677 13514 3856 18530 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 307 0 16590 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 346195
btime 1487156376
processes 904
procs_running 1
procs_blocked 0
softirq 133221 12453 43855 19 496 18837 0 2290 19298 0 35973
Last edited by boes (2017-02-15 11:08:43)
Offline
I'd call it a bug in libsensors that it (likely) writes into an array index based upon some external value, but why the heck does the kernel count the cpu nodes 0-3-4-... now?
Believing in an octacore?
Offline
some people have filed this bug on bugs.kde.org.
i will provide this information there.
Offline
this bug has been resolved at https://bugs.kde.org/show_bug.cgi?id=376537
Offline