andy motten wrote: > 2007/8/10, Klaas Gadeyne : >> On Fri, 10 Aug 2007, Jan Kiszka wrote: >>> Philippe Gerum wrote: >>>>> The linux kernel used now is 2.6.20.9 with ipipe patch 1.8-08. >>>>> We use branch 2.3.x of Xenomai (Last changed Revision 2898) >>>>> >>>>> While running xeno-test, the system locks-up just after the latency >>>>> test. >>>> Confirmed here. Houston, we do have a problem with the switchtest, or >>>> soimething this test triggers (and not necessarily the FPU mgmt)... >>> Any news on this? Does it already happen by just running switchtest >>> stand-alone (it doesn't do so here at least)? Is this a pure 2.3.x >>> issue, or is it also visible for 2.4? /me currently rebuilds some trees >>> to assess the local situation. >> Andy will probably continue testing today, so more info will follow, but >> (see >> ) at >> first sight we encountered similar issues on trunk (2.2.x seems >> unaffected). >> >> Klaas > > > We have disabled NMI watchdog like Gilles Chanteperdrix suggested in his > previous message. > > For the moment We have no hard locks anymore. The linux kernel used is still > 2.6.20.9 with ipipe patch 1.8-08. > We use branch 2.3.x of Xenomai (Last changed Revision 2898). The only thing > We have changed is turning off the "NMI watchdog". > > There is no obvious reason why this happened (according to us), but it may > have something to do with the AGP bus (we turned it OFF in this kernel, it > was already turned OFF in the previous tests, but it was ON in the first > tests). Yet another broken x86 system...? > > For seeing if this system will not hard lock anymore, the system will stay > on this weekend (continuously running xeno-tests with high loads). We will > inform you of the results after the weekend. BTW, given that the SMI workaround is infunctional on your system: Do you get reasonable latencies ATM? It looked to me like the NMI watchdog might have triggered due to SMI-related delays. [/me still wonders what Philippe found...] Jan