kdb
[Top] [All Lists]

Re: Fw: xscale arm kernel 2.4.19-rmk7-ds3 with kdb integrated - question

To: "Jan Rovins" <janr@xxxxxxxx>
Subject: Re: Fw: xscale arm kernel 2.4.19-rmk7-ds3 with kdb integrated - question/help
From: Keith Owens <kaos@xxxxxxx>
Date: Fri, 18 Jun 2004 06:57:41 +1000
Cc: kdb@xxxxxxxxxxx, "marks" <marks@xxxxxxxx>
In-reply-to: Your message of "Thu, 17 Jun 2004 16:29:47 -0400." <09f701c454a9$d52feab0$4c01a8c0@mtlnj.adax>
Sender: kdb-bounce@xxxxxxxxxxx
On Thu, 17 Jun 2004 16:29:47 -0400, 
"Jan Rovins" <janr@xxxxxxxx> wrote:
>> Last we spoke I had gotten kdb integrated with the xscale arm kernel
>> 2.4.19-rmk7-ds3.  However, when we invoke kdb (CTRL-A in the minicom
>> session) and try to use the "ps" command (similar to the ps command we all
>> know and love) we get the following output:
>> 
>> Entering kdb (current=0xceb7c000, pid 223) due to Keyboard Entry
>> kdb>
>> kdb> ps
>> Task Addr       Pid   Parent [*] cpu State Thread     Command
>> 0xc0218000        0        0  1    0   R  0xc0218270  swapper
>>   Error: does not match running process table (0xceb7c000)
>> 0xc0538000        1        0  1    0   S  0xc0538270  init
>>   Error: does not match running process table (0xceb7c000)
>> 0xc05ce000        2        1  1    0   S  0xc05ce270  keventd
>>   Error: does not match running process table (0xceb7c000)

All the tasks are marked as being active on cpu 0, which is impossible;
one cpu, one active task.  kdb_task_has_cpu() is returning true for all
tasks.  kdb_task_has_cpu() is common code which works for other
architectures, check your merge to find out why it always returns true
for you.

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>