Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Process blocked (all threads) by devc-pty?: (3 Items)
   
Process blocked (all threads) by devc-pty?  
A developer is encountering an issue wherein a BB10 process appears to be blocked for a period of several minutes. 

No threads are responding. I added a heartbeat thread to log the status of threads every second, and captured thread 
states pre-and post-block.

The process is an automated test framework to test that the installer is working by installing apps, such as Music Store
.  It receives instructions over PPS from another process, attempts an install and returns the results in the same 
manner.  I'm relying on another user to reproduce this, as I cannot locally. The "result" seems to be successful (music 
store installed), but the block time is excessive (6.5 minutes in this case).

Checking pidin on a subsequent run, we're seeing the following stats for the process:
    pid tid name               prio STATE       Blocked                     
62406885   1 ./InstallerApi      10r MUTEX       (0x80c2fcc) 62406885-03 #1  
62406885   2 ./InstallerApi      10r SIGWAITINFO                             
62406885   3 ./InstallerApi      10r REPLY       4681795

Which seems to point to 4681795 as the culprit:

    pid tid name               prio STATE       Blocked                     
4681795   1 base/sbin/devc-pty  20r RECEIVE     1                           

which according to the docs is the pty (pseudoterminal?) manager.  I'm not sure if this is a wild goose chase, or is 
accurate, and if so, why devc-pty would be completely blocking all process threads from executing.

Slog is attached.

Additional info

Thread status - Just before blocking (heartbeat from process log)
Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 18051888 
sp: 133217656 stkbase: 132694016 tls: 133221984 stksize: 528384 tid_flags: 0        priority: 10 real_priority: 10 
policy: 2 state: 6   syscall: 11 last_cpu: 0 timeout: 0        last_chid: -1 start_time: 1392102846808986439 sutime: 
648628428   extsched:  reserved2: 7f0beb8
Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: AI listener thread  tid: 2 flags: 0 why: 0 what: 0 ip: 18052880 
sp: 134097396 stkbase: 133963776 tls: 134098528 stksize: 135168 tid_flags: 67108864 priority: 10 real_priority: 10 
policy: 2 state: 11  syscall: 32 last_cpu: 1 timeout: 16779264 last_chid: -1 start_time: 1392102849108394360 sutime: 
200430213   extsched:  reserved2: 7f0beb8
Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Work thread         tid: 3 flags: 0 why: 0 what: 0 ip: 18053992 
sp: 134478776 stkbase: 134348800 tls: 134481920 stksize: 135168 tid_flags: 67239936 priority: 10 real_priority: 10 
policy: 2 state: 12  syscall: 75 last_cpu: 0 timeout: 16781312 last_chid: -1 start_time: 1392102898768756582 sutime: 
24172488    extsched:  reserved2: 7f0beb8

Thread status - Just after blocking (from app)
Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 18051888 
sp: 133217656 stkbase: 132694016 tls: 133221984 stksize: 528384 tid_flags: 0        priority: 10 real_priority: 10 
policy: 2 state: 6   syscall: 11 last_cpu: 0 timeout: 0 last_chid: -1 start_time: 1392102846808986439 sutime: 667764981 
 extsched:  reserved2: 7f0beb8
Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: AI listener thread  tid: 2 flags: 0 why: 0 what: 0 ip: 18053132 
sp: 134030388 stkbase: 133963776 tls: 134098528 stksize: 135168 tid_flags: 67108864 priority: 10 real_priority: 10 
policy: 2 state: 13  syscall: 80 last_cpu: 0 timeout: 0 last_chid: -1 start_time: 1392102849108394360 sutime: 204458961 
 extsched:  reserved2: 7f0beb8
Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: Work thread         tid: 3 flags: 0 why: 0 what: 0 ip: 18051860 
sp: 134477000 stkbase: 134348800 tls: 134481920 stksize: 135168 tid_flags: 67239936 priority: 10 real_priority: 10 
policy: 2 state: 6   syscall: 11 last_cpu: 1 timeout: 0 last_chid: -1 start_time: 1392102898768756582 sutime: 66474342  
 extsched: ...
