← Back to team overview

kernel-packages team mailing list archive

[Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4


This bug was fixed in the package powerd -

powerd (0.13+13.10.20131007.1-0ubuntu1) saucy; urgency=low

  [ Seth Forshee ]
  * Don't reset the activity timer for touch events if the screen is of
    (LP: #1234743). (LP: #1234743)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 98
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Mon, 07 Oct 2013 12:06:34 +0000

** Branch linked: lp:ubuntu/saucy-proposed/powerd

** Changed in: powerd (Ubuntu)
       Status: New => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  omapfb module floods system with udev events on samsung galaxy nexus
  when playing mp4

Status in “linux” package in Ubuntu:
Status in “powerd” package in Ubuntu:
  Fix Released

Bug description:
  Playing an mp4 on a Samsung Galaxy Nexus using today's image (3 Oct
  2013) for 30 minutes I observed that init is busy and also consuming
  heap quite rapidly.

  Attached is the output from running health-check (found in PPA:colin-
  king/white) on init pid 1114.

  Key points:

  1. messages being read/written at ~600 messages a second, hence the high context switch rate and ~4.9% CPU load. 
  2. heap consumption: ~30K a second using brk() and 2K a second via mmap

  To reproduce:

  Install health-check:

  sudo add-apt-repository ppa:colin-king/white
  sudo apt-get update && sudo apt-get install health-check

  Download a large mp4 to the phone. Keep screen from blanking using:

  sudo powerd-cli display on bright &

  then play the mp4:

  dbus-launch mediaplayer-app test.mp4

  And then observe that init is busy for 300 seconds:

  ps -e | grep init
      1 ?        00:02:56 init
    348 ?        00:00:00 init
   1114 ?        00:03:22 init

  sudo health-check -p 1114 -d 300

  Attached are my results for a 30 minute run.

To manage notifications about this bug go to: