Am 12.02.2013 um 15:28 schrieb Bruce Ashfield: > > I agree that such a long SMI isn't likely, but running the hwlat > detector is a fairly simple way to see if time is in fact being > stolen from your kernel, so it's something to look into. hwlat - up to now - was unknown to me. I will give it a try. Thanks. >> BTW: Are there any links to SMI events in a multi second >> range? What in a system is done within such a long time span? > > I've never seen it first hand, but I have heard of thermal SMIs that > can "borrow" quite a bit of time (depending on what your platform > is doing). Like anything, not all BIOS/SMIs are created equal :) :) > Which of course can be more of a problem in your > case, since it sounds like you aren't on exactly > the same h/w as the problematic system. Thats the case - yes. But I can try here, build an installation packet for the customer system. Remote control the customer - so he can activate that packet and send me results. > Anyway, just a thought and something to rule out. > If the customer machines can have tracing enabled, you can always set > a latency threshold and stop tracing when it is crossed. That should > get you insight into what is happening in the long latency case. You are right - great idea. Thank you very much Ralf -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
