>From camera-app: Max nice priority 0 0 Max realtime priority 0 0
We're not setting the nice value as done by android since we flipped the container, and afaik we still don't have a policy that describes the nice priority for specific processes (system, phablet, etc). The binder message itself is harmless, and we're ignoring it at syslog already, just annoying the kernel log buffer ring. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-maguro in Ubuntu. https://bugs.launchpad.net/bugs/1202887 Title: 'binder: RLIMIT_NICE not set' when using binder from the ubuntu side Status in Touch Preview Images: New Status in “linux-grouper” package in Ubuntu: New Status in “linux-maguro” package in Ubuntu: New Status in “linux-mako” package in Ubuntu: New Status in “linux-manta” package in Ubuntu: New Bug description: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- saucy.git;a=blob;f=drivers/staging/android/binder.c;hb=refs/heads/mako#l516 """ static void binder_set_nice(long nice) { long min_nice; if (can_nice(current, nice)) { set_user_nice(current, nice); return; } min_nice = 20 - current->signal->rlim[RLIMIT_NICE].rlim_cur; binder_debug(BINDER_DEBUG_PRIORITY_CAP, "binder: %d: nice value %ld not allowed use " "%ld instead\n", current->pid, nice, min_nice); set_user_nice(current, min_nice); if (min_nice < 20) return; binder_user_error("binder: %d RLIMIT_NICE not set\n", current->pid); } """ That happens because binder expects it to be able to change the nice value for the specific process, and fails when the process is started by Ubuntu, which has a default nice value of 0 (rlimit nice is set to 40 40 by default in android, via android's init). To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1202887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
