CentOS - Aug 2013 - Message from syslogd@localhost ... kernel:Disabling IRQ #17

" Message from syslogd at localhost at Aug 27 08:57:53 ...
  kernel:Disabling IRQ #17" is the message I got
on all my terminal windows at the time indicated.

What is it complaining about?
What should I do about it?

I got some information from dmesg.
It mentions IRQ 17, but the only error is
from before the most recent hibernation.

Here are some excerpts, in order from dmesg:

SELinux: initialized (dev proc, type proc), uses genfs_contexts
hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger 
bdl_pos_adj.
fuse init (API version 7.13)
[Hardware Error]: Machine check events logged
SELinux: initialized (dev sdc1, type vfat), uses genfs_contexts
PM: Syncing filesystems ... done.

ata_piix 0000:00:1f.1: PCI INT A disabled
ACPI: Preparing to enter system sleep state S4
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
CPU 1 is now offline
SMP alternatives: switching to UP code
PM: Creating hibernation image:
PM: Need to copy 141814 pages
PM: Restoring platform NVS memory
microcode: CPU0 updated to revision 0x2e, date = 2004-08-11
Force enabled HPET at resume
Enabling non-boot CPUs ...
SMP alternatives: switching to SMP code
Booting Node 0 Processor 1 APIC 0x1
Initializing CPU#1
microcode: CPU1 updated to revision 0x2e, date = 2004-08-11
CPU1 is up
ACPI: Waking up from system sleep state S4
ata_piix 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2880003, 
writing 0x2880007)

Restarting tasks ... done.
psmouse serio1: ID: 10 00 64
e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
irq 17: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.32-358.14.1.el6.i686 #1
Call Trace:
  [<c04bb8d4>] ? __report_bad_irq+0x24/0x90
  [<c04bba90>] ? note_interrupt+0x150/0x190
  [<c04bc0eb>] ? handle_fasteoi_irq+0x9b/0xc0
  [<c040b9f2>] ? handle_irq+0x32/0x60
  [<c045fe95>] ? irq_exit+0x35/0x70
  [<c040b027>] ? do_IRQ+0x47/0xc0
  [<c0409f10>] ? common_interrupt+0x30/0x38
  [<f80b00d8>] ? radeon_connector_set_property+0x1a8/0x2a0 [radeon]
  [<f80d2f80>] ? r600_irq_process+0x140/0x6f0 [radeon]
  [<f80b9042>] ? radeon_driver_irq_handler_kms+0x12/0x20 [radeon]
  [<c04b9f25>] ? handle_IRQ_event+0x45/0x140
  [<c04bc0b5>] ? handle_fasteoi_irq+0x65/0xc0
  [<c040b9f2>] ? handle_irq+0x32/0x60
  [<c040b027>] ? do_IRQ+0x47/0xc0
  [<c0409f10>] ? common_interrupt+0x30/0x38
  [<c0434f52>] ? native_safe_halt+0x2/0x10
  [<c041121d>] ? default_idle+0x4d/0xc0
  [<c0408884>] ? cpu_idle+0x94/0xd0
  [<c0ac39fc>] ? start_kernel+0x3b0/0x3b5
  [<c0ac348a>] ? unknown_bootoption+0x0/0x190
handlers:
[<f849b2e0>] (snd_intel8x0_interrupt+0x0/0x250 [snd_intel8x0])
[<f915c7f0>] (azx_interrupt+0x0/0x1a0 [snd_hda_intel])
Disabling IRQ #17

google has not helped much.
I note that https://bugzilla.redhat.com/show_bug.cgi?id=381331
was closed with a WONTFIX.

I also grepped dmesg for IRQ and 17.
There were four distinct messages:
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
snd_hda_intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Disabling IRQ #17
The first and last were there once, first and last.
The others alternated, eleven times each.

I think I kow what snd_hda_intel and Intel ICH are, but it doesn't help
I'm really fuzzy on i801_smbus.

What is syslogd complaining about and what should I do about it?

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword."  --  Lily

On Tue, 27 Aug 2013, Michael Hennebry wrote:
> " Message from syslogd at localhost at Aug 27 08:57:53 ...
>  kernel:Disabling IRQ #17" is the message I got
> on all my terminal windows at the time indicated.
>
> What is it complaining about?
> What should I do about it?
Got it again, but I still don't know what to do about it.

Does the "nobody cared" in dmesg always indicate an error?

In case it helps:
root at localhost ~]# cat /proc/interrupts
            CPU0       CPU1
   0:        388          0   IO-APIC-edge      timer
   1:         24          0   IO-APIC-edge      i8042
   4:          2          0   IO-APIC-edge
   7:          0          0   IO-APIC-edge      parport0
   8:          1          0   IO-APIC-edge      rtc0
   9:          0          0   IO-APIC-fasteoi   acpi
  12:    1209667          0   IO-APIC-edge      i8042
  14:      87454          0   IO-APIC-edge      ata_piix
  15:    2100846          0   IO-APIC-edge      ata_piix
  16:     189823        428   IO-APIC-fasteoi   uhci_hcd:usb2, uhci_hcd:usb5,
radeon
  17:    1070465       3084   IO-APIC-fasteoi   Intel ICH5, snd_hda_intel
  18:     485983       3203   IO-APIC-fasteoi   uhci_hcd:usb4, ata_piix
  19:      19004          0   IO-APIC-fasteoi   uhci_hcd:usb3
  20:     701755          0   IO-APIC-fasteoi   eth0
  23:         24          0   IO-APIC-fasteoi   ehci_hcd:usb1
NMI:          0          0   Non-maskable interrupts
LOC:   27051069   26635940   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:          0          0   Performance monitoring interrupts
IWI:          0          0   IRQ work interrupts
RES:   25665728   27955646   Rescheduling interrupts
CAL:       3143      11747   Function call interrupts
TLB:     288739     318210   TLB shootdowns
TRM:      13108      13108   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:        287        283   Machine check polls
ERR:          0
MIS:          0

IIRC snd_hda_intel is sound.
My sound still works.

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword."  --  Lily