Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
QNX Operating System/Discussion/OSTech/New to Adaptive Partitioning, problems on PXA270/List of Posts
Forum Topic - New to Adaptive Partitioning, problems on PXA270: Page 1 of 2 (41 Items)
   
Update
Ken Schumm
10/23/2008 1:23 PM
post15459
New to Adaptive Partitioning, problems on PXA270   
As a first task I'd like to set up a debug partition so a user can telnet and log into a heavily loaded target.

A debug partition was set up : aps -b10 DevDebug

Then io-net and inetd are launched into the DevDebug partition.

pidin sched shows that io-net and inetd are running in the new partition.

After telneting into an unloaded system pidin shows that telnetd and sh are also assigned to the new partition.

But... when the system is heavily loaded we cannot telnet into the target. If we telnet into an unloaded target, then 
apply the load, the shell becomes unresponsive until the system again becomes unloaded. If the load continues telnet 
eventually disconnects.

It sort of seems like AP isn't working. I thought that maybe the flash driver and inflator needed to also be in the new 
partition so commands could be loaded from flash, but shouldn't those threads inherit the new partition?

Heres the output of aps show:
                    +---- CPU Time ----+-- Critical Time --
Partition name   id | Budget |    Used | Budget |      Used
--------------------+------------------+-------------------
System            0 |    90% |  37.26% |  100ms |   0.000ms
DevDebug          1 |    10% |  62.69% |    0ms |   0.000ms
--------------------+------------------+-------------------
Total               |   100% |  99.95% |

Here's the output of pidin sched:

     pid tid name               prio cpu ExtSched             STATE      
       1   1 procnto              0f   0 System               READY      
       1   2 procnto             70r   0 System               RECEIVE    
       1   3 procnto             10r   0 System               RECEIVE    
       1   4 procnto             10r   0 System               RECEIVE    
       1   5 procnto             10r   0 System               RECEIVE    
       1   6 procnto             10r   0 System               RECEIVE    
       1   7 procnto             70r   0 System               RECEIVE    
       1   8 procnto             10r   0 DevDebug             RUNNING    
       1   9 procnto             10r   0 System               RECEIVE    
       1  10 procnto             10r   0 System               RECEIVE    
       2   1 ot/devf-dbpxa270dp  10r   0 System               SIGWAITINFO
       2   2 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
       2   3 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
       2   5 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
       2   6 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
       3   1 oot/devc-serpxa250  10r   0 System               RECEIVE    
       4   1 proc/boot/slogger   30r   0 System               RECEIVE    
       5   1 proc/boot/pipe      10r   0 System               SIGWAITINFO
       5   2 proc/boot/pipe      10r   0 System               RECEIVE    
       5   3 proc/boot/pipe      10r   0 System               RECEIVE    
       5   4 proc/boot/pipe      10r   0 System               RECEIVE    
       5   5 proc/boot/pipe      10r   0 System               RECEIVE    
    8199   1 sbin/inflator       10r   0 System               RECEIVE    
    8199   2 sbin/inflator       10r   0 System               RECEIVE    
    8199   3 sbin/inflator       10r   0 System               RECEIVE    
    8199   4 sbin/inflator       24r   0 System               RECEIVE    
   53256   1 sbin/io-net         10r   0 DevDebug             SIGWAITINFO
   53256   2 sbin/io-net         21r   0 DevDebug             RECEIVE    
   53256   3 sbin/io-net         18r   0 DevDebug             RECEIVE    
   53256   4 sbin/io-net         10r   0 DevDebug             RECEIVE    
   53256   5 sbin/io-net         21r   0 DevDebug             RECEIVE    
   53256   6 sbin/io-net         17f   0 DevDebug             CONDVAR    
   53256   7 sbin/io-net         10r   0 DevDebug             RECEIVE    
   53256   8 sbin/io-net         18r   0 DevDebug       ...
