lkml.org 
[lkml]   [2006]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
From
Date
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/

\
 
 \ /
  Last update: 2006-01-03 16:04    [W:0.034 / U:0.816 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site