[Test case]
1. Install the updated package on an x86 system.
2. Reboot.
3. Confirm that the machine boots successfully.
Check on Lenovo x220. Works OK. Passed.
4. Install the updated package on a non-maguro arm system.
5. Reboot.
6. Confirm that the machine boots successfully.
Checked on LG
tag verification-done
Thanks Colin for the comprehensive testing!
--
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
** Changed in: powerd (Ubuntu Saucy)
Status: New = Fix Released
--
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
This bug was fixed in the package systemd - 204-0ubuntu19
---
systemd (204-0ubuntu19) saucy; urgency=low
* Add 0031-ignore-omap-vsync.patch: Gross, but effective hack to ignore
VSYNC change uevents from omapfb, as they happen at each vsync and thus
keep waking up udevd
This bug was fixed in the package systemd - 204-0ubuntu19
---
systemd (204-0ubuntu19) saucy; urgency=low
* Add 0031-ignore-omap-vsync.patch: Gross, but effective hack to ignore
VSYNC change uevents from omapfb, as they happen at each vsync and thus
keep waking up udevd
This is systemd-udevd with the patch, built on the Ubuntu armhf porter
box. That's what I used for testing on the maguro.
** Attachment added: patched systemd-udevd (ARM)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880064/+files/systemd-udevd
--
You received
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
Steve wanted a 0-day SRU with this so that we can build new phone images
with that included. The way the patch is done is that it doesn't change
anything on !arm; this both avoids potentially breaking
i386/amd64/powerpc, and also avoids penalizing those platforms with the
unnecessary extra netlink
This is udevadm with the patch.
** Attachment added: patched udevadm (ARM)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880065/+files/udevadm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Martin: tested this fix and it definitely stops the messages. Thanks!
--
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
** Changed in: lxc-android-config (Ubuntu)
Status: In Progress = Invalid
--
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
On top of pitti's patch, we should ensure that Mir correctly calls into
the power HAL as in
https://android.googlesource.com/platform/frameworks/native/+/03e407270c7ad76632f982c886d0776bed9e9b4c/services/surfaceflinger/DisplayHardware/PowerHAL.cpp:47.
We ignored the call as it is a no-op on Mako.
** Tags added: patch
--
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
Status in Upstart:
Fix
I agree, this is a horrible, horrible patch; and thank you very much for
writing it.
--
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
Hello Colin, or anyone else affected,
Accepted systemd into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/204-0ubuntu19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:~xnox/ubuntu/saucy/systemd/udevd-ignore
--
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
Can anyone confirm that you see these bits:
DRIVER=omapfb
VSYNC=number
in udevadm monitor --kernel -e on that device? It would be really
strange if not, I just want to make double-sure about that before I
start working on a fix tomorrow morning.
--
You received this bug notification because
@Martin, output from udevadm monitor --kernel -e
KERNEL[71.872711] change /devices/platform/omapfb (platform)
ACTION=change
DEVPATH=/devices/platform/omapfb
DRIVER=omapfb
MODALIAS=platform:omapfb
SEQNUM=4650
SUBSYSTEM=platform
VSYNC=71872436527
KERNEL[71.889678] change
Taking over from Dmitrijs as per Steve's request, Dmitrijs got pulled
into installer bugs.
** Changed in: systemd (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Which appears to be getting a FD to kernel event source, via socket
created by
https://android.googlesource.com/platform/hardware/libhardware_legacy/+/android-4.3_r3/uevent/uevent.c
so if we filter those VSYNC events on the udev source, systemd-udev
upstart et al user space shouldn't be
Note, ideally we would already filter them at the kernel netlink
source
That's possible because that android driver doesn't use libudev to get
these events, but sets up its own netlink socket. We really don't want
to see these events anywhere else.
--
You received this bug notification because
when systemd-udevd bug #1235649 is implemented lxc-android-config should
include a udev rule to tag the offending device with tag ignore.
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc-android-config (Ubuntu)
Status: New =
Actually ignore #25.
This bug is about spam from the omapfb modules:
- spam is blocked/ignored in upstart-udev-bridge - Fix Released
- we still need the kernel uevent in linux package - Invalid
- systemd (udevd) should gain ability to ignore events from certain devices (by
tag) - In progress
-
pitti pointed on IRC to
https://android.googlesource.com/kernel/msm/+/57195292 ... which doesnt
help for our driver, but the problem does not seem to be uniqe
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
adjusting bug description, this is sadly a constant condition, not
related to movie playback
** Summary changed:
- omapfb module floods system with udev events on samsung galaxy nexus when
playing mp4
+ omapfb module floods system with udev events on samsung galaxy nexus
--
You received this
h !
look what i found !
http://review.cyanogenmod.org/#/c/28068/
--
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
i cut that down to http://paste.ubuntu.com/6217518/, applied it and
built a kernel ... sadly now Mir does not start at all, SurfaceFlinger
does, but is very slow and complains:
W/SurfaceFlinger( 659): Timed out waiting for hw vsync; faking it
so i guess for using this patch some changes on the
isn't that's kind of what we concluded back in comment #11?
--
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
I believe the library /vendor/lib/hw/hwcomposer.omap4.so depends on
these VSYNCs, I'm unsure how the plumbing works between the kernel and
this library - is this proprietary code?
The kernel just shoves these VSYNC uevents outs for the
hwcompiser.omap4.so to handle. I am of the current
@Dmitrijs,
Today's image is far better, see the attached data for mediaplayer-
app, unity8 and init when playing an mp4. You will see that init is now
far less loaded and not being saturated by events and hence not context
switching like crazy.
** Attachment added: health-check analysis of
We can't disable VSYNC uevent, it's required by the driver. All we can
do is to ignore it later on upper layers, such as upstart.
--
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
So upstart's udev bridge needs to have a capability of filtering events.
Adding an upstart upstream task
** Also affects: upstart
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Branch linked: lp:~xnox/upstart/workaround-1234743
--
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
This bug was fixed in the package powerd -
0.13+13.10.20131007.1-0ubuntu1
---
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
Enabling Mir with VSYNC disabled in the omapfb driver leaves me in a
state with just a blank screen. I can login via adb shell, so I need to
debug this a bit deeper.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks James, I will look into what the driver is doing.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
I suppose this is a driver that would still be in the picture when
switching to Mir, and we can't hope to avoid the issue by changing
display servers? You could test this by following the directions at
https://wiki.ubuntu.com/Touch/Testing/Mir.
--
You received this bug notification because you
38 matches
Mail list logo
