LHC@home

While running LHC@home... When it's time for the screensaver to come on. The LHC@home graphics seems to be having trouble loading or something because it will just go to a blank screen and once in a while it will blink like it's trying load up the screensaver. I'm running sixtrack 4.64 and running BOINC 4.23. Is there a known bug?

---

> While running LHC@home... When it's time for the screensaver to come on. The
> LHC@home graphics seems to be having trouble loading or something because it
> will just go to a blank screen and once in a while it will blink like it's
> trying load up the screensaver. I'm running sixtrack 4.64 and running BOINC
> 4.23. Is there a known bug?
>
This has been around since before the break. There actually seems to be some improvement with the latest version. It no longer seems to be impossible to get out of the screensaver mode when this happens.

---

BOINC WIKI

BOINCing since 2002/12/8

> > While running LHC@home... When it's time for the screensaver to come on.
> The
> > LHC@home graphics seems to be having trouble loading or something because
> it
> > will just go to a blank screen and once in a while it will blink like
> it's
> > trying load up the screensaver. I'm running sixtrack 4.64 and running
> BOINC
> > 4.23. Is there a known bug?
> >
> This has been around since before the break. There actually seems to be some
> improvement with the latest version. It no longer seems to be impossible to
> get out of the screensaver mode when this happens.

I'm still seeing this with BOINC 4.45 and Sixtrack 4.67 on a Windows XP SP2 GenuineIntel x86 Family 6 Model 8 Stepping 6 797MHz. (I haven't seen it yet on my other computer, where the only difference is that it's Stepping 10 997Mhz). When I kill Sixtrack from the task manager, my computer is fine, but it trashes the WU. I detached from the project for now with this host because I seem to just be wasting CPU time and trashing WUs. Below are the last LHC messages I got. Any insight?

7/6/2005 1:29:41 PM|LHC@home|Restarting result wjun2A_v6s4hvpac_mqx__1__64.257_59.267__6_8__6__50_1_sixvf_boinc504_4 using sixtrack version 4.67
7/6/2005 1:29:42 PM||Suspending work fetch because computer is overcommitted.
7/6/2005 1:29:42 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
7/6/2005 1:29:43 PM||request_reschedule_cpus: process exited
7/6/2005 1:31:35 PM|LHC@home|Unrecoverable error for result wjun2A_v6s4hvpac_mqx__1__64.257_59.267__6_8__6__50_1_sixvf_boinc504_4 (Incorrect function. (0x1) - exit code 1 (0x1))
7/6/2005 1:31:39 PM||request_reschedule_cpus: process exited
7/6/2005 1:31:39 PM|LHC@home|Deferring communication with project for 1 minutes and 0 seconds
7/6/2005 1:31:39 PM|LHC@home|Computation for result wjun2A_v6s4hvpac_mqx__1__64.257_59.267__6_8__6__50_1_sixvf_boinc504_4 finished
7/6/2005 1:31:41 PM|LHC@home|Started upload of wjun2A_v6s4hvpac_mqx__1__64.257_59.267__6_8__6__50_1_sixvf_boinc504_4_0
7/6/2005 1:31:42 PM|LHC@home|Finished upload of wjun2A_v6s4hvpac_mqx__1__64.257_59.267__6_8__6__50_1_sixvf_boinc504_4_0
7/6/2005 1:31:42 PM|LHC@home|Throughput 0 bytes/sec
7/6/2005 1:31:48 PM|LHC@home|Resetting project
7/6/2005 1:31:48 PM||request_reschedule_cpus: exit_tasks
7/6/2005 1:31:48 PM|LHC@home|Detaching from project

---

> I haven't seen it yet on
> my other computer, where the only difference is that it's Stepping 10 997Mhz

Nevermind, it just happened on that machine too.

---

same problem here.

---

This is pretty much what I get ...... maybe 1 second of being able to do something (like try & shut down BOINC) and 10 seconds of lock-up ......

I've just started with LHC, and am very disappointed that Sixpack is behavikng so badly. I never get any issues on the other BOINC projects I'm part of.

This is so bad, in my opinion, and has little if anything listed in the project about it that I have seen (certainly not in 'Known Bugs') that I'm thinking (after only 2 days & 3 failed WUs) of dropping the project entirely ......

Can anyone make some sensible suggestions about the problem ?

Mike

---

I can't make any suggestions about the problem, but you might do better to post the question in the Number Crunching forum, where more people will see it. I think there's already a thread running on this topic.

For what it's worth, I've been with LHC since day 1, and the screen saver is something I've never had trouble with.

Giskard

---

Gaspode the UnDressed
http://www.littlevale.co.uk

same here, and i'm getting really sick of it! Please someone help us with this problem!

---

same here, and i'm getting really sick of it! Please someone help us with this problem!

:D

---

I am having a very similar problem. I have my screensaver set to come on after 10 minutes, which generally works like a charm, but after I enter in my password to unlock my machine, it's at that point that I enter into the loop of 10s unresponsive followed by 1s of responsive until I suspend the LHC program that is running. I'm running WinXP SP 2, BOINC 5.2.7, sixtrack 4.67.

I suspect the problem is due to the schedule switching out screensavers as it cycles through tasks from alternative projects.

---

Very simple fix until the problems are resolved
Just set your screensaver to "blank"

This way you wont experience the problems (not here from day 1, but never had problems with it on blank)
Plus it will waste less cycles on a screensaver that are better spent on the project itself.

If ya really have to see it you can just view the graphics directly ;)

(note.. I think this doesnt crash... cant remember if I looked at this projects graphics that way with current versions but I cant check cause the work is out... shouldnt cause problems)

Dont leave over it :D

---