Comment 37 for bug 1629469

This issue persists in the kernel version 4.8.3 too.

Please advice me the next steps:

Should I create a new bug report:
 if yes, how can i correctly define problematical process/module, one PID of which should be defined to apport-cli?
- kworker/4u+
- /usr/bin/ibus-daemon --daemonize --xin
2 above have a few CPU activity while flowing messages to kern.log.

Should i report directly-online this bug or i can save a local report-file with further transfer to a bug-tracking system?