Database Users

Lag-on-wake idea - G Tablet Android Development

I have an idea for the lag on wake issue that seems endemic to the new kernel in the current TNTLite 3.x, Vegan beta 4 and stock 3389 ROMs.
I think I've confirmed this isn't an issue with Calendar, at least not in Vegan beta4, because I disabled everything Calendar related in AutoStarts and it was still happening all the time.
I've been poking around, reading about CPU governors, and exploring the /sys filesystem.
What I've found is that the default kernel seems to have only two governor settings - performance and powersave, the former of which pegs the CPU at maxfrequency and the latter pegs the CPU at minfrequency. The ondemand governor that my Nexus One uses and that a lot of Android devices use seems to be disabled here, perhaps because it doesn't play nice with Tegra2, perhaps because they just couldn't be bothered.
I believe what's happening is that when the G Tablet is asleep for a longer period of time, the governor gets set to powersave mode. When the G Tablet wakes up it's presumably supposed to be set back to performance mode. Apparently that isn't happening all the time.
My proposal to confirm this is to try to get the lag condition to happen again, then to issue the following commands from the terminal window and see if the issue resolves itself:
Code:
sudo echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
sudo echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
It's also possible that since the governor is getting truly stuck in the powersave mode, this won't successfully "unstick" it. But it's worth trying - if we can confirm that this is what's happening, I suspect we can hack our way to a proper fix, especially now that we have the kernel source as of about an hour ago.
Going to try sleeping my tablet for a while, see if this gets me anywhere... will update...
EDIT: this doesn't fix the issue once it happens. But I can confirm that when it's lagging which just happened after an hour's sleep, that cpuinfo_cur_freq file shows 216000 (even though I had minfreq set in OC Widget to 528000, hmm). So it's obviously getting stuck at that very, very slow clock setting.
Also, I was at 85% battery when this happened, so it's not only at low battery readings that this occurs, at least on beta4 of Vegan.
This all confirms to me that I am on the right track, this is absolutely an issue with the governor.
-----------------------------------------------------------------------------------------------
EDIT: Adding this summary of the thread below.
Update.zip files with alternate kernels for users of Vegan b4 and TNTLite 3.1.x ROMs (see these posts):
For Vegan beta4:
http://forum.xda-developers.com/showpost.php?p=10138407&postcount=112
For TNTLite (vsc build)
http://forum.xda-developers.com/showpost.php?p=10170515&postcount=206
Information for kernel developers:
We identified two patches to fix the lag-on-wake issue. These patches are:
http://nv-tegra.nvidia.com/gitweb/?...it;h=24026696dcd728be545c07fcd3b4bd7e1483c553
http://nv-tegra.nvidia.com/gitweb/?...it;h=01a0b8146665a17dd063b4b8e2fe80e5bd795c22
The first of these appears to be the critical one, the latter to handle some possible corner case issues.
Additionally, there is an issue with the kernel config that affected apps trying to install to the SD card. We fixed that using a subset of the patch here:
http://nv-tegra.nvidia.com/gitweb/?...it;h=555d0c0e5b9a86b5e291216d59406709b34480d6
Specifically, my subset patch is posted at this location: http://forum.xda-developers.com/showpost.php?p=10168177&postcount=5
Synopsis of what we learned:
Under certain conditions (LP1 suspend?), when the Tegra 2 was in a suspend state and a driver returned an error on wake-up, there is a step in the resume process where the voltage was supposed to be reset to the CPU, and that step was getting skipped. When the voltage was stuck low, the CPU would get stuck at minimum frequency, 216MHz and couldn't be pushed back to 1GHz or any other setting by the governor. There was a patch from NVidia that fixed this behavior, from a newer branch of the Tegra 2 source code than what Viewsonic used. We integrated this patch and found that indeed, it resolved the problem.

I had this issue with 3.0 but I reinstalled the ROM and did a data, cash and delvik wipe and have not had the issue since.
The first install I did not do a wipe and ran into the lag issue. But ever since I did the reinstall with the wipe I have not had any slow downs at all.
EDIT: Disregard the above, the lag came back.

mzimand said:
I had this issue with 3.0 but I reinstalled the ROM and did a data, cash and delvik wipe and have not had the issue since.
The first install I did not do a wipe and ran into the lag issue. But ever since I did the reinstall with the wipe I have not had any slow downs at all.
Click to expand...
Click to collapse
First thing I want to say is that I'm not a dev.
However I've been playing with the lag issue for a while since I updated as soon as the update showed on my Tablet and it showed pretty quickly for me. I didn't think this issue was related to the calendar problem that roth mentioned because I experienced it before I even installed GApps to my tablet.
I suspected some power saving issue from the beginning and what I've also noticed is no matter how long it sleeps, it doesn't happen at a certain battery level....in my case I went from 100% to ~45% and had no slowdown, even after sleeping.
So if you're at anything above 60% for example and sleep or don't use the tablet for even the hour or more, when you get back to it - it's just as fast as you left it.
In my experience, this happens when the Tablet is at roughly 30% - maybe a bit more, maybe less depending on your battery calibration and readings.
In order to really test this - wait until your tablet is at 20-30% and then leave it alone or make it sleep and try it to see if it slows down. If it does not, then maybe you're on to something with wiping the data/cache/dalvik. If you indeed show no signs of slowdown, I will try wiping as well in order to confirm so pls let me know when you can. Thanks.

The reason I think this might not be kernel related is that I ran Vegan for a couple weeks straight without issues. Each time I install a new ROM I can recreate the issue when it has a clean data partition. If I restore my old data partition I well cease to see the lag on wake. I have tested and tested this, and each time it is related to the data partition.
It really is a shot it the dark looking at anything, but my bet is on some type of thread that is being called either on wakeup or before sleep that stalls out. Many apps use that time to sync, or read from disk.

Here is what I found tonight after some testing:
1.) Once the processor drops to the 216000 freq it's pretty much stuck there till you reboot. Couldn't find a way to snap it out of it.
2.) On a clean boot my cpuinfo_cur_freq file fluctuates between 246406 and 286484, but there is no slowness. Everything is blazing fast. Weird...
3.) After booting, setting cpu0's scaling_min_freq file to 1000000 does, in fact, change the speed listed in cpuinfo_cur_freq for both cpus.
4.) Overclock Widget doesn't set the governor profile "performance". It only sets the min and max speed. I think this may be part of the problem.
5.) Running "tegrastats -max" from a term is supposed to disable CPU frequency changes and enable max speed.
As a test I set the freq and governor, and also ran tegrastats. We'll see how the tab does in the morning.

anlog said:
Here is what I found tonight after some testing:
1.) Once the processor drops to the 216000 freq it's pretty much stuck there till you reboot. Couldn't find a way to snap it out of it.
2.) On a clean boot my cpuinfo_cur_freq file fluctuates between 246406 and 286484, but there is no slowness. Everything is blazing fast. Weird...
3.) After booting, setting cpu0's scaling_min_freq file to 1000000 does, in fact, change the speed listed in cpuinfo_cur_freq for both cpus.
4.) Overclock Widget doesn't set the governor profile "performance". It only sets the min and max speed. I think this may be part of the problem.
5.) Running "tegrastats -max" from a term is supposed to disable CPU frequency changes and enable max speed.
As a test I set the freq and governor, and also ran tegrastats. We'll see how the tab does in the morning.
Click to expand...
Click to collapse
I'm glad somebody else is observing the same thing about "sticking" at 216MHz - it's hard to imagine that isn't related to the slowdown. It would also roughly explain the magnitude of shift in the Quadrant scores observed during the slowdown. Your clean boot behavior and mine are different because I've been running Overclock Widget. Also, if the cpu_info_curfreq is fluctuating that implies the governor is changing the frequency.
Good find on the tegrastats command, I wasn't aware of that one. I'm fairly hopeful you won't see the slowdown after running that.
Another thing - I'm starting to pick through the kernel source diffs a bit (I can't even get the kernel to build, as it seems to be angry that my Linux boxes are all 64 bit). I decided to peek through dmesg and see if it gave us any clues.
Lots of good info on the suspend/resume cycling in dmesg. Going to see if I can get this sucker to lag out again and then look at dmesg output to see if there are any clues.

I got the lag with 3.0 and never went into sleep mode. Seems the lag issue is random to any rom with the newest kernel.

rcgabriel said:
I'm glad somebody else is observing the same thing about "sticking" at 216MHz - it's hard to imagine that isn't related to the slowdown. It would also roughly explain the magnitude of shift in the Quadrant scores observed during the slowdown. Your clean boot behavior and mine are different because I've been running Overclock Widget. Also, if the cpu_info_curfreq is fluctuating that implies the governor is changing the frequency.
Good find on the tegrastats command, I wasn't aware of that one. I'm fairly hopeful you won't see the slowdown after running that.
Another thing - I'm starting to pick through the kernel source diffs a bit (I can't even get the kernel to build, as it seems to be angry that my Linux boxes are all 64 bit). I decided to peek through dmesg and see if it gave us any clues.
Lots of good info on the suspend/resume cycling in dmesg. Going to see if I can get this sucker to lag out again and then look at dmesg output to see if there are any clues.
Click to expand...
Click to collapse
UPDATE:
1.) Just wanted to clarify that even though the CPU speed was fluctuating in the 200,000's after a clean boot, it felt like it was running at 1ghz speed. Not sure what that's all about, but it seems that anything other than 216,000 = fast.
2.) I don't believe Overclock Widget is designed for multiple processors. While setting the parameter of one CPU usually scales the other, I've seen a couple of bugs with Overclock Widget where the parameters of one CPU were changed but not the other. I think a script running at boot to set the parameters and run tegrastats would be better
3.) The "performance" governor has to be manually set for both cpus.
4.) I'm not 100% certain tegrastats actually does anything with our build. I don't get an error when running it, but I do know that it definitely doesn't take the unit out of "slow" mode. Hopefully it keeps it from dropping if run at boot time.
5.) After leaving the unit sleeping and charging last night, this morning I am still at 1ghz. So far so good!

