Kerneloops

Similar reports
Problem #647706
Component
kernel Tainted
Last affected version
0:3.10.0-693.el7
Executable
unknown
First occurrence
2022-04-13
Last occurrence
2024-02-21
Unique reports
3
Quality
-51

Statistics

Operating system Unique / Total count
CentOS 7 3 / 4
Operating system Count
CentOS 7 4
Architecture Count
x86_64 4
Related packages Count
kernel 4
 0:3.10.0-693.el7 4

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.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.


Backtrace

Frame # Function Binary Source or offset Line
1
dump_stack
vmlinux 0xffffffff816a3d91
Build id: 3.10.0-693.el7.x86_64
0x19
2
__report_bad_irq
vmlinux 0xffffffff81132ff2
Build id: 3.10.0-693.el7.x86_64
0x32
3
note_interrupt
vmlinux 0xffffffff81133412
Build id: 3.10.0-693.el7.x86_64
0x132
4
handle_irq_event_percpu
vmlinux 0xffffffff81130c05
Build id: 3.10.0-693.el7.x86_64
0x55
5
handle_irq_event
vmlinux 0xffffffff81130c6c
Build id: 3.10.0-693.el7.x86_64
0x3c
6
handle_fasteoi_irq
vmlinux 0xffffffff81134149
Build id: 3.10.0-693.el7.x86_64
0x59
7
handle_irq
vmlinux 0xffffffff8102d2c8
Build id: 3.10.0-693.el7.x86_64
0xb8
8
? tick_check_idle
vmlinux 0xffffffff810f3ddc
Build id: 3.10.0-693.el7.x86_64
0x8c
9
? atomic_notifier_call_chain
vmlinux 0xffffffff816b053a
Build id: 3.10.0-693.el7.x86_64
0x1a
10
do_IRQ
vmlinux 0xffffffff816b75ed
Build id: 3.10.0-693.el7.x86_64
0x4d
11
common_interrupt
vmlinux 0xffffffff816ac1ed
Build id: 3.10.0-693.el7.x86_64
0x6d
12
? cpuidle_enter_state
vmlinux 0xffffffff81527a02
Build id: 3.10.0-693.el7.x86_64
0x52
13
? cpuidle_enter_state
vmlinux 0xffffffff815279f8
Build id: 3.10.0-693.el7.x86_64
0x48
14
cpuidle_idle_call
vmlinux 0xffffffff81527b48
Build id: 3.10.0-693.el7.x86_64
0xd8
15
arch_cpu_idle
vmlinux 0xffffffff81034fee
Build id: 3.10.0-693.el7.x86_64
0xe
16
cpu_startup_entry
vmlinux 0xffffffff810e7bca
Build id: 3.10.0-693.el7.x86_64
0x14a
17
rest_init
vmlinux 0xffffffff81692c57
Build id: 3.10.0-693.el7.x86_64
0x77
18
start_kernel
vmlinux 0xffffffff81b45060
Build id: 3.10.0-693.el7.x86_64
0x439
19
? repair_env_string
vmlinux 0xffffffff81b44a30
Build id: 3.10.0-693.el7.x86_64
0x5c
20
? early_idt_handler_array
vmlinux 0xffffffff81b44120
Build id: 3.10.0-693.el7.x86_64
0x120
21
x86_64_start_reservations
vmlinux 0xffffffff81b445ef
Build id: 3.10.0-693.el7.x86_64
0x24
22
x86_64_start_kernel
vmlinux 0xffffffff81b44740
Build id: 3.10.0-693.el7.x86_64
0x14f
irq 16: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W      ------------   3.10.0-693.el7.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. H270-HD3/H270-HD3-CF, BIOS F5 04/24/2017
 ffff88080d674600 18c2b080829969e9 ffff88082ec03e58 ffffffff816a3d91
 ffff88082ec03e80 ffffffff81132ff2 ffff88080d674600 0000000000000010
 00000000000000e3 ffff88082ec03ec0 ffffffff81133412 ffff88082ec03ed4
Call Trace:
 <IRQ>  [<ffffffff816a3d91>] dump_stack+0x19/0x1b
 [<ffffffff81132ff2>] __report_bad_irq+0x32/0xd0
 [<ffffffff81133412>] note_interrupt+0x132/0x1f0
 [<ffffffff81130c05>] handle_irq_event_percpu+0x55/0x80
 [<ffffffff81130c6c>] handle_irq_event+0x3c/0x60
 [<ffffffff81134149>] handle_fasteoi_irq+0x59/0x100
 [<ffffffff8102d2c8>] handle_irq+0xb8/0x150
 [<ffffffff810f3ddc>] ? tick_check_idle+0x8c/0xd0
 [<ffffffff816b053a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff816b75ed>] do_IRQ+0x4d/0xe0
 [<ffffffff816ac1ed>] common_interrupt+0x6d/0x6d
 <EOI>  [<ffffffff81527a02>] ? cpuidle_enter_state+0x52/0xc0
 [<ffffffff815279f8>] ? cpuidle_enter_state+0x48/0xc0
 [<ffffffff81527b48>] cpuidle_idle_call+0xd8/0x210
 [<ffffffff81034fee>] arch_cpu_idle+0xe/0x30
 [<ffffffff810e7bca>] cpu_startup_entry+0x14a/0x1c0
 [<ffffffff81692c57>] rest_init+0x77/0x80
 [<ffffffff81b45060>] start_kernel+0x439/0x45a
 [<ffffffff81b44a30>] ? repair_env_string+0x5c/0x5c
 [<ffffffff81b44120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffff81b445ef>] x86_64_start_reservations+0x24/0x26
 [<ffffffff81b44740>] x86_64_start_kernel+0x14f/0x172