From: "Pali Rohár" <pali.rohar@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] dell-smm: Blacklist Dell Studio XPS 8000
Date: Sun, 17 Jan 2016 16:51:33 +0000 [thread overview]
Message-ID: <201601171751.33737@pali> (raw)
In-Reply-To: <569BAD28.3060701@leemhuis.info>
[-- Attachment #1.1: Type: Text/Plain, Size: 1108 bytes --]
On Sunday 17 January 2016 17:36:21 Guenter Roeck wrote:
> On 01/17/2016 07:03 AM, Thorsten Leemhuis wrote:
> > Since Linux 4.0 the CPU fan speed is going up and down on Dell
> > Studio XPS 8000 and 8100 for unknown reasons. The 8100 was already
> > blacklisted in Commit a4b45b25f1 This patch blacklists the XPS
> > 8000.
> >
> > Without further debugging on the affected machine, it is not
> > possible to find the problem. For more details see
> > https://bugzilla.kernel.org/show_bug.cgi?id=100121
> >
> > Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> > Acked-by: Pali Rohár <pali.rohar@gmail.com>
> > Cc: stable@vger.kernel.org # v4.0+, will need backport
>
> Applied.
>
> Thanks,
> Guenter
>
Anyway, I would be more happy if somebody with that machine could debug
this issue or at least find part/code/function which cause this problem.
Adding another machine on blacklist is just hot-fix for this problem.
But as stated in commit message, it is really impossible to debug it
without that problematic machine...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2016-01-17 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 15:03 [lm-sensors] [PATCH] dell-smm: Blacklist Dell Studio XPS 8000 Thorsten Leemhuis
2016-01-17 16:36 ` Guenter Roeck
2016-01-17 16:51 ` Pali Rohár [this message]
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=201601171751.33737@pali \
--to=pali.rohar@gmail.com \
--cc=lm-sensors@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 read-only IMAP folder(s) and NNTP newsgroup(s).