View Full Message
Attilla Danko(deleted)
10/23/2008 3:06 PM
post15465
Re: New to Adaptive Partitioning, problems on PXA270   
Err. I'm confused. Is the debug partition on the target machine you're telnetting into, or is it on the machine you're 
telnetting from?

Ken Schumm wrote:
> As a first task I'd like to set up a debug partition so a user can telnet and log into a heavily loaded target.
> 
> A debug partition was set up : aps -b10 DevDebug
> 
> Then io-net and inetd are launched into the DevDebug partition.
> 
> pidin sched shows that io-net and inetd are running in the new partition.
> 
> After telneting into an unloaded system pidin shows that telnetd and sh are also assigned to the new partition.
> 
> But... when the system is heavily loaded we cannot telnet into the target. If we telnet into an unloaded target, then 
apply the load, the shell becomes unresponsive until the system again becomes unloaded. If the load continues telnet 
eventually disconnects.
> 
> It sort of seems like AP isn't working. I thought that maybe the flash driver and inflator needed to also be in the 
new partition so commands could be loaded from flash, but shouldn't those threads inherit the new partition?
> 
> Heres the output of aps show:
>                     +---- CPU Time ----+-- Critical Time --
> Partition name   id | Budget |    Used | Budget |      Used
> --------------------+------------------+-------------------
> System            0 |    90% |  37.26% |  100ms |   0.000ms
> DevDebug          1 |    10% |  62.69% |    0ms |   0.000ms
> --------------------+------------------+-------------------
> Total               |   100% |  99.95% |
> 
> Here's the output of pidin sched:
> 
>      pid tid name               prio cpu ExtSched             STATE      
>        1   1 procnto              0f   0 System               READY      
>        1   2 procnto             70r   0 System               RECEIVE    
>        1   3 procnto             10r   0 System               RECEIVE    
>        1   4 procnto             10r   0 System               RECEIVE    
>        1   5 procnto             10r   0 System               RECEIVE    
>        1   6 procnto             10r   0 System               RECEIVE    
>        1   7 procnto             70r   0 System               RECEIVE    
>        1   8 procnto             10r   0 DevDebug             RUNNING    
>        1   9 procnto             10r   0 System               RECEIVE    
>        1  10 procnto             10r   0 System               RECEIVE    
>        2   1 ot/devf-dbpxa270dp  10r   0 System               SIGWAITINFO
>        2   2 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
>        2   3 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
>        2   5 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
>        2   6 ot/devf-dbpxa270dp  10r   0 System               RECEIVE    
>        3   1 oot/devc-serpxa250  10r   0 System               RECEIVE    
>        4   1 proc/boot/slogger   30r   0 System               RECEIVE    
>        5   1 proc/boot/pipe      10r   0 System               SIGWAITINFO
>        5   2 proc/boot/pipe      10r   0 System               RECEIVE    
>        5   3 proc/boot/pipe      10r   0 System               RECEIVE    
>        5   4 proc/boot/pipe      10r   0 System               RECEIVE    
>        5   5 proc/boot/pipe      10r   0 System               RECEIVE    
>     8199   1 sbin/inflator       10r   0 System               RECEIVE    
>     8199   2 sbin/inflator       10r   0 System               RECEIVE    
>     8199   3 sbin/inflator       10r   0 System               RECEIVE    
>     8199   4 sbin/inflator       24r   0 System               RECEIVE    
>    53256   1 sbin/io-net         10r   0 DevDebug             SIGWAITINFO
>    53256   2 sbin/io-net         21r   0 DevDebug             RECEIVE   ...
View Full Message
Ken Schumm
10/23/2008 3:24 PM
post15467
Re: New to Adaptive Partitioning, problems on PXA270   
I'm telnetting from a Windows host to a QNX target. Of course this means the partition is also on the QNX target.
Adam Mallory
10/23/2008 3:38 PM
post15469
RE: New to Adaptive Partitioning, problems on PXA270   
One thing I saw was that your devc-pty is not running in the debug
partition.  That is required for telnet AFAIK.


