Date: Tue, 4 Nov 2003 00:07:14 -0500 From: "nw1" <network101@covad.net> To: "Technical Director" <trodat@ultratrends.com> Cc: freebsd-questions@freebsd.org Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable-- Message-ID: <008c01c3a291$83406920$0300a8c0@install> References: <Pine.BSF.4.21.0311032052420.22706-100000@server1.ultratrends.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Annotated below. ----- Original Message ----- From: "Technical Director" <trodat@ultratrends.com> To: <freebsd-questions@freebsd.org> Sent: Monday, November 03, 2003 11:07 PM Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable-- > > Forgive me for saying: > No need to ask for forgiveness. I'm looking for honest feedback. :) I have been working with both Tyan and AMD to resolve this, the issue is still here, --more below. > If this system is borked with FreeBSD due to the cpu's not cycling > 'down', then use a different operating system. FreeBSD is not responsible > for your trouble if you can solve the problem by moving on. Doing so and > solving the problem is more important than holding the OS and the > contributors to it accountable to something so seemingly far fetched. I'm kind of stuck on FreeBSD. Not interested in moving on to another *nix or any other OS for that matter. > > One way to test overall integrity of your hardware is to boot to bios and > leave it. Does it bake out on you? Then there is definitely something > wrong with your hardware, perhaps a fan is spinning less rpms than when > new. This has been done. Both the machine with the heat issue and his sister (18" apart) run neck and neck with respect to the hardware monitor readings, temperatures and such, and neither box, as you put it; "bakes out on me/us" <-- this has been tested overnight in a warm environment, the same environment that the OS runs in normally except for this test, we cut the air-conditioner off. This issue I'm dealing with only happens when Freebsd is loaded and the air conditioner is off. > > In my humble opinion this is probably not associated with the OS, but, > that doesn't solve 'your' problem. So besides seeing it for myself I can't > see an absolute need to use FreeBSD, in your words the problem, and not > use some other [$]NIX. > We would rather change hardware than leave FreeBSD --at this point. > One last thing, if your CPU's are baking out and crashing, are you not > nervous that under load this will happen no matter what the OS? Tweaking > system variables will not help you if your server is working ultra-hard, > at some point you will reach a mark that your system should still be able > to do which currently it can't. This does make absolute sense, but this isn't a publicly accessable machine, so it would rarely reach that max_load to cause it to overheat as its doing now, provided, I can find someone to answer the second outstanding question; Where are those sysctl variables that i was previously able to set? They are no longer available > > I doubt hardware manufactuers put out equipment that can't run at 100% at > least. > > My 2 cents. Your "2-cents" makes perfect sense, but as I posted above, I would rather replace either/ or both the motherboard and both processors. Before doing so, I had to hear what the community at large thinks about this. Thank you. :-) > > R. > > On Mon, 3 Nov 2003, nw1 wrote: > > > Both the board(s) and the processors were RMA'd. > > Both boards and all four (4) processors were swapped around between > both OS's and the > > problem remains using the hardware with the FreeBSD OS. The latest > BIOS is installed. > > > > We also have a newly purchased board (S-2466), the same thing occurs. > > > > Details @ http://69.3.136.141/freebsd/installation/sysctl_variables_missing > > > > ----- Original Message ----- > > From: "jon" <jonathan88@email.com> > > To: "nw1" <network101@covad.net> > > Sent: Monday, November 03, 2003 10:00 PM > > Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable-- > > > > > > > On Mon, 2003-11-03 at 19:57, nw1 wrote: > > > > > What version of FreeBSD are you using? > > > > > Did you compile amp into the kernel? > > > > > > > > I think you're not understanding what I posted @ > > > > http://69.3.136.141/freebsd/installation/sysctl_variables_missing > > > > > > > > The first line has what version I'm running. The entire document @ > > > > http://69.3.136.141/freebsd/installation/sysctl_variables_missing implies; this was a > > > > running system with no serious issues; meaning; the sysctl items I'm speaking of were > > in > > > > fact available and working. > > > > > > i can say from prior experience w/ hardware, if you system has > > > overheated you dont know where you stand (you may have damaged all kinds > > > of stuff, we had a board that over heated; then 2nd ide channel went > > > down, when we used micron ram!?! and micron was fine in board until the > > > overheat then any other brand ram worked) tyan has a three year warranty > > > use it! BUT my bet is there is a change in the chipset and you wont get > > > the sysctl mibs anyway. you try the newest BIOS flash? > > > > > > good luck > > > > > > if you want to ensure you get a new board, flex it until you stretch a > > > trace or two. > > > > > > > > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?008c01c3a291$83406920$0300a8c0>