kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #19643
[Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4
After some digging I've found the following:
1. commit a4e449e8a08e727b8160cb4e4a0367c447148d2f enables
drivers/video/omap2/omapfb/omapfb-main.c to send VSYNC uevents on each
vsync.
2. hwcomposer.omap4.so handles this VSYNC event, and inspecting
/proc/$pid/maps it appears this is used by surface flinger.
3. reverting this commit does indeed reduce the events as received by
init, however, surface flinger runs incredibly slowly as it does not get
the vsync events.
Since this is a tight coupling between an Android H/W abstraction and
the kernel driver, I'm not sure how we progress on this. I don't have
the know-how on hwcomposer to figure out how to decouple this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234743
Title:
omapfb module floods system with udev events on samsung galaxy nexus
when playing mp4
Status in “linux” package in Ubuntu:
Incomplete
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
--desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop
--stage_hint=main_stage
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234743/+subscriptions