From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Ani Joshi <ajoshi@shell.unixbox.com>
Cc: "PPC-DEV" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: /proc/ppc_htab
Date: Mon, 17 Apr 2000 23:51:25 +0100 [thread overview]
Message-ID: <200004172244.XAA17952@hyperion.valhalla.net> (raw)
>> A few days ago I saw `mmu_context_overflow' in my kernel messages.
>> The machine locked up on `cat /proc/ppc_htab'. Fortunately it autorebooted
>> after 180 seconds and came back to life again.
>
> I also saw this a few weeks ago, and was meaning to fix it but I was
> unable to reproduce it.
I have not seen the mmu_context_overflow - but the /proc/ppc_htab has been
causing a lock-up since at least 2.3.51 (sorry it slipped my mind).
I'm using Paul's rsync (latest I've tried is 2.3.99-pre3).
> I'm sure you don't feel like crashing a remote box again, but if you or
> anyone else could cat /proc/ppc_htab and tell if panics and perhaps post
> the OOPS.
Unfortunately there was no panic, OOPS or anything - and - unlike Geert's my
system never came back - just locked up completely - requiring a three
finger salute to get anywhere. G3/minitower (beige).
Not as much help as I would like - apart from the fact that it was
completely repeatable - I'm out of circulation for 5 weeks now - paid work
;-) but if there's anything I can supply by tomorrow night that will throw
more light on it - let me know.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-17 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-17 22:51 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-17 19:30 /proc/ppc_htab Geert Uytterhoeven
2000-04-17 20:27 ` /proc/ppc_htab Dan Malek
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=200004172244.XAA17952@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=ajoshi@shell.unixbox.com \
--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).