-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster 

> -----Original Message-----
> From: Ken Schumm [mailto:community-noreply@qnx.com]
> Sent: Thursday, October 23, 2008 3:25 PM
> To: ostech-core_os
> Subject: Re: New to Adaptive Partitioning, problems on PXA270
> 
> I'm telnetting from a Windows host to a QNX target. Of course this
means
> the partition is also on the QNX target.
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15467
Ken Schumm
10/23/2008 3:53 PM
post15471
Re: RE: New to Adaptive Partitioning, problems on PXA270   
> One thing I saw was that your devc-pty is not running in the debug
> partition.  That is required for telnet AFAIK.
> 
> 
> -- 
>  Cheers,
>     Adam

Thanks, but moving devc-pty to the debug partition didn't help.

It shouldn't matter since the server thread should inherit cycles from the partition being served, right?
Adam Mallory
10/23/2008 4:26 PM
post15472
RE: RE: New to Adaptive Partitioning, problems on PXA270   
> It shouldn't matter since the server thread should inherit cycles from
the
> partition being served, right?

I just wanted to mention the pty requirement for telnet.  You should
capture a kernel instrumentation log using tracelogger to gain more
insight on what is going on and hopefully answer why.




-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster
Ken Schumm
10/27/2008 11:08 AM
post15564
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
To simplify the problem I started a login shell on the serial port. The shell is running in the DevDebug partition with 
10% budget. When the target is heavily loaded any command issued on this shell hangs as if it cannot be loaded from 
flash. This is the same behavior that occurs on a telnet shell. So it looks the flash driver is not inheriting the cpu 
budget from the partition.
Adam Mallory
10/27/2008 11:12 AM
post15565
RE: RE: RE: New to Adaptive Partitioning, problems on PXA270   
Ah, that's different from your original post.  I interpreted that you
could not type at all (ie. no character echo).  Not being able to start
commands is a different ball game.

What shell are you using?

Can you copy the same command/binary to /dev/shmem and attempt to
execute it to see if you can still reproduce the issue?


-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster 

> -----Original Message-----
> From: Ken Schumm [mailto:community-noreply@qnx.com]
> Sent: Monday, October 27, 2008 11:09 AM
> To: ostech-core_os
> Subject: Re: RE: RE: New to Adaptive Partitioning, problems on PXA270
> 
> To simplify the problem I started a login shell on the serial port.
The
> shell is running in the DevDebug partition with 10% budget. When the
> target is heavily loaded any command issued on this shell hangs as if
it
> cannot be loaded from flash. This is the same behavior that occurs on
a
> telnet shell. So it looks the flash driver is not inheriting the cpu
> budget from the partition.
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15564
Ken Schumm
10/27/2008 11:27 AM
post15566
Re: RE: RE: RE: New to Adaptive Partitioning, problems on PXA270   
Sorry if my original post was not clear, the word "unresponsive" was not specific. Keystrokes always echo, but commands 
do not load and execute when the target is under load.

I copied pidin to /dev/shmem, made it executable, applied a load to the target, then tried to run /dev/shmem/pidin from 
the serial shell and it would not load and execute.

After reducing the load on the target it ran just fine.

I double checked and the shell is definitely running in the 10% budget DevDebug partition.
Adam Mallory
10/27/2008 1:04 PM
post15571
RE: RE: RE: RE: New to Adaptive Partitioning, problems on PXA270   
What is priority is the CPU load you're running?  Is it a straight CPU
burning example (have you tried that as well?)?


-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster 

