All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Adrian Schröter" <adrian@suse.de>,
	"Knut Petersen" <Knut_Petersen@t-online.de>,
	linux-kernel@vger.kernel.org, "Andrew Morton" <akpm@osdl.org>,
	pavel@ucw.cz, lenb@kernel.org, "Zhang, Rui" <rui.zhang@intel.com>,
	"Jean Delvare" <khali@linux-fr.org>,
	"Alexey Starikovskiy" <aystarik@gmail.com>
Subject: Re: 2.6.22 regression: thermal trip points
Date: Thu, 2 Aug 2007 13:15:56 +0100	[thread overview]
Message-ID: <20070802121556.GA30114@srcf.ucam.org> (raw)
In-Reply-To: <1186056386.18821.497.camel@queen.suse.de>

On Thu, Aug 02, 2007 at 02:06:26PM +0200, Thomas Renninger wrote:
> On Thu, 2007-08-02 at 12:57 +0100, Matthew Garrett wrote:
> > On Thu, Aug 02, 2007 at 12:59:47PM +0100, Alan Cox wrote:
> > > Windows as I understand it has vendor mechanisms to allow the bits
> > > shipped with the OS to override/ignore just about everything trip points
> > > included. Lots of hardware that requires fixups in Linux and just works
> > > in Windows is not Linux bugs but Windows magic .inf files and other
> > > registry gunge done by the machine vendor. We see this in ATA, in power
> > > management and elsewhere.
> > 
> > I've seen no evidence that this happens with thermal trip points.
> 
> WMI needed for fan control -- FSC Amilo M3438G
> http://bugzilla.kernel.org/show_bug.cgi?id=5670

That machine has no active thermal trip points, so I'm not sure how it's 
relevant here. By the sounds of the bug log, I suspect Linux just runs 
slightly hotter on the machine than Windows does - especially since the 
user isn't running the closed nvidia driver, so there's nothing to carry 
out any power management on the GPU.
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2007-08-02 12:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  8:40 2.6.22 regression: thermal trip points Knut Petersen
2007-08-02  8:52 ` Andrew Morton
2007-08-02 10:48   ` Andi Kleen
2007-08-02 11:00     ` Alan Cox
2007-08-02 12:05       ` Andi Kleen
2007-08-02 13:04         ` Alan Cox
2007-08-02 13:16           ` Andi Kleen
2007-08-02 15:57             ` Pavel Machek
2007-08-02 18:38               ` Andi Kleen
2007-08-02 18:40                 ` Matthew Garrett
2007-08-03 11:16                 ` Thomas Renninger
2007-08-03 18:59                   ` Len Brown
2007-08-06  9:55                     ` Pavel Machek
2007-08-07 18:58                       ` Len Brown
2007-08-07 21:49                         ` Pavel Machek
2007-08-13 12:30                           ` Pavel Machek
2007-08-02 15:55     ` Pavel Machek
2007-08-02  9:42 ` Thomas Renninger
2007-08-02  9:45   ` Adrian Schröter
2007-08-02  9:58     ` Thomas Renninger
2007-08-02 11:02       ` Alan Cox
2007-08-02 11:13         ` Matthew Garrett
2007-08-02 11:45           ` Thomas Renninger
2007-08-02 11:56             ` Matthew Garrett
2007-08-02 12:42               ` Thomas Renninger
2007-08-02 12:55                 ` Matthew Garrett
2007-08-02 11:59           ` Alan Cox
2007-08-02 11:57             ` Matthew Garrett
2007-08-02 12:06               ` Thomas Renninger
2007-08-02 12:15                 ` Matthew Garrett [this message]
2007-08-02 12:35                   ` Thomas Renninger
2007-08-02 12:47                     ` Matthew Garrett
2007-08-02 21:56     ` Len Brown
2007-08-02 21:56       ` Len Brown
2007-08-02 11:32   ` Knut Petersen
2007-08-02 12:06     ` Andi Kleen
2007-08-02 13:06       ` Alan Cox
2007-08-02 16:07     ` Pavel Machek
2007-08-02 19:25     ` Krzysztof Halasa
2007-08-02 21:56 ` Len Brown
2007-08-02 21:56   ` Len Brown
2007-08-03 11:43   ` Renato S. Yamane
2007-08-03 18:35     ` Len Brown
2007-08-03 12:53   ` Knut Petersen
2007-08-03 18:30     ` Len Brown

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=20070802121556.GA30114@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=Knut_Petersen@t-online.de \
    --cc=adrian@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=aystarik@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rui.zhang@intel.com \
    --cc=trenn@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.