• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 647 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.

GingerBread-2.3-DevKit-1.0 on DM3730 responses slowly

puyou lu
Intellectual 260 points
Other Parts Discussed in Thread: DM3730

i'm using prbuilt kernel and filesystem of AM37X fom TI-Android-GingerBread-2.3-DevKit-1.0.tar.gz on DM3730 EVM board.

When I put filesystem in an SD card, Android comes up successfully, and evrything else is OK.

But when I tried to mount NFS filesystem, Android brings up after very-very long time, and the GUI response after a very-very long time after a tap on the touch screen.

I'm wondering if  there's some problem with the Ethernet driver of DM3730?

 

thanks.

  • 0
    TI__Genius 10210 points

    Do you see the same issue with the Android Froyo images also?

  • 0 in reply to Vishveshwar Bhat
    Intellectual 265 points

    I have the same issue.

    2.3 for AM is quite slow if you run it on DM.

    But with froyo(2.2), the  prebuild image for AM works well also on DM(I know it without dsp)

  • 0 in reply to nan zhao
    Intellectual 260 points

    Yeah, only the froyo version has the problem.

  • 0 in reply to Vishveshwar Bhat
    Intellectual 260 points

    I found something from ddms of android sdk when booting from NFS:

     

     

    01-01 00:54:34.054: ERROR/ActivityManager(1339): ANR in com.android.email

    01-01 00:54:34.054: ERROR/ActivityManager(1339): Reason: Executing service com.android.email/.service.EmailBroadcastProcessorService

    01-01 00:54:34.054: ERROR/ActivityManager(1339): Load: 2.78 / 2.66 / 1.81

    01-01 00:54:34.054: ERROR/ActivityManager(1339): CPU usage from 59178ms to -792ms ago:

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0.8% 298/rpciod/0: 0% user + 0.8% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0.7% 1492/com.android.email: 0.3% user + 0.3% kernel / faults: 1487 minor 82 major

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0.6% 1339/system_server: 0.3% user + 0.2% kernel / faults: 1093 minor 63 major

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0.3% 1501/android.process.media: 0.2% user + 0.1% kernel / faults: 337 minor 10 major

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0.1% 894/adbd: 0% user + 0.1% kernel / faults: 1 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 311/nfsiod: 0% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 1456/android.process.acore: 0% user + 0% kernel / faults: 70 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 5/events/0: 0% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 978/logcat: 0% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 6/khelper: 0% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 883/servicemanager: 0% user + 0% kernel / faults: 4 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 1326/zygote: 0% user + 0% kernel / faults: 17 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 1422/com.android.phone: 0% user + 0% kernel / faults: 33 minor 16 major

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   0% 1425/com.android.launcher: 0% user + 0% kernel / faults: 58 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):  +0% 1515/com.android.bluetooth: 0% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339): 99% TOTAL: 1.3% user + 1.6% kernel + 96% iowait + 0% irq + 0.8% softirq

    01-01 00:54:34.054: ERROR/ActivityManager(1339): CPU usage from 2231ms to 2758ms later:

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   9.4% 1339/system_server: 5.6% user + 3.7% kernel / faults: 88 minor

    01-01 00:54:34.054: ERROR/ActivityManager(1339):     7.5% 1441/Binder Thread #: 5.6% user + 1.8% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):     5.6% 1353/ActivityManager: 1.8% user + 3.7% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):     1.8% 1344/Compiler: 1.8% user + 0% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339):   1.8% 298/rpciod/0: 0% user + 1.8% kernel

    01-01 00:54:34.054: ERROR/ActivityManager(1339): 100% TOTAL: 7.6% user + 1.9% kernel + 90% iowait

    01-01 00:54:34.539: INFO/Process(1339): Sending signal. PID: 1492 SIG: 9

    01-01 00:54:34.734: INFO/ActivityManager(1339): Process com.android.email (pid 1492) has died.

    01-01 00:54:34.742: WARN/ActivityManager(1339): Scheduling restart of crashed service com.android.email/com.android.exchange.SyncManager in 5000ms

    01-01 00:54:34.750: WARN/ActivityManager(1339): Scheduling restart of crashed service com.android.email/.service.EmailBroadcastProcessorService in 116012ms

     

     

    from the cpu's iowait percentage, I guess the problem is probably caused by the ethernet drivers.