• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 6286 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

After startup binder messages

Kiran Karra
Prodigy 130 points
Other Parts Discussed in Thread: 4430

Hi All,

I have just successfully got Gingerbread 2.3.4 working on the BeagleBoard XM, thanks to the instructions posted on the Ti WIKI.  I am connected to the BeagleBoard via a serial cable, and am looking at the debug messages.  I noticed the following messages, and am wondering if other people see the binder messages that are bolded below?  Are these normal?

enabling adb
adb_open
# warning: `zygote' uses 32-bit capabilities (legacy support in use)
usb 1-2.4: USB disconnect, address 4
usb 1-2.4: new low speed USB device using ehci-omap and address 5
usb 1-2.4: New USB device found, idVendor=093a, idProduct=2510
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.4: Product: USB Optical Mouse
usb 1-2.4: Manufacturer: PixArt
input: PixArt USB Optical Mouse as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.0/input/input3
generic-usb 0003:093A:2510.0002: input: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-ehci-omap.0-2.4/input0
binder: release 1435:1435 transaction 2686 out, still active
binder: 1122:1529 transaction failed 29189, size 14628-0
binder: send failed reply for transaction 2686, target dead
binder: release 1683:1683 transaction 4115 out, still active
binder: 1122:1122 transaction failed 29189, size 5276-0
binder: send failed reply for transaction 4115, target dead
binder: release 1765:1765 transaction 4318 out, still active
binder: release 1765:1809 transaction 4278 out, still active
binder: release 1765:1810 transaction 4284 out, still active
binder: release 1765:1811 transaction 4312 out, still active
binder: 1409:1568 transaction failed 29189, size 28-4
binder: send failed reply for transaction 4278, target dead
binder: 1409:1424 transaction failed 29189, size 28-4
binder: send failed reply for transaction 4284, target dead
binder: 1409:1427 transaction failed 29189, size 28-4
binder: send failed reply for transaction 4312, target dead
binder: 1409:1812 transaction failed 29189, size 2372-0
binder: send failed reply for transaction 4318, target dead

Thanks a lot again for your help.

