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, October 3, 2012 2:10:48 PM UTC-7, John Tapsell wrote: > > 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 write '435' (Permission > denied); background=0 > > etc. > > Any ideas please? > > John > > > > On Monday, 13 August 2012 17:44:35 UTC+1, Glenn Kasten wrote: >> >> 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 supply a link to >> these, it will help diagnose to see the other reports. >> >> On Friday, August 10, 2012 2:46:18 AM UTC-7, failuch wrote: >>> >>> Hello all, >>> >>> I saw that a lot of people encountered these error : >>> >>> W/ActivityManager( 349): Failed setting process group of 4911 to 0 >>> W/SchedPolicy( 349): add_tid_to_cgroup failed to write '4911' >>> (Permission denie >>> d); background=1 >>> >>> >>> >>> And I was unable to find explanation/solution for this problem, >>> although >>> >>> I have checked cgroups are mounted and /dev/cpuctl/tasks exist >>> >>> Can you please to comment ? >>> >>> >>> ThX >>> >> -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
