public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Claußen" <jan.claussen10@web.de>
To: "Guenter Roeck" <linux@roeck-us.net>,
	"Jan Claußen" <jan.claussen10@web.de>,
	linux-hwmon@vger.kernel.org
Subject: Re: Weird Dell SMM bug since 6.18
Date: Fri, 13 Mar 2026 20:06:11 +0100	[thread overview]
Message-ID: <DH1W16PFES8U.3MBLJIJPV48JQ@web.de> (raw)
In-Reply-To: <97b6c751-0115-4d00-b212-352f37e5914d@roeck-us.net>

I was actually in a fixed state for some reason and everything worked. I then tried to get back to the broken state and seems that echoing 2 into the pwmX_enable endpoints followed by reboot did the trick.

I then reverted the commits you suggested and it indeed fixed the issue. What to do now? Should coolercontrol adjust its code to this change or the commit be get reverted upstream?

My two cents regarding cranking the fans up to max until the control software kicks in: I think medium fan speed should be sufficent. I actually would always default to BIOS control and make the control software in userspace responsible for setting pwmX_enable.

Regards,
Jan

  reply	other threads:[~2026-03-13 19:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 12:39 Weird Dell SMM bug since 6.18 Jan Claußen
2026-03-13 16:43 ` Guenter Roeck
2026-03-13 19:06   ` Jan Claußen [this message]
2026-03-13 23:10     ` Armin Wolf
2026-03-16 15:52       ` Guenter Roeck
2026-03-16 20:10         ` Jan Claußen
2026-03-17  0:55           ` Guenter Roeck
2026-03-17  1:29             ` Armin Wolf
2026-03-19  9:49               ` Guy Boldon
2026-03-19 15:52                 ` Guenter Roeck
2026-03-22 10:18                   ` Guy Boldon
2026-03-23 10:25                     ` Armin Wolf

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=DH1W16PFES8U.3MBLJIJPV48JQ@web.de \
    --to=jan.claussen10@web.de \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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