From: niessner@jpl.nasa.gov
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where is the interrupt going?
Date: Thu, 22 Nov 2007 15:56:33 -0800 [thread overview]
Message-ID: <20071122155633.nzkk5gfz4go8ogc8@webmail.jpl.nasa.gov> (raw)
In-Reply-To: <9a8748490711211816g5df5a81age77ad28c7382a11b@mail.gmail.com>
I do not think so. I have printk (KERN_NOTICE ...) scattered
throughout to make sure the ioctl() is succeeding and to print out
registers on the hardware. Those are showing up in /var/log/messages
without a hitch. If there is a setting for printk in interrupts, then
maybe because I would not know the macro to look for in the
configuration.
Quoting Jesper Juhl <jesper.juhl@gmail.com>, on Wed 21 Nov 2007
06:16:45 PM PST:
> On 22/11/2007, Al Niessner <Al.Niessner@jpl.nasa.gov> wrote:
>>
>> Quickly stated, I have a piece of hardware on the PCI bus that is
>> generating an interrupt (can watch it with a scope) but my handler is
>> not being called (no printk in /var/log/messages). So, where has the
>> interrupt gone?
>>
> Just to rule out the trivial causes. Could it be that you've simply
> not configured your system to log messages at the loglevel that your
> printk() is using?
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please http://www.expita.com/nomime.html
>
next prev parent reply other threads:[~2007-11-23 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 1:08 Where is the interrupt going? Al Niessner
2007-11-22 1:56 ` Alan Cox
2007-11-22 2:14 ` Kyle McMartin
2007-11-22 2:16 ` Jesper Juhl
2007-11-22 23:56 ` niessner [this message]
2007-11-22 2:20 ` Kyle McMartin
2007-11-23 0:48 ` niessner
2007-11-23 1:25 ` Alan Cox
2007-11-23 1:58 ` Bartlomiej Zolnierkiewicz
2007-11-23 10:36 ` Alan Cox
2007-11-23 3:18 ` Marin Mitov
2007-11-23 4:31 ` niessner
2007-11-23 8:16 ` Jiri Slaby
2007-11-22 2:50 ` Arjan van de Ven
2007-11-23 21:53 ` Benjamin Herrenschmidt
2007-11-26 22:49 ` Al Niessner
[not found] <fa.KsmqgW5tYuaXUkIKwnbJk9eJIAI@ifi.uio.no>
[not found] ` <fa.JGl5fAfWYHut6bLbEcD35M84qbY@ifi.uio.no>
[not found] ` <fa.4GMGd+vtd9BoH5cWYyPKXdddZG4@ifi.uio.no>
2007-11-23 1:20 ` Robert Hancock
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=20071122155633.nzkk5gfz4go8ogc8@webmail.jpl.nasa.gov \
--to=niessner@jpl.nasa.gov \
--cc=jesper.juhl@gmail.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;
as well as URLs for NNTP newsgroup(s).