Okay, minor step - I managed to get into the lag state again and capture the wakeup activity from dmesg. Attached is what happened in dmesg when the system tried to wakeup:
Code:
<4>[ 2896.054620] Enabling non-boot CPUs ...
<4>[ 2896.094664] CPU1: Booted secondary processor
<7>[ 2896.094840] CPU0 attaching NULL sched-domain.
<7>[ 2896.257924] CPU0 attaching sched-domain:
<7>[ 2896.257966] domain 0: span 0-1 level CPU
<7>[ 2896.258006] groups: 0 1
<7>[ 2896.258069] CPU1 attaching sched-domain:
<7>[ 2896.258102] domain 0: span 0-1 level CPU
<7>[ 2896.258136] groups: 1 0
<4>[ 2896.258729] CPU1 is up
<4>[ 2896.265833] *** Wakeup from LP1 ***
<6>[ 2896.275836] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 2896.281719] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 2896.287588] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 2896.293450] tegra_uart tegra_uart.4: tegra_uart_resume called
<6>[ 2896.299635] wakeup wake lock: mmc_delayed_work
<4>[ 2896.304965] Resume SDIO2Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 2896.384399] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 2896.390585] h2w: off
<6>[ 2896.536957] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 2896.880520] Restarting tasks ...
<6>[ 2896.885505] nvrm_notifier_show: blocking
<4>[ 2896.900670] done.
<6>[ 2896.902777] tegra_pm_notifier: start processing event=4
<6>[ 2896.910332] notify_daemon: wait for nvrm_daemon
<6>[ 2896.933747] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 2896.947458] nvrm_notifier_show: blocking
<6>[ 2896.960167] tegra_pm_notifier: finished processing event=4
<6>[ 2896.976796] suspend: exit suspend, ret = 0 (2010-12-25 17:58:31.059770041 UTC)
<6>[ 2897.646318] PM: Syncing filesystems ... done.
<6>[ 2897.853777] tegra_pm_notifier: start processing event=3
<6>[ 2897.853814] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 2897.853997] notify_daemon: wait for nvrm_daemon
<6>[ 2897.857518] nvrm_notifier_show: blocking
<6>[ 2897.857544] tegra_pm_notifier: finished processing event=3
<4>[ 2897.857558] Freezing user space processes ...
<6>[ 2897.862377] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 2897.897408] (elapsed 0.03 seconds) done.
<4>[ 2897.901342] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 2897.946079] tegra_grhost tegra_grhost: suspending
<6>[ 2897.995191] tegra_grhost tegra_grhost: suspended
<4>[ 2898.000022] Suspend SDIO3Suspend SDIO2
<6>[ 2898.003762] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 2898.009875] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 2898.015848] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 2898.021775] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 2898.029954] DVFS set core at 1200mV
<4>[ 2898.039188] RM power state before suspend: Active (2)
<6>[ 2898.044378] wakeup wake lock: dhd_wake_lock
<4>[ 2898.048660] Active Module: 0x16
<4>[ 2898.060829] Disabling non-boot CPUs ...
<7>[ 2898.064739] CPU0 attaching NULL sched-domain.
<7>[ 2898.064786] CPU1 attaching NULL sched-domain.
<7>[ 2898.166172] CPU0 attaching NULL sched-domain.
<5>[ 2898.166901] CPU1: clean shutdown
<4>[ 2903.940840] Enabling non-boot CPUs ...
<4>[ 2903.985153] CPU1: Booted secondary processor
<7>[ 2903.985351] CPU0 attaching NULL sched-domain.
<7>[ 2904.161206] CPU0 attaching sched-domain:
<7>[ 2904.161247] domain 0: span 0-1 level CPU
<7>[ 2904.161288] groups: 0 1
<7>[ 2904.161350] CPU1 attaching sched-domain:
<7>[ 2904.161383] domain 0: span 0-1 level CPU
<7>[ 2904.161418] groups: 1 0
<4>[ 2904.162007] CPU1 is up
<4>[ 2904.169112] *** Wakeup from LP1 ***
<4>[ 2904.173194] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<6>[ 2904.192091] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 2904.205609] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 2904.211490] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 2904.217356] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 2904.389852] LP1(PMU flag set) -->Out.
<4>[ 2904.394220] Resume SDIO2Resume SDIO3h2w: offswitch-dock: dock_switch_work_func
<4>[ 2904.475173] switch-dock: desktop_dock = 0switch-dock: state = 0
<6>[ 2904.909094] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 2905.452278] Restarting tasks ...
<6>[ 2905.457281] nvrm_notifier_show: blocking
<4>[ 2905.464230] dhdsdio_htclk: HT Avail request error: -35
<6>[ 2905.470039] request_suspend_state: wakeup (3->0) at 665179051856 (2010-12-25 17:58:39.181279035 UTC)
<4>[ 2905.481490] done.
<6>[ 2905.485183] tegra_pm_notifier: start processing event=4
<6>[ 2905.490567] notify_daemon: wait for nvrm_daemon
<6>[ 2905.506260] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 2905.515835] request_suspend_state: sleep (0->3) at 665224872861 (2010-12-25 17:58:39.227104040 UTC)
<6>[ 2905.525994] tegra_pm_notifier: finished processing event=4
<6>[ 2905.526044] nvrm_notifier_show: blocking
<6>[ 2905.542803] suspend: exit suspend, ret = 0 (2010-12-25 17:58:39.254074042 UTC)
<6>[ 2909.383679] PM: Syncing filesystems ... done.
<6>[ 2909.570068] tegra_pm_notifier: start processing event=3
<6>[ 2909.570106] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 2909.570293] notify_daemon: wait for nvrm_daemon
<6>[ 2909.574045] nvrm_notifier_show: blocking
<6>[ 2909.574071] tegra_pm_notifier: finished processing event=3
<4>[ 2909.574085] Freezing user space processes ...
<6>[ 2909.579063] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 2909.614570] (elapsed 0.04 seconds) done.
<4>[ 2909.618506] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 2909.645993] tegra_grhost tegra_grhost: suspending
<6>[ 2909.650737] tegra_grhost tegra_grhost: suspended
<4>[ 2909.655579] Suspend SDIO3Suspend SDIO2
<6>[ 2909.659274] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 2909.665485] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 2909.671440] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 2909.677400] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 2909.685695] DVFS set core at 1200mV
<4>[ 2909.695809] RM power state before suspend: Active (2)
<4>[ 2909.700946] Active Module: 0x16
<4>[ 2909.713166] Disabling non-boot CPUs ...
<7>[ 2909.717075] CPU0 attaching NULL sched-domain.
<7>[ 2909.717120] CPU1 attaching NULL sched-domain.
<7>[ 2909.823323] CPU0 attaching NULL sched-domain.
<5>[ 2909.824083] CPU1: clean shutdown
<4>[ 2913.962567] Enabling non-boot CPUs ...
<4>[ 2914.005848] CPU1: Booted secondary processor
<7>[ 2914.006025] CPU0 attaching NULL sched-domain.
<7>[ 2914.147290] CPU0 attaching sched-domain:
<7>[ 2914.147332] domain 0: span 0-1 level CPU
<7>[ 2914.147373] groups: 0 1
<7>[ 2914.147437] CPU1 attaching sched-domain:
<7>[ 2914.147469] domain 0: span 0-1 level CPU
<7>[ 2914.147505] groups: 1 0
<4>[ 2914.148092] CPU1 is up
<4>[ 2914.155196] *** Wakeup from LP1 ***
<4>[ 2914.159175] gpio_keys_isr
<4>[ 2914.161937] gpio_keys_isr
<6>[ 2914.169912] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 2914.175793] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 2914.181661] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 2914.187688] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 2914.194418] Resume SDIO2
<6>[ 2914.196870] wakeup wake lock: mmc_delayed_work
<4>[ 2914.202368] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 2914.298461] switch-dock: desktop_dock = 0h2w: offgpio_keys_isr
<4>[ 2914.327263] switch-dock: state = 0
<4>[ 2914.339183] Restarting tasks ...
<6>[ 2914.355481] nvrm_notifier_show: blocking
<4>[ 2914.379544] done.
<6>[ 2914.381480] tegra_pm_notifier: start processing event=4
<6>[ 2914.397254] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 2914.403283] notify_daemon: wait for nvrm_daemon
<6>[ 2914.409378] nvrm_notifier_show: blocking
<6>[ 2914.415203] tegra_pm_notifier: finished processing event=4
<6>[ 2914.435267] suspend: exit suspend, ret = 0 (2010-12-25 17:58:48.597119011 UTC)
<6>[ 2914.454982] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 2914.481208] gpio_keys_isr
<4>[ 2914.483839] gpio_keys_isr
<4>[ 2914.552830] gpio_keys_isr
<6>[ 2914.695077] PM: Syncing filesystems ... gpio_keys_isr
<4>[ 2914.760382] gpio_keys_isr
<4>[ 2914.876996] gpio_keys_isr
<4>[ 2914.965104] done.
<6>[ 2914.980288] tegra_pm_notifier: start processing event=3
<6>[ 2914.985553] notify_daemon: wait for nvrm_daemon
<6>[ 2914.985567] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 2914.997591] tegra_pm_notifier: finished processing event=3
<6>[ 2914.997655] nvrm_notifier_show: blocking
<4>[ 2915.008522] Freezing user space processes ...
<6>[ 2915.017796] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 2915.024342] (elapsed 0.00 seconds) done.
<4>[ 2915.028285] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 2915.041537] gpio_keys_isr
<6>[ 2915.074420] tegra_grhost tegra_grhost: suspending
<4>[ 2915.170193] gpio_keys_isr
<4>[ 2915.295102] gpio_keys_isr
<4>[ 2915.337013] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90000
<4>[ 2915.404565] gpio_keys_isr
<6>[ 2915.443428] tegra_grhost tegra_grhost: suspended
<4>[ 2915.448202] Suspend SDIO3Suspend SDIO2
<6>[ 2915.451865] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 2915.458008] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 2915.463961] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 2915.469880] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 2915.477918] DVFS set core at 1200mV
<3>[ 2915.482118] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
<3>[ 2915.488936] PM: Device power.0 failed to suspend late: error -11
<3>[ 2915.495195] PM: Some devices failed to power down
<6>[ 2915.505268] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 2915.511197] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 2915.517116] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 2915.522986] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 2915.529681] Resume SDIO2
<6>[ 2915.532135] wakeup wake lock: mmc_delayed_work
<4>[ 2915.537642] Resume SDIO3gpio_keys_isr
<4>[ 2915.623091] switch-dock: dock_switch_work_func
<4>[ 2915.627735] h2w: offswitch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 2915.679249] gpio_keys_isr
<4>[ 2915.799761] gpio_keys_isr
<6>[ 2915.826060] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 2915.901172] gpio_keys_isr
<4>[ 2916.220150] gpio_keys_isr
<4>[ 2916.315085] gpio_keys_isr
<4>[ 2916.398396] Restarting tasks ...
<6>[ 2916.408347] nvrm_notifier_show: blocking
<4>[ 2916.417953] done.
<6>[ 2916.419922] tegra_pm_notifier: start processing event=4
<6>[ 2916.425395] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 2916.429205] notify_daemon: wait for nvrm_daemon
<6>[ 2916.437485] tegra_pm_notifier: finished processing event=4
<6>[ 2916.437648] nvrm_notifier_show: blocking
<4>[ 2916.440250] gpio_keys_isr
<6>[ 2916.453371] suspend: exit suspend, ret = 0 (2010-12-25 17:58:50.615197150 UTC)
<6>[ 2916.705173] PM: Syncing filesystems ... done.
<6>[ 2916.902603] tegra_pm_notifier: start processing event=3
<6>[ 2916.902685] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 2916.903021] notify_daemon: wait for nvrm_daemon
<6>[ 2916.906721] nvrm_notifier_show: blocking
<6>[ 2916.906781] tegra_pm_notifier: finished processing event=3
<4>[ 2916.906813] Freezing user space processes ...
<6>[ 2916.916502] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 2916.956909] (elapsed 0.05 seconds) done.
<4>[ 2916.960869] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 2917.006454] tegra_grhost tegra_grhost: suspending
<4>[ 2917.162623] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<4>[ 2917.372994] Release quickly(LP1) -->Out.
<6>[ 2917.736102] tegra_grhost tegra_grhost: suspended
<4>[ 2917.741186] Suspend SDIO3Suspend SDIO2
<6>[ 2917.745056] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 2917.751211] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 2917.757226] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 2917.763233] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 2917.770409] DVFS set core at 1200mV
<3>[ 2917.774674] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
<3>[ 2917.781494] PM: Device power.0 failed to suspend late: error -11
<3>[ 2917.787780] PM: Some devices failed to power down
<6>[ 2917.797837] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 2917.803761] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 2917.809633] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 2917.815542] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 2917.822252] Resume SDIO2
<6>[ 2917.824779] wakeup wake lock: mmc_delayed_work
<4>[ 2917.830232] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 2917.914758] switch-dock: desktop_dock = 0h2w: offswitch-dock: state = 0
<6>[ 2918.072560] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 2918.763608] Restarting tasks ...
<6>[ 2918.768570] nvrm_notifier_show: blocking
<4>[ 2918.774787] done.
<6>[ 2918.776305] request_suspend_state: wakeup (3->0) at 674353826619 (2010-12-25 17:58:53.332658039 UTC)
<6>[ 2918.786076] tegra_pm_notifier: start processing event=4
<6>[ 2918.791509] notify_daemon: wait for nvrm_daemon
<6>[ 2918.796158] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 2918.809484] nvrm_notifier_show: blocking
<6>[ 2918.813546] tegra_pm_notifier: finished processing event=4
<6>[ 2918.819398] suspend: exit suspend, ret = 0 (2010-12-25 17:58:53.375764043 UTC)
<6>[ 2918.829644] nvrm_notifier_show: returning with 'PM_DISPLAY_ON'
<6>[ 2918.836047] notify_daemon: wait for nvrm_daemon
<4>[ 2918.840873] PM_SCREEN_IS_OFF set to 0
<6>[ 2919.188879] nvrm_notifier_show: blocking
<4>[ 2941.617843] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90004
<4>[ 2941.757539] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90000
<4>[ 2957.037550] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90008
<4>[ 2957.167859] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90000
<4>[ 2976.927540] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90004
<4>[ 2977.039658] SO340010: gpio_val=0xc0980000, button_val = 0xdbb90000
I had to press the power button twice to get it to wake up since the first press didn't seem to do anything. You can see it looks like it woke, tried to suspend again, then woke again (if not even a bit more glitchy than that). There's the false wakeup, the error -11 failed to suspend - I don't think those are part of a normal, healthy wakeup procedure.
While not crystal clear to me, I suspect that something visible here, possibly the pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11 is at the heart of the lag issue.
It would be very helpful is somebody else would try taking a dmesg snapshot after a laggy wake-up and see if you see any of the same stuff (from the terminal emulator type dmesg > /sdcard/dmesg.out and then copy the dmesg.out file from your /sdcard area to your desktop).
I'll reboot, re-sleep and see if a second dmesg snapshot looks similar, then compare to a healthy wake-up.

I built this kernel yesterday just before we left for vacation. It worked fine when I mixed it with vegan4 but had issues with making the market fix work. Tried a few times but I can't get full market functionality. It seems to fix the lag when turning it on but I forgot my tablet for further testing. If anyone is interested, just unzip and put this boot.img under vegan's zip file to replace the boot.img.
Please let me know how it goes. BTW, clockwork installation is a must.

