Page 1 of 1

Project: 3062 (Run 2, Clone 71, Gen 29)

Posted: Sun May 04, 2008 10:50 am
by p2501
Hello,

my first post in here! :biggrin:

I woke up today, sat in front of my pc and wondered why two cores were running really hot (by hot I mean about 5-7 degree above normal). Then I checked Fahmon to see that one smp client spat out this line: "Warning: long 1-4 interactions". It's crunching Project: 3062 (Run 2, Clone 71, Gen 29). The warning came 22% in and by now two and a half hour went past and it's still stuck. Is this behaviour normal for this project too? Or should I kill it? :|

Whoop-dee-doo, this is what happened just now:

Code: Select all

[07:48:45] Warning:  long 1-4 interactions
[10:39:11] At least 3 hours since checkpoint written...
[10:41:11] 
[10:41:11] Folding@home Core Shutdown: EARLY_UNIT_END
[10:41:11] 
[10:41:11] Folding@home Core Shutdown: EARLY_UNIT_END
[10:41:14] CoreStatus = 7B (123)
[10:41:14] Client-core communications error: ERROR 0x7b
[10:41:14] Deleting current work unit & continuing...
[10:43:34] - Preparing to get new work unit...
[10:43:34] + Attempting to get work packet
[10:43:34] - Connecting to assignment server
[10:43:35] - Successful: assigned to (171.64.65.63).
[10:43:35] + News From Folding@Home: Welcome to Folding@Home
[10:43:35] Loaded queue successfully.
What the hell is that? I never experienced problems like this...

Edit: Changed topic to standard project naming scheme.

Re: Project: 3062 (Run 2, Clone 71, Gen 29)

Posted: Sun May 04, 2008 6:17 pm
by bruce
Welcome to the folding support forum, p2501.

I wish I had better news for you. Two of the problems that have been reported with the SMP Beta have been (1) Long 1-4 interactions, and (2) ERROR 0x7b

When people have reported the Warning: long 1-4 interactions they often report that the analysis ends abruptly and the WU is deleted. Yours is different in that it apparently entered a loop. Fortunately the anti-looping code did work and it killed the WU after 3 hours. This is not the typical scenario, so thank you for reporting it.

Error 0x7b is an error code returned from Windows by Microsoft and the cause is unknown.

Until there is a later beta version ready for distribution, things like this will happen from time to time -- unfortunately.

Re: Project: 3062 (Run 2, Clone 71, Gen 29)

Posted: Sat May 17, 2008 4:19 pm
by p2501
Nothing out of the ordinary, it was a standard 0x7b problem, I lost the wu. :(
(Forgot to reply :ewink: )

Re: Project: 3062 (Run 2, Clone 71, Gen 29)

Posted: Sun May 18, 2008 4:37 am
by nwkelley
thanks for the detailed report p2501, i'll make sure the researcher running this server is made aware of your post.
nick