From: Dan Malek <dan@mvista.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mmu_context_overflow
Date: Thu, 15 Feb 2001 12:29:11 -0500 [thread overview]
Message-ID: <3A8C11E7.D0CA22F9@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.05.10102151820520.23079-100000@callisto.of.borg
Geert Uytterhoeven wrote:
>
> I found this in my kernel message log:
>
> | mmu_context_overflow
>
> running 2.4.1 from January 31 on a CHRP LongTrail with 604e.
I'm assuming this occurred just once. It's really no big deal
(except it is a one-time overhead to invalidate all contexts).
If it continues to happen, let me know and I'll ask for more
system information.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:21 mmu_context_overflow Geert Uytterhoeven
2001-02-15 17:29 ` Dan Malek [this message]
2001-02-15 20:34 ` mmu_context_overflow christopher.murtagh
2001-02-15 22:27 ` mmu_context_overflow Benjamin Herrenschmidt
2001-02-16 5:40 ` mmu_context_overflow christopher.murtagh
2001-02-16 8:28 ` mmu_context_overflow Benjamin Herrenschmidt
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=3A8C11E7.D0CA22F9@mvista.com \
--to=dan@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).