weirdcrap Posted November 11, 2016 Share Posted November 11, 2016 I upgraded from 6.2.2 to 6.2.4 two-three days ago and I haven't really been watching the logs much. Since the upgrade to 6.2.4 I have noticed the following in my system log twice now, once this morning and once this afternoon (even after rebooting in between): Nov 11 17:12:08 Node kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Nov 11 17:12:08 Node kernel: CPU: 0 PID: 11501 Comm: emhttp Not tainted 4.4.30-unRAID #2 Nov 11 17:12:08 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Nov 11 17:12:08 Node kernel: 0000000000000000 ffff88081f203e70 ffffffff8136f79f ffff8807e5674800 Nov 11 17:12:08 Node kernel: 0000000000000000 ffff88081f203e98 ffffffff8107f8ce ffff8807e5674800 Nov 11 17:12:08 Node kernel: 0000000000000000 0000000000000010 ffff88081f203ed0 ffffffff8107fb9b Nov 11 17:12:08 Node kernel: Call Trace: Nov 11 17:12:08 Node kernel: <IRQ> [<ffffffff8136f79f>] dump_stack+0x61/0x7e Nov 11 17:12:08 Node kernel: [<ffffffff8107f8ce>] __report_bad_irq+0x2b/0xb4 Nov 11 17:12:08 Node kernel: [<ffffffff8107fb9b>] note_interrupt+0x1a0/0x22e Nov 11 17:12:08 Node kernel: [<ffffffff8107d8d1>] handle_irq_event_percpu+0xe2/0xf0 Nov 11 17:12:08 Node kernel: [<ffffffff8107d915>] handle_irq_event+0x36/0x54 Nov 11 17:12:08 Node kernel: [<ffffffff810803c5>] handle_fasteoi_irq+0x8c/0xf4 Nov 11 17:12:08 Node kernel: [<ffffffff8100e0e8>] handle_irq+0x17/0x1b Nov 11 17:12:08 Node kernel: [<ffffffff8100db3e>] do_IRQ+0x46/0xc2 Nov 11 17:12:08 Node kernel: [<ffffffff8162a6c2>] common_interrupt+0x82/0x82 Nov 11 17:12:08 Node kernel: <EOI> Nov 11 17:12:08 Node kernel: handlers: Nov 11 17:12:08 Node kernel: [<ffffffff814b1e61>] usb_hcd_irq Nov 11 17:12:08 Node kernel: Disabling IRQ #16 Here is my lsdev output (I haven't restarted UnRAID again yet tonight, bunch of people streaming): Device DMA IRQ I/O Ports ------------------------------------------------ 0000:00:02.0 f000-f03f 0000:00:1f.2 27 f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 0000:00:1f.3 f040-f05f 0000:02:00.0 e000-e0ff 0000:03:00.0 29 d000-d01f d020-d023 d030-d037 d040-d043 d050-d057 0000:04:00.0 30 c000-c01f c020-c023 c030-c037 c040-c043 c050-c057 7-edge 7 ACPI 1800-1803 1804-1805 1808-180b 1810-1815 1820-182f 1850-1850 acpi 9 ahci c000-c01f c020-c023 c030-c037 c040-c043 c050-c057 d000-d01f d020-d023 d030-d037 d040-d043 d050-d057 f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 cascade 4 dma 0080-008f dma1 0000-001f dma2 00c0-00df dmar0 24 dmar1 25 ehci_hcd:usb1 16 ehci_hcd:usb2 23 eth0 28 fpu 00f0-00ff i801_smbus 18 f040-f05f i8042 1 12 it87 0a35-0a36 0a35-0a36 keyboard 0060-0060 0064-0064 parport0 5 0378-037a PCI 0000-0cf7 0cf8-0cff 0d00-ffff c000-cfff d000-dfff e000-efff pic1 0020-0021 pic2 00a0-00a1 pnp 04d0-04d1 0680-069f 0a00-0a0f 0a20-0a2f 0a30-0a3f 164e-164f 1854-1857 1c00-1cfe 1d00-1dfe 1e00-1efe 1f00-1ffe ffff-ffff ffff-ffff ffff-ffff PNP0C04:00 00f0-00f0 r8169 e000-e0ff rtc0 8 0070-0077 serial 03f8-03ff timer 0 timer0 0040-0043 timer1 0050-0053 vga+ 03c0-03df xhci_hcd 26 and my proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 30 0 0 0 IR-IO-APIC 2-edge timer 1: 2 0 0 0 IR-IO-APIC 1-edge i8042 5: 0 0 0 0 IR-IO-APIC 5-edge parport0 7: 20 0 0 0 IR-IO-APIC 7-edge 8: 46 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 12: 4 0 0 0 IR-IO-APIC 12-edge i8042 16: 100001 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 29 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 DMAR-MSI 0-edge dmar0 25: 0 0 0 0 DMAR-MSI 1-edge dmar1 26: 1098951 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 27: 1357019 0 0 0 IR-PCI-MSI 512000-edge 0000:00:1f.2 28: 29824263 0 0 0 IR-PCI-MSI 1048576-edge eth0 29: 1010454 0 0 0 IR-PCI-MSI 1572864-edge 0000:03:00.0 30: 20852 0 0 0 IR-PCI-MSI 2097152-edge 0000:04:00.0 NMI: 0 0 0 0 Non-maskable interrupts LOC: 14841433 13022098 13103008 12792463 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 Performance monitoring interrupts IWI: 2 1 2 1 IRQ work interrupts RTR: 0 0 0 0 APIC ICR read retries RES: 3403886 3696337 3346919 3162996 Rescheduling interrupts CAL: 16277 10323 9302 10017 Function call interrupts TLB: 422395 427894 417297 509851 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 105 105 105 105 Machine check polls ERR: 20 MIS: 0 PIN: 0 0 0 0 Posted-interrupt notification event PIW: 0 0 0 0 Posted-interrupt wakeup event I don't have any USB devices plugged in to my UnRAID besides the data cable for my UPS which appears to still be working fine as it is reporting stats. I have attached my Diagnostics log. I checked and I have the latest BIOS version from Gigabyte for my motherboard. I have another Unraid server with some different hardware and I haven't seen any of these USB issues with it and it's also on 6.2.4 Edit: Furthermore, I hadn't plugged any USB devices into my server in a few months so I can't say when this started but yesterday and today on 6.2.4 when I try to mount a USB device with unassigned devices I see a number of USB reset errors after I try to mount them through unassigned devices. It shows the spinning mounting animation and then just disappear. I can manually navigate to the /mnt/disks/ folder and see the device but when trying to copy or read files I receive an i/o error. Here is an excerpt from my system log with the USB resets: Nov 11 09:57:37 Node kernel: usb 3-2: new high-speed USB device number 4 using xhci_hcd Nov 11 09:57:38 Node kernel: usb-storage 3-2:1.0: USB Mass Storage device detected Nov 11 09:57:38 Node kernel: scsi host15: usb-storage 3-2:1.0 Nov 11 09:57:39 Node kernel: scsi 15:0:0:0: Direct-Access Wearable AirStash A02 PQ: 0 ANSI: 0 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: Attached scsi generic sg12 type 0 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Write Protect is off Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Mode Sense: 1b 00 00 00 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] No Caching mode page found Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Assuming drive cache: write through Nov 11 09:57:39 Node kernel: sdm: sdm1 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Attached SCSI removable disk Nov 11 09:57:55 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:58:11 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:58:12 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log unassigned.devices.log Nov 11 09:58:29 Node mount.exfat: volume was not unmounted cleanly Nov 11 09:58:44 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:59:02 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:59:07 Node kernel: usb 3-2: device descriptor read/64, error -110 Nov 11 09:59:18 Node kernel: usb 3-2: USB disconnect, device number 4 Nov 11 09:59:18 Node kernel: sd 15:0:0:0: [sdm] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Nov 11 09:59:18 Node kernel: sd 15:0:0:0: [sdm] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 11 10:02:04 Node sshd[21977]: Accepted publickey for chris from 162.218.150.130 port 58951 ssh2: RSA SHA256:SYxfyeDR9+KFcVaAl11Xt+D5um7ctM81aeKdqdGqv24 Nov 11 10:02:10 Node su[22036]: Successful su for root by chris Nov 11 10:02:10 Node su[22036]: + /dev/pts/2 chris:root Nov 11 10:03:31 Node mount.exfat: failed to read directory cluster 0x7 Nov 11 10:03:31 Node kernel: Buffer I/O error on dev sdm1, logical block 1320, async page read Nov 11 10:04:12 Node mount.exfat: failed to write super block Nov 11 10:05:14 Node kernel: usb 3-10: new high-speed USB device number 5 using xhci_hcd Nov 11 10:05:14 Node kernel: usb-storage 3-10:1.0: USB Mass Storage device detected Nov 11 10:05:14 Node kernel: scsi host16: usb-storage 3-10:1.0 Nov 11 10:05:15 Node kernel: scsi 16:0:0:0: Direct-Access Wearable AirStash A02 PQ: 0 ANSI: 0 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Write Protect is off Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Mode Sense: 1b 00 00 00 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] No Caching mode page found Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Assuming drive cache: write through Nov 11 10:05:15 Node kernel: sdm: sdm1 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:05:31 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:05:47 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:10:41 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:10:57 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:14:26 Node kernel: usb 3-10: USB disconnect, device number 5 Nov 11 10:16:02 Node kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd Nov 11 10:16:02 Node kernel: usb-storage 4-1:1.0: USB Mass Storage device detected Nov 11 10:16:02 Node kernel: scsi host17: usb-storage 4-1:1.0 Nov 11 10:16:03 Node kernel: scsi 17:0:0:0: Direct-Access Monster MONSTER DIGITAL PMAP PQ: 0 ANSI: 6 Nov 11 10:16:03 Node kernel: sd 17:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] 120999936 512-byte logical blocks: (62.0 GB/57.7 GiB) Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Write Protect is off Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Mode Sense: 23 00 00 00 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] No Caching mode page found Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Assuming drive cache: write through Nov 11 10:16:05 Node kernel: sdm: sdm1 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:18:13 Node kernel: usb 4-1: USB disconnect, device number 2 Nov 11 10:18:22 Node kernel: usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd Nov 11 10:18:22 Node kernel: usb-storage 4-2:1.0: USB Mass Storage device detected Nov 11 10:18:22 Node kernel: scsi host18: usb-storage 4-2:1.0 Nov 11 10:18:23 Node kernel: scsi 18:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Write Protect is off Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Mode Sense: 23 00 00 00 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Nov 11 10:18:23 Node kernel: sdm: sdm1 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:18:37 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Nov 11 10:18:49 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log unassigned.devices.log Nov 11 10:18:55 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog I tried the slots on the front of the case and the back of the motherboard and I tried multiple devices. I hooked up an SSD in an orico USB 3 drive enclosure and with an NTFS file system, error. Hooked up a random flash drive formatted in exfat, error. However when I hooked up my monster digital USB 3.0 flash drive that I know i have hooked up to Unraid before I didn't get an error and everything worked fine (this was also exfat formatted). I know the log shows that the drive I attached was not unmounted cleanly but this also happened with the Orico USB 3.0 enclosure with a freshly formatted SSD in it so I don't think the unclean removal is the cause. On an unrelated note did LimeTech change where system logs are saved to on the flash with V6.x? I went to grab logs from the past few weeks and noticed that according to the log/folder time stamps a log hasn't been saved to my flash (/boot/logs) since September 18th and I know I have rebooted quite a few times since september. EDIT2: I also noticed this at the very beginning of my syslog: spurious 8259A interrupt: IRQ7 which appears to have been reported by other users in the 6.2.x announcement threads. Sent with tapatalk node-diagnostics-20161111-1720.zip Quote Link to comment
RobJ Posted November 12, 2016 Share Posted November 12, 2016 These are always a little tough to deal with, because there's little I can say to help. At least in your case, it didn't affect anything if you were not using any USB ports. After it was disabled, any USB ports using usb1 would not work. The only thing I can say is - keep updating. It's a bug, somewhere, but difficult to know where. Because it's an IRQ, it's low level, almost certainly below all unRAID modules. So it could be a bug in a driver, or the kernel, or the motherboard BIOS, or the firmware on a device. What is concerning though is that IRQ assignments like most others are dynamic, and can change between boots. So this time it appears to be assigned to certain USB ports you weren't using, but next time it could be assigned to something you *are* using. Long ago, I had it happen to the USB port my boot drive was plugged in, and to my network card, and to some of my SATA ports! That means I either lost the flash drive, or the network, or some of my drives, and sometimes 2 of those together! If it happens again and something stops working, just reboot. Quote Link to comment
weirdcrap Posted November 12, 2016 Author Share Posted November 12, 2016 These are always a little tough to deal with, because there's little I can say to help. At least in your case, it didn't affect anything if you were not using any USB ports. After it was disabled, any USB ports using usb1 would not work. The only thing I can say is - keep updating. It's a bug, somewhere, but difficult to know where. Because it's an IRQ, it's low level, almost certainly below all unRAID modules. So it could be a bug in a driver, or the kernel, or the motherboard BIOS, or the firmware on a device. What is concerning though is that IRQ assignments like most others are dynamic, and can change between boots. So this time it appears to be assigned to certain USB ports you weren't using, but next time it could be assigned to something you *are* using. Long ago, I had it happen to the USB port my boot drive was plugged in, and to my network card, and to some of my SATA ports! That means I either lost the flash drive, or the network, or some of my drives, and sometimes 2 of those together! If it happens again and something stops working, just reboot. Thanks for the reply. So far after two reboots it has always been IRQ #16 that has problems and it seems to happen after I have tried to plugin a USB device and mount it with unassigned devices as far as I can tell. Neither time has it affected a port or set of ports that have something important plugged in like my APC or the boot flash. Like I said I had issues with UAD yesterday with a device and didn't notice anything in the log about the IRQ until this morning. Then after the reboot I tried to plug in a completely different device and the same thing happened. I can't recall if both times it was usb1. I will try updating my test box to the latest RC even though it isn't having this issue and if everything seems stable I will upgrade NODE next. Could you possibly answer my question at the very end of my monster post, did the place on the flash drive logs are saved get moved? my /boot/logs folder doesn't appear to have been touched since mid September... Quote Link to comment
RobJ Posted November 12, 2016 Share Posted November 12, 2016 Could you possibly answer my question at the very end of my monster post, did the place on the flash drive logs are saved get moved? my /boot/logs folder doesn't appear to have been touched since mid September... Recent unRAID releases have begun saving syslog.txt to the root of the flash. Powerdown saved timestamped logs and diagnostics to the logs folder, so perhaps you uninstalled powerdown in September? I believe they are talking about adding configurable saving of logs and diagnostics, and I believe the Tips and Tweaks plugin has features to do it also. Quote Link to comment
weirdcrap Posted November 13, 2016 Author Share Posted November 13, 2016 Could you possibly answer my question at the very end of my monster post, did the place on the flash drive logs are saved get moved? my /boot/logs folder doesn't appear to have been touched since mid September... Recent unRAID releases have begun saving syslog.txt to the root of the flash. Powerdown saved timestamped logs and diagnostics to the logs folder, so perhaps you uninstalled powerdown in September? I believe they are talking about adding configurable saving of logs and diagnostics, and I believe the Tips and Tweaks plugin has features to do it also. That sounds about right, I uninstalled it whenever he announced that he was discounting support for the powerdown plugin. So UnRAID only saves the most recent shutdown log now? EDIT: I installed dlandon's tips and tweaks plugin to regain the syslog archiving as I find it indispensable to be able to look back at past logs for troubleshooting intermittent issues. Sent from my Nexus 6P using Tapatalk Quote Link to comment
wayner Posted February 7, 2018 Share Posted February 7, 2018 Did you ever fix this. I get this error message on my system although I am not sure that it is causing any issues. I had this under 6.3.5 and now under 6.4.1. On my monitor it also gives the Disabling IRQ 16 message. Feb 3 19:14:57 Hoylake kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Feb 3 19:14:57 Hoylake kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 4.14.16-unRAID #1 Feb 3 19:14:57 Hoylake kernel: Hardware name: System manufacturer System Product Name/P8H67-M EVO, BIOS 3602 10/31/2012 Feb 3 19:14:57 Hoylake kernel: Call Trace: Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: dump_stack+0x5d/0x79 Feb 3 19:14:57 Hoylake kernel: __report_bad_irq+0x32/0xac Feb 3 19:14:57 Hoylake kernel: note_interrupt+0x1d4/0x225 Feb 3 19:14:57 Hoylake kernel: handle_irq_event_percpu+0x39/0x3f Feb 3 19:14:57 Hoylake kernel: handle_irq_event+0x31/0x4f Feb 3 19:14:57 Hoylake kernel: handle_fasteoi_irq+0x8c/0xf3 Feb 3 19:14:57 Hoylake kernel: handle_irq+0x1c/0x1f Feb 3 19:14:57 Hoylake kernel: do_IRQ+0x3b/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: RIP: 0010:ip_sabotage_in+0x2b/0x31 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffff88061f203a60 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff9e Feb 3 19:14:57 Hoylake kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000101536f4c Feb 3 19:14:57 Hoylake kernel: RDX: ffff8805fe8a2090 RSI: 00000000fffffe01 RDI: ffffffff8150ba23 Feb 3 19:14:57 Hoylake kernel: RBP: ffff8805637c0e80 R08: 0000000000000001 R09: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: R10: ffff88061f2039a0 R11: ffff880602c150a0 R12: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: R13: ffff88061f203aa0 R14: 0000000000f00008 R15: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: ? ip_finish_output2+0x278/0x2c2 Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: ip_rcv+0x2f2/0x346 Feb 3 19:14:57 Hoylake kernel: ? ip_local_deliver_finish+0x1b8/0x1b8 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x6ba/0x733 Feb 3 19:14:57 Hoylake kernel: ? ip_output+0xc4/0xcf Feb 3 19:14:57 Hoylake kernel: netif_receive_skb_internal+0xbb/0xd0 Feb 3 19:14:57 Hoylake kernel: br_pass_frame_up+0x12d/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_port_flags_change+0xf/0xf Feb 3 19:14:57 Hoylake kernel: br_handle_frame_finish+0x429/0x459 Feb 3 19:14:57 Hoylake kernel: ? ipt_do_table+0x55f/0x587 [ip_tables] Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_hook_thresh+0x93/0x9e Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing_finish+0x268/0x27a Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? nf_nat_ipv4_in+0x21/0x68 [nf_nat_ipv4] Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing+0x2d8/0x2e8 Feb 3 19:14:57 Hoylake kernel: ? br_nf_forward_ip+0x32c/0x32c Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: br_handle_frame+0x2a0/0x2d3 Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_handle_local_finish+0x31/0x31 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x463/0x733 Feb 3 19:14:57 Hoylake kernel: ? napi_gro_receive+0x42/0x76 Feb 3 19:14:57 Hoylake kernel: ? rtl8169_poll+0x49e/0x4bc [r8169] Feb 3 19:14:57 Hoylake kernel: process_backlog+0x8c/0x12d Feb 3 19:14:57 Hoylake kernel: net_rx_action+0xfb/0x24f Feb 3 19:14:57 Hoylake kernel: __do_softirq+0xcd/0x1c2 Feb 3 19:14:57 Hoylake kernel: irq_exit+0x4f/0x8e Feb 3 19:14:57 Hoylake kernel: do_IRQ+0xa5/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: RIP: 0010:cpuidle_enter_state+0xe0/0x135 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffad Feb 3 19:14:57 Hoylake kernel: RAX: ffff88061f220900 RBX: 0000000000000000 RCX: 000000000000001f Feb 3 19:14:57 Hoylake kernel: RDX: 000014814bafc212 RSI: 0000000000020140 RDI: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: RBP: ffff88061f228600 R08: 000043fc5a01fd81 R09: 0000000000000018 Feb 3 19:14:57 Hoylake kernel: R10: ffffffff81c03ea8 R11: 0000000000000048 R12: 0000000000000001 Feb 3 19:14:57 Hoylake kernel: R13: 000014814bafc212 R14: ffffffff81c59138 R15: 000014814baf9ec5 Feb 3 19:14:57 Hoylake kernel: ? cpuidle_enter_state+0xbb/0x135 Feb 3 19:14:57 Hoylake kernel: do_idle+0x11a/0x179 Feb 3 19:14:57 Hoylake kernel: cpu_startup_entry+0x18/0x1a Feb 3 19:14:57 Hoylake kernel: start_kernel+0x3ea/0x3f2 Feb 3 19:14:57 Hoylake kernel: secondary_startup_64+0xa5/0xb0 Feb 3 19:14:57 Hoylake kernel: handlers: Feb 3 19:14:57 Hoylake kernel: [] usb_hcd_irq Feb 3 19:14:57 Hoylake kernel: Disabling IRQ #16 Quote Link to comment
weirdcrap Posted February 7, 2018 Author Share Posted February 7, 2018 (edited) 1 hour ago, wayner said: Did you ever fix this. I get this error message on my system although I am not sure that it is causing any issues. I had this under 6.3.5 and now under 6.4.1. On my monitor it also gives the Disabling IRQ 16 message. Feb 3 19:14:57 Hoylake kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Feb 3 19:14:57 Hoylake kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 4.14.16-unRAID #1 Feb 3 19:14:57 Hoylake kernel: Hardware name: System manufacturer System Product Name/P8H67-M EVO, BIOS 3602 10/31/2012 Feb 3 19:14:57 Hoylake kernel: Call Trace: Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: dump_stack+0x5d/0x79 Feb 3 19:14:57 Hoylake kernel: __report_bad_irq+0x32/0xac Feb 3 19:14:57 Hoylake kernel: note_interrupt+0x1d4/0x225 Feb 3 19:14:57 Hoylake kernel: handle_irq_event_percpu+0x39/0x3f Feb 3 19:14:57 Hoylake kernel: handle_irq_event+0x31/0x4f Feb 3 19:14:57 Hoylake kernel: handle_fasteoi_irq+0x8c/0xf3 Feb 3 19:14:57 Hoylake kernel: handle_irq+0x1c/0x1f Feb 3 19:14:57 Hoylake kernel: do_IRQ+0x3b/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: RIP: 0010:ip_sabotage_in+0x2b/0x31 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffff88061f203a60 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff9e Feb 3 19:14:57 Hoylake kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000101536f4c Feb 3 19:14:57 Hoylake kernel: RDX: ffff8805fe8a2090 RSI: 00000000fffffe01 RDI: ffffffff8150ba23 Feb 3 19:14:57 Hoylake kernel: RBP: ffff8805637c0e80 R08: 0000000000000001 R09: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: R10: ffff88061f2039a0 R11: ffff880602c150a0 R12: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: R13: ffff88061f203aa0 R14: 0000000000f00008 R15: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: ? ip_finish_output2+0x278/0x2c2 Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: ip_rcv+0x2f2/0x346 Feb 3 19:14:57 Hoylake kernel: ? ip_local_deliver_finish+0x1b8/0x1b8 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x6ba/0x733 Feb 3 19:14:57 Hoylake kernel: ? ip_output+0xc4/0xcf Feb 3 19:14:57 Hoylake kernel: netif_receive_skb_internal+0xbb/0xd0 Feb 3 19:14:57 Hoylake kernel: br_pass_frame_up+0x12d/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_port_flags_change+0xf/0xf Feb 3 19:14:57 Hoylake kernel: br_handle_frame_finish+0x429/0x459 Feb 3 19:14:57 Hoylake kernel: ? ipt_do_table+0x55f/0x587 [ip_tables] Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_hook_thresh+0x93/0x9e Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing_finish+0x268/0x27a Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? nf_nat_ipv4_in+0x21/0x68 [nf_nat_ipv4] Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing+0x2d8/0x2e8 Feb 3 19:14:57 Hoylake kernel: ? br_nf_forward_ip+0x32c/0x32c Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: br_handle_frame+0x2a0/0x2d3 Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_handle_local_finish+0x31/0x31 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x463/0x733 Feb 3 19:14:57 Hoylake kernel: ? napi_gro_receive+0x42/0x76 Feb 3 19:14:57 Hoylake kernel: ? rtl8169_poll+0x49e/0x4bc [r8169] Feb 3 19:14:57 Hoylake kernel: process_backlog+0x8c/0x12d Feb 3 19:14:57 Hoylake kernel: net_rx_action+0xfb/0x24f Feb 3 19:14:57 Hoylake kernel: __do_softirq+0xcd/0x1c2 Feb 3 19:14:57 Hoylake kernel: irq_exit+0x4f/0x8e Feb 3 19:14:57 Hoylake kernel: do_IRQ+0xa5/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: RIP: 0010:cpuidle_enter_state+0xe0/0x135 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffad Feb 3 19:14:57 Hoylake kernel: RAX: ffff88061f220900 RBX: 0000000000000000 RCX: 000000000000001f Feb 3 19:14:57 Hoylake kernel: RDX: 000014814bafc212 RSI: 0000000000020140 RDI: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: RBP: ffff88061f228600 R08: 000043fc5a01fd81 R09: 0000000000000018 Feb 3 19:14:57 Hoylake kernel: R10: ffffffff81c03ea8 R11: 0000000000000048 R12: 0000000000000001 Feb 3 19:14:57 Hoylake kernel: R13: 000014814bafc212 R14: ffffffff81c59138 R15: 000014814baf9ec5 Feb 3 19:14:57 Hoylake kernel: ? cpuidle_enter_state+0xbb/0x135 Feb 3 19:14:57 Hoylake kernel: do_idle+0x11a/0x179 Feb 3 19:14:57 Hoylake kernel: cpu_startup_entry+0x18/0x1a Feb 3 19:14:57 Hoylake kernel: start_kernel+0x3ea/0x3f2 Feb 3 19:14:57 Hoylake kernel: secondary_startup_64+0xa5/0xb0 Feb 3 19:14:57 Hoylake kernel: handlers: Feb 3 19:14:57 Hoylake kernel: [] usb_hcd_irq Feb 3 19:14:57 Hoylake kernel: Disabling IRQ #16 Nope, everytime I plug a USB device into the front USB 3.0 ports I see the irq 16 disabled message. I hardly ever plug in USB devices to this server anymore so I kind of forgot about it lol. What usb chipset do you have? When I go into work tomorrow I will run dmesg on the server and figure out what I have and see if they are related. Edited February 7, 2018 by weirdcrap Quote Link to comment
wayner Posted February 7, 2018 Share Posted February 7, 2018 The USB is from a Asus P8H67-M Evo Asus motherboard and has an i5-2500K CPU. The USB chipsets are: ASMedia® USB 3.0 controller : 2 x USB 3.1 Gen 1 port(s) (2 at back panel, blue) Intel® H67(B3) chipset : 12 x USB 2.0 port(s) (4 at back panel, black, 8 at mid-board) I am not sure which ports I am using but I am pretty sure it is the USB 2.0 ports. I do have two Hauppauge HD-PVRs plugged in as I use this system as a SageTV DVR/media server with the SageTV docker and the LibreElec DVB edition of unRAID. But I never plug things in or out, but it is possible that the HD-PVRs may go up or done that could cause it to behave as if I new USB device was plugged in. Quote Link to comment
weirdcrap Posted February 7, 2018 Author Share Posted February 7, 2018 My Mobo is a Gigabyte B85M-DS3H-A with an i7-4770. According to UnRAID my USB chipsets are both Intel 8 Series C220 based: IOMMU group 3: [8086:8c31] 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) IOMMU group 5: [8086:8c2d] 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) I currently only have a USB keyboard and my APC UPS plugged into two of the back USB2.0 ports. Quote Link to comment
BobPhoenix Posted February 8, 2018 Share Posted February 8, 2018 9 hours ago, wayner said: The USB is from a Asus P8H67-M Evo Asus motherboard and has an i5-2500K CPU. The USB chipsets are: ASMedia® USB 3.0 controller : 2 x USB 3.1 Gen 1 port(s) (2 at back panel, blue) Intel® H67(B3) chipset : 12 x USB 2.0 port(s) (4 at back panel, black, 8 at mid-board) I am not sure which ports I am using but I am pretty sure it is the USB 2.0 ports. I do have two Hauppauge HD-PVRs plugged in as I use this system as a SageTV DVR/media server with the SageTV docker and the LibreElec DVB edition of unRAID. But I never plug things in or out, but it is possible that the HD-PVRs may go up or done that could cause it to behave as if I new USB device was plugged in. You could try disabling the USB3.1 controller in the bios while leaving the USB2.0 controller and see if that gets rid of your problems. HD-PVRs only need USB2.0 so you would still have that working. You might also try moving around any PCIe cards to different slots as that may also eliminate the problem from suggestions I've seen to others with this problem. When I got this I ended up having better luck without the USB3.0 controller but in my case it just took longer for the error to show up. I ran out of time to test further changes so swapped unRAID to a different MB and put Win7 back on the original. Quote Link to comment
wayner Posted February 12, 2018 Share Posted February 12, 2018 (edited) Thanks Bob - I will try that when I get a chance. Even with this I haven't really been having issues. I did have a crash or two when the system was first built a year ago but it has been pretty stable since then. The system went down one other time on Dec 30 but I am not sure if that was a crash or if something else happened. I was thinking that I didn't have any PCI cards but I think I do have a FireWire card to use for changing channels on my STBs. I think it is the older PCI rather than PCIe is that matters. Edited February 13, 2018 by wayner Quote Link to comment
weirdcrap Posted February 25, 2018 Author Share Posted February 25, 2018 On 2/12/2018 at 3:40 PM, wayner said: Thanks Bob - I will try that when I get a chance. Even with this I haven't really been having issues. I did have a crash or two when the system was first built a year ago but it has been pretty stable since then. The system went down one other time on Dec 30 but I am not sure if that was a crash or if something else happened. I was thinking that I didn't have any PCI cards but I think I do have a FireWire card to use for changing channels on my STBs. I think it is the older PCI rather than PCIe is that matters. I may have just solved my irq16 issue, several restarts and USB devices plugged into ports and the front and back have not produced a new IRQ16 disabled error. I found a post on the ubuntu forums that suggested swapping PCI-E cards to different slots fixed it for one user with a Gigabyte motherboard like mine. I had to come in to work on the server today anyways as one of my drives was throwing errors at boot that got its speed downgraded from 6GBps to 3GBps so I figured what the hell I might as well try it. Originally I had two PCI-E 1x expansion cards plugged into the two 1x slots at the bottom of the board. I moved the bottom one off the 1x slot and put it into the x16 slot (I have no need for a GPU) and everything SEEMS to be happy now. IRQ16 is still what it always was according to /proc/interrupts: root@Node:/home/user# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 25 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 5: 0 0 0 0 0 0 0 0 IR-IO-APIC 5-edge parport0 8: 4 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 16: 40 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 38 0 0 0 0 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 25: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 26: 23814 0 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 27: 100794 0 0 0 0 0 0 0 IR-PCI-MSI 512000-edge ahci[0000:00:1f.2] 28: 4017 0 0 0 0 0 0 0 IR-PCI-MSI 524288-edge ahci[0000:01:00.0] 29: 2511 0 0 0 0 0 0 0 IR-PCI-MSI 2097152-edge ahci[0000:04:00.0] 30: 708529 0 0 0 0 0 0 0 IR-PCI-MSI 1572864-edge eth0 NMI: 0 0 0 0 0 0 0 0 Non-maskable interrupts LOC: 140729 218526 231275 187016 186757 154390 152016 148618 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 0 0 0 0 Performance monitoring interrupts IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 20997 7530 3206 2167 1897 1142 1148 958 Rescheduling interrupts CAL: 2144 2680 3039 2932 2581 2553 2516 2791 Function call interrupts TLB: 675 1322 1617 1496 1328 1298 1357 1577 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 DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 5 5 5 5 5 5 5 5 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event We will see if it continues to behave itself over the next week or so. TL;DR try moving your PCI-E cards around if you have other open slots, it may resolve your issue (YMMV). Quote Link to comment
wayner Posted February 28, 2018 Share Posted February 28, 2018 Thanks, I will try moving my PCIe FireWire card the next time I take my system down. Quote Link to comment
wayner Posted March 2, 2018 Share Posted March 2, 2018 It turns out that I don't have any PCI cards - I thought that I may have been using a firewire PCI card but I have firewire on the mobo. Anything else that could be causing this conflict, like USB ports? Quote Link to comment
weirdcrap Posted April 9, 2018 Author Share Posted April 9, 2018 On 3/2/2018 at 1:19 PM, wayner said: It turns out that I don't have any PCI cards - I thought that I may have been using a firewire PCI card but I have firewire on the mobo. Anything else that could be causing this conflict, like USB ports? My issue has not resurfaced since moving my cards around, so it essentially boiled down to some sort of intermittent IRQ conflict because of a shared PCI-E bus I am assuming. Do you have any free USB headers (for front case plugs or the like) on your board? Maybe those are causing the intermittent conflict? I'm honestly just grasping at straws for you though. My only other suggestion is to get really vague with your google terms. I think I found my solution Googling for some combination of Ubuntu and the IRQ 16 error messages thinking that it being one of the most common OSes I was likely to find at least some sort of direction to take my troubleshooting in. Quote Link to comment
weirdcrap Posted September 29, 2019 Author Share Posted September 29, 2019 (edited) Well this has resurfaced for me. but it still hasn't broken anything as far as I can tell. Sep 17 04:51:50 Node kernel: Sep 17 07:29:15 Node kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Sep 17 07:29:15 Node kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.19.56-Unraid #1 Sep 17 07:29:15 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F3 06/23/2017 Sep 17 07:29:15 Node kernel: Call Trace: Sep 17 07:29:15 Node kernel: <IRQ> Sep 17 07:29:15 Node kernel: dump_stack+0x5d/0x79 Sep 17 07:29:15 Node kernel: __report_bad_irq+0x32/0xac Sep 17 07:29:15 Node kernel: note_interrupt+0x1d3/0x224 Sep 17 07:29:15 Node kernel: handle_irq_event_percpu+0x4c/0x6a Sep 17 07:29:15 Node kernel: handle_irq_event+0x33/0x51 Sep 17 07:29:15 Node kernel: handle_fasteoi_irq+0x92/0x102 Sep 17 07:29:15 Node kernel: handle_irq+0x1c/0x1f Sep 17 07:29:15 Node kernel: do_IRQ+0x43/0xc7 Sep 17 07:29:15 Node kernel: common_interrupt+0xf/0xf Sep 17 07:29:15 Node kernel: </IRQ> Sep 17 07:29:15 Node kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141 Sep 17 07:29:15 Node kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 ae 0c be ff fb 66 0f 1f 44 00 00 <48> 2b 1c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cb Sep 17 07:29:15 Node kernel: RSP: 0018:ffffc900031bbea0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde Sep 17 07:29:15 Node kernel: RAX: ffff8887ff120b00 RBX: 0000a4530e23770a RCX: 000000000000001f Sep 17 07:29:15 Node kernel: RDX: 0000a4530e23770a RSI: 0000000025bbf79e RDI: 0000000000000000 Sep 17 07:29:15 Node kernel: RBP: ffff8887ff12b500 R08: 0000000000000002 R09: 00000000000203c0 Sep 17 07:29:15 Node kernel: R10: 0000000000000000 R11: 00022d77397ef3ce R12: 0000000000000001 Sep 17 07:29:15 Node kernel: R13: 0000000000000001 R14: ffffffff81e59ef8 R15: 0000000000000000 Sep 17 07:29:15 Node kernel: do_idle+0x192/0x20e Sep 17 07:29:15 Node kernel: cpu_startup_entry+0x6a/0x6c Sep 17 07:29:15 Node kernel: start_secondary+0x197/0x1b2 Sep 17 07:29:15 Node kernel: secondary_startup_64+0xa4/0xb0 Sep 17 07:29:15 Node kernel: handlers: Sep 17 07:29:15 Node kernel: [<00000000fef8a509>] usb_hcd_irq Sep 17 07:29:15 Node kernel: Disabling IRQ #16 Sep 17 07:29:22 Node kernel: usb 3-4: USB disconnect, device number 3 Sep 17 07:29:22 Node acpid: input device has been disconnected, fd 4 Sep 17 07:29:22 Node acpid: input device has been disconnected, fd 5 Sep 17 07:29:22 Node kernel: usb 3-3: USB disconnect, device number 2 lsdev output: Device DMA IRQ I/O Ports ------------------------------------------------ 0000:00:02.0 f000-f03f 0000:00:1f.2 f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 0000:00:1f.3 f040-f05f 0000:01:00.0 e000-e0ff 0000:03:00.0 d000-d0ff ACPI 1800-1803 1804-1805 1808-180b 1820-182f 1850-1850 acpi 9 ahci f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 ahci[0000:00:1f.2] 27 cascade 4 dma 0080-008f dma1 0000-001f dma2 00c0-00df dmar0 24 dmar1 25 ehci_hcd:usb1 16 ehci_hcd:usb2 23 eth0 28 fpu 00f0-00ff i801_smbus 18 f040-f05f it87 0a35-0a36 0a35-0a36 keyboard 0060-0060 0064-0064 mpt2sas0-msix0 29 parport0 5 0378-037a PCI 0000-0cf7 0cf8-0cff 0d00-ffff d000-dfff e000-efff pic1 0020-0021 pic2 00a0-00a1 pnp 04d0-04d1 0680-069f 0a00-0a0f 0a20-0a2f 0a30-0a3f 164e-164f 1800-18fe 1854-1857 1c00-1cfe 1d00-1dfe 1e00-1efe 1f00-1ffe ffff-ffff ffff-ffff ffff-ffff PNP0C04:00 00f0-00f0 rtc0 8 0070-0077 serial 03f8-03ff timer 0 timer0 0040-0043 timer1 0050-0053 vga+ 03c0-03df xhci_hcd 26 proc/interrupts: root@Node:/home/chris# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 15 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 5: 0 0 0 0 0 0 0 0 IR-IO-APIC 5-edge parport0 8: 0 0 0 0 0 0 0 16 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 16: 0 0 0 0 100000 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 0 0 0 0 0 62 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 25: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 26: 0 0 0 0 0 0 10613557 0 IR-PCI-MSI 327680-edge xhci_hcd 27: 0 0 0 83353875 0 0 0 0 IR-PCI-MSI 512000-edge ahci[0000:00:1f.2] 28: 0 0 0 586057487 0 0 0 0 IR-PCI-MSI 1572864-edge eth0 29: 0 0 13951420 0 0 0 0 0 IR-PCI-MSI 524288-edge mpt2sas0-msix0 NMI: 0 0 0 0 0 0 0 0 Non-maskable interrupts LOC: 278243094 323272078 320776461 464369672 390006397 466715885 334314596 489841114 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 0 0 0 0 Performance monitoring interrupts IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 91232179 22428605 15629623 15981257 17978417 14902807 13537502 16131185 Rescheduling interrupts CAL: 27296443 26806269 26849196 27112582 26490375 26579613 26184317 26649685 Function call interrupts TLB: 27324127 26834263 26876023 27138924 26516517 26605214 26208642 26673101 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 DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 3720 3721 3721 3721 3721 3721 3721 3721 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts HRE: 0 0 0 0 0 0 0 0 Hyper-V reenlightenment interrupts HVS: 0 0 0 0 0 0 0 0 Hyper-V stimer0 interrupts ERR: 1 MIS: 0 PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event Edited September 29, 2019 by weirdcrap Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.