From: Ralf Baechle <ralf@linux-mips.org>
To: Rishabh@soc-soft.com
Cc: linux-mips@linux-mips.org
Subject: Re: HIGHMEM Query
Date: Tue, 22 Feb 2005 11:00:16 +0000 [thread overview]
Message-ID: <20050222110016.GA26269@linux-mips.org> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C571A8D@soc-mail.soc-soft.com>
On Tue, Feb 22, 2005 at 02:31:16PM +0530, Rishabh@soc-soft.com wrote:
> Thanks for the valuable input, I checked the TLB Entry and found
>
> Value in EntryLo0/1 seems absurd. Can you suggest me some way about how
> to approach this problem?
An undecoded oops message is useless, sorry.
Ralf
next prev parent reply other threads:[~2005-02-22 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 9:01 HIGHMEM Query Rishabh
2005-02-22 9:01 ` Rishabh
2005-02-22 11:00 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-17 5:10 Rishabh
2005-02-17 5:10 ` Rishabh
2005-02-17 20:36 ` Ralf Baechle
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=20050222110016.GA26269@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Rishabh@soc-soft.com \
--cc=linux-mips@linux-mips.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