> -----Original Message-----
> From: Ken Schumm [mailto:community-noreply@qnx.com]
> Sent: Monday, October 27, 2008 11:28 AM
> To: ostech-core_os
> Subject: Re: RE: RE: RE: New to Adaptive Partitioning, problems on
PXA270
> 
> Sorry if my original post was not clear, the word "unresponsive" was
not
> specific. Keystrokes always echo, but commands do not load and execute
> when the target is under load.
> 
> I copied pidin to /dev/shmem, made it executable, applied a load to
the
> target, then tried to run /dev/shmem/pidin from the serial shell and
it
> would not load and execute.
> 
> After reducing the load on the target it ran just fine.
> 
> I double checked and the shell is definitely running in the 10% budget
> DevDebug partition.
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15566
Ken Schumm
10/27/2008 1:37 PM
post15572
Re: RE: RE: RE: RE: New to Adaptive Partitioning, problems on PXA270   
The shell is 10r, so anything it loads would be the same.

I wrote a quick program to delay(500) then do a printf and it continues just fine under load. Under load you can also 
type at the shell prompt, or just hit enter, and the prompt comes right back.

The problem seems to occur when commands are loaded when the system is very busy.

Even at 10r the partition should get it's budget of cpu cycles, right?

Thanks,
Ken

> What is priority is the CPU load you're running?  Is it a straight CPU
> burning example (have you tried that as well?)?
> 
> 
> -- 
>  Cheers,
>     Adam
> 
>    QNX Software Systems
>    [ amallory@harman.com ]
>    ---------------------------------------------------
>    With a PC, I always felt limited by the software available.
>    On Unix, I am limited only by my knowledge.
>        --Peter J. Schoenster 
> 
> > -----Original Message-----
> > From: Ken Schumm [mailto:community-noreply@qnx.com]
> > Sent: Monday, October 27, 2008 11:28 AM
> > To: ostech-core_os
> > Subject: Re: RE: RE: RE: New to Adaptive Partitioning, problems on
> PXA270
> > 
> > Sorry if my original post was not clear, the word "unresponsive" was
> not
> > specific. Keystrokes always echo, but commands do not load and execute
> > when the target is under load.
> > 
> > I copied pidin to /dev/shmem, made it executable, applied a load to
> the
> > target, then tried to run /dev/shmem/pidin from the serial shell and
> it
> > would not load and execute.
> > 
> > After reducing the load on the target it ran just fine.
> > 
> > I double checked and the shell is definitely running in the 10% budget
> > DevDebug partition.
> > 
> > _______________________________________________
> > OSTech
> > http://community.qnx.com/sf/go/post15566
Adam Mallory
10/27/2008 1:44 PM
post15573
RE: New to Adaptive Partitioning, problems on PXA270   
For giggles can you boost the priority of the shell in your debug
partition to 11 (or another higher priority that no other tasks in ANY
partition are running at)?

Have you taken a kernel trace of the scenario yet?


-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster 

> -----Original Message-----
> From: Ken Schumm [mailto:community-noreply@qnx.com]
> Sent: Monday, October 27, 2008 1:38 PM
> To: ostech-core_os
> Subject: Re: RE: RE: RE: RE: New to Adaptive Partitioning, problems on
> PXA270
> 
> The shell is 10r, so anything it loads would be the same.
> 
> I wrote a quick program to delay(500) then do a printf and it
continues
> just fine under load. Under load you can also type at the shell
prompt, or
> just hit enter, and the prompt comes right back.
> 
> The problem seems to occur when commands are loaded when the system is
> very busy.
> 
> Even at 10r the partition should get it's budget of cpu cycles, right?
> 
> Thanks,
> Ken
> 
> > What is priority is the CPU load you're running?  Is it a straight
CPU
> > burning example (have you tried that as well?)?
> >
> >
> > --
> >  Cheers,
> >     Adam
> >
> >    QNX Software Systems
> >    [ amallory@harman.com ]
> >    ---------------------------------------------------
> >    With a PC, I always felt limited by the software available.
> >    On Unix, I am limited only by my knowledge.
> >        --Peter J. Schoenster
> >
> > > -----Original Message-----
> > > From: Ken Schumm [mailto:community-noreply@qnx.com]
> > > Sent: Monday, October 27, 2008 11:28 AM
> > > To: ostech-core_os
> > > Subject: Re: RE: RE: RE: New to Adaptive Partitioning, problems on
> > PXA270
> > >
> > > Sorry if my original post was not clear, the word "unresponsive"
was
> > not
> > > specific. Keystrokes always echo, but commands do not load and
execute
> > > when the target is under load.
> > >
> > > I copied pidin to /dev/shmem, made it executable, applied a load
to
> > the
> > > target, then tried to run /dev/shmem/pidin from the serial shell
and
> > it
> > > would not load and execute.
> > >
> > > After reducing the load on the target it ran just fine.
> > >
> > > I double checked and the shell is definitely running in the 10%
budget
> > > DevDebug partition.
> > >
> > > _______________________________________________
> > > OSTech
> > > http://community.qnx.com/sf/go/post15566
> 
> 
> 
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15572
Ken Schumm
10/27/2008 1:55 PM
post15574
Re: RE: New to Adaptive Partitioning, problems on PXA270   
Our highest priority process runs at 80 so I boosted the shell to 81.

