From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
trenn@suse.de, thoenig@suse.de, stable@kernel.org
Subject: Re: [patch] smbus unhiding kills thermal management
Date: Sat, 13 May 2006 02:04:34 +0200 [thread overview]
Message-ID: <44652292.6070401@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0605121547090.27910@montezuma.fsmlabs.com>
Zwane Mwaikambo wrote:
> On Fri, 12 May 2006, Carl-Daniel Hailfinger wrote:
>
>> Pavel Machek wrote:
>>> Do not enable the SMBus device on Asus boards if suspend
>>> is used. We do not reenable the device on resume, leading to all sorts
>>> of undesirable effects, the worst being a total fan failure after
>>> resume on Samsung P35 laptop.
>>>
>>> Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
>>> Signed-off-by: Pavel Machek <pavel@suse.cz>
>> This is probably also -stable material.
>
> Isn't it inevitable that we're going to have to rerun quirks on resume on
> some hardware?
Yes, but until we have a proper infrastructure for that, we have to
disable the smbus unhiding as a safe fix.
If you have the time to whip up a patch to add a sane quirks-on-resume
infrastructure, I'd be grateful. See the thread
"[RFC] [PATCH] Execute PCI quirks on resume from suspend-to-RAM" for
some ugly proof-of-concept.
My main motivation was to prevent bricking my laptop. Added functionality
is desirable, but secondary.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2006-05-13 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 9:53 [patch] smbus unhiding kills thermal management Pavel Machek
2006-05-12 10:13 ` Carl-Daniel Hailfinger
2006-05-12 10:20 ` Pavel Machek
2006-05-12 10:49 ` Jan Engelhardt
2006-05-12 15:15 ` [stable] " Greg KH
2006-05-13 19:05 ` Pavel Machek
2006-05-12 23:34 ` Zwane Mwaikambo
2006-05-13 0:04 ` Carl-Daniel Hailfinger [this message]
2006-05-12 18:27 ` Andrew Morton
2006-05-12 22:48 ` Carl-Daniel Hailfinger
2006-05-13 0:20 ` Nigel Cunningham
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=44652292.6070401@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=stable@kernel.org \
--cc=thoenig@suse.de \
--cc=trenn@suse.de \
--cc=zwane@arm.linux.org.uk \
/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