Replicated lag-on-wake again, again the schizo suspending-and-resuming resulting in an error -11 (see time==513):
Code:
<4>[ 426.333956] Enabling non-boot CPUs ...
<4>[ 426.397867] CPU1: Booted secondary processor
<7>[ 426.398040] CPU0 attaching NULL sched-domain.
<7>[ 426.577293] CPU0 attaching sched-domain:
<7>[ 426.577335] domain 0: span 0-1 level CPU
<7>[ 426.577375] groups: 0 1
<7>[ 426.577438] CPU1 attaching sched-domain:
<7>[ 426.577471] domain 0: span 0-1 level CPU
<7>[ 426.577506] groups: 1 0
<4>[ 426.578097] CPU1 is up
<4>[ 426.585199] *** Wakeup from LP1 ***
<6>[ 426.595087] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 426.601029] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 426.606945] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 426.612815] tegra_uart tegra_uart.4: tegra_uart_resume called
<6>[ 426.618916] wakeup wake lock: mmc_delayed_work
<4>[ 426.624301] Resume SDIO2Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 426.715163] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 426.721348] h2w: offRestarting tasks ...
<6>[ 426.899672] nvrm_notifier_show: blocking
<4>[ 426.918553] done.
<6>[ 426.920495] tegra_pm_notifier: start processing event=4
<6>[ 426.926471] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 426.932745] notify_daemon: wait for nvrm_daemon
<6>[ 426.940765] nvrm_notifier_show: blocking
<6>[ 426.940789] tegra_pm_notifier: finished processing event=4
<6>[ 426.959554] suspend: exit suspend, ret = 0 (2010-12-25 18:20:05.571657007 UTC)
<6>[ 427.005290] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 429.134609] STA connect received 1
<6>[ 448.012941] PM: Syncing filesystems ... done.
<6>[ 448.426906] tegra_pm_notifier: start processing event=3
<6>[ 448.432159] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 448.438468] notify_daemon: wait for nvrm_daemon
<6>[ 448.446870] tegra_pm_notifier: finished processing event=3
<6>[ 448.446936] nvrm_notifier_show: blocking
<4>[ 448.458098] Freezing user space processes ...
<6>[ 448.464042] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 448.472020] (elapsed 0.00 seconds) done.
<4>[ 448.475979] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 448.505007] tegra_grhost tegra_grhost: suspending
<6>[ 448.509716] tegra_grhost tegra_grhost: suspended
<4>[ 448.514562] Suspend SDIO3Suspend SDIO2
<6>[ 448.518248] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 448.524417] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 448.530374] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 448.536324] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 448.544509] DVFS set core at 1200mV
<4>[ 448.558549] RM power state before suspend: Active (2)
<4>[ 448.563627] Active Module: 0x16
<4>[ 448.575870] Disabling non-boot CPUs ...
<7>[ 448.579787] CPU0 attaching NULL sched-domain.
<7>[ 448.579834] CPU1 attaching NULL sched-domain.
<7>[ 448.684904] CPU0 attaching NULL sched-domain.
<5>[ 448.685686] CPU1: clean shutdown
<4>[ 480.508813] Enabling non-boot CPUs ...
<4>[ 480.568298] CPU1: Booted secondary processor
<7>[ 480.568476] CPU0 attaching NULL sched-domain.
<7>[ 480.676031] CPU0 attaching sched-domain:
<7>[ 480.676072] domain 0: span 0-1 level CPU
<7>[ 480.676113] groups: 0 1
<7>[ 480.676177] CPU1 attaching sched-domain:
<7>[ 480.676210] domain 0: span 0-1 level CPU
<7>[ 480.676245] groups: 1 0
<4>[ 480.676837] CPU1 is up
<4>[ 480.683941] *** Wakeup from LP1 ***
<4>[ 480.688019] gpio_keys_isr
<6>[ 480.692014] wakeup wake lock: event0-913
<6>[ 480.698689] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 480.704567] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 480.710438] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 480.716372] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 480.723324] Resume SDIO2Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 480.823245] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 480.829430] h2w: ongpio_keys_isr
<4>[ 480.878910] Restarting tasks ...
<6>[ 480.891029] nvrm_notifier_show: blocking
<4>[ 480.907919] done.
<6>[ 480.909857] tegra_pm_notifier: start processing event=4
<6>[ 480.915203] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 480.921261] notify_daemon: wait for nvrm_daemon
<6>[ 480.932125] nvrm_notifier_show: blocking
<6>[ 480.936834] tegra_pm_notifier: finished processing event=4
<6>[ 480.951908] suspend: exit suspend, ret = 0 (2010-12-25 18:20:59.573952008 UTC)
<6>[ 481.001596] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 481.347112] gpio_keys_isr
<6>[ 481.401784] PM: Syncing filesystems ... gpio_keys_isr
<4>[ 484.216910] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<6>[ 484.232979] request_suspend_state: wakeup (3->0) at 160183913324 (2010-12-25 18:21:02.855013324 UTC)
<4>[ 484.378285] Left2Light(noflag)-->Out.
<6>[ 484.959180] request_suspend_state: sleep (0->3) at 160910114397 (2010-12-25 18:21:03.581215397 UTC)
<4>[ 485.631786] done.
<6>[ 485.646998] tegra_pm_notifier: start processing event=3
<6>[ 485.652282] notify_daemon: wait for nvrm_daemon
<6>[ 485.652297] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 485.666729] tegra_pm_notifier: finished processing event=3
<6>[ 485.666802] nvrm_notifier_show: blocking
<4>[ 485.678182] Freezing user space processes ...
<6>[ 485.684152] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 485.688473]
<3>[ 485.688490] Freezing of tasks aborted after 0.00 seconds (304 tasks refusing to freeze):
<4>[ 485.688938]
<4>[ 485.688946] Restarting tasks ... done.
<6>[ 485.693044] tegra_pm_notifier: start processing event=4
<6>[ 485.693058] notify_daemon: wait for nvrm_daemon
<6>[ 485.715126] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 485.722917] tegra_pm_notifier: finished processing event=4
<6>[ 485.722975] nvrm_notifier_show: blocking
<6>[ 485.734571] suspend: exit suspend, ret = -16 (2010-12-25 18:21:04.356609470 UTC)
<6>[ 489.559256] PM: Syncing filesystems ... done.
<6>[ 489.853201] tegra_pm_notifier: start processing event=3
<6>[ 489.858473] notify_daemon: wait for nvrm_daemon
<6>[ 489.858495] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 489.872985] tegra_pm_notifier: finished processing event=3
<6>[ 489.873054] nvrm_notifier_show: blocking
<4>[ 489.884355] Freezing user space processes ...
<6>[ 489.890324] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 489.896842] (elapsed 0.00 seconds) done.
<4>[ 489.900805] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 489.931573] tegra_grhost tegra_grhost: suspending
<6>[ 489.936283] tegra_grhost tegra_grhost: suspended
<4>[ 489.941162] Suspend SDIO3Suspend SDIO2
<6>[ 489.944851] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 489.951029] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 489.956991] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 489.962944] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 489.971227] DVFS set core at 1200mV
<4>[ 489.984757] RM power state before suspend: Active (2)
<4>[ 489.989834] Active Module: 0x16
<4>[ 490.002059] Disabling non-boot CPUs ...
<7>[ 490.005968] CPU0 attaching NULL sched-domain.
<7>[ 490.006015] CPU1 attaching NULL sched-domain.
<7>[ 490.113730] CPU0 attaching NULL sched-domain.
<5>[ 490.114511] CPU1: clean shutdown
<4>[ 494.398795] Enabling non-boot CPUs ...
<4>[ 494.461892] CPU1: Booted secondary processor
<7>[ 494.462069] CPU0 attaching NULL sched-domain.
<7>[ 494.641461] CPU0 attaching sched-domain:
<7>[ 494.641503] domain 0: span 0-1 level CPU
<7>[ 494.641543] groups: 0 1
<7>[ 494.641607] CPU1 attaching sched-domain:
<7>[ 494.641640] domain 0: span 0-1 level CPU
<7>[ 494.641674] groups: 1 0
<4>[ 494.642262] CPU1 is up
<4>[ 494.649369] *** Wakeup from LP1 ***
<4>[ 494.653384] gpio_keys_isr
<6>[ 494.661558] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 494.667440] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 494.673312] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 494.679239] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 494.685965] Resume SDIO2
<6>[ 494.688420] wakeup wake lock: mmc_delayed_work
<4>[ 494.693859] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 494.770970] switch-dock: desktop_dock = 0gpio_keys_isr
<4>[ 494.776252] switch-dock: state = 0
<4>[ 494.779811] h2w: onRestarting tasks ...
<6>[ 494.823447] nvrm_notifier_show: blocking
<4>[ 494.847457] done.
<6>[ 494.849538] tegra_pm_notifier: start processing event=4
<6>[ 494.854787] notify_daemon: wait for nvrm_daemon
<6>[ 494.854807] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 494.870807] nvrm_notifier_show: blocking
<6>[ 494.886154] tegra_pm_notifier: finished processing event=4
<6>[ 494.939900] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<6>[ 494.951799] suspend: exit suspend, ret = 0 (2010-12-25 18:21:13.632966013 UTC)
<4>[ 495.095388] gpio_keys_isr
<4>[ 495.171339] gpio_keys_isr
<4>[ 495.265635] gpio_keys_isr
<4>[ 495.324107] gpio_keys_isr
<6>[ 495.380095] PM: Syncing filesystems ... gpio_keys_isr
<4>[ 495.512617] gpio_keys_isr
<4>[ 495.661902] gpio_keys_isr
<4>[ 495.710074] done.
<6>[ 495.720079] tegra_pm_notifier: start processing event=3
<6>[ 495.720116] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 495.720293] notify_daemon: wait for nvrm_daemon
<6>[ 495.743127] nvrm_notifier_show: blocking
<6>[ 495.747069] tegra_pm_notifier: finished processing event=3
<4>[ 495.752748] Freezing user space processes ...
<6>[ 495.760286] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 495.766643] (elapsed 0.00 seconds) done.
<4>[ 495.770600] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 495.819838] tegra_grhost tegra_grhost: suspending
<6>[ 495.959112] tegra_grhost tegra_grhost: suspended
<4>[ 495.963913] Suspend SDIO3Suspend SDIO2
<6>[ 495.967663] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 495.973800] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 495.979747] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 495.985694] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 495.993784] DVFS set core at 1200mV
<4>[ 496.005585] RM power state before suspend: Active (2)
<4>[ 496.010662] Active Module: 0x16
<4>[ 496.022866] Disabling non-boot CPUs ...
<7>[ 496.026837] CPU0 attaching NULL sched-domain.
<7>[ 496.026886] CPU1 attaching NULL sched-domain.
<7>[ 496.172300] CPU0 attaching NULL sched-domain.
<5>[ 496.173074] CPU1: clean shutdown
<4>[ 498.222010] Enabling non-boot CPUs ...
<4>[ 498.263490] CPU1: Booted secondary processor
<7>[ 498.263670] CPU0 attaching NULL sched-domain.
<7>[ 498.386579] CPU0 attaching sched-domain:
<7>[ 498.386621] domain 0: span 0-1 level CPU
<7>[ 498.386660] groups: 0 1
<7>[ 498.386725] CPU1 attaching sched-domain:
<7>[ 498.386757] domain 0: span 0-1 level CPU
<7>[ 498.386791] groups: 1 0
<4>[ 498.387380] CPU1 is up
<4>[ 498.394485] *** Wakeup from LP1 ***
<4>[ 498.398594] PMU Resume Irq. In 1, 0 --> Send First KEY_F4(LP1) -->
<6>[ 498.404650] wakeup wake lock: gpio_f4_wake
<4>[ 498.415495] Send a simulate KEY_F4 ****
<6>[ 498.421622] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 498.436757] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 498.451684] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 498.467021] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 498.561443] Release quickly(LP1) -->Out.
<4>[ 498.566280] Resume SDIO2Resume SDIO3h2w: onswitch-dock: dock_switch_work_func
<4>[ 499.198942] switch-dock: desktop_dock = 0switch-dock: state = 0
<6>[ 499.393196] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 500.415072] Restarting tasks ...
<6>[ 500.420086] nvrm_notifier_show: blocking
<6>[ 500.432446] request_suspend_state: wakeup (3->0) at 170061520136 (2010-12-25 18:21:18.720073021 UTC)
<4>[ 500.444020] done.
<6>[ 500.447932] tegra_pm_notifier: start processing event=4
<6>[ 500.454058] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 500.461749] notify_daemon: wait for nvrm_daemon
<6>[ 500.468825] nvrm_notifier_show: blocking
<6>[ 500.474256] tegra_pm_notifier: finished processing event=4
<6>[ 500.481222] suspend: exit suspend, ret = 0 (2010-12-25 18:21:18.768889026 UTC)
<6>[ 500.488483] nvrm_notifier_show: returning with 'PM_DISPLAY_ON'
<6>[ 500.490920] notify_daemon: wait for nvrm_daemon
<4>[ 500.500234] PM_SCREEN_IS_OFF set to 0
<6>[ 500.821240] nvrm_notifier_show: blocking
<6>[ 501.114867] request_suspend_state: sleep (0->3) at 170743970205 (2010-12-25 18:21:19.402526090 UTC)
<4>[ 502.131509] stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
<4>[ 502.139372] SO340010: so340010_kbd_early_suspend() IN
<4>[ 502.145236] SO340010: so340010_kbd_early_suspend() OUT
<6>[ 502.150508] notify_daemon: wait for nvrm_daemon
<6>[ 502.150523] nvrm_notifier_show: returning with 'PM_DISPLAY_OFF'
<4>[ 502.150538] PM_SCREEN_IS_OFF set to 1
<6>[ 502.215332] nvrm_notifier_show: blocking
<6>[ 503.791096] PM: Syncing filesystems ... done.
<6>[ 504.193553] tegra_pm_notifier: start processing event=3
<6>[ 504.193579] notify_daemon: wait for nvrm_daemon
<6>[ 504.193604] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 504.215560] tegra_pm_notifier: finished processing event=3
<4>[ 504.222117] Freezing user space processes ...
<6>[ 504.226511] nvrm_notifier_show: blocking
<6>[ 504.230637] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 504.237318] (elapsed 0.01 seconds) done.
<4>[ 504.241256] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 504.265702] tegra_grhost tegra_grhost: suspending
<6>[ 505.163335] tegra_grhost tegra_grhost: suspended
<4>[ 505.168142] Suspend SDIO3Suspend SDIO2
<6>[ 505.171913] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 505.178063] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 505.184043] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 505.190000] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 505.198231] DVFS set core at 1200mV
<4>[ 505.208426] RM power state before suspend: Active (2)
<4>[ 505.213503] Active Module: 0x16
<4>[ 505.225777] Disabling non-boot CPUs ...
<7>[ 505.229807] CPU0 attaching NULL sched-domain.
<7>[ 505.229854] CPU1 attaching NULL sched-domain.
<7>[ 505.371149] CPU0 attaching NULL sched-domain.
<5>[ 505.371924] CPU1: clean shutdown
<4>[ 510.490962] Enabling non-boot CPUs ...
<4>[ 510.537206] CPU1: Booted secondary processor
<7>[ 510.537383] CPU0 attaching NULL sched-domain.
<4>[ 510.611430] dhdsdio_htclk: HT Avail request error: -35
<6>[ 510.632664] wakeup wake lock: dhd_watchdog_thread
<7>[ 510.695049] CPU0 attaching sched-domain:
<7>[ 510.695090] domain 0: span 0-1 level CPU
<7>[ 510.695131] groups: 0 1
<7>[ 510.695195] CPU1 attaching sched-domain:
<7>[ 510.695228] domain 0: span 0-1 level CPU
<7>[ 510.695263] groups: 1 0
<4>[ 510.695853] CPU1 is up
<4>[ 510.702960] *** Wakeup from LP1 ***
<4>[ 510.707069] gpio_keys_isr
<6>[ 510.715736] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 510.721722] tegra_uart tegra_uart.2: tegra_uart_resume called
<4>[ 510.727677] SO340010: gpio_val=0xc0980000, button_val = 0xdba40000
<6>[ 510.734010] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 510.739951] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 510.746657] Resume SDIO2Resume SDIO3gpio_keys_isr
<4>[ 510.821256] switch-dock: dock_switch_work_func
<4>[ 510.825815] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 510.831997] h2w: offRestarting tasks ... gpio_keys_isr
<6>[ 510.888704] nvrm_notifier_show: blocking
<4>[ 510.928414] done.
<6>[ 510.930350] tegra_pm_notifier: start processing event=4
<6>[ 510.949863] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 510.955922] notify_daemon: wait for nvrm_daemon
<6>[ 510.961800] nvrm_notifier_show: blocking
<6>[ 510.967375] tegra_pm_notifier: finished processing event=4
<6>[ 510.992735] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<6>[ 511.023651] suspend: exit suspend, ret = 0 (2010-12-25 18:21:29.648418015 UTC)
<4>[ 511.050324] gpio_keys_isr
<4>[ 511.182853] gpio_keys_isr
<4>[ 511.383731] gpio_keys_isr
<4>[ 511.468647] gpio_keys_isr
<4>[ 511.623606] gpio_keys_isr
<4>[ 511.772148] gpio_keys_isr
<4>[ 511.965776] gpio_keys_isr
<6>[ 512.102903] PM: Syncing filesystems ... done.
<6>[ 512.312248] tegra_pm_notifier: start processing event=3
<6>[ 512.312289] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 512.312477] notify_daemon: wait for nvrm_daemon
<6>[ 512.336440] nvrm_notifier_show: blocking
<6>[ 512.340379] tegra_pm_notifier: finished processing event=3
<4>[ 512.345892] Freezing user space processes ...
<6>[ 512.353673] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 512.360104] (elapsed 0.00 seconds) done.
<4>[ 512.364062] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 512.413839] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<4>[ 512.824978] Release quickly(LP1) -->Out.
<6>[ 512.830109] tegra_grhost tegra_grhost: suspending
<6>[ 512.834975] tegra_grhost tegra_grhost: suspended
<4>[ 512.975485] Suspend SDIO3Suspend SDIO2
<6>[ 512.979177] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 512.985291] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 512.991262] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 512.997212] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 513.005350] DVFS set core at 1200mV
<3>[ 513.009606] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
<3>[ 513.016425] PM: Device power.0 failed to suspend late: error -11
<3>[ 513.022654] PM: Some devices failed to power down
<6>[ 513.032678] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 513.038553] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 513.044418] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 513.050333] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 513.057018] Resume SDIO2
<6>[ 513.059476] wakeup wake lock: mmc_delayed_work
<4>[ 513.064946] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 513.155124] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 513.161310] h2w: off
<6>[ 513.303637] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 514.210503] Restarting tasks ...
<6>[ 514.215401] nvrm_notifier_show: blocking
<6>[ 514.224630] request_suspend_state: wakeup (3->0) at 178741913895 (2010-12-25 18:21:32.849360251 UTC)
<4>[ 514.238668] done.
<6>[ 514.243026] tegra_pm_notifier: start processing event=4
<6>[ 514.259163] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 514.268324] notify_daemon: wait for nvrm_daemon
<6>[ 514.277032] nvrm_notifier_show: blocking
<6>[ 514.282184] tegra_pm_notifier: finished processing event=4
<6>[ 514.308845] suspend: exit suspend, ret = 0 (2010-12-25 18:21:32.933580259 UTC)
<6>[ 514.340146] nvrm_notifier_show: returning with 'PM_DISPLAY_ON'
<6>[ 514.347391] notify_daemon: wait for nvrm_daemon
<4>[ 514.353767] PM_SCREEN_IS_OFF set to 0
<6>[ 514.796232] nvrm_notifier_show: blocking
<4>[ 521.222850] h2w: h2w_switch_irq_isrh2w: onSO340010: gpio_val=0xc0980000, button_val = 0xdba40004
<4>[ 533.359945] SO340010: gpio_val=0xc0980000, button_val = 0xdba40000
Going to go peek through the source and try to trace through platform_pm_suspend_noirq and see if I can figure anything out...
Oh, and @clemsyn, I already am using my own build from source of the kernel, and the issue is still there. So unless you rolled some patches into the power management/cpufreq/suspend-resume code, I bet the issue is still there in your kernel, just hasn't happened yet on your tablet since updating your kernel.
EDIT: hmm, I've found other references to that error -11 issue with other Android devices. Seems to be a symptom of rapid suspend/resume cycling. I can't tell if the suspend-resume cycle is a symptom of the slowdown or the cause though. I am now suspecting more likely a symptom than a cause, i.e. the tablet is stuck on slow CPU mode so attempts to wake take forever to go through, thus the system takes a couple button presses before it finally wakes.

