http://www.mail-archive.com/android-kernel@googlegroups.com/msg00825.html it does seem a real problem, in case we go ahead to build drivers as modules.
On Tue, Apr 6, 2010 at 5:12 PM, Pavan Savoy <pavan.sa...@gmail.com> wrote: > http://www.mail-archive.com/android-kernel@googlegroups.com/msg00825.html > > > On Tue, Apr 6, 2010 at 9:51 AM, Pavan Savoy <pavan.sa...@gmail.com> wrote: > >> Yes, Have seen it too :( >> module usage count doesn't reduce once accessed from UI. No idea WHY... >> >> So we started loading it during boot. >> >> >> On Tue, Apr 6, 2010 at 12:22 AM, guru <guru.nav...@gmail.com> wrote: >> >>> Hi Bheemsen, >>> >>> In unsuccessful case, it is not coming out of D/bluedroid( 1223): >>> GURU:Calling delete_module function. >>> >>> if i do lsmod, it is showing unloading bt module and we cannot remove >>> also... >>> >>> Regards >>> Gururaja B O >>> On Apr 6, 10:19 am, guru <guru.nav...@gmail.com> wrote: >>> > Hi, >>> > >>> > Below is for successful condition: >>> > >>> > D/bluedroid( 1223): bt_disable >>> > >>> > I/bluedroid( 1223): Stopping bluetoothd deamon >>> > >>> > I/bluedroid( 1223): Remove bt module... >>> > >>> > D/bluedroid( 1223): rmmod IN >>> > >>> > D/bluedroid( 1223): GURU:maxtry 9 >>> > >>> > D/bluedroid( 1223): GURU:Calling delete_module >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/devices/virtual/ >>> > bluetooth/hci0 >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/bus/sdio/drivers/ >>> > sdio_bt >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/module/bt >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/bluedroid( 1223): GURU:Exiting delete_module >>> > >>> > D/bluedroid( 1223): GURU:Return value of delete_module=0 >>> > >>> > I/bluedroid( 1223): set_bluetooth_power >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:init_wirelessutil IN >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:init_wirelessutil OUT >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:set_power IN >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:set_power OUT >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:deinit_wirelessutil IN >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:deinit_wirelessutil OUT >>> > >>> > I/bluedroid( 1223): check_sdcc_ready >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:init_wirelessutil IN >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:init_wirelessutil OUT >>> > >>> > E/FX_WIRELESSUTIL( 1223): Read (/sys/bus/platform/drivers/msm_sdcc/ >>> > msm_sdcc.4/refcnt) : (1) >>> > >>> > E/FX_WIRELESSUTIL( 1223): Close /sys/bus/platform/drivers/msm_sdcc/ >>> > msm_sdcc.4/refcnt. >>> > >>> > E/FX_WIRELESSUTIL( 1223): Start to check sdcc.. >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/devices/platform/ >>> > msm_sdcc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:1 >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/devices/platform/ >>> > msm_sdcc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:2 >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/devices/platform/ >>> > msm_sdcc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:3 >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > D/mountd ( 1176): Thread recv uevent: remove@/devices/platform/ >>> > msm_sdcc.4/mmc_host/mmc2/mmc2:0001 >>> > >>> > E/dun_service( 1187): The value returned from >>> > dun_getusbmodemstate_fromsys is 2 >>> > >>> > E/FX_WIRELESSUTIL( 1223): SDIO card is removed. >>> > >>> > E/FX_WIRELESSUTIL( 1223): Get SDCC refcnt: 1 >>> > >>> > E/FX_WIRELESSUTIL( 1223): Decrease reference count. >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:deinit_wirelessutil IN >>> > >>> > E/FX_WIRELESSUTIL( 1223): GURU:deinit_wirelessutil OUT >>> > >>> > I/bluedroid( 1223): set_driver_status >>> > >>> > I/bluedroid( 1223): bt_disable OUT >>> > >>> > Unsuccessful case: >>> > D/bluedroid( 1223): bt_disable >>> > >>> > I/bluedroid( 1223): Stopping bluetoothd deamon >>> > >>> > I/bluedroid( 1223): Remove bt module... >>> > >>> > D/bluedroid( 1223): rmmod IN >>> > >>> > D/bluedroid( 1223): GURU:maxtry 9 >>> > >>> > D/bluedroid( 1223): GURU:Calling delete_module >>> > >>> > D/dalvikvm( 1436): GC freed 5386 objects / 293040 bytes in 37ms >>> > >>> > W/ActivityManager( 1223): Timeout of broadcast >>> > BroadcastRecord{443e5bf0 android.intent.action.TIME_TICK} - >>> > receiver=android.app.ActivityThread$PackageInfo$ReceiverDispatcher >>> > $innerrecei...@442b34c0 >>> > >>> > W/ActivityManager( 1223): Receiver during timeout: >>> > BroadcastFilter{44294920 ReceiverList{442a3488 1223 system/1000 local: >>> > 442b34c0}} >>> > >>> > I/power ( 1223): *** set_screen_state 0 >>> > >>> > I/KeyguardViewMediator( 1223): onScreenTurnedOff(2) >>> > >>> > I/KeyguardViewMediator( 1223): wait keyguard visible in Window >>> > timeout,maybe bring some issue time span=500 >>> > >>> > I/GUI_ORT ( 1223): mOrientationListener is not Ready >>> > >>> > I/Process ( 1223): Sending signal. PID: 1223 SIG: 3 >>> > >>> > I/dalvikvm( 1223): threadid=7: reacting to signal 3 >>> > >>> > I/dalvikvm( 1223): Wrote stack trace to '/local/log/anr/traces.txt' >>> > >>> > I/Watchdog( 1223): Watchdog is killing the system process >>> > >>> > W/Process ( 1223): killProcess pid=1223 >>> > >>> > W/Process ( 1223): java.lang.RuntimeException >>> > >>> > W/Process ( 1223): at android.os.Process.killProcess(Process.java: >>> > 730) >>> > >>> > W/Process ( 1223): at >>> com.android.server.Watchdog.run(Watchdog.java: >>> > 853) >>> > >>> > I/Process ( 1223): Sending signal. PID: 1223 SIG: 9 >>> > >>> > regards >>> > Gururaja >>> > On Apr 6, 9:54 am, Bheemsen <bheems...@gmail.com> wrote: >>> > >>> > > Can you attach the logs (logcat). >>> > >>> > > Regards, >>> > > Bheemsen >>> > >>> > > On Tue, Apr 6, 2010 at 10:05 AM, guru <guru.nav...@gmail.com> wrote: >>> > > > Hi All, >>> > >>> > > > I performed the below task repeatedly from Bluetooth UI >>> > >>> > > > 1. Bluetooth trun on/off >>> > > > 2. make bluetooth discoverable >>> > > > 3. scan for devices >>> > >>> > > > after doing these tasks for 10 to 15 times, Bluetooth application >>> > > > hangs. >>> > >>> > > > when I see the log... it is telling "module unloading"... but it >>> > > > doesnt unload. It gives errno 16(device or resource busy) if tried >>> to >>> > > > unload the module manually... >>> > >>> > > > why this error is coming? and where I have to look-in to this >>> problem? >>> > >>> > > > Thanks >>> > > > Gururaja b O >>> > >>> > > > -- >>> > > > unsubscribe: >>> > > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >>> <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> >>> > >>> > > > website:http://groups.google.com/group/android-porting >>> > >>> > > > To unsubscribe, reply using "remove me" as the subject. >>> > >>> > > -- >>> > > Regards >>> > > Bheemsen >>> >>> -- >>> unsubscribe: >>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >>> website: http://groups.google.com/group/android-porting >>> >> >> >> >> -- >> --Pavan Savoy >> >> > > > -- > --Pavan Savoy > > -- --Pavan Savoy -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
