07-20-2006
Hi...
Interrupt Request Line (IRQ) are hardware lines over which devices can send interrupt signals to the microprocessor.
Therefore, what I probably make out from the output is that a device has been assigned an IRQ which is clashing with the IRQ of another device, therefore the kernel disables that IRQ and logs the output.
--
ATUL
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Working out of AIX 4.3.
All logs that were written via application suddenly stopped. executing a tail -f <logfile> was not producing any results.
Tried to refresh the syslogd (daemon). When executing "refresh -s syslogd" system would display
<<0513-036 The request could not be passed to... (2 Replies)
Discussion started by: buRst
2 Replies
2. Cybersecurity
Hi all
My system logger has been down for the past 3 days... I am not able to get it to start from the terminal... /etc/init.d/syslogd start
I am unable to find a log as to why it is failing!!
Please advice where to look!!! I am totally lost here!
Thanks in advance...
KS (5 Replies)
Discussion started by: skotapal
5 Replies
3. UNIX for Advanced & Expert Users
I would like to start up multiple instances of syslog daemon. I am having a little difficulty. Is this at all possible?
I have separate syslog.conf1.... syslog.conf5 files.
I have linked the daemon to separate files syslogd1 ... syslogd5
I have arranged the rcd.2 start/stop scripts for... (9 Replies)
Discussion started by: Gary Dunn
9 Replies
4. UNIX for Advanced & Expert Users
I have a remote syslog server which is recieving messages from many hosts. I would like it to log them in seperate files denoted by hostname . For example all messages for host1 in a directory of the same name. Is there an easy way to do this using syslogd? I have a feeling syslog-ng provides this... (3 Replies)
Discussion started by: silvaman
3 Replies
5. Solaris
Hi friends,
is it possible to ignore special messages with syslogd? we have some errors that are firmware issues an no real faults. we serach for a way to ignore ONLY these messages... OS is solaris 10...
any ideas?
tia,
DN2 (1 Reply)
Discussion started by: DukeNuke2
1 Replies
6. AIX
Hi,
I wanted to log some authentication information, so I added following line to /etc/syslog.conf:
auth.info /home/vilius/dir1/eeerrr.log
After that I refreshed syslogd subsystem:
refresh -s syslogd
To check my logging I made few unsuccessfull attempts to login as root using ssh and... (1 Reply)
Discussion started by: vilius
1 Replies
7. Solaris
Hi All,
I can seem to find the syslog daemon in the /etc/init.d/ dir. i have made change to the syslog.conf i need to restart the daemon. am using solaris 10. i have no problem on version 9
Anyone with a template i can use for log review for auditing purposes. (1 Reply)
Discussion started by: lottiem
1 Replies
8. AIX
Hi Guys,
I am configuring syslogd for Message broker.
I know that we have to add a line user.* /var/log/wmb.log
to the /etc/syslog.conf file.
I want to know what userid does the user in user.* take?
Thanks (1 Reply)
Discussion started by: vandi
1 Replies
9. Solaris
Hi ,
Iam using Solaris8 and as I checked I found syslogd process not running
can please somebody suggest me the way to start it. (2 Replies)
Discussion started by: Laxxi
2 Replies
10. Solaris
Where do I configure where syslogd writes to log files?
I've got open files in an archive directory called errlog.131017 and audlog.131017 and, having run an fuser, it appears that syslogd is writing to these files. (3 Replies)
Discussion started by: psychocandy
3 Replies
LEARN ABOUT SUSE
request_threaded_irq
REQUEST_THREADED_IRQ(9) Hardware Interfaces REQUEST_THREADED_IRQ(9)
NAME
request_threaded_irq - allocate an interrupt line
SYNOPSIS
int request_threaded_irq(unsigned int irq, irq_handler_t handler, irq_handler_t thread_fn, unsigned long irqflags, const char * devname,
void * dev_id);
ARGUMENTS
irq
Interrupt line to allocate
handler
Function to be called when the IRQ occurs. Primary handler for threaded interrupts If NULL and thread_fn != NULL the default primary
handler is installed
thread_fn
Function called from the irq handler thread If NULL, no irq thread is created
irqflags
Interrupt type flags
devname
An ascii name for the claiming device
dev_id
A cookie passed back to the handler function
DESCRIPTION
This call allocates interrupt resources and enables the interrupt line and IRQ handling. From the point this call is made your handler
function may be invoked. Since your handler function must clear any interrupt the board raises, you must take care both to initialise your
hardware and to set up the interrupt handler in the right order.
If you want to set up a threaded irq handler for your device then you need to supply handler and thread_fn. handler ist still called in
hard interrupt context and has to check whether the interrupt originates from the device. If yes it needs to disable the interrupt on the
device and return IRQ_WAKE_THREAD which will wake up the handler thread and run thread_fn. This split handler design is necessary to
support shared interrupts.
Dev_id must be globally unique. Normally the address of the device data structure is used as the cookie. Since the handler receives this
value it makes sense to use it.
If your interrupt is shared you must pass a non NULL dev_id as this is required when freeing the interrupt.
FLAGS
IRQF_SHARED Interrupt is shared IRQF_DISABLED Disable local interrupts while processing IRQF_SAMPLE_RANDOM The interrupt can be used for
entropy IRQF_TRIGGER_* Specify active edge(s) or level
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 REQUEST_THREADED_IRQ(9)