View Full Message
Attachment: Text BrandonsSlog.log 2.39 MB
Re: Process blocked (all threads) by devc-pty?  
Hi Andrew,

This is support forum for QNX 4.25 RTOS, not for BlackBerry. Please repost your question in suitable BlackBerry 
Developer Forum:

http://supportforums.blackberry.com/t5/Developer-Support-Forums/ct-p/blackberrydev

Respectfully,
Oleg

10.03.2014, в 18:31:57, Andrew Mackie написал:

> A developer is encountering an issue wherein a BB10 process appears to be blocked for a period of several minutes. 
> 
> No threads are responding. I added a heartbeat thread to log the status of threads every second, and captured thread 
states pre-and post-block.
> 
> The process is an automated test framework to test that the installer is working by installing apps, such as Music 
Store.  It receives instructions over PPS from another process, attempts an install and returns the results in the same 
manner.  I'm relying on another user to reproduce this, as I cannot locally. The "result" seems to be successful (music 
store installed), but the block time is excessive (6.5 minutes in this case).
> 
> Checking pidin on a subsequent run, we're seeing the following stats for the process:
>    pid tid name               prio STATE       Blocked                     
> 62406885   1 ./InstallerApi      10r MUTEX       (0x80c2fcc) 62406885-03 #1  
> 62406885   2 ./InstallerApi      10r SIGWAITINFO                             
> 62406885   3 ./InstallerApi      10r REPLY       4681795
> 
> Which seems to point to 4681795 as the culprit:
> 
>    pid tid name               prio STATE       Blocked                     
> 4681795   1 base/sbin/devc-pty  20r RECEIVE     1                           
> 
> which according to the docs is the pty (pseudoterminal?) manager.  I'm not sure if this is a wild goose chase, or is 
accurate, and if so, why devc-pty would be completely blocking all process threads from executing.
> 
> Slog is attached.
> 
> Additional info
> 
> Thread status - Just before blocking (heartbeat from process log)
> Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 
18051888 sp: 133217656 stkbase: 132694016 tls: 133221984 stksize: 528384 tid_flags: 0        priority: 10 real_priority:
 10 policy: 2 state: 6   syscall: 11 last_cpu: 0 timeout: 0        last_chid: -1 start_time: 1392102846808986439 sutime:
 648628428   extsched:  reserved2: 7f0beb8
> Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: AI listener thread  tid: 2 flags: 0 why: 0 what: 0 ip: 
18052880 sp: 134097396 stkbase: 133963776 tls: 134098528 stksize: 135168 tid_flags: 67108864 priority: 10 real_priority:
 10 policy: 2 state: 11  syscall: 32 last_cpu: 1 timeout: 16779264 last_chid: -1 start_time: 1392102849108394360 sutime:
 200430213   extsched:  reserved2: 7f0beb8
> Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Work thread         tid: 3 flags: 0 why: 0 what: 0 ip: 
18053992 sp: 134478776 stkbase: 134348800 tls: 134481920 stksize: 135168 tid_flags: 67239936 priority: 10 real_priority:
 10 policy: 2 state: 12  syscall: 75 last_cpu: 0 timeout: 16781312 last_chid: -1 start_time: 1392102898768756582 sutime:
 24172488    extsched:  reserved2: 7f0beb8
> 
> Thread status - Just after blocking (from app)
> Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 
18051888 sp: 133217656 stkbase: 132694016 tls: 133221984 stksize: 528384 tid_flags: 0        priority: 10 real_priority:
 10 policy: 2 state: 6   syscall: 11 last_cpu: 0 timeout: 0 last_chid: -1 start_time: 1392102846808986439 sutime: 
667764981  extsched:  reserved2: 7f0beb8
> Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: AI listener thread  tid: 2 flags: 0 why: 0 what: 0 ip: 
18053132 sp: 134030388 stkbase: 133963776 tls: 134098528 stksize: 135168 tid_flags: 67108864 priority: 10 real_priority:
 10 policy: 2 state: 13  syscall: 80 last_cpu: 0 timeout: 0...
