Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751414AbWACPBw (ORCPT ); Tue, 3 Jan 2006 10:01:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751416AbWACPBw (ORCPT ); Tue, 3 Jan 2006 10:01:52 -0500 Received: from gateway-1237.mvista.com ([12.44.186.158]:9467 "EHLO hermes.mvista.com") by vger.kernel.org with ESMTP id S1751414AbWACPBv (ORCPT ); Tue, 3 Jan 2006 10:01:51 -0500 Subject: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) From: Daniel Walker To: kus Kusche Klaus Cc: Ingo Molnar , Lee Revell , linux-kernel In-Reply-To: References: Content-Type: text/plain Date: Tue, 03 Jan 2006 07:01:49 -0800 Message-Id: <1136300510.5915.4.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 755 Lines: 20 On Tue, 2006-01-03 at 15:57 +0100, kus Kusche Klaus wrote: > Ok, yet another patch. This one uses the correct lowlevel calls, and I > > fixed the call ordering. > > Hmmm, it changes a few flag and register values (e.g. lr), > but basically it gives the same BUG and Oops. > > As the first BUG is very early: > Is it possible that tracing gets called before it is initialized? Most likely . It's hard to create a global solution in the entry-*.S files cause the code in there is called so early. Daniel - 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/