> >>All the processors call the "ia64_monarch_init_handler", >>the result is that the same trace appears many times (1 per CPU in fact) >>and a kernel oops occurs (I think it is due to a concurrent access >>to the same stack without any lock mechanism). > > > What kind of machine is this? I've done my tests first on Tiger4 (with a SAL version 3.00) and after on a Bull NOvaScale 5160. These tests went to the same results... > Linux registers different OS_INIT > procedures for the monarch and non-monarch processors, so it > sounds like a SAL bug if more than one CPU calls > ia64_monarch_init_handler(). That's what I fear. Francois WELLENREITER - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Apr 1 01:26:03 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:25 EST