From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: "Luis Miguel García" <ktech@wanadoo.es>
Cc: Craig Bradney <cbradney@zip.com.au>,
Andrew Morton <akpm@osdl.org>,
david+challenge-response@blue-labs.org,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
a.verweij@student.tudelft.nl
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Fri, 06 Feb 2004 01:38:33 +0100 [thread overview]
Message-ID: <4022E209.3040909@gmx.de> (raw)
In-Reply-To: <4022DE3C.1080905@wanadoo.es>
Luis Miguel García wrote:
> Craig Bradney wrote:
>
>>
>>
>>
>> One day hopefully this will be sorted in the BIOSes and in mainline. I
>> keep having to patch for every release (although as thats the only patch
>> I have to do I'm sure there are many worse off than me). I use the 3com
>> n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
>>
>> Best patches are at:
>> http://lkml.org/lkml/2003/12/21/7
>>
>> Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
>> issues.
Unfortunately that patch doesn't work for me. Still locks if I try APIC
+CPU DIsc.
>>
>> (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
>> +exhaust fans in box)
>>
>> Craig
>>
>>
> you mean 31 - 38 C readed from /proc/acpi/temp[........]????
>
> I'm having readings of 53 in idle and even 64 while compiling!! I have
> no case fan, but I don't think it's so important for this bug difference.
The problem is, you cannot trust those infos esp not across board
manufacturers. In case of Abit nearly every bios shows different values...
I have an Athon XP running at 2.1Gz with 1.65vcore. Idle: 50°C (with CPU
Disc usually about 44-40°C) and under load about 54°C. I am usign a more
or less self-made watercooling.
Prakash
next prev parent reply other threads:[~2004-02-06 0:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 19:25 [ACPI] acpi problem with nforce motherboards and ethernet Luis Miguel García
2004-02-05 19:44 ` David Ford
2004-02-05 21:27 ` Luis Miguel García
2004-02-05 23:40 ` Andrew Morton
2004-02-06 0:08 ` Prakash K. Cheemplavam
2004-02-06 0:14 ` Craig Bradney
2004-02-06 0:22 ` Luis Miguel García
2004-02-06 0:38 ` Prakash K. Cheemplavam [this message]
2004-02-06 0:46 ` Luis Miguel García
2004-02-06 0:58 ` Prakash K. Cheemplavam
2004-02-06 1:01 ` Craig Bradney
2004-02-06 1:09 ` Luis Miguel García
2004-02-06 9:28 ` Prakash K. Cheemplavam
2004-02-06 9:26 ` Prakash K. Cheemplavam
2004-02-06 10:07 ` Craig Bradney
2004-02-06 10:40 ` Prakash K. Cheemplavam
2004-02-06 9:44 ` Daniel Drake
2004-02-06 11:04 ` Prakash K. Cheemplavam
2004-02-06 11:15 ` Prakash K. Cheemplavam
2004-02-06 12:51 ` Craig Bradney
2004-02-06 13:10 ` Arjen Verweij
2004-02-06 13:20 ` Prakash K. Cheemplavam
2004-02-06 13:34 ` Arjen Verweij
2004-02-06 13:41 ` Prakash K. Cheemplavam
2004-02-06 13:43 ` Prakash K. Cheemplavam
2004-02-06 11:08 ` Craig Bradney
2004-02-06 0:59 ` Craig Bradney
2004-02-06 0:56 ` Craig Bradney
2004-02-06 23:33 ` Maciej W. Rozycki
2004-02-07 2:50 ` Andi Kleen
2004-02-07 6:39 ` Josh McKinney
2004-02-07 10:04 ` Maciej W. Rozycki
2004-02-07 6:29 ` Luis Miguel García
2004-02-06 9:47 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
2004-02-05 18:41 ` [ACPI] " Arjen Verweij
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=4022E209.3040909@gmx.de \
--to=prakashkc@gmx.de \
--cc=a.verweij@student.tudelft.nl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=cbradney@zip.com.au \
--cc=david+challenge-response@blue-labs.org \
--cc=ktech@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
/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