From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Jean Delvare <jdelvare@suse.de>
Cc: "Jonathan Buzzard" <jonathan@buzzard.org.uk>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Guenter Roeck" <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
"Mario Limonciello" <mario.limonciello@dell.com>
Subject: Re: i8k_smm_func() takes enormous of time to execute
Date: Fri, 24 Nov 2017 12:17:30 +0100 [thread overview]
Message-ID: <2197616.V8s6m9LJcd@natalenko.name> (raw)
In-Reply-To: <1511518948.15084.9.camel@suse.de>
Hi.
On pátek 24. listopadu 2017 11:22:28 CET Jean Delvare wrote:
> Hi Oleksandr,
>
> On jeu., 2017-11-23 at 22:41 +0100, Oleksandr Natalenko wrote:
> > I've noticed that querying Dell Vostro 3360 hwmon sensor freezes the
> > system
> > completely (like, really completely, even mouse cursor does not move, and
> > sound playback stops) for approx. half of a second. Then, system recovers
> > and runs as usual. Also, sensor readings are okay, for instance:
> >
> > ===
> > $ sensors dell_smm-virtual-0
> > dell_smm-virtual-0
> > Adapter: Virtual device
> > Processor Fan: 5615 RPM
> > CPU: +51.0°C
> > Ambient: +36.0°C
> > Other: +63.0°C
> > SODIMM: +41.0°C
> > ===
> >
> > So, I've used trace-cmd to check what takes that much amount of time to
> > execute, and got this:
> >
> > ===
> > # trace-cmd record -p function_graph -l i8k_smm -F sensors
> > dell_smm-virtual-0 $ trace-cmd report
> > ...
> > sensors-23694 [002] 89099.214369: funcgraph_entry: # 503440.746 us |
> > i8k_smm();
> > ...
> > ===
> >
> > Clearly, 0.5 s delay.
> >
> > Looking at i8k_smm(), it calls i8k_smm_func() on 0th CPU:
> >
> > ===
> >
> > 232 ret = smp_call_on_cpu(0, i8k_smm_func, regs, true);
> >
> > ===
> >
> > which, in turn, does some asm magic.
> >
> > I know that SMM is kinda "black box", and kernel has little to do with it,
> > but I think that under Windows, for instance, it would work without
> > freezes. So, likely, querying SMM might be done differently.
> >
> > I do not know how to approach this issue, thus asking for help/advice.
> > Also, CCing Jonathan since the comment before asm magic says this:
> >
> > ===
> >
> > 137 * Call the System Management Mode BIOS. Code provided by Jonathan
> >
> > Buzzard.
> > ===
> >
> > This was also reported in various places before, for instance, [1], but
> > unfortunately, without any solution.
>
> There are two patches waiting to be tested in
> https://bugzilla.kernel.org/show_bug.cgi?id=195751
Tested and attached a couple of patches on top of those to the BZ. If
disabling fan control is the only approach here, I can confirm that this
works.
Thanks.
Regards,
Oleksandr
next prev parent reply other threads:[~2017-11-24 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 21:41 i8k_smm_func() takes enormous of time to execute Oleksandr Natalenko
2017-11-24 10:22 ` Jean Delvare
2017-11-24 11:17 ` Oleksandr Natalenko [this message]
2017-11-24 11:25 ` Pali Rohár
2017-11-24 12:28 ` Oleksandr Natalenko
2017-12-04 10:35 ` Pali Rohár
2017-12-04 12:08 ` Oleksandr Natalenko
2017-12-04 12:18 ` Pali Rohár
2018-01-27 14:09 ` Pali Rohár
2018-01-27 16:07 ` Guenter Roeck
2017-11-24 11:13 ` Pali Rohár
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=2197616.V8s6m9LJcd@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=jdelvare@suse.de \
--cc=jonathan@buzzard.org.uk \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mario.limonciello@dell.com \
--cc=pali.rohar@gmail.com \
/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