Bug report
22 Oct 2010 0:40:41 UTC
Topic 195400
(moderation:
Screen grabs documenting the problem are at the url
http://www.giwersworld.org/EINSTEIN/einstein.phtml
Einstein bug in linux app
by Matt Giwer, © 2010 [Oct 21]
Affected machine: AMD Athlon II x4 620 with Fedorda 13
When the machine boots boinc starts up fine. One instance in each of four cores. Sometime later I find only three cores being used with one of the cores time sharing two instances as shown below.
working wrong
The CPU history clearly show an underused core.
To fix this I manually stop and restart boinc.
working correctly
As I know just enough C to be dangerous I will leave it at simply reporting the bug.
[/url]
Bug report
)
And why would that be an Einstein bug? If at all, I'd say BOINC might be the culprit, but it sounds more like operation system (though I'm far from expert on this).
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
...and you should not run
)
...and you should not run BOINC as root...
HB
Update or down-date
)
Update or down-date BOINC?
MrS
Scanning for our furry friends since Jan 2002
RE: And why would that be
)
This does not happen with Seti or Milkyway.
RE: ...and you should not
)
Why? I agree, Beware the Root.
It is started by a line in /etc/rc.local to start it at boot time so I am not actually "running" it if this is what you mean.
RE: RE: ...and you should
)
Actually, if you're starting it from the rc.local script, then it is running with root privileges. It would be better to delete the rc.local entry, and then add BOINC to your normal user start-up menu, if possible. If you're running a distro where that's not possible, then you'll just need to open a terminal window and invoke it from the command-line.
RE: It is started by a line
)
To prevent running as root you may put something like
in a file like rc.local. It will start automatically, but won't run as root.
For example, I use BUSER=boinc that executes in its own sandbox.
Rob
RE: RE: It is started by
)
Thanks to you and Donald. I used to try to do that sort of thing but never figured out how. That should do it. Appreciated.
Self-taught obviously.
Since noticing this I started
)
Since noticing this I started monitoring an AMD Phenom Quad and do not see this happening which suggests it might be related to the Athlon II only. I have only monitored the Phenom for three day (and not seen it) vice at least twice a day on the Athlon for five days.
Matt you host is producing a
)
Matt you host is producing a mass of crashed Wus:
http://einsteinathome.org/host/3414309/tasks&offset=0&show_names=0&state=5
"09:40:44 (3067): No heartbeat from core client for 30 sec - exiting"
I think there is the base for your problems.
cu,
Michael