Kerneloops

Similar reports
Problem #647706
Component
kernel Tainted
Last affected version
0:3.10.0-514.el7
Executable
unknown
First occurrence
2021-03-19
Last occurrence
2022-06-24
Unique reports
2
Quality
-57

Statistics

Operating system Unique / Total count
CentOS 7 2 / 2
Operating system Count
CentOS 7 2
Architecture Count
x86_64 2
Related packages Count
kernel 2
 0:3.10.0-514.26.1.el7 1
 0:3.10.0-514.el7 1

Packages names with count less than the total count of reports are most probably not the cause of the problem.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.

No reports in the last 20 weeks.

No reports in the last 20 months.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.

No reports in the last 20 weeks.

No reports in the last 20 months.


Backtrace

Frame # Function Binary Source or offset Line
1
dump_stack
vmlinux 0xffffffff81685fac
Build id: 3.10.0-514.el7.x86_64
0x19
2
__report_bad_irq
vmlinux 0xffffffff81132702
Build id: 3.10.0-514.el7.x86_64
0x32
3
note_interrupt
vmlinux 0xffffffff81132b22
Build id: 3.10.0-514.el7.x86_64
0x132
4
? cpuidle_enter_state
vmlinux 0xffffffff81514052
Build id: 3.10.0-514.el7.x86_64
0x52
5
handle_irq_event_percpu
vmlinux 0xffffffff81130201
Build id: 3.10.0-514.el7.x86_64
0xe1
6
handle_irq_event
vmlinux 0xffffffff8113033d
Build id: 3.10.0-514.el7.x86_64
0x3d
7
handle_fasteoi_irq
vmlinux 0xffffffff811337da
Build id: 3.10.0-514.el7.x86_64
0x5a
8
handle_irq
vmlinux 0xffffffff8102d26f
Build id: 3.10.0-514.el7.x86_64
0xbf
9
? tick_check_idle
vmlinux 0xffffffff810f3c8a
Build id: 3.10.0-514.el7.x86_64
0x8a
10
? atomic_notifier_call_chain
vmlinux 0xffffffff8169201a
Build id: 3.10.0-514.el7.x86_64
0x1a
11
do_IRQ
vmlinux 0xffffffff81698bef
Build id: 3.10.0-514.el7.x86_64
0x4f
12
common_interrupt
vmlinux 0xffffffff8168dd6d
Build id: 3.10.0-514.el7.x86_64
0x6d
13
? hrtimer_start_range_ns
vmlinux 0xffffffff810b45a6
Build id: 3.10.0-514.el7.x86_64
0x1c6
14
? cpuidle_enter_state
vmlinux 0xffffffff81514052
Build id: 3.10.0-514.el7.x86_64
0x52
15
? cpuidle_enter_state
vmlinux 0xffffffff81514048
Build id: 3.10.0-514.el7.x86_64
0x48
16
cpuidle_idle_call
vmlinux 0xffffffff81514199
Build id: 3.10.0-514.el7.x86_64
0xd9
17
arch_cpu_idle
vmlinux 0xffffffff8103516e
Build id: 3.10.0-514.el7.x86_64
0xe
18
cpu_startup_entry
vmlinux 0xffffffff810e7c95
Build id: 3.10.0-514.el7.x86_64
0x245
19
rest_init
vmlinux 0xffffffff81674407
Build id: 3.10.0-514.el7.x86_64
0x77
20
start_kernel
vmlinux 0xffffffff81b0a05a
Build id: 3.10.0-514.el7.x86_64
0x42c
21
? repair_env_string
vmlinux 0xffffffff81b09a37
Build id: 3.10.0-514.el7.x86_64
0x5c
22
? early_idt_handlers
vmlinux 0xffffffff81b09120
Build id: 3.10.0-514.el7.x86_64
0x120
23
x86_64_start_reservations
vmlinux 0xffffffff81b095ee
Build id: 3.10.0-514.el7.x86_64
0x2a
24
x86_64_start_kernel
vmlinux 0xffffffff81b09742
Build id: 3.10.0-514.el7.x86_64
0x152
irq 16: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           OE  ------------   3.10.0-514.el7.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. Z270-HD3P/Z270-HD3P-CF, BIOS F3 01/13/2017
ffff88102e79bd00 2a3424c75054a611 ffff88102ec03e40 ffffffff81685fac
ffff88102ec03e68 ffffffff81132702 ffff88102e79bd00 0000000000000010
0000000000000000 ffff88102ec03ea8 ffffffff81132b22 ffffffff81514052
Call Trace:
<IRQ>  [<ffffffff81685fac>] dump_stack+0x19/0x1b
[<ffffffff81132702>] __report_bad_irq+0x32/0xd0
[<ffffffff81132b22>] note_interrupt+0x132/0x1f0
[<ffffffff81514052>] ? cpuidle_enter_state+0x52/0xc0
[<ffffffff81130201>] handle_irq_event_percpu+0xe1/0x1e0
[<ffffffff8113033d>] handle_irq_event+0x3d/0x60
[<ffffffff811337da>] handle_fasteoi_irq+0x5a/0x100
[<ffffffff8102d26f>] handle_irq+0xbf/0x150
[<ffffffff810f3c8a>] ? tick_check_idle+0x8a/0xd0
[<ffffffff8169201a>] ? atomic_notifier_call_chain+0x1a/0x20
[<ffffffff81698bef>] do_IRQ+0x4f/0xf0
[<ffffffff8168dd6d>] common_interrupt+0x6d/0x6d
<EOI>  [<ffffffff810b45a6>] ? hrtimer_start_range_ns+0x1c6/0x390
[<ffffffff81514052>] ? cpuidle_enter_state+0x52/0xc0
[<ffffffff81514048>] ? cpuidle_enter_state+0x48/0xc0
[<ffffffff81514199>] cpuidle_idle_call+0xd9/0x210
[<ffffffff8103516e>] arch_cpu_idle+0xe/0x30
[<ffffffff810e7c95>] cpu_startup_entry+0x245/0x290
[<ffffffff81674407>] rest_init+0x77/0x80
[<ffffffff81b0a05a>] start_kernel+0x42c/0x44d
[<ffffffff81b09a37>] ? repair_env_string+0x5c/0x5c
[<ffffffff81b09120>] ? early_idt_handlers+0x120/0x120
[<ffffffff81b095ee>] x86_64_start_reservations+0x2a/0x2c
[<ffffffff81b09742>] x86_64_start_kernel+0x152/0x175