rcgabriel said:
Replicated lag-on-wake again, again the schizo suspending-and-resuming resulting in an error -11 (see time==513):
Code:
<4>[ 426.333956] Enabling non-boot CPUs ...
<4>[ 426.397867] CPU1: Booted secondary processor
<7>[ 426.398040] CPU0 attaching NULL sched-domain.
<7>[ 426.577293] CPU0 attaching sched-domain:
<7>[ 426.577335] domain 0: span 0-1 level CPU
<7>[ 426.577375] groups: 0 1
<7>[ 426.577438] CPU1 attaching sched-domain:
<7>[ 426.577471] domain 0: span 0-1 level CPU
<7>[ 426.577506] groups: 1 0
<4>[ 426.578097] CPU1 is up
<4>[ 426.585199] *** Wakeup from LP1 ***
<6>[ 426.595087] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 426.601029] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 426.606945] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 426.612815] tegra_uart tegra_uart.4: tegra_uart_resume called
<6>[ 426.618916] wakeup wake lock: mmc_delayed_work
<4>[ 426.624301] Resume SDIO2Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 426.715163] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 426.721348] h2w: offRestarting tasks ...
<6>[ 426.899672] nvrm_notifier_show: blocking
<4>[ 426.918553] done.
<6>[ 426.920495] tegra_pm_notifier: start processing event=4
<6>[ 426.926471] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 426.932745] notify_daemon: wait for nvrm_daemon
<6>[ 426.940765] nvrm_notifier_show: blocking
<6>[ 426.940789] tegra_pm_notifier: finished processing event=4
<6>[ 426.959554] suspend: exit suspend, ret = 0 (2010-12-25 18:20:05.571657007 UTC)
<6>[ 427.005290] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 429.134609] STA connect received 1
<6>[ 448.012941] PM: Syncing filesystems ... done.
<6>[ 448.426906] tegra_pm_notifier: start processing event=3
<6>[ 448.432159] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 448.438468] notify_daemon: wait for nvrm_daemon
<6>[ 448.446870] tegra_pm_notifier: finished processing event=3
<6>[ 448.446936] nvrm_notifier_show: blocking
<4>[ 448.458098] Freezing user space processes ...
<6>[ 448.464042] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 448.472020] (elapsed 0.00 seconds) done.
<4>[ 448.475979] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 448.505007] tegra_grhost tegra_grhost: suspending
<6>[ 448.509716] tegra_grhost tegra_grhost: suspended
<4>[ 448.514562] Suspend SDIO3Suspend SDIO2
<6>[ 448.518248] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 448.524417] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 448.530374] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 448.536324] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 448.544509] DVFS set core at 1200mV
<4>[ 448.558549] RM power state before suspend: Active (2)
<4>[ 448.563627] Active Module: 0x16
<4>[ 448.575870] Disabling non-boot CPUs ...
<7>[ 448.579787] CPU0 attaching NULL sched-domain.
<7>[ 448.579834] CPU1 attaching NULL sched-domain.
<7>[ 448.684904] CPU0 attaching NULL sched-domain.
<5>[ 448.685686] CPU1: clean shutdown
<4>[ 480.508813] Enabling non-boot CPUs ...
<4>[ 480.568298] CPU1: Booted secondary processor
<7>[ 480.568476] CPU0 attaching NULL sched-domain.
<7>[ 480.676031] CPU0 attaching sched-domain:
<7>[ 480.676072] domain 0: span 0-1 level CPU
<7>[ 480.676113] groups: 0 1
<7>[ 480.676177] CPU1 attaching sched-domain:
<7>[ 480.676210] domain 0: span 0-1 level CPU
<7>[ 480.676245] groups: 1 0
<4>[ 480.676837] CPU1 is up
<4>[ 480.683941] *** Wakeup from LP1 ***
<4>[ 480.688019] gpio_keys_isr
<6>[ 480.692014] wakeup wake lock: event0-913
<6>[ 480.698689] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 480.704567] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 480.710438] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 480.716372] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 480.723324] Resume SDIO2Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 480.823245] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 480.829430] h2w: ongpio_keys_isr
<4>[ 480.878910] Restarting tasks ...
<6>[ 480.891029] nvrm_notifier_show: blocking
<4>[ 480.907919] done.
<6>[ 480.909857] tegra_pm_notifier: start processing event=4
<6>[ 480.915203] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 480.921261] notify_daemon: wait for nvrm_daemon
<6>[ 480.932125] nvrm_notifier_show: blocking
<6>[ 480.936834] tegra_pm_notifier: finished processing event=4
<6>[ 480.951908] suspend: exit suspend, ret = 0 (2010-12-25 18:20:59.573952008 UTC)
<6>[ 481.001596] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 481.347112] gpio_keys_isr
<6>[ 481.401784] PM: Syncing filesystems ... gpio_keys_isr
<4>[ 484.216910] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<6>[ 484.232979] request_suspend_state: wakeup (3->0) at 160183913324 (2010-12-25 18:21:02.855013324 UTC)
<4>[ 484.378285] Left2Light(noflag)-->Out.
<6>[ 484.959180] request_suspend_state: sleep (0->3) at 160910114397 (2010-12-25 18:21:03.581215397 UTC)
<4>[ 485.631786] done.
<6>[ 485.646998] tegra_pm_notifier: start processing event=3
<6>[ 485.652282] notify_daemon: wait for nvrm_daemon
<6>[ 485.652297] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 485.666729] tegra_pm_notifier: finished processing event=3
<6>[ 485.666802] nvrm_notifier_show: blocking
<4>[ 485.678182] Freezing user space processes ...
<6>[ 485.684152] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 485.688473]
<3>[ 485.688490] Freezing of tasks aborted after 0.00 seconds (304 tasks refusing to freeze):
<4>[ 485.688938]
<4>[ 485.688946] Restarting tasks ... done.
<6>[ 485.693044] tegra_pm_notifier: start processing event=4
<6>[ 485.693058] notify_daemon: wait for nvrm_daemon
<6>[ 485.715126] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 485.722917] tegra_pm_notifier: finished processing event=4
<6>[ 485.722975] nvrm_notifier_show: blocking
<6>[ 485.734571] suspend: exit suspend, ret = -16 (2010-12-25 18:21:04.356609470 UTC)
<6>[ 489.559256] PM: Syncing filesystems ... done.
<6>[ 489.853201] tegra_pm_notifier: start processing event=3
<6>[ 489.858473] notify_daemon: wait for nvrm_daemon
<6>[ 489.858495] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 489.872985] tegra_pm_notifier: finished processing event=3
<6>[ 489.873054] nvrm_notifier_show: blocking
<4>[ 489.884355] Freezing user space processes ...
<6>[ 489.890324] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 489.896842] (elapsed 0.00 seconds) done.
<4>[ 489.900805] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 489.931573] tegra_grhost tegra_grhost: suspending
<6>[ 489.936283] tegra_grhost tegra_grhost: suspended
<4>[ 489.941162] Suspend SDIO3Suspend SDIO2
<6>[ 489.944851] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 489.951029] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 489.956991] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 489.962944] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 489.971227] DVFS set core at 1200mV
<4>[ 489.984757] RM power state before suspend: Active (2)
<4>[ 489.989834] Active Module: 0x16
<4>[ 490.002059] Disabling non-boot CPUs ...
<7>[ 490.005968] CPU0 attaching NULL sched-domain.
<7>[ 490.006015] CPU1 attaching NULL sched-domain.
<7>[ 490.113730] CPU0 attaching NULL sched-domain.
<5>[ 490.114511] CPU1: clean shutdown
<4>[ 494.398795] Enabling non-boot CPUs ...
<4>[ 494.461892] CPU1: Booted secondary processor
<7>[ 494.462069] CPU0 attaching NULL sched-domain.
<7>[ 494.641461] CPU0 attaching sched-domain:
<7>[ 494.641503] domain 0: span 0-1 level CPU
<7>[ 494.641543] groups: 0 1
<7>[ 494.641607] CPU1 attaching sched-domain:
<7>[ 494.641640] domain 0: span 0-1 level CPU
<7>[ 494.641674] groups: 1 0
<4>[ 494.642262] CPU1 is up
<4>[ 494.649369] *** Wakeup from LP1 ***
<4>[ 494.653384] gpio_keys_isr
<6>[ 494.661558] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 494.667440] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 494.673312] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 494.679239] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 494.685965] Resume SDIO2
<6>[ 494.688420] wakeup wake lock: mmc_delayed_work
<4>[ 494.693859] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 494.770970] switch-dock: desktop_dock = 0gpio_keys_isr
<4>[ 494.776252] switch-dock: state = 0
<4>[ 494.779811] h2w: onRestarting tasks ...
<6>[ 494.823447] nvrm_notifier_show: blocking
<4>[ 494.847457] done.
<6>[ 494.849538] tegra_pm_notifier: start processing event=4
<6>[ 494.854787] notify_daemon: wait for nvrm_daemon
<6>[ 494.854807] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 494.870807] nvrm_notifier_show: blocking
<6>[ 494.886154] tegra_pm_notifier: finished processing event=4
<6>[ 494.939900] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<6>[ 494.951799] suspend: exit suspend, ret = 0 (2010-12-25 18:21:13.632966013 UTC)
<4>[ 495.095388] gpio_keys_isr
<4>[ 495.171339] gpio_keys_isr
<4>[ 495.265635] gpio_keys_isr
<4>[ 495.324107] gpio_keys_isr
<6>[ 495.380095] PM: Syncing filesystems ... gpio_keys_isr
<4>[ 495.512617] gpio_keys_isr
<4>[ 495.661902] gpio_keys_isr
<4>[ 495.710074] done.
<6>[ 495.720079] tegra_pm_notifier: start processing event=3
<6>[ 495.720116] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 495.720293] notify_daemon: wait for nvrm_daemon
<6>[ 495.743127] nvrm_notifier_show: blocking
<6>[ 495.747069] tegra_pm_notifier: finished processing event=3
<4>[ 495.752748] Freezing user space processes ...
<6>[ 495.760286] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 495.766643] (elapsed 0.00 seconds) done.
<4>[ 495.770600] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 495.819838] tegra_grhost tegra_grhost: suspending
<6>[ 495.959112] tegra_grhost tegra_grhost: suspended
<4>[ 495.963913] Suspend SDIO3Suspend SDIO2
<6>[ 495.967663] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 495.973800] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 495.979747] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 495.985694] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 495.993784] DVFS set core at 1200mV
<4>[ 496.005585] RM power state before suspend: Active (2)
<4>[ 496.010662] Active Module: 0x16
<4>[ 496.022866] Disabling non-boot CPUs ...
<7>[ 496.026837] CPU0 attaching NULL sched-domain.
<7>[ 496.026886] CPU1 attaching NULL sched-domain.
<7>[ 496.172300] CPU0 attaching NULL sched-domain.
<5>[ 496.173074] CPU1: clean shutdown
<4>[ 498.222010] Enabling non-boot CPUs ...
<4>[ 498.263490] CPU1: Booted secondary processor
<7>[ 498.263670] CPU0 attaching NULL sched-domain.
<7>[ 498.386579] CPU0 attaching sched-domain:
<7>[ 498.386621] domain 0: span 0-1 level CPU
<7>[ 498.386660] groups: 0 1
<7>[ 498.386725] CPU1 attaching sched-domain:
<7>[ 498.386757] domain 0: span 0-1 level CPU
<7>[ 498.386791] groups: 1 0
<4>[ 498.387380] CPU1 is up
<4>[ 498.394485] *** Wakeup from LP1 ***
<4>[ 498.398594] PMU Resume Irq. In 1, 0 --> Send First KEY_F4(LP1) -->
<6>[ 498.404650] wakeup wake lock: gpio_f4_wake
<4>[ 498.415495] Send a simulate KEY_F4 ****
<6>[ 498.421622] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 498.436757] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 498.451684] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 498.467021] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 498.561443] Release quickly(LP1) -->Out.
<4>[ 498.566280] Resume SDIO2Resume SDIO3h2w: onswitch-dock: dock_switch_work_func
<4>[ 499.198942] switch-dock: desktop_dock = 0switch-dock: state = 0
<6>[ 499.393196] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 500.415072] Restarting tasks ...
<6>[ 500.420086] nvrm_notifier_show: blocking
<6>[ 500.432446] request_suspend_state: wakeup (3->0) at 170061520136 (2010-12-25 18:21:18.720073021 UTC)
<4>[ 500.444020] done.
<6>[ 500.447932] tegra_pm_notifier: start processing event=4
<6>[ 500.454058] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 500.461749] notify_daemon: wait for nvrm_daemon
<6>[ 500.468825] nvrm_notifier_show: blocking
<6>[ 500.474256] tegra_pm_notifier: finished processing event=4
<6>[ 500.481222] suspend: exit suspend, ret = 0 (2010-12-25 18:21:18.768889026 UTC)
<6>[ 500.488483] nvrm_notifier_show: returning with 'PM_DISPLAY_ON'
<6>[ 500.490920] notify_daemon: wait for nvrm_daemon
<4>[ 500.500234] PM_SCREEN_IS_OFF set to 0
<6>[ 500.821240] nvrm_notifier_show: blocking
<6>[ 501.114867] request_suspend_state: sleep (0->3) at 170743970205 (2010-12-25 18:21:19.402526090 UTC)
<4>[ 502.131509] stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
<4>[ 502.139372] SO340010: so340010_kbd_early_suspend() IN
<4>[ 502.145236] SO340010: so340010_kbd_early_suspend() OUT
<6>[ 502.150508] notify_daemon: wait for nvrm_daemon
<6>[ 502.150523] nvrm_notifier_show: returning with 'PM_DISPLAY_OFF'
<4>[ 502.150538] PM_SCREEN_IS_OFF set to 1
<6>[ 502.215332] nvrm_notifier_show: blocking
<6>[ 503.791096] PM: Syncing filesystems ... done.
<6>[ 504.193553] tegra_pm_notifier: start processing event=3
<6>[ 504.193579] notify_daemon: wait for nvrm_daemon
<6>[ 504.193604] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 504.215560] tegra_pm_notifier: finished processing event=3
<4>[ 504.222117] Freezing user space processes ...
<6>[ 504.226511] nvrm_notifier_show: blocking
<6>[ 504.230637] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 504.237318] (elapsed 0.01 seconds) done.
<4>[ 504.241256] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<6>[ 504.265702] tegra_grhost tegra_grhost: suspending
<6>[ 505.163335] tegra_grhost tegra_grhost: suspended
<4>[ 505.168142] Suspend SDIO3Suspend SDIO2
<6>[ 505.171913] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 505.178063] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 505.184043] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 505.190000] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 505.198231] DVFS set core at 1200mV
<4>[ 505.208426] RM power state before suspend: Active (2)
<4>[ 505.213503] Active Module: 0x16
<4>[ 505.225777] Disabling non-boot CPUs ...
<7>[ 505.229807] CPU0 attaching NULL sched-domain.
<7>[ 505.229854] CPU1 attaching NULL sched-domain.
<7>[ 505.371149] CPU0 attaching NULL sched-domain.
<5>[ 505.371924] CPU1: clean shutdown
<4>[ 510.490962] Enabling non-boot CPUs ...
<4>[ 510.537206] CPU1: Booted secondary processor
<7>[ 510.537383] CPU0 attaching NULL sched-domain.
<4>[ 510.611430] dhdsdio_htclk: HT Avail request error: -35
<6>[ 510.632664] wakeup wake lock: dhd_watchdog_thread
<7>[ 510.695049] CPU0 attaching sched-domain:
<7>[ 510.695090] domain 0: span 0-1 level CPU
<7>[ 510.695131] groups: 0 1
<7>[ 510.695195] CPU1 attaching sched-domain:
<7>[ 510.695228] domain 0: span 0-1 level CPU
<7>[ 510.695263] groups: 1 0
<4>[ 510.695853] CPU1 is up
<4>[ 510.702960] *** Wakeup from LP1 ***
<4>[ 510.707069] gpio_keys_isr
<6>[ 510.715736] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 510.721722] tegra_uart tegra_uart.2: tegra_uart_resume called
<4>[ 510.727677] SO340010: gpio_val=0xc0980000, button_val = 0xdba40000
<6>[ 510.734010] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 510.739951] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 510.746657] Resume SDIO2Resume SDIO3gpio_keys_isr
<4>[ 510.821256] switch-dock: dock_switch_work_func
<4>[ 510.825815] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 510.831997] h2w: offRestarting tasks ... gpio_keys_isr
<6>[ 510.888704] nvrm_notifier_show: blocking
<4>[ 510.928414] done.
<6>[ 510.930350] tegra_pm_notifier: start processing event=4
<6>[ 510.949863] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 510.955922] notify_daemon: wait for nvrm_daemon
<6>[ 510.961800] nvrm_notifier_show: blocking
<6>[ 510.967375] tegra_pm_notifier: finished processing event=4
<6>[ 510.992735] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<6>[ 511.023651] suspend: exit suspend, ret = 0 (2010-12-25 18:21:29.648418015 UTC)
<4>[ 511.050324] gpio_keys_isr
<4>[ 511.182853] gpio_keys_isr
<4>[ 511.383731] gpio_keys_isr
<4>[ 511.468647] gpio_keys_isr
<4>[ 511.623606] gpio_keys_isr
<4>[ 511.772148] gpio_keys_isr
<4>[ 511.965776] gpio_keys_isr
<6>[ 512.102903] PM: Syncing filesystems ... done.
<6>[ 512.312248] tegra_pm_notifier: start processing event=3
<6>[ 512.312289] nvrm_notifier_show: returning with 'PM_SUSPEND_PREPARE'
<6>[ 512.312477] notify_daemon: wait for nvrm_daemon
<6>[ 512.336440] nvrm_notifier_show: blocking
<6>[ 512.340379] tegra_pm_notifier: finished processing event=3
<4>[ 512.345892] Freezing user space processes ...
<6>[ 512.353673] nvrm_notifier_show: false wakeup, returning with '\n'
<4>[ 512.360104] (elapsed 0.00 seconds) done.
<4>[ 512.364062] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 512.413839] PMU Resume Irq. In 1, 1 --> Send First KEY_F4(LP1) -->Send a simulate KEY_F4 ****
<4>[ 512.824978] Release quickly(LP1) -->Out.
<6>[ 512.830109] tegra_grhost tegra_grhost: suspending
<6>[ 512.834975] tegra_grhost tegra_grhost: suspended
<4>[ 512.975485] Suspend SDIO3Suspend SDIO2
<6>[ 512.979177] tegra_uart tegra_uart.4: tegra_uart_suspend called
<6>[ 512.985291] tegra_uart tegra_uart.3: tegra_uart_suspend called
<6>[ 512.991262] tegra_uart tegra_uart.2: tegra_uart_suspend called
<6>[ 512.997212] tegra_uart tegra_uart.1: tegra_uart_suspend called
<4>[ 513.005350] DVFS set core at 1200mV
<3>[ 513.009606] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
<3>[ 513.016425] PM: Device power.0 failed to suspend late: error -11
<3>[ 513.022654] PM: Some devices failed to power down
<6>[ 513.032678] tegra_uart tegra_uart.1: tegra_uart_resume called
<6>[ 513.038553] tegra_uart tegra_uart.2: tegra_uart_resume called
<6>[ 513.044418] tegra_uart tegra_uart.3: tegra_uart_resume called
<6>[ 513.050333] tegra_uart tegra_uart.4: tegra_uart_resume called
<4>[ 513.057018] Resume SDIO2
<6>[ 513.059476] wakeup wake lock: mmc_delayed_work
<4>[ 513.064946] Resume SDIO3switch-dock: dock_switch_work_func
<4>[ 513.155124] switch-dock: desktop_dock = 0switch-dock: state = 0
<4>[ 513.161310] h2w: off
<6>[ 513.303637] usb 1-1: reset high speed USB device using tegra-ehci and address 2
<4>[ 514.210503] Restarting tasks ...
<6>[ 514.215401] nvrm_notifier_show: blocking
<6>[ 514.224630] request_suspend_state: wakeup (3->0) at 178741913895 (2010-12-25 18:21:32.849360251 UTC)
<4>[ 514.238668] done.
<6>[ 514.243026] tegra_pm_notifier: start processing event=4
<6>[ 514.259163] nvrm_notifier_show: returning with 'PM_POST_SUSPEND'
<6>[ 514.268324] notify_daemon: wait for nvrm_daemon
<6>[ 514.277032] nvrm_notifier_show: blocking
<6>[ 514.282184] tegra_pm_notifier: finished processing event=4
<6>[ 514.308845] suspend: exit suspend, ret = 0 (2010-12-25 18:21:32.933580259 UTC)
<6>[ 514.340146] nvrm_notifier_show: returning with 'PM_DISPLAY_ON'
<6>[ 514.347391] notify_daemon: wait for nvrm_daemon
<4>[ 514.353767] PM_SCREEN_IS_OFF set to 0
<6>[ 514.796232] nvrm_notifier_show: blocking
<4>[ 521.222850] h2w: h2w_switch_irq_isrh2w: onSO340010: gpio_val=0xc0980000, button_val = 0xdba40004
<4>[ 533.359945] SO340010: gpio_val=0xc0980000, button_val = 0xdba40000
Going to go peek through the source and try to trace through platform_pm_suspend_noirq and see if I can figure anything out...
Oh, and @clemsyn, I already am using my own build from source of the kernel, and the issue is still there. So unless you rolled some patches into the power management/cpufreq/suspend-resume code, I bet the issue is still there in your kernel, just hasn't happened yet on your tablet since updating your kernel.
EDIT: hmm, I've found other references to that error -11 issue with other Android devices. Seems to be a symptom of rapid suspend/resume cycling. I can't tell if the suspend-resume cycle is a symptom of the slowdown or the cause though. I am now suspecting more likely a symptom than a cause, i.e. the tablet is stuck on slow CPU mode so attempts to wake take forever to go through, thus the system takes a couple button presses before it finally wakes.
Click to expand...
Click to collapse
I made a few changes in the CPU power management which IMO would help with how CPU is adjusted and also a few in yaffs: )

