Bug 1616231 - [abrt] kmem_cache_alloc_node: general protection fault in kmem_cache_alloc_node
Summary: [abrt] kmem_cache_alloc_node: general protection fault in kmem_cache_alloc_node
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:21d58e03832e10b89e98e09e32f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-15 10:58 UTC by hugo borges
Modified: 2023-09-14 04:33 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-26 21:04:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (75.55 KB, text/plain)
2018-08-15 10:58 UTC, hugo borges
no flags Details

Description hugo borges 2018-08-15 10:58:21 UTC
Additional info:
reporter:       libreport-2.9.5
general protection fault: 0000 [#1] SMP NOPTI
Modules linked in: soundcore rfkill sp5100_tco i2c_piix4 shpchp pinctrl_amd video gpio_amdpt gpio_generic wmi pcc_cpufreq acpi_cpufreq amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit gpu_sched drm_kms_helper ttm uas crc32c_intel drm usb_storage r8169 mii
CPU: 3 PID: 2 Comm: kthreadd Not tainted 4.17.12-200.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F23d 04/17/2018
RIP: 0010:prefetch_freepointer+0x10/0x20
RSP: 0018:ffffa1a980c83d10 EFLAGS: 00010286
RAX: 0000000000000000 RBX: b7ac868b8c780deb RCX: 000000000000000f
RDX: 000000000000000e RSI: b7ac868b8c780deb RDI: ffff90e61e804180
RBP: ffff90e61e804180 R08: ffff90e61ece73e0 R09: 0000000000000000
R10: ffffa1a980c83e40 R11: 0000000000000000 R12: 00000000014000c0
R13: 0000000000000000 R14: ffff90e61e804180 R15: ffff90e611ad8000
FS:  0000000000000000(0000) GS:ffff90e61ecc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f77554093a0 CR3: 0000000213ca4000 CR4: 00000000003406e0
Call Trace:
 kmem_cache_alloc_node+0x142/0x1f0
 ? copy_process.part.36+0x104/0x1aa0
 copy_process.part.36+0x104/0x1aa0
 ? update_load_avg+0x75/0x540
 ? update_curr+0xe1/0x1c0
 ? kthread_create_worker_on_cpu+0x70/0x70
 ? __switch_to+0x170/0x4b0
 _do_fork+0xe2/0x390
 ? __schedule+0x23c/0x840
 kernel_thread+0x25/0x30
 kthreadd+0x296/0x2e0
 ? kthread_create_on_cpu+0xa0/0xa0
 ret_from_fork+0x22/0x40
Code: b9 89 d3 e8 23 d4 67 00 85 c0 0f 85 c1 77 00 00 48 83 c4 08 5b 5d 41 5c 41 5d c3 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e c3 66 90 0f 1f 44 00 00 
RIP: prefetch_freepointer+0x10/0x20 RSP: ffffa1a980c83d10

Comment 1 hugo borges 2018-08-15 10:58:37 UTC
Created attachment 1476111 [details]
File: dmesg

Comment 2 Laura Abbott 2018-10-01 21:31:26 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Laura Abbott 2018-11-26 21:04:08 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel.

(Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)

Comment 4 Red Hat Bugzilla 2023-09-14 04:33:12 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.