View Full Message
Re: Process blocked (all threads) by devc-pty?  

Thread one is blocked on a mutex currently locked by thread 3:
thread 3 didn't unlock before asking work of devc-pty (read(),
write() etc...).  Thread 2 is probably blocked in poll() or
select().  A backtrace of all the threads will be more definitive.

BTW this isn't a qnx4 question.

On Tue, Mar 11, 2014 at 12:53:19PM +0400, Олег Большаков wrote:
> Hi Andrew,
> 
> This is support forum for QNX 4.25 RTOS, not for BlackBerry. Please repost your question in suitable BlackBerry 
Developer Forum:
> 
> http://supportforums.blackberry.com/t5/Developer-Support-Forums/ct-p/blackberrydev
> 
> Respectfully,
> Oleg
> 
> 10.03.2014, в 18:31:57, Andrew Mackie написал:
> 
> > A developer is encountering an issue wherein a BB10 process appears to be blocked for a period of several minutes. 
> > 
> > No threads are responding. I added a heartbeat thread to log the status of threads every second, and captured thread
 states pre-and post-block.
> > 
> > The process is an automated test framework to test that the installer is working by installing apps, such as Music 
Store.  It receives instructions over PPS from another process, attempts an install and returns the results in the same 
manner.  I'm relying on another user to reproduce this, as I cannot locally. The "result" seems to be successful (music 
store installed), but the block time is excessive (6.5 minutes in this case).
> > 
> > Checking pidin on a subsequent run, we're seeing the following stats for the process:
> >    pid tid name               prio STATE       Blocked                     
> > 62406885   1 ./InstallerApi      10r MUTEX       (0x80c2fcc) 62406885-03 #1  
> > 62406885   2 ./InstallerApi      10r SIGWAITINFO                             
> > 62406885   3 ./InstallerApi      10r REPLY       4681795
> > 
> > Which seems to point to 4681795 as the culprit:
> > 
> >    pid tid name               prio STATE       Blocked                     
> > 4681795   1 base/sbin/devc-pty  20r RECEIVE     1                           
> > 
> > which according to the docs is the pty (pseudoterminal?) manager.  I'm not sure if this is a wild goose chase, or is
 accurate, and if so, why devc-pty would be completely blocking all process threads from executing.
> > 
> > Slog is attached.
> > 
> > Additional info
> > 
> > Thread status - Just before blocking (heartbeat from process log)
> > Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 
18051888 sp: 133217656 stkbase: 132694016 tls: 133221984 stksize: 528384 tid_flags: 0        priority: 10 real_priority:
 10 policy: 2 state: 6   syscall: 11 last_cpu: 0 timeout: 0        last_chid: -1 start_time: 1392102846808986439 sutime:
 648628428   extsched:  reserved2: 7f0beb8
> > Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: AI listener thread  tid: 2 flags: 0 why: 0 what: 0 ip: 
18052880 sp: 134097396 stkbase: 133963776 tls: 134098528 stksize: 135168 tid_flags: 67108864 priority: 10 real_priority:
 10 policy: 2 state: 11  syscall: 32 last_cpu: 1 timeout: 16779264 last_chid: -1 start_time: 1392102849108394360 sutime:
 200430213   extsched:  reserved2: 7f0beb8
> > Tue Feb 11 07:14:59 2014 :: (1-Install)  :: INFO: Name: Work thread         tid: 3 flags: 0 why: 0 what: 0 ip: 
18053992 sp: 134478776 stkbase: 134348800 tls: 134481920 stksize: 135168 tid_flags: 67239936 priority: 10 real_priority:
 10 policy: 2 state: 12  syscall: 75 last_cpu: 0 timeout: 16781312 last_chid: -1 start_time: 1392102898768756582 sutime:
 24172488    extsched:  reserved2: 7f0beb8
> > 
> > Thread status - Just after blocking (from app)
> > Tue Feb 11 07:21:30 2014 :: (1-Install)  :: INFO: Name: Main                tid: 1 flags: 0 why: 0 what: 0 ip: 
18051888 sp:...
View Full Message