Still no slowdown. Come out of sleep about 20 times now. I might reflash beta 4 later to test. My power button doesn't work with beta 4, though.

anlog,
You need testers for a slow down workaround? I am volunteering. Running update 3389 with tegra performance pack right now

Testers needed....
Please test the following commands on your tablet and see if the slowdown problem still occurs...
1.) Download and install android terminal emulator (free) from the Market.
2.) Uninstall ALL overclock and cpu scaling utilities such as Overclock Widget, etc.
3.) Power cycle your tablet to reset the CPU to full speed.
4.) Open a terminal and run the following commands:
4a.) su
4b.) tegrastats -max
4c.) echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
4d.) echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
4e.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
4f.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
4g.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
4h.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
4i.) tegrastats -max (yes, run it again)
5.) After the commands in step 4 have been completed, run the following terminal commands to verify that the CPU clock has been changed:
5a.) cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq (should be 1000000)
5b.) cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq (should be 1000000)
After the above steps have been completed, use your tab regularly over next 24 hours. Don't ever power it off. Just keep it in sleep mode, use it any way you like, plug it in to power when needed. Just don't power it off. If you power it off, the settings above will be wiped out.
Once we confirm that this is working for multiple people, we should be able to add it as a startup script to any build.

Thanks....pecking at screen right now

