Jump to content

irq 16: nobody cared (SOS) (can't find other solution)

Pjrezai
in General Support

Featured Replies

Posted

Hey guys!

 

Very new to the forums so let me know if I am not doing this right.

 

I have looked into other people's threads having the same error and it hasn't helped my situation. Maybe I am missing something.

 

So I have gotten the "irq 16: nobody cared" error in the Fix Common Problems plugin but no further issues arose for awhile. Until recently when I am doing something, like moving a file in Krusader, I will see that all the shares will disappear. When I check the tower via browser all the shares are gone and I cannot access the apps on the dashboard.  I have to do a shutdown and restart for it to come back online, for it all to go down a few minutes later again. Now I just upgraded from 6.5.1 to 6.5.3 and haven't had the issue but still get the "irq 16: nobody cared" error and the log below:

 

Aug 30 14:00:07 Tower root: 136: 5111 0 0 0 0 0 7991 0 0 0 0 0 IR-PCI-MSI 58720256-edge nvme0q0, nvme0q1
Aug 30 14:00:07 Tower root: 137: 10943 5950 4759 3551 2339 1975 15001 8641 6576 5093 3224 1960 IR-PCI-MSI 376832-edge ahci[0000:00:17.0]
Aug 30 14:00:07 Tower root: 138: 908 247 176 314 161 122 540 457 326 521 139 167 IR-PCI-MSI 1048576-edge ahci[0000:02:00.0]
Aug 30 14:00:07 Tower root: 139: 590 230 130 178 56 62 336 338 147 189 92 64 IR-PCI-MSI 59244544-edge ahci[0000:71:00.0]
Aug 30 14:00:07 Tower root: 140: 0 4812 0 0 0 0 0 8855 0 0 0 0 IR-PCI-MSI 58720257-edge nvme0q2
Aug 30 14:00:07 Tower root: 141: 0 0 5379 0 0 0 0 0 9700 0 0 0 IR-PCI-MSI 58720258-edge nvme0q3
Aug 30 14:00:07 Tower root: 142: 0 0 0 3310 0 0 0 0 0 6912 0 0 IR-PCI-MSI 58720259-edge nvme0q4
Aug 30 14:00:07 Tower root: 143: 0 0 0 0 5747 0 0 0 0 0 0 0 IR-PCI-MSI 58720260-edge nvme0q5
Aug 30 14:00:07 Tower root: 144: 0 0 0 0 0 5046 0 0 0 0 0 0 IR-PCI-MSI 58720261-edge nvme0q6
Aug 30 14:00:07 Tower root: 145: 0 0 0 0 0 0 0 0 0 0 5655 0 IR-PCI-MSI 58720262-edge nvme0q7
Aug 30 14:00:07 Tower root: 146: 0 0 0 0 0 0 0 0 0 0 0 5033 IR-PCI-MSI 58720263-edge nvme0q8
Aug 30 14:00:07 Tower root: 147: 428 116 100 93 65 63 283 85 86 115 53 58 IR-PCI-MSI 2097152-edge eth0
Aug 30 14:00:07 Tower root: 148: 321629 99037 80930 104223 59794 53527 265239 94086 83052 102071 52951 45329 IR-PCI-MSI 2097153-edge eth0-TxRx-0
Aug 30 14:00:07 Tower root: 149: 310 184 111 113 113 69 376 178 104 135 88 57 IR-PCI-MSI 2097154-edge eth0-tx-1
Aug 30 14:00:07 Tower root: 150: 255802 103474 86337 103540 62281 53831 294746 92091 79259 95018 52314 44337 IR-PCI-MSI 2097155-edge eth0-tx-2
Aug 30 14:00:07 Tower root: 151: 776 179 196 199 137 95 1295 152 165 137 84 59 IR-PCI-MSI 2097156-edge eth0-tx-3
Aug 30 14:00:07 Tower root: NMI: 0 0 0 0 0 0 0 0 0 0 0 0 Non-maskable interrupts
Aug 30 14:00:07 Tower root: LOC: 231063 209599 217821 212013 239259 214116 201626 207499 210516 192083 227575 214130 Local timer interrupts
Aug 30 14:00:07 Tower root: SPU: 0 0 0 0 0 0 0 0 0 0 0 0 Spurious interrupts
Aug 30 14:00:07 Tower root: PMI: 0 0 0 0 0 0 0 0 0 0 0 0 Performance monitoring interrupts
Aug 30 14:00:07 Tower root: IWI: 0 0 0 0 0 0 0 1 0 0 0 0 IRQ work interrupts
Aug 30 14:00:07 Tower root: RTR: 0 0 0 0 0 0 0 0 0 0 0 0 APIC ICR read retries
Aug 30 14:00:07 Tower root: RES: 99392 37828 13168 108450 5994 63644 11339 7625 6777 63714 4853 52190 Rescheduling interrupts
Aug 30 14:00:07 Tower root: CAL: 2627 3087 2706 3323 2633 4534 2548 3053 2167 3058 2761 3087 Function call interrupts
Aug 30 14:00:07 Tower root: TLB: 792 1250 981 1377 854 2663 799 1290 736 1319 1014 1286 TLB shootdowns
Aug 30 14:00:07 Tower root: TRM: 0 0 0 0 0 0 0 0 0 0 0 0 Thermal event interrupts
Aug 30 14:00:07 Tower root: THR: 0 0 0 0 0 0 0 0 0 0 0 0 Threshold APIC interrupts
Aug 30 14:00:07 Tower root: DFR: 0 0 0 0 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
Aug 30 14:00:07 Tower root: MCE: 0 0 0 0 0 0 0 0 0 0 0 0 Machine check exceptions
Aug 30 14:00:07 Tower root: MCP: 3 3 3 3 3 3 3 3 3 3 3 3 Machine check polls
Aug 30 14:00:07 Tower root: HYP: 0 0 0 0 0 0 0 0 0 0 0 0 Hypervisor callback interrupts
Aug 30 14:00:07 Tower root: ERR: 0
Aug 30 14:00:07 Tower root: MIS: 0
Aug 30 14:00:07 Tower root: PIN: 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt notification event
Aug 30 14:00:07 Tower root: NPI: 0 0 0 0 0 0 0 0 0 0 0 0 Nested posted-interrupt event
Aug 30 14:00:07 Tower root: PIW: 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event

 

Any help would be GREATLY appreciated!!

Let me know if there is anything else I should add since I am new to the forums.

  • Quote

    See the sticky thread 9 from the top in the same section as this thread, entitled "Need help? Read me first"? That's a good place to start. Nobody can help you unless you post your diagnostics.

     

     

    The severity of that error depends on what is using IRQ 16. There was an interrupt on that channel but nothing responded so it went ignored. If it's your disk controller or NIC that's being ignored then it could be a real problem. If not then you might be able to ignore it. One thing you can try is a newer BIOS.

     

    And welcome, BTW. :) 

  • Quote
    • Community Expert
    21 hours ago, Pjrezai said:

    Any help would be GREATLY appreciated!!

     

    As @John_M said, diagnostics (Tools-->Diagnostics from the GUI) would potentially be helpful.

     

    Also, if you do not know what is assigned to IRQ 16, go to a command prompt (>_Terminal from the GUI, PuTTY, console if you have a monitor/keyboard attached to your server) and type "cat /proc/interrupts"

     

    This will show you what driver/process is assigned to your IRQ interrupts.  Knowing that is half the battle.

     

    NOTE: You can also get the interrupt information from the logs, but, the above is a direct way of getting the information without wading through log files.

    Edited by Hoopster

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing