From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Jürgen Stauber" <j.stauber@icloud.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: High load from process irq/65-i2c-INT3 - kernel module tps6598x
Date: Tue, 28 Jul 2020 15:32:00 +0300 [thread overview]
Message-ID: <20200728123200.GF883641@kuha.fi.intel.com> (raw)
In-Reply-To: <376EFB02-6CA2-4D5A-883B-7843B6F6B6EC@icloud.com>
Hi Jürgen,
I'm sorry about the late reply (vacation).
On Mon, Jul 20, 2020 at 06:31:04PM +0200, Jürgen Stauber wrote:
> Hi all,
>
> I was made aware in the following launchpad bug report, that I should report
> the issue directly with the upstream maintainers:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511
> <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511>
>
> As mentioned in the report, I experience high cpu load due to an interrupted
> irq/65-i2c-INT3 process. A short fix is to unload the kernel module tps6598x.
>
> Please be lenient with me, since I’ve got no glue whether I’m doing this
> correctly.
>
> In case you need more details/logs/information, please let me know.
There is one thing that you may be able to try. If you can enter the
BIOS menu, then you should be able to disable an option called
"UCMCx". Unfortunately I don't know the full path to that option in
the BIOS menu of the NUC, or is entering the BIOS menu possible in the
first place. It is also possible that there is no option "UCMCx" at
all.
Unfortunately I don't have access to NUC10 at the moment, but I'll try
get one.
Br,
--
heikki
next prev parent reply other threads:[~2020-07-28 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 16:31 Jürgen Stauber
2020-07-28 12:32 ` Heikki Krogerus [this message]
2020-08-01 4:55 ` Jürgen Stauber
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=20200728123200.GF883641@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.stauber@icloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
Powered by JetHome