From: Andi Kleen <ak@muc.de>
To: Steve Holland <sdh4_no_spammers_throwaway_acct@cornell.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86-64 general protection fault in ioremap_nocache() possibly related to memory beyond 4GB
Date: Wed, 23 Jun 2004 12:43:37 +0200 [thread overview]
Message-ID: <m37jty4krq.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2a4AK-6Ww-11@gated-at.bofh.it> (Steve Holland's message of "Wed, 23 Jun 2004 03:20:06 +0200")
Steve Holland <sdh4_no_spammers_throwaway_acct@cornell.edu> writes:
> I'm having a memory/io mapping related problem with the 2.6 kernel
> (as shipped with Fedora Core 2, tested with kernel-2.6.5-1.358
> and kernel-2.6.6-1.435).
Please try a 2.6.7 kernel.org kernel.
Also your oops messages don't contain registers for some reasons.
Please post full oops messages next time.
-Andi
next parent reply other threads:[~2004-06-23 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2a4AK-6Ww-11@gated-at.bofh.it>
2004-06-23 10:43 ` Andi Kleen [this message]
2004-06-23 1:08 x86-64 general protection fault in ioremap_nocache() possibly related to memory beyond 4GB Steve Holland
2004-06-24 18:54 ` Steve Holland
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=m37jty4krq.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sdh4_no_spammers_throwaway_acct@cornell.edu \
/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