From: Andrew Walrond <andrew@walrond.org>
To: venom@sns.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: P4 Xeon operational temperature range
Date: Sun, 05 Jan 2003 18:51:31 +0000 [thread overview]
Message-ID: <3E187EB3.8010001@walrond.org> (raw)
In-Reply-To: Pine.LNX.4.43.0301051848090.31226-100000@cibs9.sns.it
Hmmm. This is a dual xeon 2.6 blade in a very tight cluster and seems to
hovering around 55C. I had a couple strange crashes and wonder if this
might be the cause I'm unwilling to blame 2.5 ;)
Can anybody recommend a good 1u cooler assembly for socket 603 ?
venom@sns.it wrote:
> depends on the PIV version,
>
> latest 0.13 micron has a maximum temperature of 69 degrees, but if you are going
> under full load over the 50/55 start to be worried.
>
> Luigi
>
> p.s.
> For AThlon AMD talks about 95 degrees, but
> you should ttry not to go over the 60...
>
>
> On Sun, 5 Jan 2003, Andrew Walrond wrote:
>
>
>>Date: Sun, 05 Jan 2003 13:48:11 +0000
>>From: Andrew Walrond <andrew@walrond.org>
>>To: linux-kernel@vger.kernel.org
>>Subject: P4 Xeon operational temperature range
>>
>>Does anybody know off the top of their head the max tempature at which I
>>can expect a P4 Xeon to operate ?
>>
>>TIA Andrew
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
next prev parent reply other threads:[~2003-01-05 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 13:48 P4 Xeon operational temperature range Andrew Walrond
2003-01-05 14:23 ` Murray J. Root
2003-01-05 15:24 ` Andrew Walrond
2003-01-05 17:51 ` venom
2003-01-05 18:51 ` Andrew Walrond [this message]
2003-01-05 18:56 ` venom
2003-01-05 19:26 ` Andrew Walrond
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=3E187EB3.8010001@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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.