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
>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/