mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Schlichter" <thomas.schlichter@web.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "AndrewMorton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: idle Athlon with IOAPIC is 10C warmer since 2.6.3-bk1
Date: Wed, 17 Mar 2004 22:26:53 +0100	[thread overview]
Message-ID: <200403172126.i2HLQrQ09487@mailgate5.cinetic.de> (raw)

"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
> On Wed, 3 Mar 2004, Thomas Schlichter wrote:
> 
> > a few days ago I noticed that my Athlon 3000+ was relatively hot (49C) 
> > although it was completely idle. At that time I was running 2.6.3-mm3 with 
> > ACPI and IOAPIC-support enabled.
> > 
> > As I tried 2.6.3, the idle temperature was at normal 39C. So I did do some 
> > binary search with the -bk patches and found the patch that causes the high 
> > idle temperature. It is ChangeSet@1.1626 aka 8259-timer-ack-fix.patch.
> 
> Interesting -- the patch removes a pair of unnecessary for your
> configuration PIC accesses when using an I/O APIC NMI watchdog. You have 
> the NMI watchdog enabled, don't you?

No, I don't use the NMI watchdog...
So the optimization of removing these I/O accesses is bogus for my configuration. Btw. I don't know if I already mentioned it, but I use the VIA KT400 chipset. Maybe this is of interest...

The only way to cool down my CPU was to enable timer_ack.
I don't know how to help you, but of course I am willing to test patches... ;-)

   Thomas


             reply	other threads:[~2004-03-17 21:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 21:26 Thomas Schlichter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-18  0:19 Ross Dickson
2004-03-18  1:02 ` Craig Bradney
2004-03-18 11:41 ` Bernd Schubert
2004-03-18 11:55   ` Ross Dickson
2004-03-19 18:55 ` Thomas Schlichter
2004-03-19 19:22   ` Prakash K. Cheemplavam
2004-03-19 23:20     ` Len Brown
2004-03-20  9:29       ` Prakash K. Cheemplavam
2004-03-20 10:19         ` Ross Dickson
2004-03-20 10:25           ` Prakash K. Cheemplavam
2004-03-20 10:50             ` Ross Dickson
2004-03-29 19:59             ` Prakash K. Cheemplavam
2004-03-30  0:57               ` Ross Dickson
2004-03-30  9:30                 ` Prakash K. Cheemplavam
2004-03-20 13:07       ` Daniel Egger
     [not found] <A6974D8E5F98D511BB910002A50A6647615F571D@hdsmsx402.hd.intel.com>
2004-03-17 15:53 ` Len Brown
     [not found] <200403032119.58817.thomas.schlichter@web.de>
2004-03-17 15:29 ` Maciej W. Rozycki
2004-03-04 12:47 Thomas Schlichter

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=200403172126.i2HLQrQ09487@mailgate5.cinetic.de \
    --to=thomas.schlichter@web.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    /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

all inboxes | Powered by JetHome®