Kerneloops

Similar reports
Problem #505927
Component
kernel
Last affected version
0:3.10.0-1160.99.1.el7
Executable
unknown
First occurrence
2020-10-04
Last occurrence
2024-05-18
Unique reports
33
Quality
-38

Statistics

Operating system Unique / Total count
CentOS 7 33 / 529
Operating system Count
CentOS 7 529
Architecture Count
x86_64 529
Related packages Count
kernel 529
 0:3.10.0-1160.76.1.el7 72
 0:3.10.0-1160.108.1.el7 52
 0:3.10.0-1160.95.1.el7 46
 0:3.10.0-1160.90.1.el7 42
 0:3.10.0-1160.105.1.el7 35
 0:3.10.0-1160.92.1.el7 34
 0:3.10.0-1160.88.1.el7 34
 0:3.10.0-1160.81.1.el7 34
 0:3.10.0-1160.102.1.el7 33
 0:3.10.0-1160.80.1.el7 32
 0:3.10.0-1160.99.1.el7 23
 0:3.10.0-1160.114.2.el7 20
 0:3.10.0-1160.71.1.el7 17
 0:3.10.0-1160.15.2.el7 13
 0:3.10.0-1160.118.1.el7 10
 0:3.10.0-1160.83.1.el7 10
 0:3.10.0-1127.19.1.el7 7
 0:3.10.0-1160.49.1.el7 6
 0:3.10.0-1160.31.1.el7 5
 0:3.10.0-1160.25.1.el7 2
 0:3.10.0-1160.42.2.el7 2

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 0xffffffffb8b7ffa5
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x19
2
netif_set_real_num_tx_queues
vmlinux 0xffffffffb8a4f353
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x1f3
3
__alx_open
alx 0xffffffffc02a9865
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x195
4
alx_resume
alx 0xffffffffc02a9bdb
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x3b
5
pci_pm_restore
vmlinux 0xffffffffb87d65a3
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x83
6
? pci_pm_default_resume
vmlinux 0xffffffffb87d6520
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x40
7
dpm_run_callback
vmlinux 0xffffffffb88c6836
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x46
8
device_resume
vmlinux 0xffffffffb88c6986
Build id: 3.10.0-1127.19.1.el7.x86_64 		0xc6
9
async_resume
vmlinux 0xffffffffb88c6acd
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x1d
10
async_run_entry_fn
vmlinux 0xffffffffb84cdc8f
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x3f
11
process_one_work
vmlinux 0xffffffffb84be6bf
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x17f
12
worker_thread
vmlinux 0xffffffffb84bf7d6
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x126
13
? manage_workers.isra.26
vmlinux 0xffffffffb84bf6b0
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x2a0
14
kthread
vmlinux 0xffffffffb84c6691
Build id: 3.10.0-1127.19.1.el7.x86_64 		0xd1
15
? insert_kthread_work
vmlinux 0xffffffffb84c65c0
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x40
16
ret_from_fork_nospec_begin
vmlinux 0xffffffffb8b92d1d
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x7
17
? insert_kthread_work
vmlinux 0xffffffffb84c65c0
Build id: 3.10.0-1127.19.1.el7.x86_64 		0x40 
RTNL: assertion failed at net/core/dev.c (2464)
CPU: 1 PID: 17773 Comm: kworker/u16:28 Kdump: loaded Not tainted 3.10.0-1127.19.1.el7.x86_64 #1
Hardware name: System manufacturer System Product Name/M5A78L-M LX3, BIOS 1201    04/19/2013
Workqueue: events_unbound async_run_entry_fn
Call Trace:
[<ffffffffb8b7ffa5>] dump_stack+0x19/0x1b
[<ffffffffb8a4f353>] netif_set_real_num_tx_queues+0x1f3/0x200
[<ffffffffc02a9865>] __alx_open+0x195/0x4d0 [alx]
[<ffffffffc02a9bdb>] alx_resume+0x3b/0x40 [alx]
[<ffffffffb87d65a3>] pci_pm_restore+0x83/0xd0
[<ffffffffb87d6520>] ? pci_pm_default_resume+0x40/0x40
[<ffffffffb88c6836>] dpm_run_callback+0x46/0x90
[<ffffffffb88c6986>] device_resume+0xc6/0x1f0
[<ffffffffb88c6acd>] async_resume+0x1d/0x50
[<ffffffffb84cdc8f>] async_run_entry_fn+0x3f/0x130
[<ffffffffb84be6bf>] process_one_work+0x17f/0x440
[<ffffffffb84bf7d6>] worker_thread+0x126/0x3c0
[<ffffffffb84bf6b0>] ? manage_workers.isra.26+0x2a0/0x2a0
[<ffffffffb84c6691>] kthread+0xd1/0xe0
[<ffffffffb84c65c0>] ? insert_kthread_work+0x40/0x40
[<ffffffffb8b92d1d>] ret_from_fork_nospec_begin+0x7/0x21
[<ffffffffb84c65c0>] ? insert_kthread_work+0x40/0x40