This patch adds netlink filter rules to ignore change events from omapfb if they are long enough to be a VSYNC event. It is a rather gross hack, I don't want to expect the VSYNC= at a specific place in the raw packet as the order or length of the other properties might change. But I verified that doing a manual "echo change | tee /sys/devices/platform/omapfb/uevent" still gets through, whereas the offending vsync events are now quiet and don't wake up anything any more.
For testing, I ran my locally built udev with "sudo stop udev", "sudo ./systemd-udevd --daemon", started a monitor with "./udevadm monitor -e", and then: * screen activity now does not produce any omapfb change events any more. Tested remotely with starting and stopping messaging-app with "start application APP_ID=messaging-app; sleep 5; pkill -e messaging- app" * "echo change | sudo tee /sys/devices/platform/omapfb/uevent" shows that synthetic uevent on both the KERNEL and LIBUDEV netlink sources. Thanks to Omer for giving me ssh access to his maguro, which helped to shorten the turnaround time. This device was running with SurfaceFlinger, so for making triple sure another test should be done on Mir. ** Patch added: "udev: filter omapfv VSYNC uevents from netfilter" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880060/+files/0031-ignore-omap-vsync.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1234743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
