![]() |
|
|
#1 |
|
Sep 2004
2·5·283 Posts |
Hi all,
I added my T5500 machine to the project and I always get this: Code:
19:37:53 Launching siever... # Unrecognized CPUID cache code: b1 # Unrecognized CPUID cache code: 05 # Unrecognized CPUID cache code: f0 # Unrecognized CPUID cache code: 57 # Unrecognized CPUID cache code: 56 # Unrecognized CPUID cache code: 7d # Unrecognized CPUID cache code: b4 19:38:05 Siever finished... 19:38:05 Submitting results... 19:38:06 Results successfully submitted... 19:38:06 Requesting assignment... 19:38:06 Received assignment (Bristol 10_229P_2 35901718-35901720)... 19:38:06 Building .in file... 19:38:06 Updating project .in file with assigned range... 19:38:06 Launching siever... # Unrecognized CPUID cache code: b1 # Unrecognized CPUID cache code: 05 # Unrecognized CPUID cache code: f0 # Unrecognized CPUID cache code: 57 # Unrecognized CPUID cache code: 56 # Unrecognized CPUID cache code: 7d # Unrecognized CPUID cache code: b4 19:38:28 Siever finished... 19:38:28 Submitting results... 19:38:28 Results successfully submitted... 19:38:28 Requesting assignment... 19:38:29 Received assignment (Bristol 10_229P_2 35901720-35901723)... 19:38:29 Building .in file... 19:38:29 Updating project .in file with assigned range... 19:38:29 Launching siever... # Unrecognized CPUID cache code: b1 # Unrecognized CPUID cache code: 05 # Unrecognized CPUID cache code: f0 # Unrecognized CPUID cache code: 57 # Unrecognized CPUID cache code: 56 # Unrecognized CPUID cache code: 7d # Unrecognized CPUID cache code: b4 Another question, how many machines currently are running NFSNET? Thanks in advance, Carlos EDIT: I suppose it's sieving.... Last fiddled with by em99010pepe on 2007-01-24 at 20:01 |
|
|
|
|
#2 |
|
Jun 2003
The Texas Hill Country
44116 Posts |
There you go getting a "new" machine that our code doesn't recognize.
I guess that we should ask Intel and AMD to quit producing newer and better processors. :) Although they are a bit of a distraction, failure to recognize the CPUID codes and thus know the size of the L1 cache, L2 cache, etc. causes only a slight inefficiency. (perhaps a fraction of 1%) I'll try to get hold of a newer set of the CPUID specs and add some more entries to our table. |
|
|
|
|
#3 |
|
Sep 2004
283010 Posts |
I want to add more, please tell me if the client is compatible with AMD Athlon's, AMD X2 and P4 dual cores, not the core duo ones. Thanks.
Last fiddled with by em99010pepe on 2007-01-24 at 21:23 |
|
|
|
|
#4 | |
|
"Bo Chen"
Oct 2005
Wuhan,China
23×3×7 Posts |
Quote:
There is the some reference informations. 08:55:32 Received assignment (Bristol 2_772P_2 33708474-33708507)... 08:55:32 Building .in file... 08:55:32 Updating project .in file with assigned range... 08:55:32 Launching siever... # Unrecognized CPUID cache code: 60 # Unrecognized CPUID cache code: 7d Guessing 8+8k L1, 512k L2 09:02:03 Siever finished... 09:02:03 Submitting results... 09:02:05 Results successfully submitted... 09:02:05 Requesting assignment... 09:02:08 Received assignment (Bristol 2_772P_2 33708955-33708995)... 09:02:08 Building .in file... 09:02:08 Updating project .in file with assigned range... 09:02:08 Launching siever... # Unrecognized CPUID cache code: 60 # Unrecognized CPUID cache code: 7d Guessing 8+8k L1, 512k L2 Processor: Intel Pentium 4 630 Prescott 90 nm 1.420 v Description: Intel(R) Pentium(R) 4 CPU 3.00GHz L1 Cache: 16 KBytes L2 Cache: 2048 KBytes BTW, I think the time format should be (2007.05.12 08:55:32) but not 08:55:32 |
|
|
|
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Dual Core P95 64Bit P4 Equivalent problem | g0ods | Software | 9 | 2009-09-15 14:12 |
| Running DC on quad-core problem. | jasong | Hardware | 22 | 2007-11-02 05:12 |
| Intel e6600 Dual Core Problem - How to use both cores with Prime95? | Shoallakeboy | Hardware | 2 | 2006-11-06 17:55 |
| P4 dual core problem | tholloway | Hardware | 5 | 2006-10-28 20:16 |
| http://www.nfsnet.org/downloads/nfsnet-04145-powerpc-MacOSX.tgz | Death | NFSNET Discussion | 15 | 2004-06-22 07:35 |