Kerneloops

Similar reports
Problem #722738
Component
kernel
Last affected version
0:6.7.6-200.fc39
Executable
unknown
First occurrence
2023-12-29
Last occurrence
2024-04-01
Unique reports
6
Quality
-57

Statistics

Operating system Unique / Total count
Fedora 39 6 / 6
Operating system Count
Fedora 39 6
Architecture Count
x86_64 6
Related packages Count
kernel-core 4
 0:6.7.6-200.fc39 1
 0:6.6.12-200.fc39 1
 0:6.6.7-200.fc39 1
 0:6.6.8-200.fc39 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
? refcount_warn_saturate
vmlinux 0xbe
2
? refcount_warn_saturate
vmlinux 0xbe
3
? refcount_warn_saturate
vmlinux 0xbe
4
? refcount_warn_saturate
vmlinux 0xbe
5
? refcount_warn_saturate
vmlinux 0xbe
6
? refcount_warn_saturate
vmlinux 0xbe
7
? refcount_warn_saturate
vmlinux 0xbe
8
? refcount_warn_saturate
vmlinux 0xbe
9
? refcount_warn_saturate
vmlinux 0xbe
10
? refcount_warn_saturate
vmlinux 0xbe
11
? refcount_warn_saturate
vmlinux 0xbe
12
refcount_warn_saturate
vmlinux 0xbe
13
? refcount_warn_saturate
vmlinux 0xbe
14
refcount_warn_saturate
vmlinux 0xbe
15
refcount_warn_saturate
vmlinux 0xbe
16
? refcount_warn_saturate
vmlinux 0xbe
17
refcount_warn_saturate
vmlinux 0xbe
18
? refcount_warn_saturate
vmlinux 0xbe
19
refcount_warn_saturate
vmlinux 0xbe
20
? refcount_warn_saturate
vmlinux 0xbe
21
refcount_warn_saturate
vmlinux 0xbe 
WARNING: CPU: 2 PID: 26 at drivers/usb/core/urb.c:379 usb_submit_urb+0x616/0x630
Modules linked in:
CPU: 2 PID: 26 Comm: kworker/2:0 Not tainted 6.6.7-200.fc39.x86_64 #1
Hardware name: Micro-Star International Co., Ltd MS-7B86/B450 GAMING PLUS (MS-7B86), BIOS 1.40 12/21/2018
Workqueue: events_power_efficient hub_init_func2
RIP: 0010:usb_submit_urb+0x616/0x630
Code: 64 50 8c e8 7c 6f cf ff eb 96 b8 fe ff ff ff e9 45 fd ff ff 48 89 fe 48 c7 c7 68 08 9a 8b c6 05 87 c9 90 01 01 e8 5a a0 54 ff <0f> 0b e9 4d ff ff ff b8 f8 ff ff ff e9 1e fd ff ff 66 0f 1f 84 00
RSP: 0018:ffffc900001ffdb8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff88810aac2c00 RCX: c0000000ffffdfff
RDX: 0000000000000000 RSI: 00000000ffffdfff RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffc900001ffc40
R10: 0000000000000003 R11: ffffffff8c346508 R12: ffff88810aab9800
R13: ffff88810a939140 R14: 0000000000000000 R15: 0000000000000005
FS:  0000000000000000(0000) GS:ffff8887fee80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f41d3123f18 CR3: 0000000302222000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 ? usb_submit_urb+0x616/0x630
 ? __warn+0x81/0x130
 ? usb_submit_urb+0x616/0x630
 ? report_bug+0x171/0x1a0
 ? prb_read_valid+0x1b/0x30
 ? srso_return_thunk+0x5/0x10
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? usb_submit_urb+0x616/0x630
 ? usb_submit_urb+0x616/0x630
 hub_activate+0x288/0x8f0
 ? kernfs_notify_workfn+0x33/0x210
 process_one_work+0x174/0x340
 worker_thread+0x27b/0x3a0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xe8/0x120
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x34/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 </TASK>