From: benh@kernel.crashing.org
To: <linuxppc-dev@lists.linuxppc.org>,
Werner Almesberger <wa@almesberger.net>
Subject: Re: performance monitor exceptions
Date: Tue, 12 Feb 2002 13:55:01 +0100 [thread overview]
Message-ID: <20020212125502.32396@mailhost.mipsys.com> (raw)
In-Reply-To: <20020211233730.E5079@almesberger.net>
>It seems to work (I had a handler there that does something a little
>more useful), but when I start kernel builds, I get a dead system
>(rebooted by hardware watchdog) within a few minutes.
>
>Instead of SIAR, I also tried SPRG0 and SPRG1, but got exactly the
>same behaviour. Time to crash varies from one to ten minutes. The
>time increases proportionally if I use TLB[19] (~200 Hz) instead.
>
>Any ideas of what I could be trampling over (or be trampled over
>by) ? This code seems rather bullet-proof to me, and I don't think
>anything else is using SIAR, or could change it while I'm using it.
A first quick look doesn't seem to show any problem with your code
I have two clues at hand:
- I don't know how the perf. mon stuff works, but couldn't you
enter a condition were the CPU is continuously sending your the
pef monitor exception until you clear something else ?
- I encountered a problem with the TAU stuff and the 7400 where
the CPU could actually get mixed up when getting both a normal
interrupt and a TAU exception and scew up itself (by taking both
exceptions and screwing up SRR0/1)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-12 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 22:37 performance monitor exceptions Werner Almesberger
2002-02-12 12:55 ` benh [this message]
2002-02-12 18:33 ` Werner Almesberger
2002-02-13 11:14 ` Anton Blanchard
2002-02-13 12:48 ` benh
2002-02-13 19:01 ` G4 boot crash problems with 2.4 "stable" David A. Gatwood
2002-02-13 19:07 ` benh
2002-02-13 21:09 ` David A. Gatwood
2002-02-13 21:06 ` Benjamin Herrenschmidt
2002-02-13 23:48 ` Ethan Benson
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=20020212125502.32396@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wa@almesberger.net \
/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).