Would not do any good, the bug is still there under 3.19.  Right now I
am stuck with this one till I fix a bug in speakup.

Volker Armin Hemmann <[email protected]> wrote:


> how about not using an ancient kernel?
> 
> 2015-07-10 11:54 GMT+02:00 <[email protected]>:
> 
> > Hi folks.  I am using 3.16.3-gentoo kernel from gentoo-sources and I get
> > the following sometime after a boot:
> > Jul  9 20:24:26 ccs.covici.com kernel: Disabling IRQ #16
> > This is preceeded by a call trace and on my consoles I see the
> > additional  message  notody cares boot with irqpoll option.
> >
> > I did some googling and this seems to happen even in  3.19 kernels.  So
> > far the system has been still working, (I am not using a display manager
> > right now), but  it seems an instability and the funny thing is that
> > irq 16 does have a handler -- here is the complete /proc/interrupts
> >            CPU0       CPU1       CPU2       CPU3       CPU4       CPU5
> >    CPU6       CPU7
> >   0:         26          0          0          0          0          0
> >       0          0   IO-APIC-edge      timer
> >   1:      51549          0          0          0          0          0
> >       0          0   IO-APIC-edge      i8042
> >   9:          0          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   acpi
> >  12:          4          0          0          0          0          0
> >       0          0   IO-APIC-edge      i8042
> >  16:     213194          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   ehci_hcd:usb2
> >  17:          0          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   pata_marvell
> >  18:          0          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   i801_smbus
> >  19:     602063          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   snd_emu10k1
> >  23:       1889          0          0          0          0          0
> >       0          0   IO-APIC-fasteoi   ehci_hcd:usb4
> >  48:    6224537          0          0          0          0          0
> >       0          0   PCI-MSI-edge      ahci
> >  49:         10          0          0          0          0          0
> >       0          0   PCI-MSI-edge      ahci
> >  50:   31194512          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  51:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  52:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  53:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  54:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  55:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  56:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  57:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      xhci_hcd
> >  58:    1770753          0          0          0          0          0
> >       0          0   PCI-MSI-edge      eth0
> >  59:          0          0          0          0          0          0
> >       0          0   PCI-MSI-edge      eth1
> >  60:    1672015          0          0          0          0          0
> >       0          0   PCI-MSI-edge      eth2-rx-0
> >  61:    2889266          0          0          0          0          0
> >       0          0   PCI-MSI-edge      eth2-tx-0
> >  62:          2          0          0          0          0          0
> >       0          0   PCI-MSI-edge      eth2
> > NMI:        480        259        210        211        129        132
> >     138        135   Non-maskable interrupts
> > LOC:  101443384  104183840  103613415  102110376   99219886  100506540
> >  98662481   96369343   Local timer interrupts
> > SPU:          0          0          0          0          0          0
> >       0          0   Spurious interrupts
> > PMI:        480        259        210        211        129        132
> >     138        135   Performance monitoring interrupts
> > IWI:          1          0          0          0          0          0
> >       0          0   IRQ work interrupts
> > RTR:          1          0          0          0          0          0
> >       0          0   APIC ICR read retries
> > RES:     797796      82005      71556      71029       9728      19203
> >   17339      16821   Rescheduling interrupts
> > CAL:        931       1389       1310       1398       1347        980
> >    1238       1247   Function call interrupts
> > TLB:      11490       9816       8656      10847       5472       5196
> >    6390       6533   TLB shootdowns
> > TRM:          0          0          0          0          0          0
> >       0          0   Thermal event interrupts
> > THR:          0          0          0          0          0          0
> >       0          0   Threshold APIC interrupts
> > MCE:          0          0          0          0          0          0
> >       0          0   Machine check exceptions
> > MCP:        311        311        311        311        311        311
> >     311        311   Machine check polls
> > ERR:          0
> > MIS:          0
> >
> > Thanks in advance for any suggestions.
> >
> >
> > --
> > Your life is like a penny.  You're going to lose it.  The question is:
> > How do
> > you spend it?
> >
> >          John Covici
> >          [email protected]
> >
> >
> 
> ----------------------------------------------------
> Alternatives:
> 
> ----------------------------------------------------

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         [email protected]

Reply via email to