This would explain the Session consuming a lot of CPU since those events are generated by the kernel, picked up by the upstart-udev-bridge which injects them into the system init event space. These events are then noticed by the upstart-event-bridge running as phablet and injected into the Session Init with the ":sys:" prefix.
Could you run that again as "strace -fFttv -s 1024 ..." so we can see some timestamps?
Also, please attach /var/log/udev and the output of 'ls -al /proc/$session_init_pid/fd/'.
Adding kernel since as this issue only affects particular hardward, it is highly unlikely to be an Upstart issue.
jibel - thanks. It does indeed look like bug 1234743 as the trace shows a lot of the following events:
:sys:cpu- device- online device- offline supply- device- changed
:sys:cpu-
:sys:power_
This would explain the Session consuming a lot of CPU since those events are generated by the kernel, picked up by the upstart-udev-bridge which injects them into the system init event space. These events are then noticed by the upstart- event-bridge running as phablet and injected into the Session Init with the ":sys:" prefix.
Could you run that again as "strace -fFttv -s 1024 ..." so we can see some timestamps?
Also, please attach /var/log/udev and the output of 'ls -al /proc/$ session_ init_pid/ fd/'.
Adding kernel since as this issue only affects particular hardward, it is highly unlikely to be an Upstart issue.