Results 1 to 2 of 2
Hi all,
For long time I've been getting messages in terminals about IRQ #19:
Code:
daan@schmauck:~$
Message from syslogd@schmauck at Mon Mar 16 18:29:27 2009 ...
schmauck kernel: [ 987.362621] ...
- 03-16-2009 #1
Message from syslogd@schmauck: Disabling IRQ #19
Hi all,
For long time I've been getting messages in terminals about IRQ #19:
I do not note anything going wrong that seems directly related with this message, but I would like to know what it measn and how it can be fixed.Code:daan@schmauck:~$ Message from syslogd@schmauck at Mon Mar 16 18:29:27 2009 ... schmauck kernel: [ 987.362621] Disabling IRQ #19 daan@schmauck:~$
Here's some lines from dmesg:
Code:[ 987.362621] irq 19: nobody cared (try booting with the "irqpoll" option) [ 987.362621] Pid: 0, comm: swapper Tainted: P 2.6.26-1-686 #1 [ 987.362621] [<c015280b>] __report_bad_irq+0x24/0x69 [ 987.362621] [<c0152812>] __report_bad_irq+0x2b/0x69 [ 987.362621] [<c0152a24>] note_interrupt+0x1d4/0x208 [ 987.362621] [<c0151fd2>] handle_IRQ_event+0x23/0x51 [ 987.362621] [<c01530e5>] handle_fasteoi_irq+0x85/0xa4 [ 987.362621] [<c0105f3a>] do_IRQ+0x4d/0x63 [ 987.362621] [<c01042a7>] common_interrupt+0x23/0x28 [ 987.362621] [<c01300d8>] param_set_charp+0x8/0x48 [ 987.362621] [<f8850097>] acpi_idle_enter_bm+0x2a9/0x317 [processor] [ 987.362621] [<c024990d>] cpuidle_idle_call+0x5b/0x86 [ 987.362621] [<c02498b2>] cpuidle_idle_call+0x0/0x86 [ 987.362621] [<c01025ce>] cpu_idle+0xab/0xcb [ 987.362621] ======================= [ 987.362621] handlers: [ 987.362621] [<f894d8d6>] (sdhci_irq+0x0/0x4d5 [sdhci]) [ 987.362621] [<f8a5c440>] (yenta_interrupt+0x0/0xb3 [yenta_socket]) [ 987.362621] [<f8970f5e>] (ide_intr+0x0/0x19b [ide_core]) [ 987.362621] Disabling IRQ #19
OS's I use: Debian testing, Debian stable, Ubuntu, Windows XP, Windows Vista
- 03-18-2009 #2Linux Newbie
- Join Date
- Feb 2009
- Location
- Third ring of Pergatory
- Posts
- 199
I took a quick look at yenta_sockets on the internet and they seem to be used to support pcmcia. You might want to cat >> /proc/irq and see if anything is attached to 19 (unlikely) or missing an IRQ (like pcmcia). If you have PCMCIA architecture you can run a lspcmcia (as a roootlike super being) and see if all the lights are still on.[ 987.362621] [<f8a5c440>] (yenta_interrupt+0x0/0xb3 [yenta_socket])


Reply With Quote
