good all mighty
"AI39. Cache Data Access Request from One Core Hitting a Modified Line
inthe L1 Data Cache of the Other Core May Cause Unpredictable
SystemBehaviorWhen request for data from Core 1 results in a L1 cache
miss, the request isProblem:sent to the L2 cache. If this request hits
Geoff Jacobs wrote:
Michel Dierks wrote:
Geoff Jacobs wrote:
Michel Dierks wrote:
Hello,
I'm developing an application to calculate the Mandelbrot fractal.
Hmm... I never did this when I was learning the ropes. There is a pretty
example included with the mpich
Hi!Thanks a lot for the answer.Anyway, I would like to go a bit deeper on this subject. I know that there are this kind of problems in every processor. I know that the number 39 is the one of real concer. But we also know that still it seems to NOT have a fix, work around ou bios update for it. So
On 11/2/06, Chris Samuel <[EMAIL PROTECTED]> wrote:
On Thursday 02 November 2006 7:03 pm, Leif Nixon wrote:
>
> I had a real problem with that at CCGrid in Cardiff. How are
> you supposed to order a pint of Brains with a straight face?
it's not that popular on a night out in Cardiff - it's mo
On 11/12/06, Tim Moore <[EMAIL PROTECTED]> wrote:
Hello All -
I have a compute node that has started dropping off. When I say drop
off, I mean the node (while running a job) will lose all connectivity
and the machine does not respond. I have viewed the logs and can find
no reason for the node
>From the convention center, there is a street car that goes to Ybor
City, To visit Hyde Park, there is a trolley bus run by Hartline.
Trolley Bus Route http://www.hartline.org/routes/trolley/98.htm#Map
Street Car Info http://www.tecolinestreetcar.org/about/maps/index.htm
./Todd
On Sun, 2006
On Sunday 12 November 2006 16:13, Tim Moore wrote:
> Has anyone ever seen such behavior?
Others have mentioned about attaching consoles, etc, but it's also worth
trawling through any logs in /var/log to see if anything is showing up there
too.
Check dmesg whilst the node is under load, if you'
Mark Hahn wrote:
we (and the vendor) regard this as grounds for repair (usually
the power supply).
I backup what Mark says.
a) attach a console to the machine, either a serial line or a
monitor/keyboard
b) run memtest on it, followed by CPUburn or some other
compute-intensive task for a da
