Hi, Thanks so much for your response.
I've looked at the kernel code a bit (my first experience with kernel code and kdb so bear with me). I don't find anything named kdb_task_has_cpu but I do see a task_has_cpu. I'm attempting to determine if any of the applied patches changed the definition of task_has_cpu or any code that uses task_has_cpu. Is task_has_cpu the correct item for me to be examining? Also, I'd like to understand the output from the "ps" command in kdb a bit better. From what I see there is only one task in state "R" (running). All other tasks are in state "S" or state "D" (see the State column). This seems to me to indicate only one active task. Which column are you looking at that shows "All the tasks are marked as being active on cpu 0"? On Fri, 18 Jun 2004, Keith Owens wrote: > Date: Fri, 18 Jun 2004 06:57:41 +1000 > From: Keith Owens <[EMAIL PROTECTED]> > To: Jan Rovins <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], marks <[EMAIL PROTECTED]> > Subject: Re: Fw: xscale arm kernel 2.4.19-rmk7-ds3 with kdb integrated - > question/help > > On Thu, 17 Jun 2004 16:29:47 -0400, > "Jan Rovins" <[EMAIL PROTECTED]> 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. > > -- Thanks, Mark Sincerbox Adax, Inc. 1-510-548-7047 x129 --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
