From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 199035] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Date: Sat, 13 Apr 2019 17:23:25 +0000 [thread overview]
Message-ID: <bug-199035-62941-k8LzPuV5tR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199035-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199035
--- Comment #14 from John (jgwphd@yahoo.com) ---
An update: The problem I reported in January went away on its own after a few
weeks of having the problem every single day when I booted each morning. I was
installing Ubuntu software updates when they became available during that time.
There is something going on during boot that causes this problem.
"my speculation" is that I suspect a timing issue with the way things are
initialized during boot up that leads to the problem. Some strange timing issue
is occurring which causes systemd-udevd to fall into an infinite loop
(continuously looking for something or to be notified about an action
completion) and drive one of the processor cores to 100%. When a new kernel was
installed or something was done to change initialization activity during boot
the problem went away because the timing problem that created it was changed. I
believe that some kind of race condition may be at the root of the problem.
From my earlier search on the problem symptoms, it seems that when
systemd-udevd isn't working correctly you can get numerous confusing symptoms
that mysteriously go away when the something changes timing conditions during
boot. Since the problem is in the kernel then it effects other systems besides
Ubuntu.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-04-13 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199035-62941@https.bugzilla.kernel.org/>
2018-10-18 17:53 ` [Bug 199035] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel bugzilla-daemon
2018-12-22 17:54 ` bugzilla-daemon
2019-01-08 18:42 ` bugzilla-daemon
2019-01-08 19:38 ` bugzilla-daemon
2019-04-13 14:02 ` bugzilla-daemon
2019-04-13 17:23 ` bugzilla-daemon [this message]
2019-04-13 17:34 ` bugzilla-daemon
2019-04-13 18:30 ` bugzilla-daemon
2019-04-13 23:27 ` bugzilla-daemon
2019-04-14 14:22 ` bugzilla-daemon
2022-04-13 15:14 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-199035-62941-k8LzPuV5tR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).