From: Wolfgang Denk <wd@denx.de>
To: Steve Rossi <srossi@labs.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: high priority interrupts disabled
Date: Mon, 10 Dec 2001 19:38:06 +0100 [thread overview]
Message-ID: <20011210183811.E0D6B10E11@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 10 Dec 2001 12:04:16 CST." <3C14F91F.F382ABE3@labs.mot.com>
In message <3C14F91F.F382ABE3@labs.mot.com> you wrote:
>
> Another observation that I've made is that the problem doesn't occur all the
> time, but it seems to be triggered when IRQ2 is asserted during IRQ6
> processing (or while IRQ6 is asserted). If IRQ6 really is being installed with
> SA_INTERRUPT, it would make sense that IRQ2 wouldn't get serviced until IRQ6
> completes, but IRQ6 completes over 120 times before IRQ2 is serviced - that
> doesn't make sense.
Maybe you can get more information using the Linux Trace Toolkit; if
necessary, add some custom traces in the suspected areas of the
interrupt handlers. See http://www.opersys.com/LTT/index.html
Hope this helps,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
People are very flexible and learn to adjust to strange surroundings
-- they can become accustomed to read Lisp and Fortran programs, for
example. - Leon Sterling and Ehud Shapiro, Art of Prolog, MIT Press
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-10 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 20:12 high priority interrupts disabled Steve Rossi
2001-12-07 23:10 ` Dan Malek
2001-12-10 18:04 ` Steve Rossi
2001-12-10 18:38 ` Wolfgang Denk [this message]
2001-12-12 15:27 ` Steve Rossi
2001-12-12 23:09 ` high priority interrupts disabled - problem found Steve Rossi
2001-12-13 4:49 ` Dan Malek
2001-12-13 15:02 ` Steve Rossi
2001-12-13 19:35 ` 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=20011210183811.E0D6B10E11@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=srossi@labs.mot.com \
/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).