linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "zjznliang" <zjznliang_popo@163.com>,
	"linuxppc-embedded" <linuxppc-embedded@ozlabs.org>
Subject: Re: interrupts limit??
Date: Tue, 15 Nov 2005 07:40:55 -0500	[thread overview]
Message-ID: <005301c5e9e1$d4a69ed0$0301a8c0@chuck2> (raw)
In-Reply-To: 20051115054109.CE1FD68763@ozlabs.org



> Hi ,linuxppc-embedded !
>
>   I have done the interrupt request by request_irq() on the Linux 2.4.25
,when typing the 'cat /proc/interrupts', I can see the information as follow
:
>
> /proc # cat interrupts
>            CPU0
>   2:       3420   8xx SIU   Edge      wbga_interrupt
>   5:          0   8xx SIU   Edge      CPM cascade
>  15:          0   8xx SIU   Edge      tbint
>  16:          0   CPM       Edge      error
>  20:        801   CPM       Edge      SMC1
>
> and I can see the number of wbga_interrupt is increasing. But a few
minutes later ,the number is locked at 128000 as follow:
>
> /proc # cat interrupts
>            CPU0
>   2:     128000   8xx SIU   Edge      wbga_interrupt
>   5:          0   8xx SIU   Edge      CPM cascade
>  15:          0   8xx SIU   Edge      tbint
>  16:          0   CPM       Edge      error
>  20:        833   CPM       Edge      SMC1
>
> and there is no wbga_interrupt any more....what's the matter with the
interrupt?why is 128000???
>
>

The problem is not /proc/interrupts, if that's what you're thinking.  The
number can go much
higher.  Believe what it's telling you:  Your driver has a problem and has
stopped generating
interrupts.

Mark Chambers

      reply	other threads:[~2005-11-15 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15  5:26 interrupts limit?? zjznliang
2005-11-15 12:40 ` Mark Chambers [this message]

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='005301c5e9e1$d4a69ed0$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=zjznliang_popo@163.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).