Bug 1299575

Summary: [abrt] general protection fault in __kmalloc
Product: [Fedora] Fedora Reporter: Vinicius Reis <angiolucci>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: angiolucci, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fec1fba33ed39d9ce8ec7b68805bb5f7679191bf
Whiteboard: abrt_hash:749b7585796bfc65f64806b02eb72208fa1d637b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-26 16:54:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Vinicius Reis 2016-01-18 16:40:45 UTC 
Description of problem:
Crash while booting fedora.

Additional info:
reporter:       libreport-2.6.3
general protection fault: 0000 [#1] SMP 
Modules linked in: pcc_cpufreq(-) acpi_cpufreq(-) i2c_designware_platform(+) i2c_designware_core nfsd auth_rpcgss nfs_acl lockd grace sunrpc hid_multitouch hid_sensor_hub i915 i2c_algo_bit drm_kms_helper drm serio_raw sdhci_acpi sdhci mmc_core video i2c_hid fjes
CPU: 3 PID: 556 Comm: systemd-udevd Not tainted 4.3.3-300.fc23.x86_64 #1
Hardware name: Dell Inc. Inspiron 7348/0RTGX8, BIOS A08 11/13/2015
task: ffff880252539e00 ti: ffff880253664000 task.ti: ffff880253664000
RIP: 0010:[<ffffffff81204c5d>]  [<ffffffff81204c5d>] __kmalloc+0x9d/0x260
RSP: 0018:ffff880253667b68  EFLAGS: 00010246
RAX: 00ff8802521a2740 RBX: 00000000000080d0 RCX: 0000000000000000
RDX: 00000000000031fb RSI: 0000000000000000 RDI: 000000000001a0c0
RBP: ffff880253667b98 R08: ffff88025ecda0c0 R09: ffffffff813a83fb
R10: 00ff8802521a2740 R11: 0000000000000016 R12: 00000000000080d0
R13: 0000000000000025 R14: ffff880256003b00 R15: ffff880256003b00
FS:  00007fb4154bc8c0(0000) GS:ffff88025ecc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb4130c1e3e CR3: 0000000252bbb000 CR4: 00000000003406e0
Stack:
 ffffffff813a83fb 0000000000000025 0000000000000000 ffff880251b44a80
 00000000000000d0 ffff88025612d840 ffff880253667bd0 ffffffff813a83fb
 0000000000000000 0000000000000000 ffff880251b44a80 0000000000000000
Call Trace:
 [<ffffffff813a83fb>] ? kobject_get_path+0x5b/0xe0
 [<ffffffff813a83fb>] kobject_get_path+0x5b/0xe0
 [<ffffffff813a99a8>] kobject_uevent_env+0x118/0x4f0
 [<ffffffffa02dd000>] ? 0xffffffffa02dd000
 [<ffffffff813a9d8b>] kobject_uevent+0xb/0x10
 [<ffffffff814da7ae>] driver_register+0x8e/0xe0
 [<ffffffff814dbc8a>] __platform_driver_register+0x4a/0x50
 [<ffffffffa02dd017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform]
 [<ffffffff81002123>] do_one_initcall+0xb3/0x200
 [<ffffffff8120427e>] ? kmem_cache_alloc_trace+0x19e/0x220
 [<ffffffff811a4947>] ? do_init_module+0x27/0x1e5
 [<ffffffff811a497f>] do_init_module+0x5f/0x1e5
 [<ffffffff811254fe>] load_module+0x201e/0x2630
 [<ffffffff811219c0>] ? __symbol_put+0x60/0x60
 [<ffffffff811e576c>] ? alloc_vmap_area+0x2fc/0x360
 [<ffffffff81125c5e>] SyS_init_module+0x14e/0x190
 [<ffffffff8178162e>] entry_SYSCALL_64_fastpath+0x12/0x71
Code: 49 83 78 10 00 4d 8b 10 0f 84 42 01 00 00 4d 85 d2 0f 84 39 01 00 00 49 63 46 20 49 8b 3e 4c 01 d0 40 f6 c7 0f 0f 85 95 01 00 00 <48> 8b 18 48 8d 4a 01 4c 89 d0 65 48 0f c7 0f 0f 94 c0 84 c0 74 
RIP  [<ffffffff81204c5d>] __kmalloc+0x9d/0x260
 RSP <ffff880253667b68>
Comment 1 Vinicius Reis 2016-01-18 16:40:56 UTC 
Created attachment 1115896 [details]
File: dmesg
Comment 2 Laura Abbott 2016-09-23 19:45:49 UTC 
*********** MASS BUG UPDATE **************
 
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 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.
Comment 3 Laura Abbott 2016-10-26 16:54:59 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.