Summary: | ksysguard gives wild values after a few minutes | ||
---|---|---|---|
Product: | [Unmaintained] ksysguard | Reporter: | stgallag |
Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | info, johnflux, Regnaron |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
An example of the ridiculous values
Same, but notice the sensor browser is empty A tar.gz of the strace and i/o tar.gz of requested SystemLoad and ProcessTable and ksysguardrc Another sample of the requested files 1-min-load of 2000 15-min-load of 60, temp 1500 degrees The sgrd file |
Description
stgallag
2008-06-24 19:31:15 UTC
Created attachment 25568 [details]
An example of the ridiculous values
Created attachment 25569 [details]
Same, but notice the sensor browser is empty
What's more, the disk fills on the lower-right oscillate between those values
and 0, 81, and 6 (respectively), on every refresh.
It's happened three times so far, but I have not done anything unique with them, just left them on. I'm a programmer, and I'd like to help, but I know Python, not C (yet). Is it possible that some list of sensors could be out of order, or an incorrect pointer of some kind? (Just a guess) I have not looked at stdout for the last three, but I started it in a shell so if it happens again I might catch what caused it. Thanks, I haven't seen this bug myself - I'm not sure what's happening. I'll have a look in the code. Created attachment 25972 [details]
A tar.gz of the strace and i/o
Okay, It happened again.
I monitored it input/output with another ksysguard and strace'd it (about 10
seconds or 5 refreshes).
I am not exactly sure if this is related, but I think I have a similar problem: Sometimes the sensors still report the correct value, but scale completely wrong. I uploaded a screenshot where the network load sensor just goes off and scales from -1.5TiB/s to 105MiB/s instead of scaling from 0 to maybe 10MiB/s at http://www.oliver-putz.de/bugreports/Bug164851NetworkLoad.png I speculate that the cause for your problem may have to do with the way Linux measures network usage. Linux counts the bytes that have been sent and received, but about every four gigabytes, the number overflows and returns to 0. So on the next interval, the code calculates a 4 gigabyte loss, making that negative spike. Now that's just speculation because I don't know how Ksysguard calculates it, but it's not uncommon. Could you attach your .kde/share/apps/ksysguard/ProcessTable.sgrd and .kde4/share/config/ksysguardrc files please? Opps, I mean ~/.kde4/share/apps/ksysguard/SystemLoad.sgrd please - thank you :) John, attach a SystemLoad.sgrd from a session where ksysguard is spitting out crazy numbers or is one from a session where everything is tracked right fine too? THe session where it goes crazy please I'm not sure if you need those files from me too, but I attached them anyway, while running a session that went wild. Created attachment 28211 [details]
tar.gz of requested SystemLoad and ProcessTable and ksysguardrc
Created attachment 28266 [details]
Another sample of the requested files
Here are my files after ksysguard went crazy. The package includes:
ksysguardrc
ProcessTable.sgrd
SystemLoad.sgrd
A screenshot of the crazy ksysguard session
I have this almost every time after ksysguard has been running for a while (sometimes after a few minutes, sometimes half an hour, never longer than an hour). I attach screenshots. Note how the same values are dosplayed inconsistently between different screens (on the second screenshot, the left and the right are identical exept for the update interval, so the left shows a longer timeseries). Note how the average load (1min) is 20000 in one screen, but a reasonable ~1 in another. The 15minute load is 60, and the temperature is 1500 degrees. Created attachment 28281 [details]
1-min-load of 2000
see the top right panel.
Created attachment 28282 [details]
15-min-load of 60, temp 1500 degrees
Note the bottom two panels (average load 15 mins, and temperature). Left and
right have exactly the same setting, only that the right panels have 5 pixels
per timestep, and the left ones 1 pixel per timestep (i.e. the right are
closeups of the left panels).
Also compare the second panel from the top with the other attachment. Both show the 1-min-load, here it is ok, in the other one it is badly wrong.
This is on a Fujitsu Amilo 1650G laptop with Fedora 9. The problem has been there since kde 4.0 back in April or May.
Created attachment 28283 [details]
The sgrd file
SVN commit 892692 by johnflux: Don't go crazy if told to reconfigure. This fixes some very old bugs BUG:99377 BUG:164851 BUG:176160 BUG:78138 M +3 -7 SensorAgent.cc WebSVN link: http://websvn.kde.org/?view=rev&revision=892692 |