Giving it a try right now. I have definitely seen the slowdown on TNT Lite 3.1.1

Either I've gone brain dead or something is wrong with the script because I get an error "cannot create performance: directory nonexistant"
EDIT: echo "performance" > /sys....needed quotes to work for me

anlog said:
Please test the following commands on your tablet and see if the slowdown problem still occurs...
1.) Download and install android terminal emulator (free) from the Market.
2.) Uninstall ALL overclock and cpu scaling utilities such as Overclock Widget, etc.
3.) Power cycle your tablet to reset the CPU to full speed.
4.) Open a terminal and run the following commands:
4a.) su
4b.) tegrastats -max
4c.) echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
4d.) echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
4e.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
4f.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
4g.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
4h.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
4i.) tegrastats -max (yes, run it again)
5.) After the commands in step 4 have been completed, run the following terminal commands to verify that the CPU clock has been changed:
5a.) cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq (should be 1000000)
5b.) cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq (should be 1000000)
After the above steps have been completed, use your tab regularly over next 24 hours. Don't ever power it off. Just keep it in sleep mode, use it any way you like, plug it in to power when needed. Just don't power it off. If you power it off, the settings above will be wiped out.
Once we confirm that this is working for multiple people, we should be able to add it as a startup script to any build.
Click to expand...
Click to collapse
I am going to test it out, and will report.

All,
If you notice the slowdown coming back after running the commands above, repeat steps 5a and 5b (after running su) to see what the cpu speed is. If it drops to 216000, you know the slowdown is back. If it is still 1000000, then something else might be slowing the system down (try closing apps, etc).
Here are the steps:
1.) su
2.) cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq (will probably be 216000 if slowdown is back)
3.) cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq (will probably be 216000 if slowdown is back)
-EDIT-
Depending on the build you are running, you may notice that your sound stops working (as mine just did). This is not related to the CPU tweaks. I've had this problem happen randomly on several builds. Unfortuately, the only way to fix it is to restart the tab, so I guess I'm not going to have sound for awhile. I'm planning on keeping this thing going until I get a slowdown (still none yet) or one week (whichever happens first). I'm cool with rebooting once a week.

Related

Hi all,
the camera on my Glacier appears to be broken. Any "camera related" app I try to launch force closes after a few seconds. This is true for the built-in camera app, for a barcode scanner app and even for a torch app that would use the flash and not really the camera.
I have already cleared the cache and Davlik and have fixed the permissions to no avail. I ran a logcat from launching the camera app until after I clicked the "force close" button:
Code:
I/ActivityManager( 1351): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera bnds=[96,721][192,800] } from pid 1702
I/ActivityManager( 1351): Start proc com.android.camera for activity com.android.camera/.Camera: pid=3292 uid=10048 gids={1006, 1015}
I/WindowManager( 1351): Setting rotation to 1, animFlags=1
V/CameraHolder( 3292): open camera 0
W/WindowManager( 1351): App freeze timeout expired.
W/WindowManager( 1351): Force clearing freeze: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/InputDispatcher( 1351): Application is not responding: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}. 9279.3ms since event, 5004.2ms since wait started
I/WindowManager( 1351): Input event dispatching timed out sending to application AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/Process ( 1351): Sending signal. PID: 3292 SIG: 3
I/dalvikvm( 3292): threadid=4: reacting to signal 3
I/dalvikvm( 3292): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1351 SIG: 3
I/dalvikvm( 1351): threadid=4: reacting to signal 3
I/dalvikvm( 1351): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1617 SIG: 3
I/dalvikvm( 1617): threadid=4: reacting to signal 3
I/dalvikvm( 1617): Wrote stack traces to '/data/anr/traces.txt'
W/ActivityManager( 1351): Activity idle timeout for HistoryRecord{40a230d8 com.android.camera/.Camera}
I/Process ( 1351): Sending signal. PID: 1572 SIG: 3
D/dalvikvm( 1351): GC_EXPLICIT freed 732K, 38% free 6779K/10823K, external 1561K/2073K, paused 88ms
E/ActivityManager( 1351): ANR in com.android.camera (com.android.camera/.Camera)
E/ActivityManager( 1351): Reason: keyDispatchingTimedOut
E/ActivityManager( 1351): Load: 3.4 / 3.17 / 2.89
E/ActivityManager( 1351): CPU usage from 5627ms to 1ms ago:
E/ActivityManager( 1351): 4.2% 1351/system_server: 3.1% user + 1% kernel / faults: 796 minor
E/ActivityManager( 1351): 3.5% 3050/adbd: 0.1% user + 3.3% kernel
E/ActivityManager( 1351): 2.3% 1245/mediaserver: 0% user + 2.3% kernel
E/ActivityManager( 1351): 2.1% 1572/com.android.systemui: 1.2% user + 0.8% kernel / faults: 1 minor
E/ActivityManager( 1351): 1.7% 1268/logcat2: 0.1% user + 1.5% kernel
E/ActivityManager( 1351): 1.4% 3071/com.google.android.apps.maps: 1% user + 0.3% kernel / faults: 292 minor
E/ActivityManager( 1351): 1.4% 3290/logcat: 0.3% user + 1% kernel
E/ActivityManager( 1351): 0.8% 1249/akmd: 0.3% user + 0.5% kernel
E/ActivityManager( 1351): 0.7% 1252/htc_ebdlogd: 0% user + 0.7% kernel
E/ActivityManager( 1351): 0.3% 6/events/0: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0.3% 921/emmc-qd: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0% 1184/jbd2/mmcblk0p28: 0% user + 0% kernel
E/ActivityManager( 1351): 0% 1658/wpa_supplicant: 0% user + 0% kernel / faults: 11 minor
E/ActivityManager( 1351): 0% 2310/twc.provider: 0% user + 0% kernel / faults: 43 minor
E/ActivityManager( 1351): 0.1% 3292/com.android.camera: 0.1% user + 0% kernel
E/ActivityManager( 1351): 14% TOTAL: 6.9% user + 7.8% kernel
E/ActivityManager( 1351): CPU usage from 297ms to 819ms later:
E/ActivityManager( 1351): 7.4% 1351/system_server: 0% user + 7.4% kernel
E/ActivityManager( 1351): 5.5% 1528/InputDispatcher: 0% user + 5.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 1.5% user + 1.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 0% user + 3% kernel
E/ActivityManager( 1351): 1.5% 3055/adbd: 1.5% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1245/mediaserver: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 2450/Binder Thread #: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1252/htc_ebdlogd: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1268/logcat2: 0% user + 1.3% kernel / faults: 2 minor
E/ActivityManager( 1351): 1.3% 1572/com.android.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1572/ndroid.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 11% TOTAL: 5.7% user + 5.7% kernel
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
W/ActivityManager( 1351): Force finishing activity com.android.camera/.Camera
I/Process ( 1351): Sending signal. PID: 3292 SIG: 9
I/ActivityManager( 1351): Killing com.android.camera (pid=3292): user's request
I/ActivityManager( 1351): Process com.android.camera (pid 3292) has died.
W/InputManagerService( 1351): Window already focused, ignoring focus gain of: [email protected]
My next step now would be a factory reset, but before I do that I'd like to see whether anybody's got a better idea. Any help is appreciated.
Thanks.
---------- Post added at 12:51 PM ---------- Previous post was at 12:35 PM ----------
I just did another reboot and launched the camera app, again. On the first attempt the behavior was the same as before: the app force closed after a while. On any subsequent attempts to launch the camera app I now get the error message "Camera Error / Cannot connect to camera".

We need more info. Are you rooted? What rom? What kernel? Any mods, themes? Things like this can break stuff.
If youre rooted and running a custom rom, just reflash the rom from a full wipe.
Sent from my HTC Glacier using xda premium

I would try full wipe and flash the ROM again.
Sent from my HTC Glacier using XDA App

the device is rooted; I am running CM 7.0.3 with kernel 2.6.35.14 demonspeed v9. It's probably the kernel that causing these problems. After re-flashing CM 7.0.3 (thus going back to the kernel that comes with the ROM), the camera started working again ...

Hi there...I was directed here from the transformerforums.com to ask about this issue. I have a B50-vintage TF101 with keyboard dock. Since the 2nd ICS update, my Transformer has developed the annoying habit of the screen randomly popping on for no reason. I know on that other site there were users seeing this happen, but I tried my best to search here and didn't see it in the search (at least not for the Transformer).
So, I did some playing around and noticed a few things. The annoying "screen coming on for no reason" issue happens only when the tablet is docked in the keyboard. The screen will come on for 10 seconds and then go off again (my default screen timeout is 5 minutes). It is almost as though some kind of notification is coming in, waking up the tablet for a moment.
I believe the issue is the "Charged" notification. I did the following experiment several times: I undocked the tablet, allowed it to discharge to about 95%. Then I plugged it back into the keyboard dock, and waited. The tablet goes into "charging" mode (with the little bolt icon on the battery). If I hit the lock button and wait, the screen goes off and stays off..it does not randomly pop back on again. Not until "Charged" has been hit. After that, the screen randomly comes on again as before.
Further, I noticed that whenever it comes on, it activates WiFi as well. I have my WiFi set to only come on when I am using the tablet. This explains the tablet waking me up in the middle of the night with new email notifications.
Not sure if this helps any...it seems reproducable to me, and definitely a regression (especially from Honeycomb).