It worked.

I'm not quite sure how to capture a kernel trace when this problem occurs, there are no cycles left to do it (can't 
connect via tcp/ip or issue commands from the shell when this happens).

> For giggles can you boost the priority of the shell in your debug
> partition to 11 (or another higher priority that no other tasks in ANY
> partition are running at)?
> 
> Have you taken a kernel trace of the scenario yet?
> 
> 
> -- 
>  Cheers,
>     Adam
> 
>    QNX Software Systems
>    [ amallory@harman.com ]
>    ---------------------------------------------------
>    With a PC, I always felt limited by the software available.
>    On Unix, I am limited only by my knowledge.
>        --Peter J. Schoenster 
[...]
Ryan Allen(deleted)
10/27/2008 2:02 PM
post15578
RE: RE: New to Adaptive Partitioning, problems on PXA270   
Maybe you could do something like this on your serial terminal:
  1. # tracelogger -P 81 -c -n0 &
  2. put system under load
  3. try to run pidin:
       # pidin
  4. remove load from system
  5. # slay -f tracelogger

Ideally the time between 1. and 5. will be no more than a couple of seconds.

-- 
Ryan J. Allen
QNX Software Systems




-----Original Message-----
From: Ken Schumm [mailto:community-noreply@qnx.com]
Sent: Mon 2008-10-27 18:55
To: ostech-core_os
Subject: Re: RE: New to Adaptive Partitioning, problems on PXA270
 
Our highest priority process runs at 80 so I boosted the shell to 81.

It worked.

I'm not quite sure how to capture a kernel trace when this problem occurs, there are no cycles left to do it (can't connect via tcp/ip or issue commands from the shell when this happens).

> For giggles can you boost the priority of the shell in your debug
> partition to 11 (or another higher priority that no other tasks in ANY
> partition are running at)?
> 
> Have you taken a kernel trace of the scenario yet?
> 
> 
> -- 
>  Cheers,
>     Adam
> 
>    QNX Software Systems
>    [ amallory@harman.com ]
>    ---------------------------------------------------
>    With a PC, I always felt limited by the software available.
>    On Unix, I am limited only by my knowledge.
>        --Peter J. Schoenster 
[...]


_______________________________________________
OSTech
http://community.qnx.com/sf/go/post15574
Colin Burgess(deleted)
10/27/2008 2:42 PM
post15590
Re: New to Adaptive Partitioning, problems on PXA270   
-P is not a 6.3.2 tracelogger option - use on to set the priority.

I would also recommend using direct mapped mode, eg

tracelogger -S32M -M -n0

Ryan Allen wrote:
> Maybe you could do something like this on your serial terminal:
>   1. # tracelogger -P 81 -c -n0 &
>   2. put system under load
>   3. try to run pidin:
>        # pidin
>   4. remove load from system
>   5. # slay -f tracelogger
> 
> Ideally the time between 1. and 5. will be no more than a couple of seconds.
> 

