All, We are trying to enable ftrace to measure performance, and when we made the following kernel configuration
* Kernel Hacking -> Tracers -> Kernel FUNCTION_TRACER * Kernel Hacking -> Tracers -> Interrupts-off Latency Tracer * Kernel Hacking -> Tracers -> Preemption-off Latency Tracer * Kernel Hacking -> Tracers -> Trace max stack * Kernel Hacking -> Tracers -> Enable kprobes-based dynamic events * Kernel Hacking -> Tracers -> enable/disable ftrace tracepoints dynamically These changes make the following configuration in the kernel configuration CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_NOP_TRACER=y CONFIG_RING_BUFFER=y CONFIG_EVENT_TRACING=y CONFIG_EVENT_POWER_TRACING_DEPRECATED=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_TRACING=y CONFIG_ENABLE_DEFAULT_TRACERS=y CONFIG_BINARY_PRINTF=y CONFIG_PERF_EVENTS=y With these changes, we get kernel panic during boot up [ 0.000000] Kernel command line: androidboot.console=ttyO1 console=ttyUSB0,115200n8 console=ttyO1,115200n8 mem=2040M vmalloc=512M root=/dev/ram0 rw init=/init vram=40M omapfb.vram=0:8M,1:28M no_console_suspend ethhwmac=20:3A:07:FD:FC:5E factory_reset=0 altboot=0 active_partition=a active_sb2=a androidboot.serialno=FCH16368JEK hwver=262144 feature=7 tp_xscale=0 tp_yscale=0 tp_xoff=0 tp_yoff=0 emmc_stats=782,511,0,0 … [ 6.757873] twl_rtc twl_rtc: setting system clock to 2014-03-24 13:22:22 UTC (1395667342) [ 7.398071] cyttsp_i2c_reset: gpio_set_value(step3)=1 r=0 [ 7.404083] cyttsp-i2c 3-0067: cyttsp_pr_state: ACTIVE [ 7.601226] List of all partitions: [ 7.605041] b300 3866624 mmcblk0 driver: mmcblk [ 7.610931] b301 760 mmcblk0p1 00000000-0000-0000-0000-000000000000mmcblk0p1 [ 7.619873] b302 256 mmcblk0p2 00000000-0000-0000-0000-000000000000mmcblk0p2 [ 7.628814] b303 256 mmcblk0p3 00000000-0000-0000-0000-000000000000mmcblk0p3 [ 7.637817] b304 1 mmcblk0p4 00000000-0000-0000-0000-000000000000mmcblk0p4 [ 7.646820] b305 8184 mmcblk0p5 00000000-0000-0000-0000-000000000000mmcblk0p5 [ 7.655792] b306 2040 mmcblk0p6 00000000-0000-0000-0000-000000000000mmcblk0p6 [ 7.664825] b307 65528 mmcblk0p7 00000000-0000-0000-0000-000000000000mmcblk0p7 [ 7.673889] 103:00000 65528 mmcblk0p8 00000000-0000-0000-0000-000000000000mmcblk0p8 [ 7.682891] 103:00001 248 mmcblk0p9 00000000-0000-0000-0000-000000000000mmcblk0p9 [ 7.691619] cyttsp_open: CISCO low power mode disabled [ 7.691619] [ 7.691619] 103:00002 1016 mmcblk0p10 00000000-0000-0000-0000-000000000000mmcblk0p10 [ 7.691650] 103:00003 20472 mmcblk0p11 00000000-0000-0000-0000-000000000000mmcblk0p11 [ 7.691650] 103:00004 32760 mmcblk0p12 00000000-0000-0000-0000-000000000000mmcblk0p12 [ 7.691680] 103:00005 511992 mmcblk0p13 00000000-0000-0000-0000-000000000000mmcblk0p13 [ 7.691680] 103:00006 32760 mmcblk0p14 00000000-0000-0000-0000-000000000000mmcblk0p14 [ 7.691680] 103:00007 511992 mmcblk0p15 00000000-0000-0000-0000-000000000000mmcblk0p15 [ 7.691711] 103:00008 511992 mmcblk0p16 00000000-0000-0000-0000-000000000000mmcblk0p16 [ 7.691711] 103:00009 2100728 mmcblk0p17 00000000-0000-0000-0000-000000000000mmcblk0p17 [ 7.691741] b310 2048 mmcblk0boot1 (driver?) [ 7.691741] b308 2048 mmcblk0boot0 (driver?) [ 7.691772] No filesystem could mount root, tried: ext2 ext3 ext4 squashfs vfat msdos fuseblk [ 7.691772] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 7.691802] Backtrace: [ 7.691802] [<c005a848>] (dump_backtrace+0x0/0x110) from [<c0668adc>] (dump_stack+0x18/0x1c) [ 7.691833] r6:d783c020 r5:00000000 r4:c08c9de8 r3:d783c000 [ 7.691833] [<c0668ac4>] (dump_stack+0x0/0x1c) from [<c0668b70>] (panic+0x90/0x1bc) [ 7.691864] [<c0668ae0>] (panic+0x0/0x1bc) from [<c0008f9c>] (mount_block_root+0x2bc/0x2d8) [ 7.691864] r3:d783df2c r2:00000020 r1:d783df60 r0:c07a4b58 [ 7.691864] r7:00008000 [ 7.691894] [<c0008ce0>] (mount_block_root+0x0/0x2d8) from [<c000901c>] (mount_root+0x64/0x68) [ 7.691894] [<c0008fb8>] (mount_root+0x0/0x68) from [<c00091c0>] (prepare_namespace+0x1a0/0x1dc) [ 7.691894] r5:c0040145 r4:c08c6fa0 [ 7.691925] [<c0009020>] (prepare_namespace+0x0/0x1dc) from [<c0008464>] (kernel_init+0x130/0x13c) [ 7.691925] r5:c003f6f8 r4:c003f6f8 [ 7.691955] [<c0008334>] (kernel_init+0x0/0x13c) from [<c00aff4c>] (do_exit+0x0/0x79c) [ 7.691955] r5:c0008334 r4:00000000 [ 7.892883] CPU0: stopping [ 7.895812] Backtrace: [ 7.898620] [<c005a848>] (dump_backtrace+0x0/0x110) from [<c0668adc>] (dump_stack+0x18/0x1c) [ 7.907623] r6:d796a000 r5:c004e100 r4:c086a280 r3:d796a000 [ 7.914031] [<c0668ac4>] (dump_stack+0x0/0x1c) from [<c004f3f0>] (do_IPI+0x180/0x198) [ 7.922485] [<c004f270>] (do_IPI+0x0/0x198) from [<c0055a08>] (__irq_svc+0x48/0xe4) [ 7.930664] Exception stack(0xd796bd98 to 0xd796bde0) [ 7.936126] bd80: 60000013 00000002 [ 7.944885] bda0: c088db24 c088db24 c08ca2d8 00000003 c088da7c c08ca306 00000040 00000000 [ 7.953643] bdc0: 00000000 d796be94 d796bda8 d796bde0 c00ac2f0 c00acaf0 60000013 ffffffff [ 7.962463] [<c00ac688>] (vprintk+0x0/0x5ec) from [<c0668cc0>] (printk+0x24/0x2c) [ 7.970489] [<c0668c9c>] (printk+0x0/0x2c) from [<c040caa0>] (cyttsp_open+0x14c/0x168) [ 7.978973] r3:00000000 r2:00000000 r1:c06a6d98 r0:c07fa440 [ 7.985382] [<c040c954>] (cyttsp_open+0x0/0x168) from [<c0403080>] (input_open_device+0x7c/0xac) [ 7.994812] r7:00000000 r6:d7ac6594 r5:d733b280 r4:d7ac6400 [ 8.001190] [<c0403004>] (input_open_device+0x0/0xac) from [<c04825dc>] (cpufreq_interactive_input_open+0x18/0x2c) [ 8.012268] r7:c0b162ac r6:c2027000 r5:c20226c0 r4:c0b162ac [ 8.018615] [<c04825c4>] (cpufreq_interactive_input_open+0x0/0x2c) from [<c00c741c>] (process_one_work+0x130/0x50c) [ 8.029815] r4:d78c7f80 r3:c04825c4 [ 8.033874] [<c00c72ec>] (process_one_work+0x0/0x50c) from [<c00c7ba0>] (worker_thread+0x1a8/0x490) [ 8.043548] [<c00c79f8>] (worker_thread+0x0/0x490) from [<c00ce904>] (kthread+0x94/0x98) [ 8.052215] [<c00ce870>] (kthread+0x0/0x98) from [<c00aff4c>] (do_exit+0x0/0x79c) [ 8.060302] r7:00000013 r6:c00aff4c r5:c00ce870 r4:d7849e94 [ 8.066650] Rebooting in 5 seconds.. If we disable SELinux and keep the above configuration then the device boots up fine. So, is there any known limitation between selinux and ftrace configuration? Is there any thing else that we need to do to use ftrace with selinux? Thanks, Tai
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
