touch-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

This is a known issue and most affects users who perform lots of system
updates with certain kernel and/or policy changes and is exacerbated by
a high number of installed packages. We employ caching in various ways
to reduce the time to recompile all policy to only needing to do it for
certain first boot situations. Recently, there was an update that
required recompiling the policy. The next time you boot, the cache will
be used again.

This will not normally affect consumers because neither the kernel nor
the policy will change during the system image update process. There are
plans to make some sort of progress bar when it does happen, and to
improve policy compiles.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1350598

Title:
  apparmor_parser takes a long time

Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  Just updated my Nexus 7 2013 from #160 to #161. It's been sat at the
  Google logo for 15 minutes now. It looks and feels like it's hung. As
  a user I'd be rebooting it thinking it had crashed by now. I shell in
  and find apparmor_parser  using a lot of cpu for a long time.

  top - 00:14:01 up 15 min,  2 users,  load average: 5.12, 4.85, 3.21
  Tasks: 202 total,   2 running, 200 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 50.5 us,  0.8 sy,  0.0 ni, 48.5 id,  0.2 wa,  0.0 hi,  0.0 si,  0.0 st
  KiB Mem:   1848024 total,   787400 used,  1060624 free,    54216 buffers
  KiB Swap:    32764 total,        0 used,    32764 free.   579228 cached Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                               
   1970 root      20   0    4976   3652    852 R  99.8  0.2  14:31.04 apparmor_parser                                                                       
   2596 phablet   20   0    5996   1264    824 R   1.3  0.1   0:08.79 top                                                                                   
    914 root       0 -20    7572    552    396 S   0.7  0.0   0:05.02 mpdecision                                                                            
     21 root      20   0       0      0      0 S   0.3  0.0   0:00.92 kworker/0:1                                                                           
    229 root      20   0       0      0      0 S   0.3  0.0   0:00.10 jbd2/mmcblk0p30                                                                       
    982 root      20   0   38856   1164    868 S   0.3  0.1   0:01.77 adbd                                                                                  
   2570 phablet   20   0   10540   1456    692 S   0.3  0.1   0:02.30 sshd                                                                                  
      1 root      20   0    3884   2648   1068 S   0.0  0.1   0:05.98 init                                                                                  
      2 root      -2   0       0      0      0 S   0.0  0.0   0:00.01 kthreadd                                                                              
      3 root      20   0       0      0      0 S   0.0  0.0   0:00.04 ksoftirqd/0      

  
  ... it eventually finished after 18 minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1350598/+subscriptions