public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unexpected kernel messages for Sun Fire X4100 (NUMA Opteron 64bit) with SLES10
Date: Wed, 23 Aug 2006 16:35:53 +0200	[thread overview]
Message-ID: <20060823143553.GA2212@irc.pl> (raw)
In-Reply-To: <44EC7AC0.12128.6635514@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Wed, Aug 23, 2006 at 03:56:47PM +0200, Ulrich Windl wrote:
> I'm currently evaluating Novell/SUSE Enterprise Server 10 (SLES10) on a Sun Fire 
> X4100.
> That machine basically features two Dual-Core AMD Opteron CPUs with 8GB RAM each. 
> I'm running the latest SLES10 kernel (2.6.16.21-0.15-smp #1 SMP Tue Jul 25 
> 15:28:49 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux) and the latest firmware for the 
> hardware (Sun seems not to produce a lot of those however: The Service Processor 
> still runs with "Linux version 2.4.22").

  Are you sure you have latest BIOS installed? From
http://www.sun.com/download/products.xml?id=44cfd445 :
 BIOS 34 (0ABGA034). The improvements are:
    (...)
    * AMD PowerNow support

  Also, you may try if acpi-cpufreq modules works for you.


-- 
Tomasz Torcz                        To co nierealne -- tutaj jest normalne.
zdzichu@irc.-nie.spam-.pl          Ziomale na życie mają tu patenty specjalne.


[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]

  reply	other threads:[~2006-08-23 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 13:56 unexpected kernel messages for Sun Fire X4100 (NUMA Opteron 64bit) with SLES10 Ulrich Windl
2006-08-23 14:35 ` Tomasz Torcz [this message]
2006-08-24 14:39   ` Ulrich Windl

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=20060823143553.GA2212@irc.pl \
    --to=zdzichu@irc.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    /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