Bug 1636655 - [abrt] copy_process: general protection fault in copy_process
Summary: [abrt] copy_process: general protection fault in copy_process
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:c027c060b54c3617d301b73ea48...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-06 09:23 UTC by Łukasz Faber
Modified: 2019-02-21 21:11 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:11:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (83.01 KB, text/plain)
2018-10-06 09:24 UTC, Łukasz Faber
no flags Details

Description Łukasz Faber 2018-10-06 09:23:56 UTC
Description of problem:
Boot process crashed during the first boot to 4.18.11-200.

Additional info:
reporter:       libreport-2.9.5
general protection fault: 0000 [#1] SMP NOPTI
CPU: 7 PID: 1091 Comm: systemd-udevd Not tainted 4.18.11-200.fc28.x86_64 #1
Hardware name: Micro-Star International Co., Ltd. MS-7B36/B350 TOMAHAWK PLUS (MS-7B36), BIOS 1.70 04/27/2018
RIP: 0010:down_write+0x1b/0x40
Code: 83 f8 01 74 08 48 c7 43 20 01 00 00 00 5b c3 0f 1f 44 00 00 53 48 89 fb e8 72 d8 ff ff 48 89 d8 48 ba 01 00 00 00 ff ff ff ff <f0> 48 0f c1 10 85 d2 74 05 e8 27 27 ff ff 65 48 8b 04 25 00 5c 01 
RSP: 0018:ffffb157c81dbdd0 EFLAGS: 00010246
RAX: 732b414700000130 RBX: 732b414700000130 RCX: 462a414700000100
RDX: ffffffff00000001 RSI: ffff9302b788f9c8 RDI: 732b414700000130
RBP: ffffb157c81dbeb8 R08: ffffd157bfbfad70 R09: 0000000000000000
R10: ffffffffa63891a0 R11: 0000000000027360 R12: 732b414700000130
R13: ffff9302b788f9c8 R14: 0000000000000000 R15: ffff9302b656df00
FS:  00007f454ecd3180(0000) GS:ffff9302dedc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b711c10000 CR3: 00000007f7888000 CR4: 00000000003406e0
Call Trace:
 copy_process.part.36+0x16e2/0x1b20
 _do_fork+0xe2/0x390
 do_syscall_64+0x5b/0x160
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f454d8d38a3
Code: db 45 85 f6 0f 85 ad 01 00 00 64 4c 8b 04 25 10 00 00 00 31 d2 4d 8d 90 d0 02 00 00 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 f1 00 00 00 41 89 c5 85 c0 0f 85 f8 00 00 
RSP: 002b:00007ffd1ea3dd40 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffd1ea3dd40 RCX: 00007f454d8d38a3
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007ffd1ea3ddc0 R08: 00007f454ecd3180 R09: 00007ffd1ea3fd50
R10: 00007f454ecd3450 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd1ea3dd60 R14: 0000000000000000 R15: 0000000000000020
Modules linked in: parport_pc(+) parport wmi gpio_amdpt pinctrl_amd gpio_generic pcc_cpufreq acpi_cpufreq dm_crypt amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit gpu_sched drm_kms_helper ttm crct10dif_pclmul r8169 crc32_pclmul crc32c_intel drm ghash_clmulni_intel ccp mii nvme hid_microsoft nvme_core

Comment 1 Łukasz Faber 2018-10-06 09:24:14 UTC
Created attachment 1491003 [details]
File: dmesg

Comment 2 Justin M. Forbes 2019-01-29 16:26:38 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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.20.5-100.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 Justin M. Forbes 2019-02-21 21:11:40 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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