-- 
cburgess@qnx.com
Ken Schumm
10/27/2008 3:41 PM
post15593
Re: New to Adaptive Partitioning, problems on PXA270   
> -P is not a 6.3.2 tracelogger option - use on to set the priority.
> 
> I would also recommend using direct mapped mode, eg
> 
> tracelogger -S32M -M -n0

If it was easy everyone would be doing it :)

Using Colin's suggestion there is now a 12MB event file in /dev/shmem on the target. Unfortunately, any attempt to ftp 
it to the host for examination results in an ftp error "550 Not a plain file". I've tried binary and ascii modes with 
the same result. Turns out the file looks like a named special file (n set in the permissions mask). If it can't be 
ftp'd over to the host it's not of much use :(
Colin Burgess(deleted)
10/27/2008 3:47 PM
post15594
Re: New to Adaptive Partitioning, problems on PXA270   
The IDE target filesystem view can transfer it (albeit slowly).  Do you have fs-nfs or fs-cifs on the target -that would
 be fastest.

Colin

Ken Schumm wrote:
>> -P is not a 6.3.2 tracelogger option - use on to set the priority.
>>
>> I would also recommend using direct mapped mode, eg
>>
>> tracelogger -S32M -M -n0
> 
> If it was easy everyone would be doing it :)
> 
> Using Colin's suggestion there is now a 12MB event file in /dev/shmem on the target. Unfortunately, any attempt to ftp
 it to the host for examination results in an ftp error "550 Not a plain file". I've tried binary and ascii modes with 
