From: Andi Kleen <ak@suse.de>
To: Roland Fehrenbacher <rf@q-leap.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel oops on x86_64 2.4.27 with 8GB RAM and sata_sil
Date: 30 Oct 2004 04:14:42 +0200 [thread overview]
Message-ID: <p73oeilymst.fsf@verdi.suse.de> (raw)
In-Reply-To: <16770.9441.410275.546384@gargle.gargle.HOWL.suse.lists.linux.kernel>
Roland Fehrenbacher <rf@q-leap.de> writes:
> Hi,
>
> I have appended the output of ksymoops obtained from an Oops on an
> Opteron Server that has 8GB RAM. The Oops occurs when disc access to a
> SATA disk is attempted. The disk sits on a SIL3114 controller. There
> is no oops and perfect behaviour if I specify mem=4032M as a kernel
> parameter. Anybody got an idea what is going on?
Enable CONFIG_GART_IOMMU
The kernel warned you about this BTW at boot, but you chose to ignore
the warning.
-Andi
next parent reply other threads:[~2004-10-30 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16770.9441.410275.546384@gargle.gargle.HOWL.suse.lists.linux.kernel>
2004-10-30 2:14 ` Andi Kleen [this message]
2004-10-29 11:09 Kernel oops on x86_64 2.4.27 with 8GB RAM and sata_sil Roland Fehrenbacher
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=p73oeilymst.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rf@q-leap.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