BrttClne22 Posted March 19, 2018 Share Posted March 19, 2018 As fix common problems suggested, I'm just checking to see if this is something I need to worry about. I, unfortunately, don't have a clue what I'm looking at here. Thanks in advance! unRaid 6.5.0 Gigabyte Z170X-Gaming 7 Intel Core i7-6700k EVGA GTX1080 USB Card for VM Passthrough (NEW) LSI 9207-8i > 5x 8TB WD RED > 1x 1TB Samsung EVO SSD > 1x 512GB Samsung PRO SSD (recently unassigned) 1x 512GB 950 PRO NVMe (unassigned for VM) Mar 19 17:22:38 ZEUS kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Mar 19 17:22:38 ZEUS kernel: CPU: 0 PID: 25975 Comm: find Not tainted 4.14.26-unRAID #1 Mar 19 17:22:38 ZEUS kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z170X-Gaming 7, BIOS F7 03/11/2016 Mar 19 17:22:38 ZEUS kernel: Call Trace: Mar 19 17:22:38 ZEUS kernel: <IRQ> Mar 19 17:22:38 ZEUS kernel: dump_stack+0x5d/0x79 Mar 19 17:22:38 ZEUS kernel: __report_bad_irq+0x32/0xac Mar 19 17:22:38 ZEUS kernel: note_interrupt+0x1d4/0x225 Mar 19 17:22:38 ZEUS kernel: handle_irq_event_percpu+0x39/0x3f Mar 19 17:22:38 ZEUS kernel: handle_irq_event+0x31/0x4f Mar 19 17:22:38 ZEUS kernel: handle_fasteoi_irq+0x8c/0xf3 Mar 19 17:22:38 ZEUS kernel: handle_irq+0x1c/0x1f Mar 19 17:22:38 ZEUS kernel: do_IRQ+0x3b/0xbb Mar 19 17:22:38 ZEUS kernel: common_interrupt+0x7d/0x7d Mar 19 17:22:38 ZEUS kernel: </IRQ> Mar 19 17:22:38 ZEUS kernel: RIP: 0010:path_openat+0x243/0xbec Mar 19 17:22:38 ZEUS kernel: RSP: 0018:ffffc9000547bd08 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff7e Mar 19 17:22:38 ZEUS kernel: RAX: 0000000000000140 RBX: ffffc9000547bdd0 RCX: 0000000000028000 Mar 19 17:22:38 ZEUS kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8804abe4e780 Mar 19 17:22:38 ZEUS kernel: RBP: ffff880647808c00 R08: 61c8864680b583eb R09: ffff8804abe4e780 Mar 19 17:22:38 ZEUS kernel: R10: 0000000000000000 R11: 8080808080808080 R12: ffffc9000547bef4 Mar 19 17:22:38 ZEUS kernel: R13: 00000000ffffff9c R14: 0000000000000000 R15: 0000000000000000 Mar 19 17:22:38 ZEUS kernel: ? path_openat+0x1b2/0xbec Mar 19 17:22:38 ZEUS kernel: ? btrfs_set_path_blocking+0x20/0x44 Mar 19 17:22:38 ZEUS kernel: ? btrfs_get_delayed_node+0xea/0xf4 Mar 19 17:22:38 ZEUS kernel: ? release_extent_buffer+0x7e/0x85 Mar 19 17:22:38 ZEUS kernel: do_filp_open+0x48/0x9e Mar 19 17:22:38 ZEUS kernel: ? touch_atime+0x22/0x9d Mar 19 17:22:38 ZEUS kernel: ? rcu_is_watching+0xc/0x1e Mar 19 17:22:38 ZEUS kernel: ? lockref_put_or_lock+0x33/0x51 Mar 19 17:22:38 ZEUS kernel: ? do_sys_open+0x129/0x1b0 Mar 19 17:22:38 ZEUS kernel: do_sys_open+0x129/0x1b0 Mar 19 17:22:38 ZEUS kernel: do_syscall_64+0xfe/0x107 Mar 19 17:22:38 ZEUS kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 19 17:22:38 ZEUS kernel: RIP: 0033:0x14e14324eff0 Mar 19 17:22:38 ZEUS kernel: RSP: 002b:00007fffb72798f0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 Mar 19 17:22:38 ZEUS kernel: RAX: ffffffffffffffda RBX: 00007fffb7279b10 RCX: 000014e14324eff0 Mar 19 17:22:38 ZEUS kernel: RDX: 0000000000020000 RSI: 000000000065409b RDI: 00000000ffffff9c Mar 19 17:22:38 ZEUS kernel: RBP: 0000000000020000 R08: 00007fffb7279c3f R09: 000014e143527c40 Mar 19 17:22:38 ZEUS kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Mar 19 17:22:38 ZEUS kernel: R13: 000000000065409b R14: 000014e143ce5b00 R15: 0000000000653fe0 Mar 19 17:22:38 ZEUS kernel: handlers: Mar 19 17:22:38 ZEUS kernel: [<ffffffffa0138d50>] i801_isr [i2c_i801] Mar 19 17:22:38 ZEUS kernel: [<ffffffff81410430>] vfio_intx_handler Mar 19 17:22:38 ZEUS kernel: [<ffffffff81410430>] vfio_intx_handler Mar 19 17:22:38 ZEUS kernel: Disabling IRQ #16 Link to comment
JorgeB Posted March 19, 2018 Share Posted March 19, 2018 Look for a bios update, kernel change might also help, i.e., update as soon as there's an unRAID release with a newer kernel. Link to comment
BrttClne22 Posted March 20, 2018 Author Share Posted March 20, 2018 Thanks. I'll check for a bios update now. Link to comment
BrttClne22 Posted March 20, 2018 Author Share Posted March 20, 2018 I updated the BIOS. Same issue, but the output seems to be a little shorter this time. One thing I've noticed is that one of my VMs won't autostart. I somehow doubt this has anything to do with it though. Mar 19 21:05:03 ZEUS kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Mar 19 21:05:03 ZEUS kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.26-unRAID #1 Mar 19 21:05:03 ZEUS kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-Gaming 7/Z170X-Gaming 7, BIOS F22m 03/09/2018 Mar 19 21:05:03 ZEUS kernel: Call Trace: Mar 19 21:05:03 ZEUS kernel: <IRQ> Mar 19 21:05:03 ZEUS kernel: dump_stack+0x5d/0x79 Mar 19 21:05:03 ZEUS kernel: __report_bad_irq+0x32/0xac Mar 19 21:05:03 ZEUS kernel: note_interrupt+0x1d4/0x225 Mar 19 21:05:03 ZEUS kernel: handle_irq_event_percpu+0x39/0x3f Mar 19 21:05:03 ZEUS kernel: handle_irq_event+0x31/0x4f Mar 19 21:05:03 ZEUS kernel: handle_fasteoi_irq+0x8c/0xf3 Mar 19 21:05:03 ZEUS kernel: handle_irq+0x1c/0x1f Mar 19 21:05:03 ZEUS kernel: do_IRQ+0x3b/0xbb Mar 19 21:05:03 ZEUS kernel: common_interrupt+0x7d/0x7d Mar 19 21:05:03 ZEUS kernel: </IRQ> Mar 19 21:05:03 ZEUS kernel: RIP: 0010:cpuidle_enter_state+0xe3/0x135 Mar 19 21:05:03 ZEUS kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff1c Mar 19 21:05:03 ZEUS kernel: RAX: ffff88086ec20980 RBX: 0000000000000000 RCX: 000000000000001f Mar 19 21:05:03 ZEUS kernel: RDX: 00000076bda2322a RSI: 0000000000020180 RDI: 0000000000000000 Mar 19 21:05:03 ZEUS kernel: RBP: ffff88086ec28800 R08: 000004d7bc3aa212 R09: 0000000000000018 Mar 19 21:05:03 ZEUS kernel: R10: ffffffff81c03ea8 R11: 0000000000000000 R12: 0000000000000001 Mar 19 21:05:03 ZEUS kernel: R13: 00000076bda2322a R14: ffffffff81c591b8 R15: 00000076bda22539 Mar 19 21:05:03 ZEUS kernel: ? cpuidle_enter_state+0xbb/0x135 Mar 19 21:05:03 ZEUS kernel: do_idle+0x11a/0x179 Mar 19 21:05:03 ZEUS kernel: cpu_startup_entry+0x18/0x1a Mar 19 21:05:03 ZEUS kernel: start_kernel+0x3e4/0x3ec Mar 19 21:05:03 ZEUS kernel: secondary_startup_64+0xa5/0xb0 Mar 19 21:05:03 ZEUS kernel: handlers: Mar 19 21:05:03 ZEUS kernel: [<ffffffffa00e0d50>] i801_isr [i2c_i801] Mar 19 21:05:03 ZEUS kernel: Disabling IRQ #16 Link to comment
enterpol Posted March 29, 2018 Share Posted March 29, 2018 Pretty sure you don't need to worry about this. I believe IRQ #16 is a legacy handler. It is an addressable space generally saved for add-in cards (RAID) bios if I remember correctly. If you don't have a RAID card installed, this space shouldn't need to be saved. If your BIOS is UEFI, or not in compatability mode, it could be causing it to throw these errors as well. Unless someone states to the contrary, I wouldn't worry about it. Link to comment
John_M Posted March 29, 2018 Share Posted March 29, 2018 6 hours ago, enterpol said: Pretty sure you don't need to worry about this. I believe IRQ #16 is a legacy handler. It is an addressable space generally saved for add-in cards (RAID) bios if I remember correctly. If you don't have a RAID card installed, this space shouldn't need to be saved. If your BIOS is UEFI, or not in compatability mode, it could be causing it to throw these errors as well. Unless someone states to the contrary, I wouldn't worry about it. It depends what's using IRQ 16. There isn't enough information in the syslog snippet provided to tell. In one of my machines it's used by the NIC and in another by a SATA HBA and in other people's it's used by a USB controller which may cause the boot flash to drop offline, so whether it's legacy or not it would worry me if it happened. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.