the same result. Turns out the file looks like a named special file (n set in the permissions mask). If it can't be 
ftp'd over to the host it's not of much use :(
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15593
> 

-- 
cburgess@qnx.com
Ken Schumm
10/27/2008 4:00 PM
post15596
Re: New to Adaptive Partitioning, problems on PXA270   
The IDE transfer wasn't so bad, maybe a minute.

Thanks.


> The IDE target filesystem view can transfer it (albeit slowly).  Do you have 
> fs-nfs or fs-cifs on the target -that would be fastest.
> 
> Colin
> 
> Ken Schumm wrote:
> >> -P is not a 6.3.2 tracelogger option - use on to set the priority.
> >>
> >> I would also recommend using direct mapped mode, eg
> >>
> >> tracelogger -S32M -M -n0
> > 
> > If it was easy everyone would be doing it :)
> > 
> > Using Colin's suggestion there is now a 12MB event file in /dev/shmem on the
>  target. Unfortunately, any attempt to ftp it to the host for examination 
> results in an ftp error "550 Not a plain file". I've tried binary and ascii 
> modes with the same result. Turns out the file looks like a named special file
>  (n set in the permissions mask). If it can't be ftp'd over to the host it's 
> not of much use :(
> > 
> > _______________________________________________
> > OSTech
> > http://community.qnx.com/sf/go/post15593
> > 
> 
> -- 
> cburgess@qnx.com
Adam Mallory
10/27/2008 2:02 PM
post15579
RE: RE: New to Adaptive Partitioning, problems on PXA270   
> Our highest priority process runs at 80 so I boosted the shell to 81.
> 
> It worked.

Sorry that isn't quite what I meant.  I still wanted a lowerish priority
but NOT with any other tasks at that priority (even from different
partitions), so I mentioned 11 as the next available, but only you could
really know the answer here.

> I'm not quite sure how to capture a kernel trace when this problem
occurs,
> there are no cycles left to do it (can't connect via tcp/ip or issue
> commands from the shell when this happens).

Tracelogger at priority 81 sounds like it should work.  You could log 5
seconds worth of data - so start tracelogger, apply the CPU load and
attempt to telnet in during that time.  After, just remove the load and
transfer the resulting .kev file (default location is /dev/shmem) off
the board and into your IDE for visualization.



-- 
 Cheers,
    Adam

   QNX Software Systems
   [ amallory@harman.com ]
   ---------------------------------------------------
   With a PC, I always felt limited by the software available.
   On Unix, I am limited only by my knowledge.
       --Peter J. Schoenster 

> 
> > For giggles can you boost the priority of the shell in your debug
> > partition to 11 (or another higher priority that no other tasks in
ANY
> > partition are running at)?
> >
> > Have you taken a kernel trace of the scenario yet?
> >
> >
> > --
> >  Cheers,
> >     Adam
> >
> >    QNX Software Systems
> >    [ amallory@harman.com ]
> >    ---------------------------------------------------
> >    With a PC, I always felt limited by the software available.
> >    On Unix, I am limited only by my knowledge.
> >        --Peter J. Schoenster
> [...]
> 
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post15574
Ken Schumm
10/27/2008 2:22 PM
post15584
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
OK, I first tried the shell priority at 15, which is above photon, graphics, and our gui and below most everything else.
 That didn't work.

Next the shell priority was set to 40, which is above everything except our watchdog kicker and two interrupt threads. 
That didn't work either. The watchdog kicker is at priority 80 and only wakes up once a second and writes to a port. One
 of the interrupt threads is at priority 70 to manage the power key (to power the unit off even if the software goes 
nuts). The other interrupt thread handles a DSP interrupt at up to 10kHz. This data interrupt is what we can vary with 
an ARB to increase/decrease the target load. At 10 kHz there are enough cycles for the GUI to process data and update 
the screen at priority 11.

I'll do an event analysis after lunch.
Ken Schumm
10/27/2008 2:35 PM
post15587
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
Tracelogger reports a whole bunch of messages like this:

"Help, we're dropping buffers! <736 dropped so far>"

It was running at priority 81.
Ken Schumm
10/27/2008 6:14 PM
post15600
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
[...]

> 
> I'll do an event analysis after lunch.

After examining the event log, what appears to be happening in the case of the serial port shell is that keystrokes from
 the host are sent to devc-serpxa250 (the interrupts show characters arriving), and the driver is echoing the characters
 back to the host terminal, but when the unit is under load the typed in command string is never passed to the shell 
(there seems to be no reply done from the serial port driver to a shell).
Hans-Peter Reichert
11/03/2008 3:10 PM
post15874
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
are there any news available on this issue?
this is a realy intressting thread, cause we are also using APS
and there isn't realy an explanation for this behaviour.
/hp
Ken Schumm
11/03/2008 3:46 PM
post15878
Re: RE: RE: New to Adaptive Partitioning, problems on PXA270   
> are there any news available on this issue?
> this is a realy intressting thread, cause we are also using APS
> and there isn't realy an explanation for this behaviour.
> /hp


Are you having the same problem?  I thought maybe our situation was unusual.
Hans-Peter Reichert
11/07/2008 1:43 AM
post16153
AW: RE: RE: New to Adaptive Partitioning, problems on PXA270   
no, we do not see exactly the same problem.
 

>-----Ursprüngliche Nachricht-----
>Von: Ken Schumm [mailto:community-noreply@qnx.com] 
>Gesendet: Montag, 3. November 2008 21:46
>An: ostech-core_os
>Betreff: Re: RE: RE: New to Adaptive Partitioning, problems on PXA270
>
>> are there any news available on this issue?
>> this is a realy intressting thread, cause we are also using APS and 
>> there isn't realy an explanation for this behaviour.
>> /hp
>
>
>Are you having the same problem?  I thought maybe our 
>situation was unusual.
>
>_______________________________________________
>OSTech
>http://community.qnx.com/sf/go/post15878
>
> 
 
*******************************************
Harman Becker Automotive Systems GmbH
Management Board: Dr. Klaus Blickle (Chairman), Dr. Udo Hüls, Michael Mauser, Regis Baudot
Chairman of the Supervisory Board: Ansgar Rempp | Domicile: Karlsbad | 
Local Court Mannheim: Register No. 361395

 
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat 
sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail
. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have 
received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************
12Next

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems