Leondre Posted May 2, 2018 Share Posted May 2, 2018 Found this gem in the syslog today, would anyone be able to shed any light on why this would have happened? Nothing appears to be broken at the moment. Strangely the timestamp seems to match the only hardware change I've made to the machine in a very long time and that was just plugging in a hdmi cable to the onboard GPU, though I don't understand why that would cause it. May 1 18:49:06 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) May 1 18:49:06 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.35-unRAID #1 May 1 18:49:06 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z270N-WIFI/Z270N-WIFI-CF, BIOS F5 07/06/2017 May 1 18:49:06 Tower kernel: Call Trace: May 1 18:49:06 Tower kernel: <IRQ> May 1 18:49:06 Tower kernel: dump_stack+0x5d/0x79 May 1 18:49:06 Tower kernel: __report_bad_irq+0x32/0xac May 1 18:49:06 Tower kernel: note_interrupt+0x1d4/0x225 May 1 18:49:06 Tower kernel: handle_irq_event_percpu+0x39/0x3f May 1 18:49:06 Tower kernel: handle_irq_event+0x31/0x4f May 1 18:49:06 Tower kernel: handle_fasteoi_irq+0x8c/0xf3 May 1 18:49:06 Tower kernel: handle_irq+0x1c/0x1f May 1 18:49:06 Tower kernel: do_IRQ+0x3b/0xbb May 1 18:49:06 Tower kernel: common_interrupt+0x7d/0x7d May 1 18:49:06 Tower kernel: </IRQ> May 1 18:49:06 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe3/0x135 May 1 18:49:06 Tower kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff7d May 1 18:49:06 Tower kernel: RAX: ffff88042ec20980 RBX: 0000000000000000 RCX: 000000000000001f May 1 18:49:06 Tower kernel: RDX: 00024e417ba40eef RSI: 0000000000020180 RDI: 0000000000000000 May 1 18:49:06 Tower kernel: RBP: ffff88042ec28800 R08: 0006b245a498f2dc R09: 0000000000000018 May 1 18:49:06 Tower kernel: R10: ffffffff81c03ea8 R11: 0000000000000000 R12: 0000000000000001 May 1 18:49:06 Tower kernel: R13: 00024e417ba40eef R14: ffffffff81c591f8 R15: 00024e417ba40215 May 1 18:49:06 Tower kernel: ? cpuidle_enter_state+0xbb/0x135 May 1 18:49:06 Tower kernel: do_idle+0x11a/0x179 May 1 18:49:06 Tower kernel: cpu_startup_entry+0x18/0x1a May 1 18:49:06 Tower kernel: start_kernel+0x3e4/0x3ec May 1 18:49:06 Tower kernel: secondary_startup_64+0xa5/0xb0 May 1 18:49:06 Tower kernel: handlers: May 1 18:49:06 Tower kernel: [<ffffffffa0000d50>] i801_isr [i2c_i801] May 1 18:49:06 Tower kernel: Disabling IRQ #16 root@Tower:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 44 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 8: 18 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: 100000 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi i801_smbus 120: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 121: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 122: 0 0 0 0 0 0 0 0 DMAR-MSI 128-edge dmar0-prq 123: 3284078 0 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 124: 16477549 0 0 0 0 0 0 0 IR-PCI-MSI 376832-edge ahci[0000:00:17.0] 125: 1 0 0 0 0 0 0 0 IR-PCI-MSI 3670016-edge eth0 126: 52832651 0 0 0 0 0 0 0 IR-PCI-MSI 524288-edge mpt2sas0-msix0 127: 69674258 0 0 0 0 0 0 0 IR-PCI-MSI 3670017-edge eth0-rx-0 128: 344802 0 0 0 0 0 0 0 IR-PCI-MSI 3670018-edge eth0-rx-1 129: 24255990 0 0 0 0 0 0 0 IR-PCI-MSI 3670019-edge eth0-tx-0 130: 51567192 0 0 0 0 0 0 0 IR-PCI-MSI 3670020-edge eth0-tx-1 131: 344802 0 0 0 0 0 0 0 IR-PCI-MSI 520192-edge eth1 NMI: 0 0 612 0 0 0 0 0 Non-maskable interrupts LOC: 216834455 258160260 164850430 119864597 302686535 281394935 129574123 109494595 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 612 0 0 0 0 0 Performance monitoring interrupts IWI: 2 0 27 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 50032888 12236939 68080807 52929105 1340832 1106603 66894393 43870617 Rescheduling interrupts CAL: 550854 629917 567107 604028 655691 654758 603215 618110 Function call interrupts TLB: 498074 577130 453380 446509 602377 601486 455888 487348 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: 2106 2106 2106 2106 2106 2106 2106 2106 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 tower-diagnostics-20180502-0615.zip Quote Link to comment
JorgeB Posted May 2, 2018 Share Posted May 2, 2018 Should be safe to ignore, bios update and/or newer kernel might fix it. 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.