I have the same issue, but it's not because of the charge notification. I don't charge it while using it, so when I'm doing something and using my docked tablet on the side for research and neglect it for a while, I notice it'll turn on by itself. This happens pretty consistently, so I don't have to do any weird combination of activities to produce it.
Listen to music?
Chat using Google Talk?
Browse the web?
All of them produce the same effect if I let it sleep. I have wifi set to always on but the transformer docked. I'll try keeping it undocked to see if it happens.
In every instance I didn't have it plugged in.
This is among a few other issues I have that I hope is resolved with the representative allowing us to log our devices so they can replicate the problem.

I'm having the same problem: link

Just a thought; have you got WiFi on?
Mine does this too sometimes, doesn't really bother me because it turns off by itself at the lockscreen and when closed it should also. No negative effect on battery life, it does as expected.

Hah, this is funny. I wanted to check if the screen wake-ups would occur without the dock, so after a while, I realized I didn't notice the screen turning on at all. Just as I was about to check, the Asus logo popped up, so my tablet rebooted.

It is same here.
After update to 9.2.1.17. Only in dock. Without dock, this never happen.
If someone is interested, here is log from another user from another forum:
Code:
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/AlarmManager( 166): Triggered Alarm 4144aa18 RTC_WAKEUP IntentSender{41804ce8: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=1117631ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1204K, 16% free 7160K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 462K, 17% free 7115K/8519K, paused 2ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 83K, 13% free 7435K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 130K, 10% free 7706K/8519K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 216K, 8% free 7888K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 245K, 6% free 8038K/8519K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 445K, 7% free 8026K/8583K, paused 2ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{419f6e40 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5286ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/dalvikvm( 166): GC_FOR_ALLOC freed 1136K, 22% free 17763K/22727K, paused 82ms
V/alogcat (20906): save instance
V/alogcat (20906): paused
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/dalvikvm( 5588): GC_CONCURRENT freed 2094K, 39% free 17346K/28295K, paused 2ms+9ms
D/BatteryService( 166): level:34 scale:100 status:4 health:2 present:true dock_status:1 dock_level:0 dock_ac_online:false voltage: 7 temperature: 255 technology: Li-ion AC powered:false USB powered:false icon:17302840 invalid charger:0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 1
D/AlarmManager( 166): Triggered Alarm 419f6e40 RTC_WAKEUP IntentSender{413f93a0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9727ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
I/alogcat (20906): new intent: android.intent.action.MAIN
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1244K, 16% free 7275K/8583K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 581K, 18% free 7114K/8583K, paused 1ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 80K, 14% free 7442K/8583K, paused 3ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 113K, 10% free 7739K/8583K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 251K, 8% free 7905K/8583K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 244K, 7% free 8051K/8583K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 451K, 7% free 8020K/8583K, paused 1ms+5ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/AlarmManager( 166): Added alarm Alarm{419341d8 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5283ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/TaskWidgetDataUtils(20018): In trigger refresh list utils
D/TaskWidgetDataUtils(20018): getWidgetData()
D/AlarmManager( 166): Triggered Alarm 419341d8 RTC_WAKEUP IntentSender{415b2b60: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9741ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1247K, 15% free 7356K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 580K, 17% free 7223K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 97K, 13% free 7551K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 167K, 11% free 7780K/8647K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 227K, 9% free 7948K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 310K, 8% free 8025K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 473K, 9% free 7945K/8647K, paused 1ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41b76e60 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:24
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5288ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/AlarmManager( 166): Triggered Alarm 41b76e60 RTC_WAKEUP IntentSender{412e2dd0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9725ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1226K, 17% free 7259K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 470K, 17% free 7229K/8647K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 55K, 13% free 7586K/8647K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 144K, 10% free 7834K/8647K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 256K, 8% free 7979K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 271K, 7% free 8096K/8647K, paused 2ms+3ms
D/OpenGLRenderer( 166): Flushing caches (mode 0)
D/PowerManagerService( 166): @PowerManagement: 'keyguard' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
I/TabletStatusBar( 361): DISABLE_CLOCK: no
V/TabletStatusBar( 361): setLightsOn(true)
D/dalvikvm(20906): GC_CONCURRENT freed 499K, 8% free 8034K/8647K, paused 2ms+7ms
I/TextType( 465): TextType = 0x0
W/InputManagerService( 166): Window already focused, ignoring focus gain of: [email protected]
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41a6bd00 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:34
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
V/ ( 166): void cb_onMotion(uint16_t)

Same issue here after second ICS update (17) (also reboots but this is not the thread)
bye!

Very interesting...on the other forum, someone else confirmed the same behaviour, but it only seems to happen with certain models (B50, B70, B80...but NOT B90).
Quite annoying...I'm a bit concerned this continual on/off cycle is going to damage the backlight. I have my WiFi set to only come on when the screen comes on, so the random screen-on issue keeps activating the WiFi as well.
On my B50 I can make the problem "go away" for a while if I discharge my tablet to about 95%, and then re-dock in the keyboard.

Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.

Mine does it too along with random reboots and wont wake after a long deep sleep of 3 to 4 hours

I've had the "really hot" thing happen to me once as well. And recently I noticed the back of the tablet, right near the SD slot, the casing has bulged out a small amount (however I don't know if it's always been that way and I only just noticed it)...I hope that's not where the battery is located.
I haven't had a random crash on my B50 since I disabled the Asus Quick Setting. It's been stable all week in that sense, but I doubt my experience will match anyone else.
Oyeve said:
Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.
Click to expand...
Click to collapse

Oyeve said:
Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.
Click to expand...
Click to collapse
The same thing happens to mine, except I haven't noticed the overheating (thankfully). The reboot-->freeze at logo happened again today while listening to music. I'm hoping I hear from Gary and get that logging program so they can fix it.

Mine did that a live wallpaper once I installed a regular wallpaper it stopped

I tried that just now; set a static wallpaper instead of my live one. Didn't make a difference...
Edit:
I ran a test with and without the dock now as well. I can confirm the issue only occurs when the TF is docked.

I can confirm it does it regularly with out the dock as well.

i believe the screen comes alive each time the tablet charges to 100%, whether docked (with and without usb charging taking place, but dock battery is >100%, ie. not flat out yet), or when usb connected to charger or pc. it seems that the product is designed that when the tab is docked, the battery on the dock will transfer charges to the tab until the dock is flat out. once flat out and no usb charging taking place, the tab doesnt get charged and will not hit 100% again.
i dont think the screen comes alive when the tablet is docked and closed instead of opened position.
after 2weeks on ics, experienced 1 time screen freezes in boot up ASUS logo. and the back is hotter than normal.

I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway

*Detection* said:
I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway
Click to expand...
Click to collapse
Ditto
Unusable after ICS update

This is my concern as well. There's something funny going on with the charging and I'd hate to think the batteries are getting damaged. I'm not at the point of turning my tablet off but I will say...it's getting quite annoying!
*Detection* said:
I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway
Click to expand...
Click to collapse

I got my keyboard Thursday and witnessed this problem until Sunday. It would occur almost every few minutes. Sunday morning I installed Codename Android ROM and have been constantly watching my screen ever since. It has not turned on once by itself. Dock battery is fully drained now and tab is just now dropping below 100%. Will post if status changes.

Among other problem, my phone has started shutting down randomly after 5-15 minute. Here is the last_kmsg :
Code:
[ 1502.022310] batt_temp_monitor_work: stop charging!! state = 7 temp = -300 mvolt = 3990
[ 1502.022432] batt_temp_set_current_limit: value = 900
[ 1502.022523] batt_temp_charger_disable
[ 1502.036227] healthd: battery l=49 v=3881 t=-30.0 h=3 st=4 c=142 chg=u
[ 1502.042514] adjust_soc: ibat_ua = 142200, vbat_uv = 3901515, soc = 86, batt_temp=-300
[ 1502.093300] healthd: battery l=56 v=3897 t=-30.0 h=3 st=4 c=142 chg=u
[ 1504.182267] mdm_status_change: unexpected reset external modem id 0
120 Corrected bytes, 1 unrecoverable blocks
Boot info:
Last boot reason: hw_reset_or_poweron
Any idea ? Also the charging port is not working, I get the lightning icon but it says not charging. The only way I can charge the phone is by wireless charging

Hi,
This is my first post to this forum. Please forgive me if this question has already been answered ad-nauseum but I haven't been able to find an adequate answer to it after what seems like exhaustive searching on this forum or on google.
I have successfully rooted my nook simple touch running firmware 1.2.1 (multiple times now, that part is simple). I have access to the google play store and the android store, but I still would like to have the ability to sideload .apk files.
The problem that I run into is that I seem to have almost no space for applications on my device. I can manage to get opera mini, dropbox, kindle, and ES file explorer going, and I might be able to install several other small apps if I tried, but I haven't been able to install EZPDF reader due to what appears to be space limitation.
I have tried the following:
- installing through the play store - installation fails
- installing by tapping on the .apk file while browsing my SD card using either ES file explorer or relaunch - out of space error
- installing by running the ADB install command - install failed due to insufficient storage
- I have also tried the [-s] command with adb install and prompt does not recognize that qualifier
- installing by simply copying the .apk file to the /system/app folder (this actually gets the application into my applications list and I can open it but then it claims it can't access my SD card and closes down
I really am starting to feel frustrated, especially since it seems like others are able to install large numbers of apps without running into this type of problem. How limited is the space on the NST and is there any way to install applications to the SD card to prevent running out of space so quickly? Perhaps I simply need to forgo the idea of having more than a small handful of applications? Thanks very much in advance.

First thing to check.
Code:
adb shell df
...
/data: 808292K total, 87864K used, 720428K available (block size 4096)
...
Then in two different windows do:
Code:
adb logcat
Code:
adb install [i]whatever.apk[/i]

Renate NST said:
First thing to check.
Code:
adb shell df
...
/data: 808292K total, 87864K used, 720428K available (block size 4096)
...
Then in two different windows do:
Code:
adb logcat
Code:
adb install [i]whatever.apk[/i]
Click to expand...
Click to collapse
So for the first (and that's after I have deleted as many apps as I can stand. Left amazon app store, market search, google apps, kindle, es file explorer and dropbox):
ben$ adb shell df
/dev: 116448K total, 0K used, 116448K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16344K total, 400K used, 15944K available (block size 8192)
/system: 396656K total, 221551K used, 175105K available (block size 1024)
/data: 146735K total, 135842K used, 10893K available (block size 1024)
/cache: 198321K total, 9335K used, 188986K available (block size 1024)
/media: 856404K total, 44K used, 856360K available (block size 4096)
/sdcard: 15335680K total, 57248K used, 15278432K available (block size 32768)
ben$ adb install /Users/ben/Downloads/EZPDF.reader-2.5.0.3-signed.apk
failed to copy '/Users/ben/Downloads/EZPDF.reader-2.5.0.3-signed.apk' to '/data/local/tmp/EZPDF.reader-2.5.0.3-signed.apk': No space left on device
rm failed for /data/local/tmp/EZPDF.reader-2.5.0.3-signed.apk, No such file or directory
Logcat output (during and immediately after the install command):
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 12 msecs
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/wpa_supplicant( 891): CTRL-EVENT-STATE-CHANGE id=1 state=6
V/WifiMonitor( 807): Event [CTRL-EVENT-STATE-CHANGE id=1 state=6]
I/wpa_supplicant( 891): WPA: Group rekeying completed with 00:19:e3:fb:a1:27 [GTK=CCMP]
I/wpa_supplicant( 891): CTRL-EVENT-STATE-CHANGE id=1 state=7
V/WifiMonitor( 807): Event [WPA: Group rekeying completed with 00:19:e3:fb:a1:27 [GTK=CCMP]]
V/WifiMonitor( 807): Event [CTRL-EVENT-STATE-CHANGE id=1 state=7]
V/WifiStateTracker( 807): Changing supplicant state: COMPLETED ==> GROUP_HANDSHAKE
V/WifiStateTracker( 807): Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WindowManager( 807): CALLING monitor
D/WindowManager( 807): mHomeKeyHeldAt =1403064346572; mFlip = false
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME + (down && repeatCount == 0 && !mDisableInput) == true ==> recognize home key pressed
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WindowManager( 807): CALLING monitor
D/WindowManager( 807): toggle quicknav95
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME & mHomePressed
W/WindowManager( 807): Unable to find ITelephony interface
D/EPD#StatusBar( 807): set region 3 1 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 807): epd_set_region: 3 (0,0,600,800) 1,0 1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 22 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
E/TC ( 1100): KPICollector: 1403064347424 platform qn_home_press
D/EPD#ActivityResume( 807): Disable EPD for 250ms!!!!!!!!
I/ActivityManager( 807): Starting activity: Intent { act=com.bn.intent.action.home flg=0x14400000 cmp=android/com.android.internal.app.ResolverActivity }
E/TC ( 1100): KPICollector: 1403064347454 ActivityManager background {"component":"com.rockolabs.adbkonnect/.AdbKonnectActivity"}
E/TC ( 1100): KPICollector: 1403064347456 ActivityManager foreground {"component":"android/com.android.internal.app.ResolverActivity"}
D/EPD#StatusBar( 807): resetRegion 3
D/NATIVE-EPD( 807): epd_reset_region: 0x08
D/EPD#StatusBar( 807): Disable EPD for 150ms!!!!!!!!
V/Activity( 807): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
I/ActivityManager( 807): Displayed activity android/com.android.internal.app.ResolverActivity: 73 ms (total 73 ms)
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 13 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/ActivityManager( 807): Starting activity: Intent { act=com.bn.intent.action.home flg=0x17c00000 cmp=com.harasoft.relaunch/.Home1 }
I/ActivityManager( 807): Starting activity: Intent { flg=0x4000000 cmp=com.harasoft.relaunch/.ReLaunch (has extras) }
W/ActivityManager( 807): Activity is launching as a new task, so cancelling activity result.
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
E/TC ( 1100): KPICollector: 1403064349494 ActivityManager background {"component":"android/com.android.internal.app.ResolverActivity"}
E/TC ( 1100): KPICollector: 1403064349498 ActivityManager foreground {"component":"com.harasoft.relaunch/.Home1"}
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 14 msecs
D/dalvikvm( 807): GC freed 37230 objects / 2142120 bytes in 85ms
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
D/ReLaunchApp( 1113): --- onResume(ReLaunch)
D/dalvikvm( 1113): GC freed 8125 objects / 546704 bytes in 45ms
I/ActivityManager( 807): Displayed activity com.harasoft.relaunch/.ReLaunch: 563 ms (total 593 ms)
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 28 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 66 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 44 msecs
I/ActivityManager( 807): Starting activity: Intent { cmp=com.harasoft.relaunch/.AllApplications (has extras) }
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
D/ReLaunchApp( 1113): --- onResume(AllApps)
D/dalvikvm( 1113): GC freed 9179 objects / 464984 bytes in 55ms
I/ActivityManager( 807): Displayed activity com.harasoft.relaunch/.AllApplications: 430 ms (total 430 ms)
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/ActivityManager( 807): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.estrongs.android.pop/.view.FileExplorerActivity }
V/Activity( 1212): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
E/TC ( 1100): KPICollector: 1403064353853 ActivityManager background {"component":"com.harasoft.relaunch/.AllApplications"}
E/TC ( 1100): KPICollector: 1403064353879 ActivityManager foreground {"component":"com.estrongs.android.pop/.view.FileExplorerActivity"}
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
D/dalvikvm( 1212): GC freed 17357 objects / 969872 bytes in 72ms
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 21 msecs
D/dalvikvm( 1820): GC freed 1111 objects / 76976 bytes in 34ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 11 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 34 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 39 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/dalvikvm( 1100): GC freed 1599 objects / 78840 bytes in 33ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 42 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 35 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 14 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/dalvikvm( 1212): GC freed 17489 objects / 1116816 bytes in 73ms
D/dalvikvm( 1212): GC freed 6279 objects / 603384 bytes in 61ms
D/dalvikvm( 1212): GC freed 594 objects / 203872 bytes in 58ms
D/dalvikvm( 1212): GC freed 697 objects / 211904 bytes in 59ms
D/dalvikvm( 1212): GC freed 825 objects / 218136 bytes in 59ms
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 34 msecs
D/dalvikvm( 1113): GC freed 4876 objects / 294608 bytes in 57ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 11 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 46 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
Thanks for your help!

Something has gotten screwed up with either the partitioning or else the formatting of the /data partition.
It should be showing somewhere near 840 Megs for the partition or 800 Megs on a df command.
You are showing 150 Megs.
Step 1: Do a complete, ~1.9 GB backup using noogie and Win32DiskImager
Step 2:
Code:
C:\>imagefix [i]mybackup.img[/i]
Image is partitioned as stock NST
...
This will tell you instantly if the partitioning is stock.
If it's not, stop here.
Step 3: Get ClockworkMod Recovery running as either a recovery image on internal storage, on external storage or through USB boot. Connect to it with ADB.
Step 4:
Code:
# e2fsck /dev/block/mmcblk0p8

@Renate ... @nmyshkin ...
noogie boot
Code:
lsblk
gives the following partition structure
Code:
sdc 8:32 1 1.9G 0 disk
├─sdc1 8:33 1 76M 0 part /media/muz/boot
├─sdc2 8:34 1 16M 0 part /media/muz/rom
├─sdc3 8:35 1 190M 0 part /media/muz/factory
├─sdc4 8:36 1 1K 0 part
├─sdc5 8:37 1 288M 0 part /media/muz/18216b6d-59fc-4b61-b9db-652bbb5e848d
├─sdc6 8:38 1 240M 0 part /media/muz/NOOK
├─sdc7 8:39 1 240M 0 part /media/muz/cache
└─sdc8 8:40 1 802M 0 part /media/muz/userdata
but the ReLaunch shows only ... Total : 227MB / Free: 118 ... but the above partition table shows
Code:
/userdata
of 802 MB ... Where did almost 600MB vanish in between ?
Is there any way I can reclaim almost 600 MB of user data space ?
thanks.

aiamuzz said:
Where did almost 600MB vanish in between ?
Is there any way I can reclaim almost 600 MB of user data space ?
thanks.
Click to expand...
Click to collapse
Where indeed? I am not familiar with noogie and its output, but I have seen this kind of complaint before. You've been really busy with flashing one thing after another on your device, including cloning a device running FW 1.1.5. I think you need to slow down and re-start from the cleanest configuration you can get.
You said you had a complete backup of the device as received from the seller. Here is what I would do:
1. Restore that backup.
2. De-register offline (boot, as soon as "Read Forever" appears, press and hold the lower hardware buttons until the prompt appears). Proceed to delete user data.
3. Make a NookManager card (BE SURE to use the updated version. The old version will not work properly with FW 1.2.2) and use the "rescue" option to initiate a factory re-image of the device. This is your best bet to getting things back to the way they should be before trying out modifications.
4. After the re-image is done you will be left at the "Welcome" screen. Connect your device via USB to your PC and drag the 1.2.2 update zip onto the "Nook" drive. Let the device sleep and it will install the update.
5. Register the device.
6. Root with NookManager.
7. Customize as desired.
I'd be surprised if this did not make the issue you describe disappear.

This morning I just did an update to my Onyx Poke 3. Since they are pretty obtuse, it's a full update, 1.4 GB. Good luck finding space for that.
I have a whole recovery/update install system which can access a USB flash drive. It worked just fine.
Oh, wait, you're still talking about the NST??? How about sticking it on an SD card in the slot? Hmm?

nmyshkin said:
Where indeed? I am not familiar with noogie and its output, but I have seen this kind of complaint before. You've been really busy with flashing one thing after another on your device, including cloning a device running FW 1.1.5. I think you need to slow down and re-start from the cleanest configuration you can get.
You said you had a complete backup of the device as received from the seller. Here is what I would do:
1. Restore that backup.
2. De-register offline (boot, as soon as "Read Forever" appears, press and hold the lower hardware buttons until the prompt appears). Proceed to delete user data.
3. Make a NookManager card (BE SURE to use the updated version. The old version will not work properly with FW 1.2.2) and use the "rescue" option to initiate a factory re-image of the device. This is your best bet to getting things back to the way they should be before trying out modifications.
4. After the re-image is done you will be left at the "Welcome" screen. Connect your device via USB to your PC and drag the 1.2.2 update zip onto the "Nook" drive. Let the device sleep and it will install the update.
5. Register the device.
6. Root with NookManager.
7. Customize as desired.
I'd be surprised if this did not make the issue you describe disappear.
Click to expand...
Click to collapse
I have done the following ... booted into nook manager, rescued through th factory zip ... that returned my device to 1.1.5 ... isn't this as clean as it gets ... cleaner than i received from the seller which had 1.2.1 ???
Right now as i type this ... I have built a device coming the factory zip way out of the Nook Manager(Stealth version) ... I've removed RelaunchX after mapping the button to the app drawer(a very clean implementation minus the overheads of a full fledged lancher i hope), thanks for this implementation as it just gets the job done, its not like our low spec'd device required a full launcher, a launcher was only to access the app drawer, and the standalone app drawer implementation does that job giving it a clean experience.
Some advice ?
1. Would you recommend installing CWM recovery to the above setup ? ...
ABOUT reclaiming the userdata partition ...
---------------------------------------------------------------------
2. I was wondering if i could somehow format/clear the /userdata partition somehow(CWM recovery ? or gparted with a noogie boot that mounts partitions on my linux desktop - I hope gparted does not corrupt the other partition structure/information proprietary to B&N) ... can I ?
3. If that's doable i was wondering what will be the repercussions of doing it ...
- Will i lose the B&N Nook Store registration ?
- Will i be able to re-register from that point onwards ? ... or ...
- Coming clean from the start is the only way to register the device at B&N(If so then that's of no use)

aiamuzz said:
but the ReLaunch shows only ... Total : 227MB / Free: 118
Click to expand...
Click to collapse
The /data partition is ~800 M (for apps, system & /data/media/B&N Downloads for B&N books)
The /media partition is ~250 M (for sideloaded books)
There is no 600 M discrepancy.

aiamuzz said:
1. Would you recommend installing CWM recovery to the above setup ? ...
Click to expand...
Click to collapse
Absolutely not. It will replace the stock recovery and you may come to regret that. If you want CWM, make an sdcard following the directions in that thread. That's how I use it.
aiamuzz said:
ABOUT reclaiming the userdata partition ...
---------------------------------------------------------------------
2. I was wondering if i could somehow format/clear the /userdata partition somehow(CWM recovery ? or gparted with a noogie boot that mounts partitions on my linux desktop - I hope gparted does not corrupt the other partition structure/information proprietary to B&N) ... can I ?
3. If that's doable i was wondering what will be the repercussions of doing it ...
- Will i lose the B&N Nook Store registration ?
- Will i be able to re-register from that point onwards ? ... or ...
- Coming clean from the start is the only way to register the device at B&N(If so then that's of no use)
Click to expand...
Click to collapse
If you must go into this (see reply by @Renate above), there is a thread that describes repartitioning with gparted: https://forum.xda-developers.com/t/...ch-resize-partitions-non-destructive.1279091/
Fooling with the partitions is a recipe for disaster, IMHO, so unless a previous owner has done some damage you need to repair and your device is a doorstop, I would not go there for all the used NSTGs in Romania.
Edit: FWIW, here is a df of one of my registered devices with stock partitioning. Yours may vary slightly but should be similar in terms of 1K-blocks:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 115644 0 115644 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mmcblk0p2 16116 218 15899 1% /rom
/dev/block/mmcblk0p5 285583 165242 117393 58% /system
/dev/block/mmcblk0p8 808292 277164 522916 35% /data
/dev/block/mmcblk0p7 237987 6259 229271 3% /cache
/dev/block//vold/179:6 245484 504 244980 0% /media
/dev/block//vold/179:17 13721336 790072 12931264 6% /sdcard

My Nexus 6P lately has been getting really slow after being on for a few days. I ran:
Code:
adb shell
top -m 20 -s rss
And I think it looks unusual that my 'logd' is spinning out of control like this:
Code:
User 6%, System 48%, IOW 10%, IRQ 1%
User 90 + Nice 28 + Sys 928 + Idle 641 + IOW 193 + IRQ 17 + SIRQ 17 = 1914
PID PR CPU% S #THR VSS RSS PCY UID Name
348 3 0% S 7 1263224K 947564K bg logd /system/bin/logd
4866 3 1% S 110 2439336K 131284K fg system system_server
16227 0 0% S 20 1698620K 124780K fg system com.android.settings
6114 2 0% S 47 1725224K 115604K fg u0_a27 com.android.systemui
19588 0 0% S 33 2253364K 89148K bg u0_a29 com.google.android.googlequicksearchbox
7176 0 0% S 238 1826080K 82560K fg u0_a280 com.fitbit.FitbitMobile
14869 1 0% S 100 1723796K 74144K fg u0_a12 com.google.android.gms.persistent
22388 0 1% S 53 1692288K 64760K bg u0_a175 com.facebook.orca
23633 0 2% S 66 1824088K 61444K bg u0_a79 com.facebook.katana
13291 1 0% S 59 1773460K 57124K fg u0_a12 com.google.android.gms
Code:
logcat -g
main: ring buffer is 256Kb (556Mb consumed), max entry is 5120b, max payload is 4076b
system: ring buffer is 256Kb (33Mb consumed), max entry is 5120b, max payload is 4076b
crash: ring buffer is 256Kb (36Kb consumed), max entry is 5120b, max payload is 4076b
Does anyone knows what this means and how I can stop it from happening? It is ruining an otherwise great phone.