[android-kernel] Re: Kernel porting ERRORs Failed setting process group of NNN to 0/1; add_tid_to_cgroup failed

2012-10-11 Thread Glenn Kasten
Your version of the source code appears to be missing this commit commit 4a12178d3dd5b06a215076c60dc7cb124d711373 cgroup: Add generic cgroup subsystem permission checks You may be looking at a branch which lacks Android patches. On Monday, October 8, 2012 5:56:35 AM UTC-7, John Tapsell wrot

[android-kernel] Re: Kernel porting ERRORs Failed setting process group of NNN to 0/1; add_tid_to_cgroup failed

2012-10-08 Thread John Tapsell
Thanks for the help Glenn - I now have more details. The process triggering the warning is system_server, and this is running as user "system". It is trying to write the pid of various other processes (com.android.inputmethod.latin, com.android.phone. com.android.launcher, etc) into /dev/input

[android-kernel] Re: Kernel porting ERRORs Failed setting process group of NNN to 0/1; add_tid_to_cgroup failed

2012-10-05 Thread Glenn Kasten
I suggest getting a stack trace at the time of log, to see what is happening. For example at that ALOGE also log the tid and fd, and then do an abort() or *(char*) 0 = 0; This will prevent the system from running of course, but a logcat during bootup should show why it's failing. On Wednesday,

[android-kernel] Re: Kernel porting ERRORs Failed setting process group of NNN to 0/1; add_tid_to_cgroup failed

2012-10-04 Thread John Tapsell
Hi Glenn, Can you give any more hints about what to look for in init.rc ? The cgroups code is exactly the same in my init.rc I have: > ls -l /dev/cpuctl/tasks -rwxrwxrwx system system 0 2000-01-01 00:23 tasks Yet I still get: W/SchedPolicy( 189): add_tid_to_cgroup failed to

[android-kernel] Re: Kernel porting ERRORs Failed setting process group of NNN to 0/1; add_tid_to_cgroup failed

2012-08-13 Thread Glenn Kasten
Sometimes this is caused by incorrect init.rc. Make sure your init.rc has all of the latest changes from system/core/rootdir/init.rc especially if you have forked it. You mentioned a "lot of people" have seen this .. were these on other external postings or bug reports? if so can you please su