[Galaxy Note GT-N7000 Android Development] samarium:
While it is happening when using TWRP, the kernel is the same one as used by the ROM, which is why I posted it here, since it is a kernel crash.

I'll follow up chasmodo's parameter request, and post a follow up.

---------- Post added at 05:23 PM ---------- Previous post was at 04:37 PM ----------

My phone normally uses ondemand/cfq.

My crash is when I've rebooted into recovery, so I don't understand why using the phone normally for 10 min would do anything since I'll be rebooting the kernel to activate recovery.

I have tried tar zcvf /storage/sdcard1/tmp/test.tgz /system /data while the phone is booted normally, and it didn't crash like it did in recovery.

### from normal, interestingly looks like only one cpu is active at the moment

# grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
ondemand
# grep . /sys/block/mmc*/queue/scheduler
/sys/block/mmcblk0/queue/scheduler:noop deadline [cfq] row bfq sio vr
/sys/block/mmcblk1/queue/scheduler:noop deadline [cfq] row bfq sio vr
#

### from recovery:

~ # grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor:ondemand
~ # grep . /sys/block/mmc*/queue/scheduler
/sys/block/mmcblk0/queue/scheduler:noop deadline [cfq] row bfq sio vr
/sys/block/mmcblk1/queue/scheduler:noop deadline [cfq] row bfq sio vr
~ #

Interestingly, while I was booted into recovery to extract the governor/iosched info, and it was idling, it crashed with the same message:

<6>[ 240.184245] c0 kadaptiveup D c0c436fc 0 1058 2 0x00000000^M
<4>[ 240.184387] c0 Backtrace: ^M
<4>[ 240.184521] c0 [<c0c43354>] (__schedule+0x0/0x8c4) from [<c0c43d74>] (schedule+0x50/0x68)^M
<4>[ 240.184699] c0 [<c0c43d24>] (schedule+0x0/0x68) from [<c072d39c>] (kthread+0x70/0x94)^M
<4>[ 240.184867] c0 [<c072d32c>] (kthread+0x0/0x94) from [<c0715200>] (do_exit+0x0/0x6e4)^M
<4>[ 240.184992] c0 r6:c0715200 r5:c072d32c r4:e3843f04^M
<0>[ 240.185180] c0 Kernel panic - not syncing: hung_task: blocked tasks^M
<4>[ 240.190362] c0 Backtrace: ^M
<4>[ 240.193054] c0 [<c06d7a90>] (dump_backtrace+0x0/0x10c) from [<c0c3e5f4>] (dump_stack+0x18/0x1c)^M
<4>[ 240.201767] c0 r6:e3aeeac8 r5:c0fa9640 r4:c1055a40 r3:00000000^M
<4>[ 240.207619] c0 [<c0c3e5dc>] (dump_stack+0x0/0x1c) from [<c0c3e924>] (panic+0x80/0x1ac)^M
<4>[ 240.215576] c0 [<c0c3e8a4>] (panic+0x0/0x1ac) from [<c0756a18>] (watchdog+0x270/0x29c)^M
<4>[ 240.223437] c0 r3:00000001 r2:c0f89b70 r1:00000000 r0:c0d903c4^M
<4>[ 240.229285] c0 r7:000003db^M
<4>[ 240.232098] c0 [<c07567a8>] (watchdog+0x0/0x29c) from [<c072d3b8>] (kthread+0x8c/0x94)^M
<4>[ 240.240048] c0 [<c072d32c>] (kthread+0x0/0x94) from [<c0715200>] (do_exit+0x0/0x6e4)^M
<4>[ 240.247746] c0 r6:c0715200 r5:c072d32c r4:e3843f24^M
<6>[ 240.252714] c0 notifier_call_chain : NOTIFY BAD sec_debug_panic_handler^M
<0>[ 240.259225] c0 Rebooting in 1 seconds..^M
<0>[ 241.267022] c0 sec_reboot (104, (null))^M

Maybe it is a more general kernel issue.

Chas, are you suggesting I should raise on the raw_kernel thread? IIRC you said that anything in rawkernel eventually ends up in Omni kernel?