Kerneloops

Similar reports
Problem #722284
Component
kernel
Last affected version
0:3.10.0-957.el7
Executable
unknown
First occurrence
2020-09-26
Last occurrence
2026-08-05
Unique reports
37
Quality
-52

Statistics

Operating system Unique / Total count
CentOS 7 37 / 102
Operating system Count
CentOS 7 102
Architecture Count
x86_64 102
Related packages Count
kernel 102
 0:3.10.0-957.el7 84
 0:3.10.0-957.1.3.el7 13
 0:3.10.0-957.27.2.el7 2
 0:3.10.0-957.12.1.el7 1
 0:3.10.0-957.5.1.el7 1
 0:3.10.0-957.10.1.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:

History

Daily:

Weekly:

Monthly:


Backtrace

Frame # Function Binary Source or offset Line
1
dump_stack
vmlinux 0xffffffffa5d61dc1
Build id: 3.10.0-957.el7.x86_64 		0x19
2
__report_bad_irq
vmlinux 0xffffffffa574c972
Build id: 3.10.0-957.el7.x86_64 		0x32
3
note_interrupt
vmlinux 0xffffffffa574cd92
Build id: 3.10.0-957.el7.x86_64 		0x132
4
handle_irq_event_percpu
vmlinux 0xffffffffa574a465
Build id: 3.10.0-957.el7.x86_64 		0x55
5
handle_irq_event
vmlinux 0xffffffffa574a4cc
Build id: 3.10.0-957.el7.x86_64 		0x3c
6
handle_fasteoi_irq
vmlinux 0xffffffffa574db29
Build id: 3.10.0-957.el7.x86_64 		0x59
7
handle_irq
vmlinux 0xffffffffa562e554
Build id: 3.10.0-957.el7.x86_64 		0xe4
8
? tick_check_idle
vmlinux 0xffffffffa570babc
Build id: 3.10.0-957.el7.x86_64 		0x8c
9
do_IRQ
vmlinux 0xffffffffa5d795dd
Build id: 3.10.0-957.el7.x86_64 		0x4d
10
common_interrupt
vmlinux 0xffffffffa5d6b362
Build id: 3.10.0-957.el7.x86_64 		0x162
11
? hrtimer_start_range_ns
vmlinux 0xffffffffa56c5cad
Build id: 3.10.0-957.el7.x86_64 		0x1ed
12
? cpuidle_enter_state
vmlinux 0xffffffffa5badfb7
Build id: 3.10.0-957.el7.x86_64 		0x57
13
? cpuidle_enter_state
vmlinux 0xffffffffa5badfad
Build id: 3.10.0-957.el7.x86_64 		0x4d
14
cpuidle_idle_call
vmlinux 0xffffffffa5bae10e
Build id: 3.10.0-957.el7.x86_64 		0xde
15
arch_cpu_idle
vmlinux 0xffffffffa56366de
Build id: 3.10.0-957.el7.x86_64 		0xe
16
cpu_startup_entry
vmlinux 0xffffffffa56fc3ba
Build id: 3.10.0-957.el7.x86_64 		0x14a
17
rest_init
vmlinux 0xffffffffa5d4feb7
Build id: 3.10.0-957.el7.x86_64 		0x77
18
start_kernel
vmlinux 0xffffffffa63861c6
Build id: 3.10.0-957.el7.x86_64 		0x44b
19
? repair_env_string
vmlinux 0xffffffffa6385b7b
Build id: 3.10.0-957.el7.x86_64 		0x5c
20
? early_idt_handler_array
vmlinux 0xffffffffa6385120
Build id: 3.10.0-957.el7.x86_64 		0x120
21
x86_64_start_reservations
vmlinux 0xffffffffa638572f
Build id: 3.10.0-957.el7.x86_64 		0x24
22
x86_64_start_kernel
vmlinux 0xffffffffa6385885
Build id: 3.10.0-957.el7.x86_64 		0x154
23
start_cpu
vmlinux 0xffffffffa56000d5
Build id: 3.10.0-957.el7.x86_64 		0x5 
irq 16: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 3.10.0-957.el7.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H61-S3, BIOS FB 07/18/2012
Call Trace:
<IRQ>  [<ffffffffa5d61dc1>] dump_stack+0x19/0x1b
[<ffffffffa574c972>] __report_bad_irq+0x32/0xd0
[<ffffffffa574cd92>] note_interrupt+0x132/0x1f0
[<ffffffffa574a465>] handle_irq_event_percpu+0x55/0x80
[<ffffffffa574a4cc>] handle_irq_event+0x3c/0x60
[<ffffffffa574db29>] handle_fasteoi_irq+0x59/0x110
[<ffffffffa562e554>] handle_irq+0xe4/0x1a0
[<ffffffffa570babc>] ? tick_check_idle+0x8c/0xd0
[<ffffffffa5d795dd>] do_IRQ+0x4d/0xf0
[<ffffffffa5d6b362>] common_interrupt+0x162/0x162
<EOI>  [<ffffffffa56c5cad>] ? hrtimer_start_range_ns+0x1ed/0x3c0
[<ffffffffa5badfb7>] ? cpuidle_enter_state+0x57/0xd0
[<ffffffffa5badfad>] ? cpuidle_enter_state+0x4d/0xd0
[<ffffffffa5bae10e>] cpuidle_idle_call+0xde/0x230
[<ffffffffa56366de>] arch_cpu_idle+0xe/0xc0
[<ffffffffa56fc3ba>] cpu_startup_entry+0x14a/0x1e0
[<ffffffffa5d4feb7>] rest_init+0x77/0x80
[<ffffffffa63861c6>] start_kernel+0x44b/0x46c
[<ffffffffa6385b7b>] ? repair_env_string+0x5c/0x5c
[<ffffffffa6385120>] ? early_idt_handler_array+0x120/0x120
[<ffffffffa638572f>] x86_64_start_reservations+0x24/0x26
[<ffffffffa6385885>] x86_64_start_kernel+0x154/0x177
[<ffffffffa56000d5>] start_cpu+0x5/0x14