mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mdaljeet@in.ibm.com
To: linux-kernel@vger.kernel.org
Subject: interrupt problem....
Date: Tue, 26 Jun 2001 10:19:04 +0530	[thread overview]
Message-ID: <CA256A77.001B2342.00@d73mta01.au.ibm.com> (raw)

I am experiencing a strange problem.
I am doing a continuous DMA for long hours using a card on my system. In my
code I enable interrupts and clear the interrupts in the interrupt handler
which is called on completion of every DMA cycle. Now, the program works
fine for say 16-20 hours but I think when the debug files'(where i put some
debug information for each DMA cycle + system log files etc) size becomes
too large, card stops generating interrupts.

1. There is a bit in card that tells that DMA is complete
2. There is a bit in card that tells card to generate interrupt when DMA is
complete
3. If we clear the above two bits, the interrupt handling is complete

Now, DMA is getting complete as the bits specified in the point 1 and 2 are
getting set. I have added a 'printk' in the interrupt handler to see
whether the card is generating interrupts or not. Card stops generating
interrupt. Even if I delete all the debug files and start my program again,
same thing happens. After I reboot the system and run my program, the card
starts working properly with same code.

I have noted following things:

a) If I delete all the system log files and restrict the size of my debug
file, the code runs fine for more than 48 hours. Basically I stop the
program after having a 48 hour run.
b) If the system log files has large size and I do not delete them before
starting my program, the card stops generating interrupts after 16-20 hours
of run.

Any pointers to the problem......????

Regards,
Daljeet.



                 reply	other threads:[~2001-06-26  6:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CA256A77.001B2342.00@d73mta01.au.ibm.com \
    --to=mdaljeet@in.ibm.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®