From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: ross@datscreative.com.au
Cc: linux-kernel@vger.kernel.org, Jamie Lokier <jamie@shareable.org>,
Ian Kumlien <pomac@vapor.com>,
Jesse Allen <the3dfxdude@hotmail.com>,
Craig Bradney <cbradney@zip.com.au>
Subject: Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay.
Date: Fri, 13 Feb 2004 12:17:34 +0100 [thread overview]
Message-ID: <402CB24E.3070105@gmx.de> (raw)
In-Reply-To: <200402120122.06362.ross@datscreative.com.au>
Hi,
I am just testing this patch with latest 2.6.3-rc2-mm1. It works in that
sense, that my machine doesn't lock up of APIC issue. (If it locks up -
hasn't done yet - then because of something else, I am currently
discssing it in another thread...)
But it doesn't work in the sense of cooling my machine down. Though
athcool reports disconnect is activated it behaves like it is not, ie,
turning disconnect off makes no difference in temperatures. Your old
tack patch in conjunction with 2.6.2-rc1 (linus) works like a charm, ie
no lock-ups and less temp.
Any idea? I haven't taken out the apic_tack line, but I have added the
idle=... line. Should that be a problem? I mean the apic_tack should
safely be ignored, isn't it? Since I swap kernels quite often, I am too
lazy to edit the boot line every time...
Prakash
next prev parent reply other threads:[~2004-02-13 11:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:22 [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-12 18:17 ` Derek Foreman
2004-02-12 16:11 ` Daniel Drake
2004-02-12 19:30 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead " Carlos Silva
2004-02-12 19:54 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead " Derek Foreman
2004-02-12 21:44 ` Jesse Allen
2004-02-12 21:52 ` Derek Foreman
2004-02-12 22:06 ` Craig Bradney
2004-02-12 23:04 ` Jesse Allen
2004-02-12 23:15 ` Craig Bradney
2004-02-12 23:37 ` Jesse Allen
2004-02-12 23:50 ` Craig Bradney
2004-02-12 23:20 ` Roberto Sanchez
2004-02-13 11:17 ` Prakash K. Cheemplavam [this message]
2004-02-13 14:41 ` Ross Dickson
2004-02-13 15:55 ` Nforce2, APIC, CPU Disconnect and setup_boot_APIC_clock() cheuche+lkml
2004-02-14 1:24 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-14 4:46 ` GCC feature request: warn on "if (function_name)" Jamie Lokier
2004-02-14 4:51 ` Andrew Pinski
2004-02-14 11:16 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Prakash K. Cheemplavam
2004-02-14 16:13 ` Ross Dickson
2004-02-14 21:46 ` Ian Kumlien
2004-02-23 1:33 ` Prakash K. Cheemplavam
2004-02-23 19:50 ` Jesse Allen
2004-02-23 1:37 ` Prakash K. Cheemplavam
2004-02-25 12:38 ` Ross Dickson
2004-02-25 19:49 ` Prakash K. Cheemplavam
2004-02-25 21:44 ` Arjen Verweij
2004-02-26 0:13 ` Ross Dickson
2004-02-26 9:59 ` Mikael Pettersson
2004-03-07 14:46 ` Craig Bradney
2004-03-08 22:42 ` Arjen Verweij
2004-03-08 22:59 ` Craig Bradney
2004-03-08 23:11 ` Arjen Verweij
2004-03-14 12:04 ` Arjen Verweij
2004-03-09 18:38 ` Josh McKinney
2004-03-24 15:59 ` Edd Dumbill
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=402CB24E.3070105@gmx.de \
--to=prakashkc@gmx.de \
--cc=cbradney@zip.com.au \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.com \
--cc=ross@datscreative.com.au \
--cc=the3dfxdude@hotmail.com \
/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