mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: howarth@bromo.msbb.uc.edu (Jack Howarth)
To: linux-kernel@vger.kernel.org
Subject: W2100Z Critical temperature explained
Date: Tue, 25 Oct 2005 12:43:39 -0400 (EDT)	[thread overview]
Message-ID: <20051025164339.431C81DC06D@bromo.msbb.uc.edu> (raw)

     Has anyone else run into the following problem with the 2.6.12
or 2.6.13 kernels on a Sun W2100Z dual opteron workstation? I found
that the Fedora Core 4 kernel 2.6.12-1.1456_FC4smp was causing random
shutdowns with error messages that 'Critical Temperature was reached: 68 C'.
This was occuring repeatedly under that kernel. After switching to the
latest FC4 kernel, 2.6.13-1.1532_FC4smp, these temperature events seemed
to have been eliminated for now. 
     However in calling the Sun Java Desktop support group, I was told
that the earlier BIOS versions on the W2100Z had bugs that can cause the
errors I was seeing as well as causing the cpu fans to self destruct.
The fix is apparently to upgrade the BIOS to the current one on their
Supplemental 2.1 CD. Is there some site this sort of information should
be added to? Perhaps Linux would be well served if there was a list of
motherboard BIOS kept and noted added regarding compatibility with
various Linux kernels. Certainly in cases like these where destruction
can occur due to the bugs in the firmware, this merits being passed
along to the Linux kernel users.
                     Jack



             reply	other threads:[~2005-10-25 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 16:43 Jack Howarth [this message]
2005-10-25 18:42 ` Alan Cox
2005-11-10 16:27   ` Kjartan Maraas
2005-10-25 23:02 Jack Howarth

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=20051025164339.431C81DC06D@bromo.msbb.uc.edu \
    --to=howarth@bromo.msbb.uc.edu \
    --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

all inboxes | Powered by JetHome®