>>>What I've noticed using traces (and further an ITP tool) is that for >>>each processor the "ia64_monarch_init_handler" is ever called. :-( >> >>Are you saying that more than one processor calls >>ia64_monarch_init_handler()? If so, I think something >>is broken. > > > Or are you saying that NO processor gets to ia64_monarch_init_handler? 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). > Just a sanity check ... when you set the ITP breakpoint to catch > the entry ... you did set it at the *physical* address of this function? Yes, using Hardware breakpoints. When managing INIT interrupt, SAL calls the physical address of my function. - 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 Wed Mar 31 01:41:58 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:25 EST