Kiran

  • 0
    TI__Expert 4390 points

    Hi Kiran,

    1. Could you descibe scenario for which, these messages are being displayed ?

    2. This messages are normal, if  service are not ready accept more connections....or serivice has been stopped externally.

    BR,

    satish

  • 0 in reply to Satish Patel
    Prodigy 130 points

    Hi,

    I let the entire system start up normally, and do not click anything in the GUI.  After about 10 seconds of being started up, the system shows those errors.  I just didn't know if this was something to be worried about or not.

    Thanks again,

    Kiran

  • 0 in reply to Kiran Karra
    TI__Expert 4390 points

    Hi Kiran,

    Nothing to worry abot this. Sometime it happens that service might required some special feature which is not avaialbel for the build or not implemented.

    Do not worry on this messages.

    BR,

    satish

  • 0 in reply to Satish Patel
    Prodigy 115 points

    hello to all, 
    I  am building 4.0.3 android source code for blaze 4430 board, now everything is setup but at last facing similar issue.
    After flash images, system booted and show UI, but after around 10 sec device reboot automatic and then give stable UI.

    any one have idea why this is happening, why device rebooting automatically ?

    This is my terminal log : 

    first acc_open come and then binder related issue ...after this device reboot again ...and then acc_open again and give stable UI.

       . . . . . . . . . . . . . .  .

       . . . . . . . . . . . . . .  .

    79217] acc_open 
    [ 49.981689] acc_release  
    [   60.534179] eth0: no IPv6 routers present                                    
    [   61.736083] mtp_open                                                         
                                                                                    
    shell@android:/ $                                                               
    shell@android:/ $                                                               
    shell@android:/ $                                                               
    shell@android:/ $                                                               
    shell@android:/ $                                                               
    shell@android:/ $                                                               
    shell@android:/ $ [   76.072662] binder: release 193:205 transaction 7931 in, se
    [   76.079711] binder: send failed reply for transaction 7931 to 509:558        
    [   76.087768] binder: send failed reply for transaction 10089 to 702:725       
    [   76.105102] binder: 413:699 transaction failed 29189, size 184-0             
    [   76.114624] binder: 646:670 transaction failed 29189, size 196-4             
    [   76.129455] binder: 646:670 transaction failed 29189, size 204-0             
    [   76.151916] binder: 646:685 transaction failed 29189, size 272-4             
    [   76.166503] binder: 646:670 transaction failed 29189, size 272-4             
    [   76.404663] binder: 413:699 transaction failed 29189, size 108-4             
    [   76.411315] binder: 566:700 transaction failed 29189, size 1204-4            
    [   76.417510] alarm_release: clear alarm, pending 0                            
    [   76.417541] alarm_release: clear alarm, pending 0                            
    [   76.417541] alarm_release: clear alarm, pending 0                            
    [   76.443664] binder: 413:699 transaction failed 29189, size 80-4              
    [   77.372802] request_suspend_state: wakeup (0->0) at 77369903569 (2000-01-01 )
    [   77.403503] mtp_release                                                      
    [   77.410400] init: untracked pid 351 exited                                   
    [   77.415161] init: untracked pid 371 exited                                   
    [   77.429626] init: untracked pid 116 exited                                   
    [   77.434173] init: untracked pid 334 exited                                   
    [   77.438690] init: untracked pid 382 exited                                   
    [   77.450927] init: untracked pid 413 exited                                   
    [   77.455444] init: untracked pid 482 exited                                   
    [   77.488616] init: untracked pid 122 exited                                   
    [   77.493804] init: untracked pid 702 exited                                   
    [   77.566802] init: untracked pid 463 exited                                   
    [   77.571533] init: untracked pid 541 exited                                   
    [   77.576568] init: untracked pid 580 exited                                   
    [   77.581176] init: untracked pid 673 exited                                   
    [   77.598785] init: untracked pid 447 exited                                   
    [   77.603302] init: untracked pid 646 exited                                   
    [   77.628204] init: untracked pid 625 exited                                   
    [   77.668670] rpmsg_omx rpmsg-omx1: local addr assigned: 0x401                 
    [   77.674865] omap-iommu omap-iommu.0: iommu_get: ducati qos_request           
    [   77.696899] omap_hwmod: ipu: failed to hardreset                             
    [   77.703918] omap-iommu omap-iommu.0: ducati: version 2.1                     
    [   77.755065] init: untracked pid 509 exited                                   
    [   77.816619] rpmsg_omx rpmsg13: conn rsp: status 0 addr 101                   
    [   78.514068] rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101      
    [   78.521972] rpmsg_omx rpmsg-omx1: local addr assigned: 0x401                 
    [   78.529693] rpmsg_omx rpmsg13: conn rsp: status 0 addr 101                   
    [   78.983947] rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101      
    [   78.991790] rpmsg_omx rpmsg-omx1: local addr assigned: 0x401                 
    [   78.999114] rpmsg_omx rpmsg13: conn rsp: status 0 addr 101                   
                                                                                    
    shell@android:/ $ [   84.358703] omap-rproc omap-rproc.1: rproc_watchdog_isr    
    [   84.364624] omap_rproc_dump_registers: REGISTER DUMP FOR REMOTEPROC ipu      
    [   84.372619] omap_rproc_dump_registers: PC is at 00342242                     
    [   84.379455] omap_rproc_dump_registers: LR is at 0024fa71                     
    [   84.385498] omap_rproc_dump_registers: pc : [<00342242>]    lr : [<0024fa71>0
    [   84.385528] sp : 85a1b688  ip : 80419348  fp : 0a92935f                      
    [   84.400878] omap_rproc_dump_registers: r10: 00000014  r9 : 85a1b6dc  r8 : 000
    [   84.409118] omap_rproc_dump_registers: r7 : 00000000  r6 : 00000001  r5 : 00e
    [   84.418670] omap_rproc_dump_registers: r3 : 00000000  r2 : 50001000  r1 : 000
    [   84.428131] omap_rproc_dump_registers: Flags: nZCv  IRQs on  FIQs on         
    [   84.435516] _event_notify: remoteproc: ipu has crashed                       
    [   84.441070] rpmsg_rproc_error: Fatal error in ipu                            
    [   84.446166] rpmsg_rproc_error: Fatal error in ipu                            
    [   84.451293] rpmsg_reset_work: reseting virtio device 2                       
                                                                                    
    [   84.457580] rpmsg_resmgr rpmsg7: Enter rprm_remove                           
    [   84.464202] rpmsg_omx rpmsg-omx0: rpmsg omx driver is removed                
    [   84.471099] rpmsg_reset_work: reseting virtio device 3                       
    [   84.476776] rpmsg_resmgr rpmsg9: Enter rprm_remove                           
    [   84.482849] rpmsg_omx rpmsg-omx1: rpmsg omx driver is removed                
    shell@android:/ [   84.490722] rproc_reset_poolmem: invalid pool                
    $ [   84.496490] omap-rproc omap-rproc.1: stopped remote processor ipu          
    [   84.503967] omap-rproc omap-rproc.1: powering up ipu                         
    [   84.509582] virtio_rpmsg_bus virtio4: rpmsg backend virtproc probed successfy
    [   84.519134] virtio_rpmsg_bus virtio5: rpmsg backend virtproc probed successfy
    [   84.582824] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 56
    [   84.591308] omap-rproc omap-rproc.1: BIOS image version is 2                 
    [   84.643463] omap-iommu omap-iommu.0: iommu_get: ducati qos_request           
    [   84.665740] omap_hwmod: ipu: failed to hardreset                             
                                                                                    
    [   84.671478] omap-iommu omap-iommu.0: ducati: version 2.1                     
    [   84.685638] omap-rproc omap-rproc.1: remote processor ipu is now up          
    shell@android:/ $ [   84.700256] omap_rpmsg_mbox_callback: received echo reply !
    [   84.707580] omap_rpmsg_mbox_callback: received echo reply from ipu !         
    [   84.714782] omap_rpmsg_mbox_callback: received echo reply from ipu !         
    [   84.721618] omap_rpmsg_mbox_callback: received echo reply from ipu !         
    [   84.728546] virtio_rpmsg_bus virtio4: creating channel rpmsg-client-sample a2
    [   84.737457] virtio_rpmsg_bus virtio4: creating channel rpmsg-client-sample a3
    [   84.746795] virtio_rpmsg_bus virtio4: creating channel rpmsg-omx addr 0x3c   
    [   84.754974] rpmsg_omx rpmsg-omx0: new OMX connection srv channel: 1024 -> 60!
    [   84.846374] virtio_rpmsg_bus virtio5: creating channel rpmsg-omx addr 0x3c   
    [   84.862792] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
    [   85.816345] request_suspend_state: wakeup (0->0) at 85813415533 (2000-01-01 )
    [ 86.228912] acc_open 
    [ 86.231414] acc_release 
    [ 87.416107] mtp_open  
    . . . . . . . . . . . . . . . . . . . .  . . 
    . . . . . . . . . . . . . . . . . .  .
  • 0 in reply to shubham patni
    Expert 2725 points

    Hi,

    I am also getting the same error and I can't get the android desktop in Jelly bean

    [   76.166503] binder: 646:670 transaction failed 29189, size 272-4             
    [   76.404663] binder: 413:699 transaction failed 29189, size 108-4             
    [   76.411315] binder: 566:700 transaction failed 29189, size 1204-4            
    [   76.417510] alarm_release: clear alarm, pending 0                            
    [   76.417541] alarm_release: clear alarm, pending 0                            
    [   76.417541] alarm_release: clear alarm, pending 0                            
    [   76.443664] binder: 413:699 transaction failed 29189, size 80-4              
    [   77.372802] request_suspend_state: wakeup (0->0) at 77369903569 (2000-01-01 )

    Please anybody can suggest me to fix this issue.

    Thanks & Regards,

    Salih

  • 0 in reply to Muhammad Salih
    Intellectual 375 points

    Hi Salih,

    Im also getting the same issue on my custom board based on SAMA5D3, were you able to find the cause of the issue. It would give us a clue


    Thanks in advance,

    Dhiv