From: David Stroupe <dstroupe@keyed-upsoftware.com>
To: linux-kernel@vger.kernel.org
Subject: printk in interrupt handler
Date: Tue, 30 Apr 2002 12:57:12 -0500 [thread overview]
Message-ID: <3CCEDAF8.5030809@keyed-upsoftware.com> (raw)
I am writing a device driver that responds to interrupts on my custom
device. I have a user-space application that talks to this driver. I
am debugging the user space code using gdb. If I place a breakpoint in
my user code at the first instruction that should be executed after
receipt of an interrupt, I get my breakpoint. Within my driver I have
printk's placed in the handler and in the blocked read instruction that
would give me additional info about the source of the interrupt, irq
status register etc, byt these printk's never appear. Obviously since
the blocked I/O releases, these instructions must be getting executed.
Are these printk commands not flushed due to the debugger's influence?
Is there a way for me to flush them more quickly so that I may view
them with dmesg (or looking at the messages file)?
TIA
--
Best regards,
David Stroupe
Keyed-Up Software
reply other threads:[~2002-04-30 17:57 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=3CCEDAF8.5030809@keyed-upsoftware.com \
--to=dstroupe@keyed-upsoftware.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