Re: [PATCH][2.5] reproducible smp_call_function/_interrupt cache update race.

From: Zwane Mwaikambo (zwane@linuxpower.ca)
Date: Fri Mar 28 2003 - 09:57:56 EST


On Fri, 28 Mar 2003, Zwane Mwaikambo wrote:

> Hi
> I'm not quite sure how to describe this. I have a 3 Processor
> Pentium 133 system which has been oopsing reliably (i have over 5 of
> these oopses). What appears to be the problem is that the current memory
> barrier in smp_call_function is a simple gcc anti optimisation barrier, we
> really need a memory barrier there so that the other cpu's get the right
> value when they get IPI'd immediately afterwards. The system was going
> down reliably under my test load in under 5minutes, i have run with this
> patch for;
>
> 02:11:24 up 45 min, 5 users, load average: 175.21, 174.89, 160.77

 11:00:31 up 8:29, 5 users, load average: 2.06, 2.28, 2.33

And still going strong, it finally even completed the dbench 128 run
(first time since 2.5.66 got released).

Linus please apply.

        Zwane

-- 
function.linuxpower.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:32 EST